I was happily running win2k pro for over eight months without issue. Then one day, I reboot, and it blue screens in the transition between the VGA-mode loading screen and switching to my desktop resolution. That's not to say that it's a graphics issue, that's just the point at which it happens.
After this happens once, it just keeps happening. Loading the last good configuration does nothing. Replacing ntoskrnl.exe does nothing. No viruses present (upon scanning the old win2k dir from a new install). Safe mode does the same blue screen at the same point in the boot process.
I can find nothing in common between the three times this happened. This time, I did absolutely nothing, my machine was on for less than an hour.
*** STOP: 0x0000001E (0x00000005, 0x8050955F, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 8050955F base at 80400000, DateStamp 3ad7ad60 - ntoskrnl.exe
Microsoft support describes this as a rather generic error message that one receives when, well, something is b0rked.
Eight months without a problem, then this, three times in less than a month.
Yeah, this is desperate, but has anyone seen anything like this and successfully resolved it? Or even have the faintest clue what could be causing it?
Thanks...
(ath750 / kt133 / 256 / gf2)
After this happens once, it just keeps happening. Loading the last good configuration does nothing. Replacing ntoskrnl.exe does nothing. No viruses present (upon scanning the old win2k dir from a new install). Safe mode does the same blue screen at the same point in the boot process.
I can find nothing in common between the three times this happened. This time, I did absolutely nothing, my machine was on for less than an hour.
*** STOP: 0x0000001E (0x00000005, 0x8050955F, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 8050955F base at 80400000, DateStamp 3ad7ad60 - ntoskrnl.exe
Microsoft support describes this as a rather generic error message that one receives when, well, something is b0rked.
Eight months without a problem, then this, three times in less than a month.
Yeah, this is desperate, but has anyone seen anything like this and successfully resolved it? Or even have the faintest clue what could be causing it?
Thanks...
(ath750 / kt133 / 256 / gf2)
Facebook
Twitter