Tech Support Forum - View Single Post

Movitz · 05-25-2008, 02:31 AM

Firstly I want to thank Dai, upping the voltage helped me to get my memory stable at lower latencies. I was going to try this some day but never got around to do it until now.

I ORTHOSed my system for 8 h at 5-5-5-18 and 12 h at 4-12-12-12 without any problems. Since a faulty module would provide errors regardless of timing this effectively means that my system was stable for 20h (right?). Maybe I'll let it run for 24 h on one timing some day but for now I'm happy.

But it does not explain why I get the CRC errors. The bluescreen migh just have been fluctuations in the eldrich energies that governs the spacetime continuum and doesn't bother me as long as it doesn't repeat it self.

Should I consider the RAM non-faulty now since ORTHOS seems fine? Is is possible that the problem is with the motherboard or the HDD instead?

05-25-2008, 02:31 AM	#10 (permalink)
Movitz Registered User Join Date: Jun 2006 Posts: 40 OS: XP	Re: Bluescreen = dead RAM right? Firstly I want to thank Dai, upping the voltage helped me to get my memory stable at lower latencies. I was going to try this some day but never got around to do it until now. I ORTHOSed my system for 8 h at 5-5-5-18 and 12 h at 4-12-12-12 without any problems. Since a faulty module would provide errors regardless of timing this effectively means that my system was stable for 20h (right?). Maybe I'll let it run for 24 h on one timing some day but for now I'm happy. But it does not explain why I get the CRC errors. The bluescreen migh just have been fluctuations in the eldrich energies that governs the spacetime continuum and doesn't bother me as long as it doesn't repeat it self. Should I consider the RAM non-faulty now since ORTHOS seems fine? Is is possible that the problem is with the motherboard or the HDD instead? Last edited by Movitz; 05-25-2008 at 02:33 AM.