Strange BSOD

[iRage]

Alright Guys, I have this strange problem that I can't fix. I've tried everything I know of and still no solutions and suggestions from others of the community with no results.

I've overclocked my i7-2600K to 4.6 GHz using Offset Voltage. I also overclocked my Memory to 1600 MHz and 9-9-9-24-1T Timing, the default for the memory is 9-9-9-24-2T. With these settings I've run Prime95 for 12 Hours straight at v1.28 and received no errors what so ever.

However, when I play a game such as League of Legends which only uses 15% load at the most, and watching a Youtube Video, every so often I get the BSOD...

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Here are the fixes I've tried:

1. Reinstalled League of Legends to make sure it isn't corrupted.
2. Reinstalled Drivers
3. Upgraded Drivers
4. Downgraded Drivers
5. Ran Prime95 Small FTT for 8 Hours without receiving any errors.
6. Ran Memtest 86+ twice, 8 Hours each time without any errors.
7. Ran Windows Memory Diagnostic twice without any errors.
8. Downclocked Memory timings from 9-9-9-24-1T to 9-9-9-24-2T
9. Reinstalled Windows to make sure it isn't corrupted.
10. Upped VCore from v1.28 to v1.31 by 0.005 increments each time.
11. Disabled Spread Spectrum

I'm really at a loss to what it could be. Any ideas?

 

[Schmide]

Please don't play LOL with an unstable computer!!! For the sake of the team dude. It's not like it takes a ton of CPU.

Have you tried backing off your clock. 4.6 is kind of high without exotic cooling.

 

[iRage]

My cooling is a Noctua NH-D14, don't know a better one out their other than Water Cooling. My Temps are stable enough when running Prime95, otherwise I would have done 4.8.

I'd prefer not to go back to Stock Clocks, otherwise my i7-2600K would have been for nothing. I bought it to overclock...

 

[iRage]

Is it possible that my CPU is unstable at lower clocks, since my voltage scales and this usually happens when using programs that use very little of my CPU? If so should I just put Phase Control on Extreme and use Manual Voltage to overclock so it doesn't downclock? And if I do that, would it damage my CPU to constantly run at v1.29 even when idle?

 

[SickBeast]

Is it possible that my CPU is unstable at lower clocks, since my voltage scales and this usually happens when using programs that use very little of my CPU? If so should I just put Phase Control on Extreme and use Manual Voltage to overclock so it doesn't downclock? And if I do that, would it damage my CPU to constantly run at v1.29 even when idle?

That's very well possible. You need to stress test your CPU at each of the speed steps. I use K10Stat with my Phenom II to do this. I'm not sure what you need for an i5.

I wouldn't stop the CPU from downclocking. There is a major difference in terms of power consumption. With my setup, I save around 100 watts by aggressively downclocking my CPU.

Also, you should try some more stress tests in general. What I do personally is run LinX and Prime95 (blend test) simultaneously. If it can survive that for 15 minutes or so, it's pretty good. If you want it to be rock solid, go for longer.

 

[iRage]

That's very well possible. You need to stress test your CPU at each of the speed steps. I use K10Stat with my Phenom II to do this. I'm not sure what you need for an i5.

I wouldn't stop the CPU from downclocking. There is a major difference in terms of power consumption. With my setup, I save around 100 watts by aggressively downclocking my CPU.

Also, you should try some more stress tests in general. What I do personally is run LinX and Prime95 (blend test) simultaneously. If it can survive that for 15 minutes or so, it's pretty good. If you want it to be rock solid, go for longer.

Thats the problem I have though, I ran Prime95 Blend and Small FTT. I ran Blend for 20 Hours, Small FTT for 8 Hours, and just recently reclocked using Offset settings and ran Blend again for 8 Hours... No issues what so ever. My Voltage Monitor says at Max CPU Stress I run between v1.28 and v1.288 volts for 4.6 GHz Overclock. When Idle my voltage drops down to v0.944 at 1.6 GHz.

When I run a program like League of Legends or even watch a Youtube video I'd get a 0x000001E BSOD every few hours. Oddly enough, I can keep my computer running idle 24/7 with no BSODs even at v0.944. So I'm not sure what the problem is.

 

[SickBeast]

Personally what I would do for now would be to run the memory at stock speeds and timings. That way you can isolate the problem. If you continue to have crashes, then you will know that your CPU is the problem, not the memory.

 

[iRage]

Currently running my memory overclocked to 9-9-9-24-1T at 1600 MHz and CPU at stock with no problems, so I'm pretty sure its not the memory.

 

[Athadeus]

Thats the problem I have though, I ran Prime95 Blend and Small FTT. I ran Blend for 20 Hours, Small FTT for 8 Hours, and just recently reclocked using Offset settings and ran Blend again for 8 Hours... No issues what so ever. My Voltage Monitor says at Max CPU Stress I run between v1.28 and v1.288 volts for 4.6 GHz Overclock. When Idle my voltage drops down to v0.944 at 1.6 GHz.

When I run a program like League of Legends or even watch a Youtube video I'd get a 0x000001E BSOD every few hours. Oddly enough, I can keep my computer running idle 24/7 with no BSODs even at v0.944. So I'm not sure what the problem is.

Idle systems almost never crash. Why don't you try a lower CPU multiplier like 44x and if it is stable there, just increase the voltage to get to 4.6ghz. Using less than 1.3v for 46x stable is not common.

 

[goobernoodles]

Have you stress tested the memory? Run memtest86. If there's no errors, I'd back the O/C back down to 4.2 or so to see if the issues subside. Then work your way back up.

I'd prefer not to go back to Stock Clocks, otherwise my i7-2600K would have been for nothing. I bought it to overclock...

Backing the O/C down doesn't mean going back to stock clocks.