system state restore = BSOD

[Guest]

Hi, hopefully you guys can help me out, im having
a seriously hard time doing a system state restore o
a windows 2K advance server... the restore is being don
using the IDR option from Veritas, after the hastles wit
the system restore and having to have a network connection
otherwise the error "unable to attach to device" would be logged !?!
(lol work that one out ) when the restore is complete and the
system is rebooted is presents me with BSOD (Unaccessable_Boot_decive

I have checked the boot.ini file and all is fine there, and noticed
that the HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestor
is merging the services entrys on a restore so Ive removed the services\* entry
to force all services key to be restored, becuase i noticed there was a servic
which points to the driver file of my raid controller card (compaq 5i

Im doing the restore on identical hardware, and have repartioned the ne
drive config exactly the same as the source.

I noticed if i was to copy the system. file (System hive) from system32\config
to the destination it reproduced the same error, but if I copied the system.
file from the source machine but from the winnt\repair folder which was an
orignal hive from windows setup as it was quite a bit smaller is size..
it worked as in the machine didnt bluescreen it booted into windows, but a
few drivers were missing

please can someone point me in the right direction :

These specs are exactly the same on both source and destination

System specs
Compaq DL380 G3
Dual PIIII 2Gh
2GB Me
onboard compaq Smart array 5i

Raid config

2 x 36GB mirrored - (4 Logical drives "C:\ system" "d:\pagefile" "e:\database" "f:\logs"

Many thanks

Mik

 

[Guest]

Today ive added the /SOS /bootlog switches to the boot.ini file t
see if some drivers are not being loaded etc and have compared bot
log files and both are identicle apart from of course the time and date

Please help me out here guys, its driving me crazy and my bosses
are not going to be impressed !

Many thanks
Mik

 

[Joe Griffin [MSFT]]

Hello,

It depends on where the Stop 0x7B occurrs.
If you do the system state restore and reboot the machine, does the Stop 0x7B occur about 3/4 way down the progress bar or does it occurr immediately.
If it occurrs immediately, see if the SCSI driver is set to boot in the services key.
If it occurrs later in the startup process, then it may be caused by a filter driver. (This may be what you are experiencing).
Of course we cannot rule out a corrupt system hive.
You can restore the system stated to an alternate location and use regedt32 to load the system hive and inspect it.
Oh, bootlog only monitors the drivers that are loaded in the text part of startup. It does not monitor the drivers loading during the GUI part of the startup process.

I am also assuming that it doesn't matter whether you start the machine in safe mode or normal mode?

Joe Griffin [MS]
Windows 2000 Server Setup Team

 

[Guest]

Jon, first of all I would like to thank you for your reply ! its like
music to my hears ive hit a big wall with this one !

The stop 0x7b occurs about 3/4 of the way through the blue progress
bar and the cpqissm.sys (maybe not right spelling ) driver load
before mup.sys (before gui gets a chance) the cpqissm.sys being
the smart array 5i driver.

Just out of curiosity when I view the drivers that the raid card is using
on the source machine it has two, both the same (cpqissm) but one i
dll and other is a sys file, any idea what the differences would be
do they get loaded at different times ? as it seems .sys is the one tha
gets loaded in the first stages of the boot

Ive tried a few system hives from different backups (same source machine)
and all resorts with same stop error

yep your right, normal and safe mode both the same, also forgot to mention
ive also installed SP4 on both machines :

Please throw some ideas my way

I really want to sort/understand this, its getting personal now

Thanks again Joe.

Mik