TechSpot - PC Technology News and Analysis

Hi!

First of all, nice job you guys are doing helping out people with BSOD's, thanks a lot for your time already!
I've been having many BSOD's lately, i cant figure a pattern though. I have discarded cpu temperature, because i've seen it lock a few times hours after the pc loaded. I just moved the mouse, and got a BSOD.
But i also seen it lock up many times during games

I also got some inpage errors message in BSOD every once in a while, so i checked paging in hardrive. I tried deleting and recreating the pages on both hard drives i have, no sucess either.
Ive checked ram memory, doesn't seem faulty, but maybe that might be it, since memtest alone can't determine its working. Since i only have 1 RAM stick, i was expecting you guys could check if my dump files show a simpler answer then having to blindly buy a new memory stick just to try
I'm attaching the latest 6 minidumps, but i have about 20 of 'em

My computer is:
Shuttle Motherboard AK32 with VIA chipset (VIA 4-1 driver installed)
Athlon XP 2000+
512MB Ram
2 Hard drives, 1 Maxtor 40GB, 1 Seagate 80GB
Geforce MX 440 64mb video card
2 IDE CD Recorders

If there is anything else i can inform to help, please reply

Arthur V

Attached Files

Minidumps.zip (97.9 KB, 3 views)

Hi,

From the debug report, I believe the culprit is faulty ram. Reseat the ram to another memory slot. If windows still crashes, downclock the ram. If it still crashes, replace the ram.

Your debug report
Mini021806-01.dmp BugCheck 10000050, {e7fffff8, 0, 80564fad, 2}
Probably caused by : ntoskrnl.exe ( nt!ObDereferenceSecurityDescriptor+13 )

Mini021906-01.dmp BugCheck 100000D1, {65687475, ff, 0, 65687475}
Probably caused by : ntoskrnl.exe ( nt!KiTimerListExpire+122 )

Mini022106-01.dmp BugCheck 1000000A, {4, 2, 0, 804e6617}
Probably caused by : memory_corruption ( nt!MiRemovePageByColor+6a )

Mini022106-02.dmp BugCheck 1000000A, {85d1e7b0, 2, 0, 804dbc95}
Probably caused by : ntoskrnl.exe ( nt!KiUnlinkThread+7 )

Mini022206-01.dmp BugCheck 1000000A, {6000008, 2, 0, 804f2178}
Probably caused by : afd.sys ( afd!AfdTimeoutPoll+b7 )

Mini122605-01.dmp BugCheck 10000050, {c1508f28, 0, 804e70d5, 0}
Probably caused by : memory_corruption ( nt!MiLocateAndReserveWsle+52