Constant Random BSODs on a 5 days old system

Tews · 15 Nov 2010

Your .dmp file is still showing memory corruption... You need to retest with memtest in each memory slot to test the mobo..

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {29c000619328, 2, 1, fffff80002ae53a4}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )

Followup: MachineOwner
---------

This driver is outdated and needs to be updated ..

Code:

 PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D) ... Sonic CD/DVD driver (used by many different CD/DVD programs) ... pxHelp20.sys programs Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.
[/b]

iTitus · 15 Nov 2010

But doesn't not booting with one kind of RAM, and booting with another kind of RAM conclude that the ram is faulty?

Tews · 15 Nov 2010

Possibly, but what we are doing at this point is eliminating the mobo as a cause of the crash.. do this with the known good stick of memory...

iTitus · 15 Nov 2010

Ok I will,
But it would also be safe to replace both? Or would that create to many new variables :P
I Was looking at a Asrock 870 extreme 3 with 2 kingston KVR1333D3N9/2G sticks

bwpotter · 16 Nov 2010

I know it is an expensive proposition and at the risk of sounding like a broken record again, you really should consider a new (read different model) M/B. You're going down the same road I did! I pulled a good bit of hair out in the process too! I RMA'd the RAM twice, a processor, and the M/B once, but until I changed to a different M/B altogether, I got nowhere! IMO, it's just a bad design; other forums are littered with the same conclusion.

iTitus · 19 Nov 2010

The shop sent me new ram. Kingston this time:
KHX1333C7AD3K2/4G
http://www.valueram.com/datasheets/K...C7AD3K2_4G.pdf

It says C7 but CPU-Z reads it as 9 :O?
I guess changing the timings in the bios slows down the Mhz

Well, I'll see if there's gonna be crashes.
I'll let you know :)

Dave76 · 19 Nov 2010

Thanks for letting us know your progress.

The settings look good, lowering the MHz usually allows for tighter timings.
It all depends on the RAM specs.
You will not be able to notice the difference.

Hopefully you will have a stable system now.

iTitus · 05 Dec 2010

This is really asking for it, but I'll say it anyway:

After 2 weeks I'm still crash-free(well only opera is a little unsteady but that's something else :P ).

This was totally a RAM issue.

The only question I have left is: Officially this is C7 ram. But right now it is set to 9-9-9-24(see last post)
The guy from the shop said that I might have to set it manually, but given this screenshot, I woul

Thanks! and for the mods:
Problem solved

iTitus · 04 Apr 2011

Problem totally gone.
Conclusion: The RAM was faulty.

Thanks everyone.

Thread is lockable.

Jonathan_King · 04 Apr 2011

Thanks for reporting back iTitus! Glad you are finally stable. :)