B
Brian Smither
A while ago, after, if I recall correctly, installing an update of a device
driver offered by MS, I now get BSODs even when trying to get to safe mode.
Since this was a server, it wasn't imperative that I reboot after having
finished the update.
So, I don't really remember what the last thing I did before the BSODs.
What I did do, is to install 2K3Server. It's working fine. I plan to be in
this environment in an attempt to fix the 2KAdvServer environment. Assuming
that it is a driver that's causing the BSOD (a driver that loads in Safe
Mode, even), what driver directory do I rename in order to do a repair
installation? The INF directory? The entire System32 directory? The entire
WinNT directory - and then restore a backed-up registry?
For the rest of the question...
I did do an 'R' install (second opportunity in the install from a booted
CD), sucessfully finished, but still BSOD's. I ran Winternal's ERD
Commander, but wasn't much help in assisting me to locate drivers that I
could remove. Used last known good configuration - didn't help.
So, I figure if I could just set aside *all* drivers, and then try a repair
install (second opportunity), at least I can get get back to a raw, working
2kAdvServ environment where I won't have to re-install all the
applications.
I believe the BSOD is Stop 0A "irql not less..." with NTOSKRNL as the
identified problem.
driver offered by MS, I now get BSODs even when trying to get to safe mode.
Since this was a server, it wasn't imperative that I reboot after having
finished the update.
So, I don't really remember what the last thing I did before the BSODs.
What I did do, is to install 2K3Server. It's working fine. I plan to be in
this environment in an attempt to fix the 2KAdvServer environment. Assuming
that it is a driver that's causing the BSOD (a driver that loads in Safe
Mode, even), what driver directory do I rename in order to do a repair
installation? The INF directory? The entire System32 directory? The entire
WinNT directory - and then restore a backed-up registry?
For the rest of the question...
I did do an 'R' install (second opportunity in the install from a booted
CD), sucessfully finished, but still BSOD's. I ran Winternal's ERD
Commander, but wasn't much help in assisting me to locate drivers that I
could remove. Used last known good configuration - didn't help.
So, I figure if I could just set aside *all* drivers, and then try a repair
install (second opportunity), at least I can get get back to a raw, working
2kAdvServ environment where I won't have to re-install all the
applications.
I believe the BSOD is Stop 0A "irql not less..." with NTOSKRNL as the
identified problem.