Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

BSOD question

Sayjimwoo
Level 7

‎12-03-2013 12:53 PM - last edited on ‎03-06-2024 06:44 PM by Community Admin

I have an overclock on my i7 4770k of 4.5 ghz. (Z87 Deluxe board) My temps are low and everything runs runs great. I have been hammering games now solid for 2 months, especially BF4 for a few weeks now. Suddenly out of the blue whilst playing BF4 I got the BSOD whea uncorrectable error. I know this error is related to the CPU. Even though I have played games and used my PC solidly for 2 months could this still mean my overclock is unstable? Or just carry on as normal and monitor it?
If my system was unstable, why crash after 2 months of continuous use? Strange.
W10 Pro - Phantek ATX Glass - Asus Maximus IX Formula - Zonar Phoebus - Intel i7 7700k - Corsair H115i - Corsair Vengeance RGB 32GB DDR4 3200 MHz - 1080ti Sea Hawk X - 3x Samsung 850 evo 1tb - 2x WD Black 2tb - Pioneer Blu-Ray - Corsair RM850 - Razer Deathadder Chroma - Razer Ultimate Stealth 2016 - BenQ XL2720Z 27 144hz Gaming Monitor - Oculus Rift
Labels:
0 Kudos
15,399 Views
4 REPLIES 4

HiVizMan
Level 40

‎12-03-2013 11:57 PM

Whea errors are most often associated with memory and as you correctly stated CPU as the memory controller is on the CPU. Monitor and record what if any additional errors you get. For now just enjoy ...
To help us help you - please provide as much information about your system and the problem as possible.
0 Kudos

Kross
Level 7

‎12-04-2013 12:22 AM

Funny things happen over time with heat and silicon. My i7 920 did this same thing a few years ago. I had to play around with the voltages and overclock again to find the stability the system needed. I haven't had a single crash since then.

I agree that after a few months it's weird that it's crashing. If the stop code in the BSOD is 124, then that's related to the cpu and it's voltage most likely. Either too high or not enough voltage, more commonly the latter.

I suggest trying to mess around with the overclocking again. I would reset the CMOS and then redo the overclock. It certainly wouldn't hurt anything.
0 Kudos

Sayjimwoo
Level 7
In response to Kross

‎12-04-2013 02:28 PM

Thanks. Yeah it was a 124 error. I am currently tweaking my voltages. I suppose it wasn't 100% stable or It wouldn't have crashed at all.
W10 Pro - Phantek ATX Glass - Asus Maximus IX Formula - Zonar Phoebus - Intel i7 7700k - Corsair H115i - Corsair Vengeance RGB 32GB DDR4 3200 MHz - 1080ti Sea Hawk X - 3x Samsung 850 evo 1tb - 2x WD Black 2tb - Pioneer Blu-Ray - Corsair RM850 - Razer Deathadder Chroma - Razer Ultimate Stealth 2016 - BenQ XL2720Z 27 144hz Gaming Monitor - Oculus Rift
0 Kudos

Kross
Level 7
In response to Sayjimwoo

‎12-05-2013 04:42 AM

Sayjimwoo wrote:
Thanks. Yeah it was a 124 error. I am currently tweaking my voltages. I suppose it wasn't 100% stable or It wouldn't have crashed at all.


At least it's an easy fix in the grand scheme of all things. Voltages are easy to fix, bad ram or a bum CPU isn't. 🙂
0 Kudos