Dear People of Tom's Hardware,
I recently decided to fine-tune my OC settings and, as a result, I might've damaged hardware inside my system. Let me explain, as this is kind of a complicated issue. Specs - http://textuploader.com/axlfq
So recently I decided to fine-tune my already stable CPU OC for the best performance and stability. I now have my Vcore (manual) set to 1.22 volts in the BIOS. So I started this process by overclocking the Uncore ratio, which I initially had set to x34, but now I have found a stable point at x44. Next, I started lowering the CPU's main Vcore voltage down. Before 1.22, I was using 1.25. My CPU is currently set to run at 4.5 Ghz.
Other settings I have enabled are: Intel SpeedStep EIST, C1E, C3, and C7 Cstates, CPU VRIN LLC is set to Medium (runs at 1.75 volts, set to 1.8 in BIOS), my ram is running at 1600Mhz with 1.5 volts applied (stock XMP profile overclock), and my GPU is running stable with 146Mhz added to Core overclock and 145Mhz added to the memory clock. (More information about parts in link above). My current motherboard is running with BIOS version F6.
How the issue became apparent: I was stressing my system with 1.25 volts applied to the Vcore with Aida64 Extreme and I started noticing that after I found a safe voltage, my system was getting a BSOD. I fixed the issue through tinkering with drivers and settings and I continued to stress my system. I ran Aida64 regularly, about 2-3 hours everyday, roughly 16-20 hours total (not at once, through time). During this, my temperatures never went above 80C. The concern kicked in once I noticed when I tried to boot my system from a cold boot, and I got a boot failure. To check if it was the OC, I disabled all of my OC settings for all of my devices. Unfortunately, I still got the error. I tried a few solutions, like checking some ports and panels inside my case, fixing driver issues, chkdsk, sfc scans, and so on. I reassembled some cables, checked for any damage on the motherboard, and found nothing.
At one point, I should also mention that my computer refused to start. This is how the boot error began. I had to reset the system, load into the BIOS, and then reset again to get into Windows. Just recently, I tried another cold boot and this time, I didn't receive a boot failure, but the system took longer to load into Windows. I have a blue screen viewer dump file of the error that I recently got and I will now paste it:
==================================================
Dump File : 072917-4625-01.dmp
Crash Time : 7/29/2017 6:09:14 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : ffffbe07`69664028
Parameter 3 : 00000000`bf800000
Parameter 4 : 00000000`00000124
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14f960
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14f960
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\072917-4625-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 434,557
Dump File Time : 7/29/2017 6:09:39 PM
==================================================
Please, if you can help in anyway or give any advice, I'd appreciate it. Is there a way I can find out what hardware is possibly damaged?
UPDATE 7/30/17: Boot failure issue appears to have gone away, system starting up normal again (hallelujah). Still concerned about possibly damaged hardware.
I recently decided to fine-tune my OC settings and, as a result, I might've damaged hardware inside my system. Let me explain, as this is kind of a complicated issue. Specs - http://textuploader.com/axlfq
So recently I decided to fine-tune my already stable CPU OC for the best performance and stability. I now have my Vcore (manual) set to 1.22 volts in the BIOS. So I started this process by overclocking the Uncore ratio, which I initially had set to x34, but now I have found a stable point at x44. Next, I started lowering the CPU's main Vcore voltage down. Before 1.22, I was using 1.25. My CPU is currently set to run at 4.5 Ghz.
Other settings I have enabled are: Intel SpeedStep EIST, C1E, C3, and C7 Cstates, CPU VRIN LLC is set to Medium (runs at 1.75 volts, set to 1.8 in BIOS), my ram is running at 1600Mhz with 1.5 volts applied (stock XMP profile overclock), and my GPU is running stable with 146Mhz added to Core overclock and 145Mhz added to the memory clock. (More information about parts in link above). My current motherboard is running with BIOS version F6.
How the issue became apparent: I was stressing my system with 1.25 volts applied to the Vcore with Aida64 Extreme and I started noticing that after I found a safe voltage, my system was getting a BSOD. I fixed the issue through tinkering with drivers and settings and I continued to stress my system. I ran Aida64 regularly, about 2-3 hours everyday, roughly 16-20 hours total (not at once, through time). During this, my temperatures never went above 80C. The concern kicked in once I noticed when I tried to boot my system from a cold boot, and I got a boot failure. To check if it was the OC, I disabled all of my OC settings for all of my devices. Unfortunately, I still got the error. I tried a few solutions, like checking some ports and panels inside my case, fixing driver issues, chkdsk, sfc scans, and so on. I reassembled some cables, checked for any damage on the motherboard, and found nothing.
At one point, I should also mention that my computer refused to start. This is how the boot error began. I had to reset the system, load into the BIOS, and then reset again to get into Windows. Just recently, I tried another cold boot and this time, I didn't receive a boot failure, but the system took longer to load into Windows. I have a blue screen viewer dump file of the error that I recently got and I will now paste it:
==================================================
Dump File : 072917-4625-01.dmp
Crash Time : 7/29/2017 6:09:14 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : ffffbe07`69664028
Parameter 3 : 00000000`bf800000
Parameter 4 : 00000000`00000124
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14f960
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14f960
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\072917-4625-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 434,557
Dump File Time : 7/29/2017 6:09:39 PM
==================================================
Please, if you can help in anyway or give any advice, I'd appreciate it. Is there a way I can find out what hardware is possibly damaged?
UPDATE 7/30/17: Boot failure issue appears to have gone away, system starting up normal again (hallelujah). Still concerned about possibly damaged hardware.
Facebook
Twitter
Instagram