Windows 10: BSOD - Gaming Blizzard titles - WHEA_UNCORRECTABLE_ERROR

Hi team,

Please find attached my computers internal details and error logs, msinfo etc etc.

I've reset BIOS and upgraded all drivers, removed any clocking. Just haven't completed a fresh install which I was hoping to avoid.

I'd really appreciate any assistance here guys, these BSODs are so frequent now I can't jump in any ranked matches *Sad

Not much fun lads.

Cheers,
Kieran

:)

 

WHEA_UNCORRECTABLE_ERROR BSOD on playing games in Windows 10 PC

Original Title: WHEA_UNCORRECTABLE_ERROR

Whenever I play a game after a few minutes there is a BSOD. So far I have tried chkdsk, sfc scan, DISM, defragment, and I updated my bios and reset my bios. All of the tests I mentioned have had no errors in them.

 

Whea_uncorrectable_error only when playing games

I've been experiencing the Whea_Uncorrectable_error BSOD when playing games like CSGO or planetside 2, but not League of legends. It happened frequently when playing the mentioned games on 8.1, then when I upgraded to Win 10 it still occurred.

 

Only 1 dumpfile
Code: BugCheck 124, {0, ffffa98b1f740028, be000000, 800400} Probably caused by : GenuineIntel Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffa98b1f740028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.[/quote] WHEA error for a MCE fault
This could point to hardware problem with your CPU but more often also motherboard software and monitoring software can cause this kind of BSODs.

The driver XtuAcpiDriver Thu Feb 26 13:51:57 2015 (54EF16ED)
Driver Description: Intel extreme tuning BIOS interface driver
Driver Update Site: Drivers & Software
Update it to the latest version or remove.

Also update these older drivers
Logitech gaming software/ mouse etc.
Logitech webcamera

Intel storage driver
Intel management driver

Realtek high definition audio driver

from your supportpage of your mobo GIGABYTE - Motherboard - Socket 1150 - GA-Z97-D3H (rev. 1.2)
NB. look for the revision number of your mobo.

 

Thanks for this Lifetec, really appreciate the insight. I'll update these drivers ASAP and go from there. If it continues should i then just go buy a new cpu?

 

No, i would if it is necessary first run some CPU tests and upload the dumpfiles again.

 

Alrighty,

Any tips on what CPU tests to run mate?

I've conducted the 2 odd hours worth of memtest86+ through UEFI format in my BIOS. Updated all the relevant drivers, and now I'm getting some odd diagonal lines that are barely visible running across the entire screen.

Might be GPU playing up potentially? I'll stop guessing and let you help me I think.

Appreciate the assist so far mate.

 

CPU Stress Tests:

Intel Processor Diagnostic Tool (works in Windows)
Only need to run 1 or 2 of the tests under most circumstances.
Download Intel(R) Processor Diagnostic Tool

Prime95 Stress test your cpu
See this tutorial Prime95 - Stress Test Your CPU

Videotest Furmark
To test your GPU you can use Furmark see this tutorial FurMark - GPU Stress Test

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test (Looks like it's "BURN-IN test" now)
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 100ºC, quit the test - the video card is overheating.
- Click "Quit" to exit

What you are looking for:
- excessive heat from the GPU (report back with anything over 90ºC)
- problems with the video display (picture is distorted or jumbled, picture turns black, etc)
- problems reported by the program (I haven't seen this, but "just in case")

 

Alrighty then,

Fresh install of Windows, updated all core drivers, ran our little friend there FurMark and lo and behold at approximately 76 degrees we got the bsod.

Looks like it's the GPU from the looks of things. It's a Windforce GTX 970 Gigabyte G1 Gaming.

Attached a new log file just in case/to review. If it's the GPU i'll just go buy a new one *Smile

 

The dumpfile is again
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, ffffdd8065518028, bf800000, 124} Probably caused by : GenuineIntel Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffdd8065518028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre STACK_TEXT: ffff8000`c87e06f8 fffff803`82a5b20f : 00000000`00000124 00000000`00000000 ffffdd80`65518028 00000000`bf800000 : nt!KeBugCheckEx ffff8000`c87e0700 fffff803`8242f358 : ffffdd80`65518028 ffffdd80`64ef2290 ffffdd80`64ef2290 ffffdd80`64ef2290 : hal!HalBugCheckSystem+0xcf ffff8000`c87e0740 fffff803`82a5b6fc : 00000000`00000728 00000000`00000005 ffff8000`c87e0b30 00000000`00000000 : nt!WheaReportHwError+0x258 ffff8000`c87e07a0 fffff803`82a5ba54 : ffffdd80`00000010 ffffdd80`64ef2290 ffff8000`c87e0948 ffffdd80`64ef2290 : hal!HalpMcaReportError+0x50 ffff8000`c87e08f0 fffff803`82a5b93e : ffffdd80`64ef1eb0 00000000`00000001 00000000`00000005 00000000`00000000 : hal!HalpMceHandlerCore+0xe8 ffff8000`c87e0940 fffff803`82a5bb7e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda ffff8000`c87e0980 fffff803`82a5bd00 : ffffdd80`64ef1eb0 ffff8000`c87e0bb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce ffff8000`c87e09b0 fffff803`82358efb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 ffff8000`c87e09e0 fffff803`82358c84 : 00000000`00000000 fffff803`82358c03 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b ffff8000`c87e0b20 fffff807`9d1d1348 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x184 ffff8000`c8926858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7} Followup: MachineOwner ---------[/quote] In the dump/stacktext many references to HAL= hardware but also the mentioning of intelppm and 0x124_GenuineIntel_PROCESSOR_CACHE. So it also could be your CPU that is faulty.
I would also run the CPU tests before i would be a new GPUcard.
Have you the possibility to use a other GPUcard (spare/borrow) tot test your system.

 

I will grab another GPU and test it out yeah, I have an old Radeon junker laying around somewhere.

So essentially we are looking at either a new CPU or GPU respectively yeah?

In the process of running the CPU tests now as well.

 

Ok so I ran the Intel Processor Diag tool, no fails, all passed...
Ran the Prime 95 Stress test and copped the bsod.

So Bsod during the FurMark, and again during prime95.

I'll run prime again just to be sure and report back with logs.

 

Update : Using Speedfan I could see that there is a temp 2 that is sitting at consistently 127C.

Attachment 116038
Googling some more some people claim it could be the Northbridge temp? Do you think this has a part to play in these bsods?

Quite interesting...

 

This is a known bug/anomoly in speedfan.

from the faq from speedfan

See this What is Temp 2 in Speed-fan? (127 C) - Air Cooling - Linus Tech Tips

My temperature of aux are always around 116C.

 

Alrighty, So I just now have to try the different GPU. Gotta get the time. Thanks for your help so far mate, Ill be back in a few days to sort through next steps!