Solved Constant Random BSODs on a 5 days old system

[iTitus]

I decided to test the GFX card one more time.
That all worked out fine without crashes etc.

I'm emailing back and forth with the shop now.

Edit:
The guy said that if Memtest gave error's, the memory would probably be broken and that a RMA should solve it. So I decided to do that.
Upon getting (hopefully) new RAM I'll remove the DRAM Voltage bump and see what the new ram does in memtest86

 

[Dave76]

Sounds like a good plan.

What RAM are you getting?

Make sure it's RAM made for the AMD motherboard, 'standard or Intel RAM' won't run as well as RAM designed for AMD.
You'll have better luck with 1333MHz or lower RAM, anything higher will be difficult to get running.

Start out with XMP enabled in your BIOS, this should be the best setting.
Then check all RAM settings to be sure they match the recommended manufactures specs. It should be in un-ganged mode.
Run Memtest86+.

You may still need to bump the NB voltage, this is common for AMD RAM.

Let us know how it's going.

 

[iTitus]

I'll be getting the same GEIL modules. Which were tested by Gigabyte and approved...

 

[iTitus]

Ok so Image I could pick new RAM. Which RAM should I pick with my system.
I'm looking for 4gb in the first place, but you know 8gb is not wrong, just a little expensive
Also, here's a support list from my MoBo.

System
http://www.sevenforums.com/crashes-...andom-bsods-5-days-old-system.html#post917681

 

[Dave76]

It depends on which brand you prefer.

From your motherboard DDR3 1333 RAM list.

C13C1 2GB CORSAIR CM3X8GX3M4A1333C9 DS

G13C1 2GB GEIL GG34GB1333C9DC DS

GSET13C1 2GB G.SKILL F3-10666CL8D-4GBECO DS


Be sure to double check that the RAM is specifically designed for an AMD motherboard.
If it says Intel or doesn't name either, I would check for another from the motherboard RAM list.

Let us know how it's going.

 

[iTitus]

Just got my ram back. Triple bad:
It's different ram -_-
a) it's to big to fit under my cpu cooler, so 2/4 slots can't be used
b) it's C9 in stead of C7
c) one of the two sticks won't boot at all

Really thinking about different memory now.
Can someone with one of the memories named in the post by dave measure how high they are?

Thanks

 

[Dave76]

With my Gigabyte Intel board, CM Hyper 212 Plus, Corsair XMS DDR3 RAM, I have about 1mm clearance between the fan on the CPU cooler and the first RAM card.
The CPU cooling fan just barely covers about 30% of the first RAM card, just enough to cause a problem if the Ram was 1mm higher.
Mine is 28mm from socket to top of RAM card, Ram installed in socket.

If your board layout is similar to mine, you definitely won't fit the Corsair Dominators, the heat sink is too big. The XMS should fit.

Measure the space between your RAM socket and the Hyper 212 Plus fan housing, post it here.

I Would search/ask at the Corsair forum (or other RAM Forum), give them the above measurement.
Memory Compatibility

Better to get 2 RAM cards, as there are reports of problems when using 4 cards.
Now is the time to plan for any future upgrades. Go with 8GB now if you think you might want it later.
Or take the chance that 4 cards will work on your board.

 

[iTitus]

Just got email from the shop. Their mistake, they will be sending me the memory I had, but a fresh one. It seems all issue's will be solved and it will fit and I got my nice timings back.
Let's wait and see.
I'll get back on you guys.
Thanks

 

[Dave76]

Thanks for the update, let us know the results.

 

[iTitus]

jeeeeej
/sarcasm mode off

I got my new RAM today. Popped it in, got past bios but freezed at windows logo.
I tried a few times and managed to get it past windows logo a few times, and even into windows itself. But even changing resolution or running 2 programs made it crash.
So I've got a few BSOD's for you

Also I would like tell you about the configuration:

From the wrong RAM they sent me one stick was just broken(didn't even bios, beep error code no memory)
The other one booted fine in slots 2,3,4.(It didn't fit into slot 1 because it was too high and my CPU cooler is there)

The new correct RAM is extremely unstable.
Stick 1 didn't finish winboot in slot 1,1,4(it did boot after I wobbled it arround a bit)
It did boot once in slot 3 and not after that.
Stick 2 didn't boot in 1,2,3(after pressing it harder into the mobo it did get past winlogo but crashed on windows welcome)
and slot 4 gave me a BSOD

I was so sick of this that I tried the wrong RAM again:
Stick 1 still beeped no memory and stick 2 still booted without problems

I mean, this is clear isn't it? No memtest86 is required?

But still I don't have a clue.
My only guess is that this New correct ram is faulty aswell, in which case I will return it and get another brand that is on the QVL.

The other guess is that my MOBO is the problem. I can't really imagine why.
But a good solution seemed to get both a new(different) mobo and new(different) RAM.

This would be a costly solution, also given the fact that I would need new thermal past etc etc etc.

Could you have a look at the BSOD and advise what to do with the RAM and/or Mobo

Thanks!!

 

[Tews]

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

*******************************************************************************
*                                                                             *
*                        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 ..

 PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D) ... Sonic CD/DVD driver (used by many different CD/DVD programs) ... [url=http://www.carrona.org/pxhelp20.html]pxHelp20.sys programs[/url] [b]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]
[/b]

 

[iTitus]

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

 

[Tews]

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]

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

 

[bwpotter]

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]

The shop sent me new ram. Kingston this time:
KHX1333C7AD3K2/4G
http://www.valueram.com/datasheets/KHX1333C7AD3K2_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]

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]

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 ).

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]

Problem totally gone.
Conclusion: The RAM was faulty.

Thanks everyone.

Thread is lockable.

 

[Jonathan_King]

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