Blue screen of death. Help!

[hoyaguru]

A couple of days ago, I started to get the blue screen of death, and it has been increasing in frequency to the point that I am having a hard time getting work done. This is a work/personal computer, I have a mishmash of programs installed. I tried uninstalling my video card drivers, and I tried installing the newest drivers, no help. I tried my memory one chip at a time, same problem. I have uninstalled all of the programs I've installed in the last week, this is still happening every half hour or so. I'll be surprised if I get through writing this without it screwing up. Anyway, I wrote everything down last time it "blue" up, here is what it said:

*** STOP: 0x0000001e (0xc000001D, 0x80420424, 0xBEAB1B3C, 0x804310FC)
KMODE_EXCEPTION_NOT_HANDLED

*** Address 80420424 base at 80400000, DateStamp 3ee6C002 - ntoskrnl.exe
*** Address 804310FC base at 80400000, DateStamp 3ee6C002 - ntoskrnl.exe

Any idea what this means? Any idea where I can go to find out what this means? I'll take any advice, it's getting to the point where I can't get any work done. Thanks in advance!

 

[johnjkr1]

From my experience, KMODE blue screens are usually driver related....have you tried a format?

 

[hoyaguru]

Originally posted by: johnjkr1
From my experience, KMODE blue screens are usually driver related....have you tried a format?

Format what?

The only driver I had changed in the past month or so was my video driver. I have a NVidia G-Force 4 Ti 4200. I went to NVidia's website and downloaded and installed the newest driver. Since I started having this blue screen problem, I uninstalled the new driver and re-installed the old one, still have the same problem.

 

[johnjkr1]

By format, I meant wipe the hard drive and start over.

As for the driver, perhaps you should try getting the latest chipset drivers installed, then try the latest nvidia drivers again.

 

[hoyaguru]

Instead of going to the extreme and formatting my hard drive, I was hoping someone here might know of a way of deciphering the info from the blue screen, and that might tell me what is crashing my computer.

 

[johnjkr1]

http://support.microsoft.com/?kbid=314451

faulty driver seems to be the most likely cause

 

[stnicralisk]

Hoya,

Windows dependability decays logrithmically anyways. You will find that as time goes on an install of windows gets worse and worse. It doesnt hurt to format just burn everything you need on a cd. I suggest getting ghost so that you can more easily reinstall everything (after this format).

 

[EeyoreX]

Hoya,

Windows dependability decays logrithmically anyways. You will find that as time goes on an install of windows gets worse and worse. It doesnt hurt to format just burn everything you need on a cd. I suggest getting ghost so that you can more easily reinstall everything (after this format).

No offense, but this is a steaming pile of crap. At least in terms of a NT based OS. I have had XP installed since day one. Zero problems. I have installed 2000 boxes since day one of 2000s release and many of them are also still running without issue.

Did you install or update any drivers recently? If so, roll back to an older version of the driver and see if that fixes the problem. For other ideas and possible solutions, look at this Microsoft Technet article. If all else fails, then go ahead and reinstall. Personally I see reinstalls of Windows as a last resort, not the first. And I will reiterate my position that Wwindows installs do not get "worse and worse" as time goes on. Not unless it's a 9x based OS and/or you install a lot of BS retarded and badly written garbage software.

\Dan

 

[GOZ]

You should try to do a repair install. that way the worst thing you have to do download the servce packs and patches.
that way you don't lose you data.

 

[RadBrad]

take what you will from this read http://www.microsoft.com/windows2000/en/messages/5267.htm

Then decide from this read if you really want to debug the problem that the ntoskrnl.exe is trying to execute.
say, like an exploit trying to open a secure port, Or make an assumption that the executable is corrupt.


http://www.osr.com/ntinsider/1999/kmode_except.htm


If it was me, to get my files backed up I would unhook everything from my computer and upon a successful boot, kill all running processes and hook something that is plug and play up to back up on, and then follow the lead of this pack and repair or restore. If the ntoskrnl.exe is corrupt, then perhaps someone can show you how to restore it. Now the problem is, can you trust the files you backed up not to revive the problem. Damed if you do,,,Damned if you don,t...

 

[Smileymcsmiles]

I am sorry.. If you are running Windows XP, try using the driver rollback feature. you may also want to try the system restore feature. Go back a few days/weeks before you started to experience the issue. The calendar is also good to find out when system changes were made. You may want to check your event viewer too.