BSOD - ntoskrnl.exe

[Pappasmurf]

Morning
Here is my problem, comp was fine then all of a sudden
she freezes, had to restart her and on boot up i get BSOD with the following narrative (same narrative comes up each time, a whole lot of numbers - which i have written down if needed)
IRQL_NOT_LESS_OR_EQUAL
Address 80446BD9 base at 80400000, Datestamp 3ee6c002 - ntoskrnl.exe

Have tried booting in safe mode and get the above, have reset cmos, taken HD out checked connections, gotten the above.
Tried the recovery console from cd and it loads WIN2K files the gets BSOD but with different narrative
NTFS_File_System ... ntoskrnl.exe

I dont know what else to do as every turn is BSOD
Am using WIN2K, with maxtor HD that is about 2yrs old
Any help would would be appreciated
Has my HD died?

[russ_da_bus]

You could try doing a repair installation of Windows 2000. If the problem is still occuring after the repair then it could be a hardware issue.

[Super Nade]

Mate,

I don't know if Win2k has a system restore service. If it does, I'd strongly advise you to perform a system restore.

[Pappasmurf]

win2k has repair / recovery installation, which i have tried but i still get BSOD with the NTFS narrative

[Gnufsh]

I would suspect a driver problem or a memory issue. Can you pass memtest86?

[Pappasmurf]

I am getting BSOD on booty up, so cant get to check anything as mention cant even get into safe mode.
More info - i am on SP4 and ahve not recently installed any new software or hardware

[Slackfumasta]

memtest86 is run from a floppy (or a boot CD if you care to make one), and it's something that you should run before you check anything else.

I would first suspect a memory issue, and second would suspect another piece of hardware in your machine.

[stool]

"IRQL_NOT_LESS_OR_EQUAL" is almost(but not quite) always caused by a memory issue. Try memtest or Doc Memory first, both boot from a floppy, as suggested above. If you have more than one stick of RAM try each separately.
Overheating can sometimes cause the message too, so make sure thats not an issue.

[RJARRRPCGP]

Vcore can cause that message too. The processor may be going bad.

[Pappasmurf]

Have run memtest and all is grand
If i reformat HD and load WIN2K again will this solve the problem?

[Slackfumasta]

Not if it's caused by a flaky piece of hardware.

[Gnufsh]

Have run memtest and all is grand
If i reformat HD and load WIN2K again will this solve the problem?
It might. Depends on if it's a hardware problem or a driver/os problem. See if it starts happening after you install one of your drivers.

[Super Nade]

Mate,

Can your rig pass SuperPi32M or Prime CPU?