Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Stop error message when you try to install Windows Server 2008 on a computer that is connected to an iSCSI target LUN by using an iSCSI bootable network adapter: "Stop error code 0x00000019"


View products that this article applies to.

Symptoms

Consider the following scenario. You try to install Windows Server 2008 on the local hard disk of a computer. The computer is connected to an Internet SCSI (iSCSI) target logical unit number (LUN) by using an iSCSI bootable network adapter. The iSCSI bootable network adapter is configured to create an iSCSI Boot Firmware Table (iBFT). During the installation of Windows Server 2008, the computer restarts, and the Completing Installation page is displayed. In this scenario, you receive the following Stop error message, and the computer restarts again:
STOP 0x00000019 (0x00000020, 0x855b5010, 0x855b5240, 0x58464269)
This Stop error occurs in the Msiscsi.sys file.

Additionally, you receive the following message when the computer restarts again:
Setup encountered an error and should be rebooted to continue.

↑ Back to the top


Cause

This problem occurs because iBFT functionality is enabled in the basic input/output system (BIOS). The iBFT is a block of information that contains the various parameters that are used in the iSCSI boot process.

↑ Back to the top


Resolution

To resolve this problem, use one of the following methods.

Method 1

Disable the iBFT functionality in the BIOS.

For more information about how to disable the iBFT functionality in the BIOS, contact the computer manufacturer. For information about how to contact the computer manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416 Hardware and software vendor contact information, A-K

60781 Hardware and software vendor contact information, L-P

60782 Hardware and software vendor contact information, Q-Z

Method 2

Disconnect the iSCSI target LUN when you install Windows Server 2008.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

Stack output

When this problem occurs, the following stack output is generated:
8937b5f4 8170229f 00000003 de164fff 00000000 nt!RtlpBreakWithStatusInstruction 
[d:\longhorn_rc0\base\ntos\rtl\i386\debug2.asm @ 47]
8937b644 81702cf9 00000003 855b5010 00000046 nt!KiBugCheckDebugBreak+0x1c 
[d:\longhorn_rc0\base\ntos\ke\bugcheck.c @ 288]
8937b9f0 81702129 00000019 00000020 855b5010 nt!KeBugCheck2+0x5e1 
[d:\longhorn_rc0\base\ntos\ke\bugcheck.c @ 1284]
8937ba14 81722184 00000019 00000020 855b5010 nt!KeBugCheckEx+0x1e 
[d:\longhorn_rc0\base\ntos\ke\bugcheck.c @ 174]
8937ba88 8398eb74 855b5018 00000000 8937baa4 nt!ExFreePoolWithTag+0x17f 
[d:\longhorn_rc0\base\ntos\ex\pool.c @ 4158]
8937ba98 826eb30a 855b48d4 8937bab8 82717f53 msiscsi!iScsiFreeGlobalResources+0x24 
[d:\longhorn_rc0\drivers\storage\iscsi\client\port.c @ 1342]
8937baa4 82717f53 855b41a0 855b40e8 00000000 
storport!RaCallMiniportFreeResources+0x2d 
[d:\longhorn_rc0\drivers\storage\port\raid\port\miniport.c @ 487]
8937bab8 826e7ee9 855b41a0 00000001 855b40e8 storport!RaDeleteMiniport+0x17 
[d:\longhorn_rc0\drivers\storage\port\raid\port\miniport.c @ 108]
8937bad4 82717d12 855b40e8 855b40e8 85df0940 storport!RaidDeleteAdapter+0x3b 
[d:\longhorn_rc0\drivers\storage\port\raid\port\adapter.c @ 273]
8937baec 82717419 855b40e8 85df0940 826f4000 
storport!RaidAdapterRemoveDeviceIrp+0x53 
[d:\longhorn_rc0\drivers\storage\port\raid\port\adapter.c @ 3224]
8937bb0c 8271730d 005b40e8 00000002 85df09f8 storport!RaidAdapterPnpIrp+0xd0 
[d:\longhorn_rc0\drivers\storage\port\raid\port\adapter.c @ 1350]
8937bb28 816c6aef 855b4030 85df0940 8937bbcc storport!RaDriverPnpIrp+0x71 
[d:\longhorn_rc0\drivers\storage\port\raid\port\driver.c @ 725]
8937bb40 817e1d44 84e93da0 84e93da0 84e93c18 nt!IofCallDriver+0x63 
[d:\longhorn_rc0\base\ntos\io\iomgr\iosubs.c @ 2378]
8937bb74 818b0ad1 84e93da0 8937bba8 00000000 nt!IopSynchronousCall+0xce 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\irp.c @ 215]
8937bbd0 816ffd41 84e93da0 00000002 8ab5ad98 nt!IopRemoveDevice+0xd1 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\irp.c @ 663]
8937bbf8 818aa06f 92d0d5c8 00000015 00000000 nt!PnpRemoveLockedDeviceNode+0x176 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\remove.c @ 899]
8937bc10 818aa31f 00000002 00000015 00000000 nt!PnpDeleteLockedDeviceNode+0x2b 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\remove.c @ 284]
8937bc44 818ae0dc 84e93da0 8ab5ad98 00000002 nt!PnpDeleteLockedDeviceNodes+0x4c 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\remove.c @ 1074]
8937bd04 8179fa54 8937bd34 00000000 8ab215b8 nt!PnpProcessQueryRemoveAndEject+0x8cf 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\event.c @ 4090]
8937bd1c 817da36c 00000000 8173709c 84e8dad0 nt!PnpProcessTargetDeviceEvent+0x38 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\event.c @ 4420]
8937bd44 816c7a55 85de3ee0 00000000 84e8dad0 nt!PnpDeviceEventWorker+0x201 
[d:\longhorn_rc0\base\ntos\io\pnpmgr\event.c @ 1907]
8937bd7c 8187b6f6 85de3ee0 de16447b 00000000 nt!ExpWorkerThread+0xfd 
[d:\longhorn_rc0\base\ntos\ex\worker.c @ 1191]
8937bdc0 816de2e6 816c7958 00000001 00000000 nt!PspSystemThreadStartup+0x9d 
[d:\longhorn_rc0\base\ntos\ps\psexec.c @ 5186]
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 
[d:\longhorn_rc0\base\ntos\ke\i386\threadbg.asm @ 81]
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

↑ Back to the top


Keywords: KB949531, kbprb, kbtshoot, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 949531
Revision : 2
Created on : 1/20/2012
Published on : 1/20/2012
Exists online : False
Views : 380