0x101 with 2500k

[aidenn]

Hello,

I bought the following rig over a month and a half ago:

- 2500k
- P8P67 Deluxe
- Gainward GTX 570 Phantom
- G.Skill DDR3 8 GB (2 x 4 GB) 1600 MHz RipjawsX CL7
- Corsair 650HX
- Crucial M4 128GB
- Windows 7 Professional x64

The CPU is cooled by Mugen 2 and the temps are fine.

So, I overclocked the 2500k to 4.6 GHz (4.7 was requiring ridiculous vcores even with PLL Overvoltage to Prime95 nicely) and after a lot of testing I set the vcore at 1.36 (no PLL Overvoltage) and proceeded to enjoy the hell out of the system.

After a week or so of a perfect 24/7 work, I got my first 0x101 bluescreen while the computer was idling ("a clock interrupt was not received on a secondary processor within the allocated time interval"). I read that 0x101 means not enough vcore, so I upped it to 1.365.

After a few days I got another 0x101, so I went up to 1.375. And so the cycle went until last week, when I set it from 1.415 to 1.42. Enough is enough, I went down with the CPU to 4.5, set the vcore back at 1.35 and went on.

Today I got another 0x101. I upped the vcore to 1.36, but I fear it might not be the cause after all.

The BSODs are completely random, sometimes they happen when I play a game, sometimes when I'm browsing the web, and sometimes during the night, when the computer is just seeding torrents. Other than that, the system is completely stable and does Prime95 without a hitch.

Any ideas, guys?

 

[Eickst]

Did you test the memory also?

 

[Jbort1984]

possible power supply fluctuations?? I'm just guessing

 

[Nexus6]

Drop the vcore back, re-enable PLL overvoltage.

 

[aidenn]

Thanks, re-enabling PLL overvoltage did the trick. No 0x101s for me now for the last week. Not the best chip this one, 4,5 GHz @ 1.37v with PLL ATM. Still, it does the trick. Now I need some time to jump from straight OC to offset for low volts at idle.