Windows 2000 BSOD (I really need some help here guys)

Moz

Senior member
Jan 16, 2000
421
0
0
Ok, well you can see the components in my rig from the link below. I have been running it for about 2 months without any trouble with Windows 2000 Pro.
Today after rebooting it, it first said it needed to check D: (my storage drive - fat32) for consistency, which completes with no errors and then I get the following Blue Screen Error.

----

KMODE_EXCEPTION_NOT_HANDLED

Address 8050604E base at 80400000 Datestamp 39760637 - ntoskrnl.exe

----

Now I have tried the following:

* Booting in Safe Mode - same blue screen error (with and without network support, command prompt etc)

* Removed all my USB devices etc, and booted - same problem

* I upgraded to the 1006 Final Bios a couple of weeks back on my ASUS CUSL2-C and so since I had the original bios backed up I re-flashed to 1003 (which came with the board), this completed successfully - again same blue screen error.

I really am scratching my head as to what this problem is, is it that my C: drive (IBM 22GXP) is dead? With all this work I have to get done this is not a good time for my system to go belly up. I am thinking of booting with the Win2k Startup disks and doing a repair on it... other than that I have no ideas. I would really appreciate any help please.

Thanks in advance.
 

Moz

Senior member
Jan 16, 2000
421
0
0
A bump for great justice... only because I am in a bit of a fix here.
 

John

Moderator Emeritus<br>Elite Member
Oct 9, 1999
33,944
2
81
I used to get that msg. when I overclocked the CPU too much.
 

Moz

Senior member
Jan 16, 2000
421
0
0
The CPU is not overclocked, all BIOS settings are at default. I'm gonna go home and try the restore option, hopefully that should fix it.
 

tracerbullet

Golden Member
Feb 22, 2001
1,661
19
81
Wondered if you fixed it. I was getting this too for a while - the &quot;check...consistency&quot;, BSOD's with the same error, etc. Supposed to mean just that - a bad hard drive, or a part of it, or possibly controllers for it (SCSI drivers, etc.).

I wasn' very far into setting up my new system (dual '98 and 2000) and gave up - repartitioned, reformatted, scandisk, etc. Sure enough, there were some disk problems. Sectioned them off and have only (last night) recently put back on '98. Will be installing 2000 this weekend.

If you fixed it - please post back how. If you haven't fixed it, I'd recommend some very serious hard drive utility usage to see if you can see a problem - I did.
 

potz

Senior member
Feb 22, 2001
651
0
0
did u install any adaptec stuff? search in the microsoft knowledge base for &quot;KMODE_EXCEPTION_NOT_HANDLED&quot; it shows some adaptec stuff that can cause bsod
 

Kermit

Member
Nov 29, 1999
115
0
0
Right now I'm getting this error occasionally, and it started right after I got a new processor (Intel 1 GHz) and kept the BX mainboard- tight now my PCI bus is running at 44 MHz and this, I think, is the reason. I get the error right as I boot into W2K, and second booting is generally OK. As a workaround, I hibernate instead of just shutting down the computer and this seems to help. I agree that the hard disk controller is the most likely cause