Bsod clock interrupt secondary proc

[leejc73]

Are these regular happenings when overclocking a processor?

When I actually get the system to start up, for some reason from cold it prefers 4.8 over 4.6 my first few prime runs will throw out this failure.

I didn't get the stop error but I'm wondering if it could be down to the ram I'm running vengeance 8-8-8-24 @ 1.515 volts.

The board is also occasionally dual booting which I've read about with asus boards as well and might be fixed with a later bios.

I've got 4 sticks of 4Gb just wondering what I can push the volts and timings out to for a stable regular boot before I start bringing them down again?

Can ram cause this crash? Can it also cause the cursor "I'm doing feck all, yer can barlocks" flash type symptoms?

I'm getting the processor workable but at voltages higher than I think is possible if I can get rid of this clock secondary processor whojit.

Cheers

Lee

 

[yassarikhan786]

I'm by no means an expert but I've read that the more RAM sticks you use the less tight the timings have to be in order to achieve stability with the RAM. The recommended RAM timings should be on a sticker on the RAM itself. If the timings stated on the RAM are different to what you are seeing then set the RAM timings to those specified on the sticks.

What processor are you using by the way? I had the same problem of dual booting because of the timings on my RAM. I had it @1600Mhz with timings of 9-9-9-24 1T, but I had to change it to 9-10-9-27 1T in order to achieve stability. I used prime95 to check stability and I have been running problem free since I changed the timings. I tested the RAM at 1866Mhz with the timing at 9-10-9-27 but it wasn't stable at 1.5V. I didn't bother upping the voltage as I was satisfied with 1600Mhz.

 

[Matt_58]

i had that....

turned out Mobo was stuffed and was not delivering clean power to the CPU. check MOBO and PSU?