B
Brian Smither
After I allowed Windows 2000 Advanced Server to apply several security
updates a couple months ago, I was then greeted with a Stop 0xA "IRQL Not
Less or Equal" for every conceivable start up mode. I put another
operating system on that machine just so I could get at the files.
Recently I've (re)learned how to use the Recovery Console to run the
Spunstall script for those security updates. I've run the scripts for
KB908523 (no change), KB905915 (no change), KB912919 (no change), and
KB908519 (no change). The only one left of the group that were installed
that fateful day is KB829019 (.Net 2.0) and I don't think that could be the
problem.
I'm not sure if I SPuninstalled the updates in the same order that they
were installed. Would that make a difference?
If I recall (and that's fuzzy at best), I also allowed the updater to
install a couple of updated drivers. Now, how do I discover where the old
drivers are that I can rollback to in the Recovery Console? Is this even
possible?
I've already tried a repair install - no luck.
As this was a non-production server used for experimenting and training
only, a backup is/was of no importance.
Any instruction on how to recover from this BSOD will also be a training
experience.
I've thought about disguising the entire System32 and INF directories and
trying another repair install. That might get me away from bad drivers, if
that's what's causing the problem.
updates a couple months ago, I was then greeted with a Stop 0xA "IRQL Not
Less or Equal" for every conceivable start up mode. I put another
operating system on that machine just so I could get at the files.
Recently I've (re)learned how to use the Recovery Console to run the
Spunstall script for those security updates. I've run the scripts for
KB908523 (no change), KB905915 (no change), KB912919 (no change), and
KB908519 (no change). The only one left of the group that were installed
that fateful day is KB829019 (.Net 2.0) and I don't think that could be the
problem.
I'm not sure if I SPuninstalled the updates in the same order that they
were installed. Would that make a difference?
If I recall (and that's fuzzy at best), I also allowed the updater to
install a couple of updated drivers. Now, how do I discover where the old
drivers are that I can rollback to in the Recovery Console? Is this even
possible?
I've already tried a repair install - no luck.
As this was a non-production server used for experimenting and training
only, a backup is/was of no importance.
Any instruction on how to recover from this BSOD will also be a training
experience.
I've thought about disguising the entire System32 and INF directories and
trying another repair install. That might get me away from bad drivers, if
that's what's causing the problem.