I7-4790K OC provides help and stabilization. I'll be your best friend.
I7-4790K OC provides help and stabilization. I'll be your best friend.
I'm having some problems with my setup.
I stupidly without thinking upgraded my Bios and I lost all my OC settings.
Now my computer is giving me: Whea errors and Clock Watchdog Timeout.
Specs:
i7-4790k 4.0 ghz, was running at 4.30 no problem until now.
Gigabyte- Z97 - HD3 / REV: 2.0 BIOS: Latest
16 gigs of ram: Corsair Vengeance Pro. Running at 24000
EVGA GTX 1070 SC
EVGA - 850 Watt Gold Power Supply( Less then three weeks old, bought it because I thought my power was sagging. )
Windows 7 Ultimate.
...........................
I just want to figure out if there is actually something wrong: Aka Proc fried or Mobo is going out. Or if it's just settings.
.................
Minidumps:
On Fri 10/20/2017 10:27:00 AM your computer crashed
crash dump file: C:\Windows\Minidump\102017-26395-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800E87E028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 10/20/2017 3:00:49 AM your computer crashed
crash dump file: C:\Windows\Minidump\102017-9625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4AD01C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800E73D038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10/20/2017 2:09:15 AM your computer crashed
crash dump file: C:\Windows\Minidump\102017-23743-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002D65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10/20/2017 1:25:12 AM your computer crashed
crash dump file: C:\Windows\Minidump\102017-27066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10/20/2017 12:17:25 AM your computer crashed
crash dump file: C:\Windows\Minidump\102017-26270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
...................
Can't be thermal, even under load the processor doesn't go about 69c.
GPU stays around 50/70c
Running water cooled and average system temperature is 39c.
I've also cleaned and replaced the thermal paste.
It won't crash on me during everyday use. It'll stay stable the entire time.
But during games: Wildlands/Tarkov/PUbG it will lock up.
It ALWAYS locks up on Wildlands but it's so random, can play for hours or it can happen every few minutes.
I had previously put in 170 hours into Wildlands with no problems.
Please help.
Setting Pictures located on Google Drive, Public Access:
https://drive.google.com/drive/folders/0...sp=sharing
Did you adjust your vcore voltage during the OC? Yes, I did. I believe I've finally fixed that section. Spent a lot of time reviewing it recently.
However, I'm still experiencing random BSODs for Whea.
I've uploaded the complete file to Google Drive:
Driver Lists
Updates Installed
BSOD
Minidumps.
..........................
Latest one
A fatal hardware error occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 0
The details of this entry provide more information.
try memtest86, full loop
You got it. I'll update you tomorrow morning about the outcome and any issues found. Earlier, it wasn't the fastest test.
my 4670k requires higher ring voltage and increased vcore for effective overclocking.
Ensure your BIOS is current and reach out to Gigabyte support for assistance.