CPU: i7-4930k
GPU: GTX 760
MOBO: Asus P9X79
Cooling: Corsair H80i
RAM: Corsair Vengeance 64GB 1866 MHZ
OS: Windows 7 64bit
First time posting here, since I'm at the end of my rope.
I installed a new proc a few months ago and had it overclocked to 4.2ghz, using the Turbo features in the BIOS, and it worked great until now. Last week I got successive BSOD while rendering in Nuke with temp spikes at 81c. Temps were at 40c at idle and would shoot up to 75c after a few seconds of rendering and then to 80c. When that happened I would stop the render.
I don't know alot about overclocking, that's why I went with the auto features in the BIOS.
I reset the overclock back to optimal, and no more BSOD, but now I'm getting lags while just working where the proc spikes at 100%.
I checked the dump logs and it was the hal.dll x124 error on the BSOD. Which seems like it was due to overheating or some other failure with the cpu.
After doing my research, I'm going to redo the thermal paste, to see if that helps.
What I'm wondering is, is there any other test I can do to see if it is a fried CPU? I've tested it with intel's cpu utility and it passes fine. I want to make sure I rule out any possible setting before having to head to ebay to try and find a new proc.
Thanks
Nick
GPU: GTX 760
MOBO: Asus P9X79
Cooling: Corsair H80i
RAM: Corsair Vengeance 64GB 1866 MHZ
OS: Windows 7 64bit
First time posting here, since I'm at the end of my rope.
I installed a new proc a few months ago and had it overclocked to 4.2ghz, using the Turbo features in the BIOS, and it worked great until now. Last week I got successive BSOD while rendering in Nuke with temp spikes at 81c. Temps were at 40c at idle and would shoot up to 75c after a few seconds of rendering and then to 80c. When that happened I would stop the render.
I don't know alot about overclocking, that's why I went with the auto features in the BIOS.
I reset the overclock back to optimal, and no more BSOD, but now I'm getting lags while just working where the proc spikes at 100%.
I checked the dump logs and it was the hal.dll x124 error on the BSOD. Which seems like it was due to overheating or some other failure with the cpu.
After doing my research, I'm going to redo the thermal paste, to see if that helps.
What I'm wondering is, is there any other test I can do to see if it is a fried CPU? I've tested it with intel's cpu utility and it passes fine. I want to make sure I rule out any possible setting before having to head to ebay to try and find a new proc.
Thanks
Nick