Is my CPU dead from OC'ing?

Kinderboeno

Reputable
Feb 8, 2016
10
0
4,510
Hi everyone,

I've built a system myself last year November with these following Specs:

CPU: I5 6600K Skylake 3.5GHZ
AIO: Cooler Master Nepton 240m
Mobo: ASUS Maximus Ranger VIII
GPU: ZOTAC 980TI AMP Extreme
RAM: Kingston Hyper Fury X 2666 8GB 2 sticks
Storage: Samsung 850 evo pro 250GB(OS), WD Blue 1 TB x2(Misc Data)
PSU: Seasonic M12II-850W Evo 80+ Bronze
OS: Windows 10 x64 Pro

Everything ran smooth as butter until recently I tried overclocking my CPU and RAM. CPU from 3.5 to 4.6GHZ at constant 60 degrees during stress tests and my ram from 2133mhz to 2666mhz with no issues during stress tests and heavy gaming.

The problem

Until a few days ago, The second it loaded into the desktop, it would immediately reboot and go back to the asus POST screen and back to the desktop where it will loop again. I then reverted the default clock values of my CPU and RAM and tried again but the reboot problem did not go away.

I then tried to nuke my OS and perform a clean installation without formatting my Misc Data Drives by using my usb drive which was created using rufus. The installation went thru and rebooted, however, during the initial Windows 10 start up "Getting devices ready" screen, the logo would flash a few times before it reboots itself and it repeats in a never ending loop.

So I tried installing my OS again but this time formatting all my storage drives and choosing my SSD as the primary source. Halfway through the next few installations, I received "irql_not_less_or_equal" and "Fault in non paged Area" errors and it rebooted my system and refused to POST until i Shut-down the system.

I've tried changing from AHCI to Other OS in the BIOS but to no avail, it rebooted and crash with those errors during installation.

I then tried installing windows 7 x64 via CD. Right after the loading files bar and it shows the windows 7 logo loading animation, I BSOD getting 0x0000007f and 0x0000000A stop codes and reboots.

Things I've tried to troubleshoot so far:


-Reset my overclock to default values (all Auto)
-Clear my CMOS and flash my BIOS to both newer and older versions
-Used a single stick of RAM and swapped between sticks
-Bought another 16GB kit of the exact RAM that I have and again tried both and single sticks config
-Ran memtest on my first kit. One stick froze at #7 but if I placed the other stick together, it ran for 5 hours no errors
-Take my Mobo out and did a barebone test (Onboard Graphics, one stick ram and swap around with the new Kit, CPU, Power)
-Used another z170 mobo (ASUS Pro-Gaming), did the barebone test with this as well, and cleared my CMOS and BIOS
-Ensured that all connectors (Fans, Ram, CPU, items that were connected to the mobo were well secured
-Swapped PSUs and every component i tested above with it
-Plugging my PC directly to the wall instead of a multi plug


and every item here has basically not solved my problem. Even with a fresh 16GB kit or mobo. I'm starting to wonder if it is my CPU that is fried?

Does anyone have any advice on this? I'm at my wits end with this and my only conclusion is that the CPU is done for. But I can't test that out because I don't have a spare skylake chip.

I would really appreciate your insights about this!
 
Solution
Since you've already attempted to replace all the other parts it could be the cpu. Overclocking is always a bit of a risk and should be done in gradual steps rather than all at once. Standard warranties don't typically cover overclocking damage (if that's what in fact caused the damage) and instead Intel does offer protection for overclocking.

Here is the link to their tuning plan which is sold as additional coverage offering replacement in the event overclocking goes wrong.
https://click.intel.com/tuningplan/

Kinderboeno

Reputable
Feb 8, 2016
10
0
4,510


Yup, tried every combination i could think of with my initial set of ram and the new set i just bought and swapped motherboards as well.

I can post and enter the BIOS. But it BSODs when I try to install windows as explained in the problem section.
 

iamacow

Admirable
What was your voltage set to for the overclock? It's possible you killed the memory controller on the CPU. I doubt you killed the chip from the built in Auto OC voltage so quick. Maybe after a year or so 24/7.

Download and boot/run Memtest86 and see if your ram errors out.
 

Kinderboeno

Reputable
Feb 8, 2016
10
0
4,510


Yep! Same problem. I tried each of my storage devices individually. Same problem. Ran diagnostic tests on my SSD and everything is fine with no problems.
 

Kinderboeno

Reputable
Feb 8, 2016
10
0
4,510


Yeah I only got this chip November last year.

I think it was 1.320 in adaptive mode if I remember correctly.

I ran benchmarks and tests for a few hours during the inital overclock. No crashes, BSOD's, or performance hits and at constant 60 degrees.

The problem just decided to pop up suddenly :(

Yep I did that for about 5 hours. No Errors. Both the new and old ram kits.
 

iamacow

Admirable
So it's not your memory controller or ram. It has to be something else. If you swapped motherboard, different hard drive and it crashes when you put your cpu underload (loading windows) I'm out of ideas besides a PSU issue. Put your system back to stock and see if it boots.

If you did all that and you still cannot post than my guess is your cpu is bad. send it for a RMA.

Last possible thing I can think of is clear your CMOS.
 

Kinderboeno

Reputable
Feb 8, 2016
10
0
4,510


Yeah I tried that also. Took out the battery and cleared the CMOS for both boards. Still no go. I think its time to contact intel for an RMA :(
 
Since you've already attempted to replace all the other parts it could be the cpu. Overclocking is always a bit of a risk and should be done in gradual steps rather than all at once. Standard warranties don't typically cover overclocking damage (if that's what in fact caused the damage) and instead Intel does offer protection for overclocking.

Here is the link to their tuning plan which is sold as additional coverage offering replacement in the event overclocking goes wrong.
https://click.intel.com/tuningplan/
 
Solution