CMT6GX3M3A1600C7 BSOD in Win7 Pro 64 when running Prime95

[KitesurferX]

Hello All,

 

I have been unable to get my system to run Prime95 for any more than 2 hours. It runs for 2 or so hours then it bsod, and I receive the following Windows report for the error:

 

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.256.48

Locale ID: 1033

 

Additional information about the problem:

BCCode: 124

BCP1: 0000000000000000

BCP2: FFFFFA800673D028

BCP3: 00000000FA000000

BCP4: 0000000000400405

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

 

From what I have been able to determine from research on-line it seems to point the finger at memory issues.

 

After doing more research I switched the profile from XMP and set the major RAM settings in the bios manually based on this post and this post. After I made the manual adjustments in my bios I ran Prime95 again, and same result.

 

Also, following Yellowbeard's instructions I created a bootable USB key to test the memory. I was able to run Memtest for 9 hours with 7 passes and 0 errors.

 

I am not OCing the processor, although it is my intention to do so once it is stable at stock settings. Temps are running 54 - 59C when under load in Prime95.

 

I am out of ideas, and not sure what else could be going on. Could anyone with some more knowledge provide any thoughts or insight that I might be missing?:confused:

 

Thank you in advance for any replies.

[Ahtlon]

BCCode: 124 means low qpi/dram, try 1.35v for qpi/dram.

If you can run memtest for 9 hours doesn't mean that it is stabil in windows with prime.

I had the same problem, run 1600 with 1.30v on qpi/dram with memtest for 10 hours stabil , with prime bsod after 1 hour.With 1.35 volt rock stabil for 8 hours.

Raise your qpi/dram, some cpu's need high voltage on qpi.

I always use test 5 with memstest and blend with prime.

[KitesurferX]

Hey Ahtlon,

 

Thank you for your reply.

 

I thought that the QPI might have had something to do with it, but I do not know enough to start changing voltages without some other people's advice.

 

Based on your reply, I went into the bios and cranked QPI up from the recommended 1.2v to 1.35v. ASUS Probe is still showing the QPI varying voltage between 1.33 and 1.35. Not sure how accurate that is. I just ran IntelBurn with 15 passes @ the Very High stress level and passed with flying colors. I am going to run Prime95 blend all night and see how it goes. Last time it could not make it past 2 hours, so I should know pretty soon.

 

Thanks again for the advice, and will let you know the final result.

[trackrat]

The QPI should be fine @ 1.35 V. Asus and other software based voltage readouts are not particularly accurate. Be advised that Asus Probe can also cause system instability issues...

[Ahtlon]

You can also enable Qpi/llc ( jumper near the 24 pin power suply), but this overvolts the qpi/dram a little bit on the R3E, you will have to lower your voltage then to 1.33 to 1.34 to get max.1.35v, but its more stabil as without.

Corsair Dominator Gt and Asus Rampage III extreme is a dream team.:D:

[KitesurferX]

trackrat, thank you for the information. I was hoping that the bios was more accurate in regulating voltage vs. Probe at reading it.

 

Ahtlon, thanks to your advice all is well. I ran Prime95 on blend for 12 hours last night, and it ran without a hiccup. Thank you again.

 

Based on your second reply, you recommend that I enable the QPI_LL Switch and then lower the voltage in the bios to 1.33 or 1.34. This will result in greater stability? Thanks again for help.

[trackrat]

Asus Probe is not that accurate. To see the true mobo voltages you'd need an O-scope or at least a quality DVM. Don't be concerned with the Probe readouts. They are just a reference point.