Need help troubleshooting

[Morgoth97]

Hey, forum,

I've been having an issue with the PC I built (check signature for specification). I've been running this PC for a month now but I can't recall when the crashes began but they always exclusively happen when I'm running games.

The system would freeze and then reboot. Both CPU and GPU temperatures seem to be normal before and after the reboot; the CPU temperatures read 45 °C and the GPU temperatures read about 65 °C.

I have considered that perhaps my overclock was unstable but the system passed an Aida 64 test for 6 hours, a Prime95 test (Ver 26.6) for 3 hours (hovering 90 °C but didn't crash).

I've also considered perhaps my RAM was flawed so I re-seated the RAM and ran Memtest 86+ and the RAM passed.

 

TL;DR

System is freezing during games and restarting.

Things I tried:

- Updating motherboard's BIOS.

- Running Default settings (no overclock)

- Re seating the RAM.

- Re seating the GPU.

 

I would really appreciate your input on this.

Thanks in advanced,

Morgoth97

 

 

 

[just_dave]

What is the "38%" overclock?

Some sorta auto-oc feature?

[Morgoth97]

7 minutes ago, dave_k said:

What is the "38%" overclock?

Some sorta auto-oc feature?

I meant I'm running a 38% overclock as in my multiplier was increased by a factor of 1.38 compared to stock multiplier (36) so basically 50.

I'm running at 1.36 v.

[just_dave]

Just now, Morgoth97 said:

I meant I'm running a 38% overclock as in my multiplier was increased by a factor of 1.38.

I'm running at 1.36 v.

Isnt that too high voltage for Skylake-X?

Who understands X299 chips, @done12many2 maybe or someone different?

[Mira Yurizaki]

If it reboots automatically, did you check your system logs for Bug Checks?

[Morgoth97]

1 minute ago, dave_k said:

Isnt that too high voltage for Skylake-X?

Who understands X299 chips, @done12many2 maybe or someone different?

It is, I've seen people run 5.00 GHz at a lower voltage but any voltage lower then that would get me a blue screen. 

[IKnight]

Reset OC/BIOS and check if problem remains. 

 

[Morgoth97]

1 minute ago, M.Yurizaki said:

If it reboots automatically, did you check your system logs for Bug Checks?

I've found an entry in event viewer:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffa20238b2c028, 0x00000000b2000000, 0x0000000000400005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

[Morgoth97]

8 minutes ago, ImadKnight said:

Reset OC/BIOS and check if problem remains. 

 

Sorry if I didn't make it clear. I did in fact reset the CMOS and ran the CPU with the default BIOS settings. 

[Mira Yurizaki]

2 minutes ago, Morgoth97 said:

I've found an entry in event viewer:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffa20238b2c028, 0x00000000b2000000, 0x0000000000400005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

The error code translates to a wonderfully generic WHEA_UNCORRECTABLE_ERROR which means either you have faulty hardware or you have faulty drivers.

 

Since you have a crash dump, run WhoCrashed and it'll figure out what might've caused it.

[Morgoth97]

6 minutes ago, M.Yurizaki said:

The error code translates to a wonderfully generic WHEA_UNCORRECTABLE_ERROR which means either you have faulty hardware or you have faulty drivers.

 

Since you have a crash dump, run WhoCrashed and it'll figure out what might've caused it.

There's multiple entries all stating "WHEA_UNCORRECTABLE_ERROR" and are all caused by driver "hal.dll".

Thanks by the way, I really appreciate your input.

[Mira Yurizaki]

5 minutes ago, Morgoth97 said:

There's multiple entries all stating "WHEA_UNCORRECTABLE_ERROR" and are all caused by driver "hal.dll".

Thanks by the way, I really appreciate your input.

See if what's in this post is helpful: https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

Some other places I looked at suggest opening Command Prompt as an admin and running the two:

• sfc.exe /scannow
• dism.exe /online /cleanup-image /restorehealth

To catch if your Windows install ran into corruption issues. And the usual "check for malware" and updating your drivers.

[Morgoth97]

21 minutes ago, M.Yurizaki said:

See if what's in this post is helpful: https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

Some other places I looked at suggest opening Command Prompt as an admin and running the two:

• sfc.exe /scannow
• dism.exe /online /cleanup-image /restorehealth

To catch if your Windows install ran into corruption issues. And the usual "check for malware" and updating your drivers.

 

Thanks, I'll look into it.

[Morgoth97]

52 minutes ago, M.Yurizaki said:

See if what's in this post is helpful: https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

Some other places I looked at suggest opening Command Prompt as an admin and running the two:

• sfc.exe /scannow
• dism.exe /online /cleanup-image /restorehealth

To catch if your Windows install ran into corruption issues. And the usual "check for malware" and updating your drivers.

Update:

The article helped a bunch. I'm running a Gigabyte motherboard so I figured to install gigabyte's App center as I found @BIOS very useful for safely flashing the motherboard but according to the article most of the Gigabyte Apps are the root cause  of the issue so I'll be uninstalling all of them save Gigabyte Fusion.