Contribute
Register

System Freezes; Screens go to one black one white. (Solved)

Status
Not open for further replies.
Holy smokes! I never considered XMP may be an issue. Back in December, I also had an issue with RAM where they could not be run reliably at their advertised speed. I ended up doing a warranty replacement and since getting the replacement RAM, I've been running them 200MHz lower than advertised speed.

2666 is the advertised speed but for what ever reason with XMP It crashes! With it off it has not crashed in 12 days that is 10 days longer then the average crash and 5 days longer then the time I got with XMP off but not clocked right. It runs at the advertised speed but I manually set the clock speed in the bios, and all seems to be well. I had two sets of the same memory bought 6 months apart and they all crashed so I am not sure it is bad Ram as two of them are in this Hack and two of them are in windows machine and runs fine now.
 
2666 is the advertised speed but for what ever reason with XMP It crashes! With it off it has not crashed in 12 days that is 10 days longer then the average crash and 5 days longer then the time I got with XMP off but not clocked right. It runs at the advertised speed but I manually set the clock speed in the bios, and all seems to be well. I had two sets of the same memory bought 6 months apart and they all crashed so I am not sure it is bad Ram as two of them are in this Hack and two of them are in windows machine and runs fine now.

It never occurred to me that XMP could be an issue... I just lowered the speed from an advertised 3400MHz to 3200MHz (completely randomly decided on -200MHz) to be safe and haven't had any issues with my replacement set of RAM.

I'm never in Windows long enough to do any testing there...
 
It never occurred to me that XMP could be an issue... I just lowered the speed from an advertised 3400MHz to 3200MHz (completely randomly decided on -200MHz) to be safe and haven't had any issues with my replacement set of RAM.

I'm never in Windows long enough to do any testing there...

When you had stability issues with the memory in December were you using XMP or were you using manual clocking like you do with your CPU? Did you ever use XMP with the new ram or did you just decide to manually clock it 200 under?

In addition in another thread with a similar problem dude noticed better stability without XMP that's what is made me try but now he's running another system stable with it enabled. So I really do not know for 100% this was the solution. However I ran the system with No XMP and did to configure the memory just left everything the way defaulted got 5 days turn XMP on crashed in 2, Turned it off manual clocked he memory and here we are today with 12 days 17/hrs uptime.
 
When you had stability issues with the memory in December were you using XMP or were you using manual clocking like you do with your CPU? Did you ever use XMP with the new ram or did you just decide to manually clock it 200 under?

In addition in another thread with a similar problem dude noticed better stability without XMP that's what is made me try but now he's running another system stable with it enabled. So I really do not know for 100% this was the solution. However I ran the system with No XMP and did to configure the memory just left everything the way defaulted got 5 days turn XMP on crashed in 2, Turned it off manual clocked he memory and here we are today with 12 days 17/hrs uptime.

I always use XMP for the RAM because I don't know enough about how to set the timings.

When I got my replacement RAM, I clicked on XMP so that it can set the timings. Then lowered the actual clock speed by 200MHz.

I say use whatever works. Lol
 
Status
Not open for further replies.
Back
Top