ntoskrnl.exe BSOD

[JonUK]

Here is a nice BSOD that I can't find any information on:

STOP: 0x000000A (0xE13AA088, 0X00000002, 0x00000000, 0x80462733) IRQL_NOT_LESS_OR _EQUAL

Address 90462733 base at 80400000, Datestamp 3ee6c002 - ntoskrnl.exe


Right after much fiddling around to due to these damn BSODs I think I have come to a point where nothing seems to work for me. At first I thought that the problems were IRQ related due to the BSOD stating IRQL_LESS_OR_EQUAL but I have now managed to get my IRQs evenly distributed (Changed PC from ACPI computer to Standard PC) and now the video card, soundcard and modem do not share the same IRQ but I still get this error.

I am running the latest BIOS/drivers for my Mobo, videocard, soundcard and modem as well as Win2k Service Pack 4 all my other devices such as USB controllers, mouse etc... have up-to date drivers.

I have also physically moved the cards around in diffrent set-ups but nothing seems to work. The machine seems to operate perfectly up to the point where it locks up. Just before the BSOD if in games the machine will seem to lock-up then drop to the desktop Then it displays the BSOD. If in windows the screen just goes blank then it displays the BSOD.

Help please

ARRGGHHH

 

[EeyoreX]

Memtest should be your first stop. Download and run it, see if you get errors. Do more than one pass. If you are getting several kinds of BSOD it is more likely than not a RAM issue. Or, you could try one stick of RAM (if you have several) or replacing RAM with known good RAM. Try also moving RAM to a different slot(s).

\Dan

 

[JonUK]

I have had diffrent BSODs but I (stupidly) didn't note them down then as the computer resets unless you uncheck the box in the system properties .

I have one block of 256mb DRR 333 cheapo ram, I shall check it and see.

 

[JonUK]

I have ran memtest86 for two tests and it passed both times. So it doesn't seem to be memory either then, or is there any other tests that I can run?

 

[EeyoreX]

Even two passes might not be enough to catch the problem. If you have another stick of RAM, try that. Almost any time there are several different BSODs it is a bad RAM issue. Or perhaps a bad driver. Since you are doing a fresh install, bad drivers are not going to be the problem. Maybe borrow a stick of RAM? Or try your stick in a different slot.

\Dan

 

[JonUK]

I shall try to get some diffrent RAM or move the existing stick around. Also the machine just randomly reset without a BSOD. I seriously think it must be a hardware error now as there seems to be no other obvious problem and the BSODs never seem to be the same.

The problem is most of the machine is new apart from the Souncard, Modem and hard drives so it could be anything from bad RAM to a faulty mobo.

 

[crisp82]

I has this problem when I ran 2000. Wasn't hardware, was a software issue.

Google
Is
your friend

 

[JonUK]

I have also tried win98 on the machine, same BSODs. If its software then I have no idea what could be causing it, I have updated every driver for the hardware in the machine but no luck at all.

 

[crisp82]

Have you tried a format/install? How did u get the same error message on 98se? NTOSKRNL.exe is a part of the NT Kernel, not 98....

 

[JonUK]

I get the same BSODs like IRQL_NOT_LESS_OR_EQUAL and KMode exceptions in both O/Ses, I have re-installed both O/S many times with diffrent configurations and diffrent Service packs, drivers and the like. After all that I think that it has got to be something hardware related to still get the same problem.

 

[NogginBoink]

STOP 0x0A blue screens are almost always caused by bad drivers.

IRQLs and IRQs are only tangentally related and changing the IRQs of your hardware will not solve this problem.

 

[EeyoreX]

STOP 0x0A blue screens are almost always caused by bad drivers.

IRQLs and IRQs are only tangentally related and changing the IRQs of your hardware will not solve this problem.

While I agree this is often the case, but with a fresh install (of both Windows 2000 and Windows 98) I can't see how "bad drivers" would be the cause. Also, with the errors occuring with two totally different OSes that further makes me believe it is a hardware (ie RAM) issue.

\Dan