Continuous BSOD after memory errors

So what do you think the next course of action should be?

I think it's worth mentioning that since it reverted to 1333mhz and I updated the rtcore64 driver, it hasn't crashed (but then again, it didn't crash for 2 weeks at a time before). I enabled the option which clocks it to 1600ghz though, since I'd like to have exactly what I paid for. Is it possible if that is the issue, it doesn't like the voltage at 1.5v? I'll let you decide since you're the pro.

donmiq said:

So what do you think the next course of action should be?

I think it's worth mentioning that since it reverted to 1333mhz and I updated the rtcore64 driver, it hasn't crashed (but then again, it didn't crash for 2 weeks at a time before). I enabled the option which clocks it to 1600ghz though, since I'd like to have exactly what I paid for. Is it possible if that is the issue, it doesn't like the voltage at 1.5v? I'll let you decide since you're the pro.

Hey I would tr it for a while. If it fails back off one at a time.

zigzag3143 said:

donmiq said:

So what do you think the next course of action should be?

I think it's worth mentioning that since it reverted to 1333mhz and I updated the rtcore64 driver, it hasn't crashed (but then again, it didn't crash for 2 weeks at a time before). I enabled the option which clocks it to 1600ghz though, since I'd like to have exactly what I paid for. Is it possible if that is the issue, it doesn't like the voltage at 1.5v? I'll let you decide since you're the pro.

Hey I would tr it for a while. If it fails back off one at a time.

Thank you! I'll update you one way or another :)

donmiq said:

zigzag3143 said:

donmiq said:

So what do you think the next course of action should be?

I think it's worth mentioning that since it reverted to 1333mhz and I updated the rtcore64 driver, it hasn't crashed (but then again, it didn't crash for 2 weeks at a time before). I enabled the option which clocks it to 1600ghz though, since I'd like to have exactly what I paid for. Is it possible if that is the issue, it doesn't like the voltage at 1.5v? I'll let you decide since you're the pro.

Hey I would tr it for a while. If it fails back off one at a time.

Thank you! I'll update you one way or another :)

Good luck

A new bsod

donmiq said:

A new bsod

Still memory corruption. Are you overclocking by chance?

zigzag3143 said:

donmiq said:

A new bsod

Still memory corruption. Are you overclocking by chance?

Everything is at stock, the only thing that I could see as "overclocking" is the ram that needs the XMP profile to be set in order to have my ram running at 1600 instead of 1333ghz.

ruddiger said:

Hi donmiq et al,

I'm new to the forums here but am currently looking at building my own comp with almost identical specs to yours:

CPU: i5-2500K
Mobo: gigabyte z68a-dh3-b3
GPU: msi gtx 560 Ti hawk
RAM: Corsair vengeance 8GB 1600
PSU: Antec High Current Gamer Series 750W

I'm trying to check compatibility issues before I click the "buy" button and came across your post. Has there been any resolution to the issue in the last couple months? Is the out-of-the-box overclocking of the GPU a possible cause (since the Hawk is pre-tweaked, the Afterburner software may have been implicated in earlier BSOD's and you don't appear to get the issue until after installing the drivers)?

Hey,

I eventually ran memtest for around 3 days straight and got 1 error. I'd think I would have gotten more, but 1 was enough and I returned the ram. I ended up getting 8gb as it was on sale, and I haven't had the problem since. I'd say your build is good to go.

Sorry for never updating this and making you wait to order. Good luck, and have fun with your new computer!