ecran bleu, Inaccessible boot device et agp440.sys

octane a écrit :

je cherche a cloner des PC. J'en installe un nickel.
Je le clone a l'aide de partimage (www.partimage.org)
Je descends l'image sur le nouveau PC, mais il ne veut pas booter:
BSOD avec INACCESSIBLE_BOOT_DEVICE
Avec la console de recup, je fais un coup de fixboot, fixmbr, chkdsk /p
mais toujours rien. pas de problemes pour naviguer dans l'arborescence
avec la console de recup.

Je demarre en Safe mode, j'ai la liste des programmes qui se chargent.
Le dernier avant BSOD a l'air d'etre agp440.sys (je n'ai pas vraiment le
temps de bien le lire)

Les PC sont des DELL, a priori pas trop eloignes. G110 et G200, j'ai
aussi des G1, etc..
Qu'est ce que j'ai (mal) fait pour que ca plante? Et je ne comprends pas
trop l'erreur. Ca m'est arrive de changer de disque dur un PC avec win2000
sans soucis, deux trois reboot, et hop. La, quid? Tout a l'air d'y etre,
mais rien, pas moyen de le booter.

Est-ce qu'il y a un moyen de retablir la situation?

Bonjour,

ce n'est pas un bug, c'est une fonctionnalité.

Avant de cloner le disque, il faut exécuter l'utilitaire SYSPREP.
Ensuite pour chaque disque, l'original et les copies, au premier
démarrage, il sera demandé le keycode de Windows, et celui-ci
de Microsoft Office s'il est installé.

Ok pour le sysprep, mais pour le message "inaccessible_boot_device" c'est
plutot un problème de driver IDE puisque les machines ne sont pas
identiques.

Petit extrait de chez Microsoft (testé avec succès pour passer d'un P3 en
chipset VIA ver un P4 en chipset I845 sous w2K):
--------------------------------------------------------------------
You Receive a Stop 0x0000007B Error After You Move the Windows XP System
Disk to Another Computer
The information in this article applies to:
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
This article was previously published under Q314082 For a Microsoft Windows
2000 version of this article, see 271965.


SYMPTOMS
After you move the system (boot) disk to a backup computer, you may receive
the following Stop error when you try to start the Windows-based backup
computer:
STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE
CAUSE
This error can occur if the registry entries and drivers for the mass
storage controller hardware in the backup computer are not installed in
Windows.

For integrated device electronics (IDE) controllers, there are several
different chip sets available, such as Intel, VIA, and Promise. Each chip
set has a different Plug-n-Play identifier (PnP-ID).

The PnP-ID information of mass storage controllers for the backup computer
must be in the registry before startup so that Windows can initialize the
correct drivers.
RESOLUTION
To resolve this error, follow these steps for system recovery:
Use identical hardware for the backup computer.
Replace the problem hardware components in the backup computer with
components of the same manufacturer, make, and model as the components in
the computer that you are backing up.
If the system disk is a SCSI disk, use the same make and model of SCSI
controller in the new computer.
If the system disk is an IDE disk, use the same kind of motherboard in the
new computer, a motherboard that has the same kind of IDE chip set and the
same PnP-ID as the motherboard in the computer that you are backing up.
For SCSI-based system disks, you can prime the registry and ensure that the
drivers that 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 PnP detects the controller, sets up critical registry entries, and
copies 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
disk to another computer that has the same make and model of SCSI
controller, Windows will start successfully because Windows 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
merge the required registry entries, and to copy the drivers ahead of time
to support all IDE controllers that are natively supported by Windows. Note
that although this method might enable the relocated system disk to start
successfully, other hardware differences may lead to other problems.

This solution provides support for IDE controllers whose PnP-ID matches one
of the PnP-IDs in 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
that is detected during Setup.

After you determine which PnP-IDs are used in your computers, you can choose
to merge or to populate the registry with only the PnP-IDs that you need.

The following list shows the PnP-IDs of natively supported IDE controllers
in Windows.
;*********** Standard IDE ATA/ATAPI Controllers *********
Secondary_IDE_Channel=%SystemRoot%infMshdc.inf

;*********** Generic ESDI Hard Disk_Controller **********
*PNP0600=%SystemRoot%infMshdc.inf

;*********** Aztech IDE Controller **********************
*AZT0502=%SystemRoot%infMshdc.inf

;*********** Device ID for Generic Dual PCI IDE *********
PCICC_0101=%SystemRoot%infMshdc.inf

;************ALI IDE Controller ******************************
PCIVEN_10B9&DEV_5215=%SystemRoot%infMshdc.inf
PCIVEN_10B9&DEV_5219=%SystemRoot%infMshdc.inf
PCIVEN_10B9&DEV_5229=%SystemRoot%infMshdc.inf

;************Appian Technology **************************
PCIVEN_1097&DEV_0038=%SystemRoot%infMshdc.inf

;************CMD Technology *****************************
PCIVEN_1095&DEV_0640=%SystemRoot%infMshdc.inf
PCIVEN_1095&DEV_0646=%SystemRoot%infMshdc.inf
PCIVEN_1095&DEV_0646&REV_05=%SystemRoot%infMshdc.inf
PCIVEN_1095&DEV_0646&REV_07=%SystemRoot%infMshdc.inf
PCIVEN_1095&DEV_0648=%SystemRoot%infMshdc.inf
PCIVEN_1095&DEV_0649=%SystemRoot%infMshdc.inf

;************Compaq *************************************
PCIVEN_0E11&DEV_AE33=%SystemRoot%infMshdc.inf

;*************Intel *************************************
PCIVEN_8086&DEV_1222=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_1230=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_7010=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_7111=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_2411=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_2421=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_7199=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_244A=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_244B=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_248A=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_7199=%SystemRoot%infMshdc.inf
PCIVEN_8086&DEV_7601=%SystemRoot%infMshdc.inf

;*************PC Technology *****************************
PCIVEN_1042&DEV_1000=%systemroot%infMshdc.inf

;*************Silicon Integrated System *****************
PCIVEN_1039&DEV_0601=%SystemRoot%infMshdc.inf
PCIVEN_1039&DEV_5513=%SystemRoot%infMshdc.inf

;*************Symphony Labs *****************************
PCIVEN_10AD&DEV_0001=%SystemRoot%infMshdc.inf
PCIVEN_10AD&DEV_0150=%SystemRoot%infMshdc.inf

;*************Promise Technology ************************
PCIVEN_105A&DEV_4D33=%SystemRoot%infmshdc.inf

;*************VIA Technologies, Inc. ********************
PCIVEN_1106&DEV_0571=%SystemRoot%infMshdc.inf

;*************Standard Microsystems Corp. ***************
PCIVEN_1055&DEV_9130=%SystemRoot%infMshdc.inf

;*************Toshiba ***********************************
PCIVEN_1179&DEV_0105=%SystemRoot%infMshdc.inf


To import this information, use the following procedure on two different
test computers that exhibit the Stop 0x0000007B error after you change disks
between computers. After you follow this procedure on each test computer,
you can probably move the hard disks and start both computers without
receiving the Stop 0x0000007B error. However, other hardware differences
might 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 here **********

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1095&dev_0646&REV_05]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1095&dev_0646&REV_07]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1095&dev_0648]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1095&dev_0649]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase
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_MACHINESYSTEMCurrentControlSetServicesatapi]
"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_MACHINESYSTEMCurrentControlSetServicesIntelIde]
"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_MACHINESYSTEMCurrentControlSetServicesPCIIde]
"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 CacheI386Driver.cab file, or copy the files to the
%SystemRoot%System32Drivers folder.
In Windows Explorer, right-click the Mergeide.reg file in the floppy drive,
and then click Merge. Windows displays 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 displays another message:
Information from A:Mergeide.reg was successfully entered into the registry.
Shut down Windows, turn off the computer, and then move the system disk to
the other test computer, the one that previously produced a Stop 0x0000007B
error, and then see whether you can successfully start the second computer.
--------------------------------------------------------------------