hallo,
ich habe das problem schon seit win2k beobachtet und ist bei winxp immernoch so.
Ich hab vor mir ein neues Mainboard zu kaufen bzw. ist schon auf dem weg , aber ich möchte nicht neu formatieren. Denn wie ich es schonmal erfahren mußte wenn ich ein neues mainboard unter ,un windowsxp, einbaue , fährt windows nurnoch mit einem bluescreen hoch.
was kann ich tun das ich nicht immer formatieren muß wenn ich mir eine neues mainboard einbaue ??
Mrs. Software carmangel „Neus Mainboard , Windows startet nurnoch mit Bluescreen“
Win2k kann mit einem Mainboard mit einem neuen Chipsatz nicht starten, da es den HD-Controller nicht erkennen kann. MS empfihlt zwar dringend eine Neu-Installation, gibt aber auch eine Anleitung, um diese zu umgehen:
"STOP 0x0000007B" Error After Moving Windows 2000 System Disk to Another System
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Windows versions 2000, 2000 SP1 Advanced Server
Microsoft Windows versions 2000, 2000 SP1 Professional
Microsoft Windows versions 2000, 2000 SP1 Server
--------------------------------------------------------------------------------
SYMPTOMS
After you move the system (boot) disk to a backup computer, you may receive the following message on your Windows 2000 computer when you try to start the backup computer:
***STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE
CAUSE
The registry entries and drivers for the mass storage controller hardware in the backup computer are not installed in Windows 2000.
For integrated device electronics (IDE) controllers, there are several different chip sets available, such as Intel, VIA, and Promise. Each chip set uses a different Plug-n-Play (PNP) ID to identify it.
The PNP-ID information of mass storage controllers for the backup computer must be in the registry prior to startup for Windows 2000 to initialize the correct drivers.
RESOLUTION
The supported method of moving a Windows 2000 installation to new hardware is documented in the following Microsoft Knowledge Base article:
Q249694 How to Move a Windows 2000 Installation to Different Hardware
However, for quicker disaster recovery, follow these steps:
Use identical hardware for the backup computer.
Replace the problem hardware components in the backup computer with the same manufacturer make and model as the components in the computer you are backing up.
Use the same make and model of small computer system interface (SCSI) controller in the new computer, if the system disk is a SCSI disk.
Use the same kind of motherboard that has the same kind of IDE chip set, and the same PNP-ID as the original, if the system disk is an IDE disk.
For SCSI-based system disks, you can prime the registry, and ensure that the drivers you want are in place by installing the SCSI controller that is used by the backup computer before you transfer the system disk contents. Windows 2000 PNP will detect the controller, set up critical registry entries, and copy the appropriate driver.
After you see the SCSI controller in Device Manager, you can safely remove the alternate controller. If, at a later time, you need to move the system drive to another computer with that make and model of SCSI controller, Windows 2000 will start successfully because it has already used that controller once, and has retained the correct configuration information.
MORE INFORMATION
Although Microsoft does not support this method, it is possible to import, or to merge the required registry entries, and copy the drivers ahead of time to support all IDE controllers that are natively supported by Windows 2000. This method may enable the moved system drive to start successfully, but other hardware differences may result in other problems.
This solution will provide support for IDE controllers whose PNP-ID matches the following list. However, if you want to determine ahead of time which IDE controllers are used in your current, and backup computers, you can search the Systemroot\setupapi.log file for the PNP-ID detected during Setup.
After you determine which PNP-IDs are used in your computers, you can choose to merge, or populate the registry with only the PNP-IDs that you need.
The following list is a list of the PNP-IDs of natively supported IDE controllers in Windows 2000:
;***********(Standard IDE ATA/ATAPI controllers)*********
Primary_IDE_Channel=%systemroot%\inf\mshdc.inf
Secondary_IDE_Channel=%systemroot%\inf\mshdc.inf
;*********** Generic_ESDI_Hard_Disk_Controller **********
*PNP0600=%systemroot%\inf\mshdc.inf
;*********** Aztech IDE Controller **********************
*AZT0502=%systemroot%\inf\mshdc.inf
;*********** Device ID for generic Dual PCI IDE *********
PCI\CC_0101=%systemroot%\inf\mshdc.inf
;************Acer Labs Inc ******************************
PCI\VEN_10B9&DEV_5215=%systemroot%\inf\mshdc.inf
PCI\VEN_10B9&DEV_5219=%systemroot%\inf\mshdc.inf
PCI\VEN_10B9&DEV_5229=%systemroot%\inf\mshdc.inf
;************Appian Technology **************************
PCI\VEN_1097&DEV_0038=%systemroot%\inf\mshdc.inf
;************CMD Technology *****************************
PCI\VEN_1095&DEV_0640=%systemroot%\inf\mshdc.inf
PCI\VEN_1095&DEV_0646=%systemroot%\inf\mshdc.inf
;************Compaq *************************************
PCI\VEN_0E11&DEV_AE33=%systemroot%\inf\mshdc.inf
;*************Intel *************************************
PCI\VEN_8086&DEV_1222=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_1230=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7010=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7111=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2421=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7199=%systemroot%\inf\mshdc.inf
;*************PC Technology *****************************
PCI\VEN_1042&DEV_1000=%systemroot%\inf\mshdc.inf
;*************Silicon Integrated System *****************
PCI\VEN_1039&DEV_0601=%systemroot%\inf\mshdc.inf
PCI\VEN_1039&DEV_5513=%systemroot%\inf\mshdc.inf
;*************Symphony Labs *****************************
PCI\VEN_10AD&DEV_0001=%systemroot%\inf\mshdc.inf
PCI\VEN_10AD&DEV_0150=%systemroot%\inf\mshdc.inf
;*************Promise Technology ************************
PCI\VEN_105A&DEV_4D33=%systemroot%\inf\mshdc.inf
;*************VIA Technologies, Inc. ********************
PCI\VEN_1106&DEV_0571=%systemroot%\inf\mshdc.inf
To import this information, use the following procedure on two different test computers that exhibit the "stop 0x0000007B" error message after changing drives between computers. After you follow this procedure on each test computer, you should be able to move the hard disks, and start both computers without receiving the "stop 0x0000007B" error message. However, other hardware differences may result in other problems.
Copy the following information into Notepad, and then save the file on a 3.5-inch disk. Name the file mergeide.reg, without the .txt file name extension.
********* START COPY FROM HERE *************
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
;Add driver for Atapi (requires atapi.sys in drivers directory)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00
;Add driver for intelide (requires intelide.sys in drivers directory)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00
;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
************ END COPY HERE ***************
Extract the Atapi.sys, Intelide.sys, Pciide.sys, and Pciidex.sys files from the Systemroot\Driver Cache\i386\driver.cab file, or copy them to the Systemroot\system32\drivers directory from the most recently installed Service Pack distribution media (if the Service Pack is already installed on your computer).
In Windows Explorer, right-click the Mergeide.reg file in the floppy drive, and then click Merge. Windows 2000 will display the following message:
Are you sure you want to add the information in a:\mergeide.reg to the registry?
Click Yes.
After the import process is completed, Windows 2000 will display another message:
Information from a:\mergeide.reg was successfully entered into the registry.
Shut down, and then turn off the computer, and move the system disk drive to the other test computer that previously produced a "stop 0x0000007b" error message, and then see if you can successfully start the second computer.
Additional query words: eide 0x7b chipset setupapi Atapi Intelide Pciide Pciidex
Keywords : kbenv
Issue type : kbprb
Technology : kbwin2kAdvSer kbwin2kAdvSerSearch kbwin2kS kbwin2kSSearch kbwin2kSearch kbwin2kProSearch kbwin2kPro
