Random BSoD's 0xa 0xd1 0x4e 0x7e 0x7f XP

Status
Not open for further replies.

finaldaniel

Posts: 9   +0
Hi,

I have BSoD's for month's now when starting a game or browsing (when browsing, BSoD occurs after 1-2 hours and when starting a game it just crashes automatically)

this is my BSoD's (from minidumps)

IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x80e9e7f0 0x00000000 0x805226a0 ntoskrnl.exe

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e 0xc0000005 0x805bb452 0xb84ebc8c 0xb84eb988
ntoskrnl.exe

PFN_LIST_CORRUPT 0x0000004e 0x00000099 0x0000c9e2 0x00000004 0x00000000 win32k.sys

PFN_LIST_CORRUPT 0x0000004e 0x00000099 0x00056162 0x00000000 0x00000000 ntoskrnl.exe

IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x80e9e7f0 0x00000002 0x00000000 0x805226bc ntoskrnl.exe

IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0xbfffbff8 0x00000002 0x00000000 0x8066d755 ntoskrnl.exe

DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x100000d1 0x272f04d3 0x00000002 0x00000001 0xb4a60091 RtkHDAud.sys

IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x80ff1ff0 0x00000002 0x00000000 0x805226bc ntoskrnl.exe

PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 0xffff35ff 0x00000000 0x00000000 0x00000000 ntoskrnl.exe

IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x80ff1ff0 0x00000002 0x00000000 0x805226bc win32k.sys

UNEXPECTED_KERNEL_MODE_TRAP 0x1000007f 0x0000000d 0x00000000 0x00000000 0x00000000 NVNRM.SYS

KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x8054b569 0xb3c1f934 0x00000000 ntoskrnl.exe

IRQL_NOT_LESS_OR_EQUAL 0x1000000a 0x00000004 0x0000001c 0x00000001 0x80502386 ntoskrnl.exe

DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x100000d1 0x11111111 0x00000002 0x00000001 0xb42a58ed wdmaud.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x100000d1 0x805cb3fa 0x00000002 0x00000000 0xb32d1a6f dump_wmimmc.sys

DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x100000d1 0x805cb3fa 0x00000002 0x00000000 0xb2239a6f dump_wmimmc.sys

This is my Build:
ASUS P5N-MX
Core2Duo E4600 2.4GHz
NVIDIA 9600gt 1gb GDRR3
Samsung 920nw
Seagate Barracuda 7200.10 250GB 7200 RPM 16MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

Thanks - Daniel
 
It would have been more prudent if you zipped & posted your minidumps for analysis. Anyway, 0xD1 and 0x1a can also be caused by hardware issues.

But before going any further, have you updated anything in the period preceding the BSODs (e.g. drivers update or some new hardware addition etc.)? If so please restore your system to to such previous restore point where these changes are not present.

When was the last time you cleaned out your system (i.e. gotten rid of any dust etc.)?

If that is not the case, first, run memtest (for atleast 8 passes, more are better), to see if it is causing these issues. Regards
 
from xp, we have BSoD's like i posted then, we switched to Win7, it still occurs, then we switched back to xp its still occuring. we can't get rid off it.

we cleaned the computer last thursday so theres no help if i clean it again.

and we if we run memtest, it hangs or BSoD.

we don't know what we will gonna do to our computer, so we just browsing for 3 months. because we can't fix it.
 
I agree with Archean about running memtest and the fact if it hangs at Memtest I believe you are looking at corrupted memory at this point.

The error PFN_LIST_CORRUPT is probably the strongest indicator of bad RAM. Take out all memory sticks but one and run your system. If it doesn't crash or if it does then switch out sticks and run.
 
there's one thing i've noticed,
here in the philippines it so hot right now.. last week it rained for almost 6 hours
and exactly the same time when we cleaned the computer, so i tested it, i played call of duty 4 almost the whole day. no BSoDs or hangs, after that, i wake up in the morning to play again, after 15 minutes it hangs then BSoD.

so it can be overheating or bad RAM? or bad RAM and overheating?
 
Perhaps a mix of both; as a bad RAM stick is more susceptible to fail under duress. Whereas, a good hardware device would fail much later, that too most likely if you are pushing the envelope beyond its design limits.

Can you please tell what are the operating temperatures?
 
These doesn't seem too alarming in any way.

I am more inclined than before to say that it seems to be hardware related issue IMHO.
 
Most likely issue is your RAM, and Route very rightly suggested you to RUN memtest; I suggest you try to run it on individual RAM modules to see whether one of them is causing the issues.
 
I am inclined to say that it is an RAM issue. Did you run memtest on individual modules?
 
Status
Not open for further replies.
Back