I had my first BSOD 124 error last night while flying from Walter Suttons Farm to Jefferson Co in PNW scenery.

Specs i7 2600K, Asus P8P67Pro Rev 3.1, GTX 580 1.5gb, Corsair TX750, 8GB G-skill ripjaws x Noctua NH-D14

 

The system is only a few months old home build. I`m running it on an auto overclock and it runs FSX happily at 4.45ghz all day long usually. Temps never go above 67 Max on one of the cores with HT enabled as I do lots of video editing HT is needed.

 

.cfg tweaks bufferpools 0, affinity mask 255, LOD 6.5, wideview and V sync.

 

The only thing I changed on my setup last night was updated the NVidia driver to the latest one and re-done my Inspector settings. (could this be a driver issue)

 

From what I`ve read on the subject I`ve heard people saying to enable LLC and CPU overvoltage etc in the BIOS. Maybe I should as over this very dense scenery the chip was struggeling for juice?

 

I`m in the middle of a test flight in the NGX from LGKO-EGPH about four hours long then I`ll test last nights flight again.

 

I know I should be setting up the overclock manually and turning HT off but I was happy with the way things were running and temps were fine for me.

 

Any thoughts on this problem folks?

 

Thanks in advance Doogie

I think you should definitely OC "manually" and not use auto OC.

 

124 error is probably not enough voltage to the cpu.

 

A nice guide here http://www.overclock.net/t/1120291/solving-fixing-bsod-124-on-sandybridge-read-op-first

I think you should definitely OC "manually" and not use auto OC.

 

124 error is probably not enough voltage to the cpu.

 

A nice guide here http://www.overclock...e-read-op-first

 

Thanks for the swift reply Richard, your voicing exactly what I`m thinking. I think I`ll setup an OC`d profile for FSX with HT off and one for Video editing with HT on with slightly lower voltages and multiplyer.

 

My NGX test flight is running fine no BSOD`s yet after 3 hours with real weather which is pretty heavy cloud coverage over europe. I`ll also try the route I flew last night again just to see if it happens again.

 

This is my 2nd i72600k build and I had a nice stable clock of 4.5ghz on my last build manually, just never got round to setting this one up yet as it was running sweet the way it was. Must be the PNW scenery and heavy weather that pushed the chip to far with to little voltage for it to shutdown with no warning. As I said the temps are within limits so it`s all I can think off.

 

Thanks for the link I`ll be having a good read now :)

Add Vcore to your overclock. A 124 BSOD is just that, nothing to worry about :)

The 124 stop code indicates some sort of hardware failure. It can be any range of issues unfortunately. If it's happened out of the blue it's probably nothing to worry about, if it occurs with some sort of frequency then you have something to worry about. If it happens again you should make sure you've got the latest drivers for all of your hardware, get Windows up to date, that sorta thing. With any luck it was just Windows being Windows temperamental :Praying: .

 

Cheers,

 

Mike

Thanks for the replys guys...........I`m now sitting happily @ 4.5ghz manual overclock and HT off. I was able to repeat the problem flying over the same route. Chip was just needing more juice and I`d say things have improved a lot since changing AM to 14 from 255 and turning HT off. When recording with fraps now it bairly drops below 30fps where as before I was seeing low tweanties sometimes even high teens.

Happy bunny 1.32V 4.5ghz and temps are 10c lower than with HT on......and I`ve not noticed if any difference when using the Sony Vegas editor and rendering with HT off.

 

Cheers for the input ;)