b.s.o.d (calling cpc2004 and others for help...)

hi cpc2004,
I'm a newbie here. I'd notice you're an expert with reading minidumps. I really need your help since my pc kept on getting bsod lately. Can u help me trace who's the culprit pls? :(

Here are the last 3 1001 event log i received.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0xbf80b3b1, 0xb7e8ecc4, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0xbf80b3b1, 0xb8236894, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0xbf80b3b1, 0xb7f5ecc4, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

and here are the minidumps i collected since last month.Thank you in advanced for your help. If there's anyone else who can help me too, i really appreciate it.. thanks! http://us.i1.yimg.com/us.yimg.com/i/mesg/emoticons7/63.gifhttp://us.i1.yimg.com/us.yimg.com/i/mesg/emoticons7/77.gif

Hi Keigo,

The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram


Debug report of your minidumps
Mini090705-01.dmp BugCheck 1000008E, {c0000005, bf80b3b1, ec82ccc4, 0}
Mini090705-01.dmp Probably caused by : win32k.sys ( win32k!KillTimer2+21 )

Mini090605-01.dmp BugCheck 1000008E, {c0000005, 8053d39a, b7d4fbd4, 0}
Mini090605-01.dmp Probably caused by : win32k.sys ( win32k!HeavyAllocPool+72 )

Mini090405-01.dmp BugCheck 1000008E, {c0000005, bf816d22, b7c70568, 0}
Mini090405-01.dmp Probably caused by : hardware ( win32k!BLTRECORD::~BLTRECORD+11 )

Mini102105-01.dmp BugCheck 1000008E, {c0000005, bf80b3b1, b8236894, 0}
Mini102105-01.dmp Probably caused by : win32k.sys ( win32k!KillTimer2+21 )

Mini102005-01.dmp BugCheck 8E, {c0000005, bf80b3b1, b7f5ecc4, 0}
Mini102005-01.dmp Probably caused by : Unknown_Image

Mini101605-01.dmp BugCheck 1000008E, {c0000005, bf80b3b1, b872fcc4, 0}
Mini101605-01.dmp Probably caused by : win32k.sys ( win32k!KillTimer2+21 )

Mini101205-01.dmp BugCheck 1000008E, {c0000005, bf80b3b1, b85f7cc4, 0}
Mini101205-01.dmp Probably caused by : win32k.sys ( win32k!KillTimer2+21 )

Mini100505-01.dmp BugCheck 1000008E, {c0000005, bf80b3b1, b8657cc4, 0}
Mini100505-01.dmp Probably caused by : win32k.sys ( win32k!KillTimer2+21 )

thanks for your quick reply.. anyway i did as you said and switch places between my RAMs.. so far so good.. i'll be monitoring for the next few days for any b.s.o.d.. thanks for your help.

(wondering how you guys could read these minidumps... http://us.i1.yimg.com/us.yimg.com/i/mesg/emoticons7/77.gif )

yeay, it's almost a week by now.. and everything seems like back to normal again... thanks a lot for your help :D