Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Stupid, stupid, stupid, stupid! Help - Guru needed!
Message
De
25/07/2001 08:20:52
Mark Hall
Independent Developer & Voip Specialist
Keston, Kent, Royaume Uni
 
 
À
Tous
Information générale
Forum:
Windows
Catégorie:
Pilotes
Titre:
Stupid, stupid, stupid, stupid! Help - Guru needed!
Divers
Thread ID:
00534881
Message ID:
00534881
Vues:
49
Breifly - I've screwed my NT server, and need help getting it running again.

I recently replaced the graphics card on my development NT server. Got the machine running in basic VGA mode, and then installed drivers for the new card. On rebooting, the machine does a BSOD immediately after the VGA NT Logo screen appears (I mean that this screen flashes up for half a second and then BSOD). The same happens whether I boot to VGA mode or std NT 4.0.

The BSOD message is KMODE_EXCEPTION_NOT_HANDLED 0x0000001E. Looking in MSDN & other docs, it says that this points to a bad driver and that with luck the driver is named on the BSOD page. Unfortunately not, the screen just says that the error occurred in Win32k.sys.

So, next step was to replace the old graphics card and try to reboot - same problem, both in Std and VGA mode.

Unfortunately, the next bit is (I think) where I made a big mistake. I used the NT install CD to do a recover of the NT installation, replacing the SYSTEM registry from a very out-of-date Emergency Recovery Disk. This didn't solve the problem at all, and also made it impossible for me to do a 'restart using last known good hardware profile' as the overwrite of the SYSTEM registry removed my last known good hardware profile :-(

So, now I have added a second installation of NT to the system. This means I can boot using the 'new' installation and see/manage the files (on NTFS) from the 'bad' installation. I have tried finding all references to the newly installed driver and deleting/renaming them. Following advice on an MSDN article, I have used RegEdt32 to open the system registry hive from the bad installation and cannot find any further references to the (3dfx) driver software. I have done the same for the software registry hive.

Still I reboot and get the same BSOD - I am running out of things to try.

Can anyone help me?
Regards
Mark

Microsoft VFP MCP
Menulib - OO Menus for VFP www.hidb.com/menulib
Répondre
Fil
Voir

Click here to load this message in the networking platform