Memory corrupted after longer sleep

[VioletDragon]

I've been dealing with this bug for almost 2 years now. OS X crashes more frequently, but Win7 and Win10 are both affected in the exact same way (BSOD or KP after waking from sleep). If you restart your PC once a week you might never encounter it under Windows.

FYI, Windows users have reported this crash as well (http://forum.crucial.com/t5/Crucial...-Mode-Ballistix-Sport-GA-Z97X-SLI/td-p/171395, solved by switching to Asus motherboard), (https://forums.overclockers.co.uk/showthread.php?t=18664304, also solved by switching to an Asus board), (http://www.sevenforums.com/bsod-help-support/340313-random-bsod-when-waking-up.html, user disabled sleep entirely), (https://community.amd.com/thread/189756, two different users resolved their issue by increasing RAM voltage).

The only solution to this problem I have seen is to increase RAM voltage, which sadly hasn't worked for me.

Is you're RAM listed on the manufacturers Memory Support List?

 

[HermiG]

Is you're RAM listed on the manufacturers Memory Support List?

Yeah, they are on the QVL for my motherboard. I even RMA'd the first 2 sticks of RAM for another set, which performed exactly the same. Then I bought RAM from a different vendor with no improvement. All these dimms pass 10 passes of memtest86+ and 2 hours of Asus RealBench. Also, I have gotten weeks of system uptime using these same RAM modules on an AsRock board with the exact same timings and voltages, so the Gigabyte board is the only failure point here.

But I still haven't seen a panic with F11c BIOS, so maybe Gigabyte finally fixed it.

 

[VioletDragon]

Yeah, they are on the QVL for my motherboard. I even RMA'd the first 2 sticks of RAM for another set, which performed exactly the same. Then I bought RAM from a different vendor with no improvement. All these dimms pass 10 passes of memtest86+ and 2 hours of Asus RealBench. Also, I have gotten weeks of system uptime using these same RAM modules on an AsRock board with the exact same timings and voltages, so the Gigabyte board is the only failure point here.

But I still haven't seen a panic with F11c BIOS, so maybe Gigabyte finally fixed it.

Thats a strange one. Im out of ideas.

 

[VirtualRecess]

I've been dealing with this bug for almost 2 years now. OS X crashes more frequently, but Win7 and Win10 are both affected in the exact same way (BSOD or KP after waking from sleep). If you restart your PC once a week you might never encounter it under Windows.

FYI, Windows users have reported this crash as well (http://forum.crucial.com/t5/Crucial...-Mode-Ballistix-Sport-GA-Z97X-SLI/td-p/171395, solved by switching to an Asus motherboard), (https://forums.overclockers.co.uk/showthread.php?t=18664304, also solved by switching to an Asus board), (http://www.sevenforums.com/bsod-help-support/340313-random-bsod-when-waking-up.html, user disabled sleep entirely), (https://community.amd.com/thread/189756, two different users resolved their issue by increasing RAM voltage).

The only solution to this problem I have seen is to increase RAM voltage, which sadly hasn't worked for me.

Interesting. From reading this thread i assumed it was a OS X/Linux problem with Gigabytes BIOS. Guess it goes deeper than than that

 

[VioletDragon]

Interesting. From reading this thread i assumed it was a OS X/Linux problem with Gigabytes BIOS. Guess it goes deeper than than that

On my H97N-WIFI build it works fine but I'm not using a Beta BIOS neither. Have you checked you're BIOS settings?

 

[VirtualRecess]

On my H97N-WIFI build it works fine but I'm not using a Beta BIOS neither. Have you checked you're BIOS settings?

Yeah i've had spent a lot of time testing out various configurations in the BIOS with no luck. Also tried out the F9a beta bios for a short while which didn't help much either. The only fix I know of is if i were to revert back to 3,1. I believe its something to do with the ECC Memory in Mac Pro SMBIOS's that gets around the problem.

 

[WonkeyDonkey]

Yeah i've had spent a lot of time testing out various configurations in the BIOS with no luck. Also tried out the F9a beta bios for a short while which didn't help much either. The only fix I know of is if i were to revert back to 3,1. I believe its something to do with the ECC Memory in Mac Pro SMBIOS's that gets around the problem.

What system definition are you using currently ?

 

[VioletDragon]

Yeah i've had spent a lot of time testing out various configurations in the BIOS with no luck. Also tried out the F9a beta bios for a short while which didn't help much either. The only fix I know of is if i were to revert back to 3,1. I believe its something to do with the ECC Memory in Mac Pro SMBIOS's that gets around the problem.

Mac Pro isn't correct. Use iMac 14,2.

 

[VioletDragon]

What system definition are you using currently ?

Im using iMac 14,2

 

[VirtualRecess]

What system definition are you using currently ?

Running 14,2 atm