3 different BSOD STOP errors in 3 hours

[saiorse44]

3 different BSOD STOP errors in 3 hours (nearly there?)

Hi all, im new here

I was having problems back last month with IRQL_NOT_LESS_OR_EQUAL so i reformatted the hard drive.

I have been having IRQL_NOT_LESS_OR_EQUAL errors on and off over the last couple of weeks and this afternoon i got IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA and another error which i cant remember but it didnd display the error name on the BSOD but googling the number cam up with somthing with KERNEL in it.

They seem to happen at random intervals and also when alot is going on (e.g. RootkitChecker cant complete a scan before something goes pear-shaped.

Been keeping an eye on CPU temps but the seem OK at ~32C idle and up to ~46C when under load.

If you need any more info please ask and i will do my best.

Many Thanks,
Rob

 

[fastco]

Hi just read these instructions then zip up a few minidumps and attach them to this thread then we can analyze them to see what's up..

https://www.techspot.com/vb/topic51365.html

Disregard, just saw the minidumps you added!!!

 

[fastco]

Minidumps point to memory corruption. Download one of the memory testers from the download page and run some memroy tests.

Another cause of the crash is the file ntoskrnl.exe. Try to use the system file checker at run, type sfc.exe /scannow.

Also check the system for viruses as they can also corrupt that windows file.

If that doesn't fix the problem and the memory is ruled out then perform a repair of the current Windows installation with the XP cd.

 

[saiorse44]

Hi,

Thanks for your helpful replies.

I ran Memtest and it gave my RAM a clean bill of health.

I ran the SFC and it completed its operation without informing me of anything (is that correct?).

Went on Windows Update. Nothing to download.

Restarted system. Oddly enough display reverted back to 800x600 or less.

Installed newer GeForce drivers than i was running.

Lets hope this worked and i will keep an eye on it for a couple of days.

Thank you so much.
Rob

 

[saiorse44]

is doing it again guys!

Last night i got an 0x0000008E but it didnt create a minidump, and just now i got an IRQL_NOT_LESS_OR_EQUAL.

Here is the mindump from just now attached.

Any ideas?

 

[iss]

Your problem is undoubtably hardware related. Memtest is not a surefire test so it could still be the memory. It could also be your PSU. Download SpeedFan and check the voltages on your rails. errattic or out of spec voltages can cause all kinds of problems.

 

[saiorse44]

Hi,

Thanks for that program, attached are my results. PSU readings seem ok?

Thanks,
Rob

 

[iss]

The voltages seem to be fine. have you tried running your hard drive makers diagnostic software on the hard drive? if you dont have it you can download it from the hard drive makers website. should be in the support\downloads section.

 

[saiorse44]

Thanks!

If that doesn't fix the problem and the memory is ruled out then perform a repair of the current Windows installation with the XP cd.

I was wondering if i did a system repair, i have an XP SP1 CD but SP2 (downloaded from Windows Update) installed. What would happen if older files are copied from the CD?

Many Thanks,
Rob

 

[saiorse44]

Its happened again

Just plain rebooted once, then later i got:

0x0000008E

and something about GFBHOOK.sys (maybe?) on the blue screen.

No minidumps made.

Its all fallin apart by the looks of it

Any ideas?

 

[nickc]

Thanks!



I was wondering if i did a system repair, i have an XP SP1 CD but SP2 (downloaded from Windows Update) installed. What would happen if older files are copied from the CD?

Many Thanks,
Rob

just do the repair and then go to WINDOWSUPDATE and get the updades u need...

 

[saiorse44]

Hi all,
Its been a few days since i last posted whats been hapenning.

After another crash two days ago, scandisk (or the XP equivelant of) randomly decided to look at my hard drive during the bootup. If found two things of concern and i am let to believe that it fixed them.

Since then alot of the BSODs have stopped appearing, except for one:
IRQL_NOT_LESS_OR_EQUAL

0x0000000A (0x00000000,0x00000002,0x00000000,0x804E4E08)

This happens at random intervals and its ALWAYS at 0x804E4E08.

Is this an address in memory? Because Memtest says my RAM is fine.

Back along i changed my RAM from 256MB DDR PC2700 333MHz to 1024MB DDR PC3200 400MHz. My motherboard manual says that it supports, and i quote, "DDR200/266/333 MHz and up". I saw this "and up" bit and assumed that putting DDR400 in it would be fine. Could this not be the case?

Cheers,
Rob

 

[saiorse44]

Hi,
I checked my IRQs and nothing is sharing with anything else.

It just crashed again, new one this time, 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Applied a related (?) patch from microsoft, something to do with timings.

When it got back up from reboot. it informed me that it had recovered from a 0x0000000A (why?) and then it told me about it had recovered from a 0x0000007E. Wierd.

Considering taking my soundcard out and just using the one onboard.

:? :cry:

Cheers,
Rob

 

[Tedster]

all 3 minidumps point to corrupted hardware - in particular memory. Ensure your memory is compatible with your motherboard. Not all brands, speeds, or types are. RTFM

 

[saiorse44]

Hi,

I did read the manual, it was the "DDR200/266/333 MHz and up" bit that lead me to question my DDR400 RAM.

No crashes (yet) since MS patch.

Cheers,
Rob

 

[iss]

From what I read on the MSI webite Your board does not support DDR 400. it only supports DDR266 and DDR333.