BSOD Crashing when running games.

[CHeinz]

So a few days ago I started experiencing random crashes when running any game on my computer. At first I thought it was isolated to one game then realized it happened every game I tried, although some lasted longer than others before crashing. Both monitors have stretched distorted visual glitches when this happens and the computer automatically restarts, and will often retain this visual glitch as it boots past the BIOS page and restart several times before it allows me to use "advanced options" to try automatic repair. As far as I'm aware it only happens during games, and I've seen many other threads with almost identical crash reports but it seems rather vague and I'm a bit of a doofus so I really need help isolating the issue and component. I've already updated all drivers, and even reinstalled Windows 10 but neither has proved effective.

Here's my WhoCrashed (there were many identical .dmps before I reinstalled Windows)

On Thu 4/19/2018 5:43:29 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041918-39734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75EAA3)
Bugcheck code: 0x124 (0x0, 0xFFFF9504607DB8F8, 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

As even a boof like me can understand this is pretty vague, I also ran it through the windows debugging tool and came back with this:

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: ffff9504607db8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.309 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9504607db8f8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 6

CPU_MHZ: dbc

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: CAMERONSGAYCOMP

ANALYSIS_SESSION_TIME: 04-19-2018 19:45:19.0775

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

STACK_TEXT:
fffffa0d`5adfe5b0 fffff802`c3649b15 : ffff9504`60837700 ffff9504`607db8d0 ffff9504`5e4d8390 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
fffffa0d`5adfeae0 fffff802`c3498708 : ffff9504`607db8d0 00000000`00001000 fffff80e`00000000 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
fffffa0d`5adfeb10 fffff802`c349922b : fffff802`c356af00 fffff802`c356af00 ffff9504`5e4d8390 fffff80e`a05a71e0 : nt!WheapProcessWorkQueueItem+0x48
fffffa0d`5adfeb50 fffff802`c324e4d5 : ffff9504`5e4d8390 ffff9504`60837700 ffff9504`00000000 00000000`00001000 : nt!WheapWorkQueueWorkerRoutine+0x2b
fffffa0d`5adfeb80 fffff802`c3329c07 : ffff9504`60837700 00000000`00000080 ffff9504`5e44b440 ffff9504`60837700 : nt!ExpWorkerThread+0xf5
fffffa0d`5adfec10 fffff802`c338fcc6 : ffffe301`8ed61180 ffff9504`60837700 fffff802`c3329bc0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffffa0d`5adfec60 00000000`00000000 : fffffa0d`5adff000 fffffa0d`5adf9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e1ca14ad460db17fee32f4b133c79439b72309bb

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

TARGET_TIME: 2018-04-19T22:43:29.000Z

OSBUILD: 16299

OSSERVICEPACK: 309

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-02-28 23:36:55

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.309

ANALYSIS_SESSION_ELAPSED_TIME: 620

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH: {6fd7875b-9a1b-9e09-d6d6-816026a875c8}

Followup: MachineOwner
---------

1: kd> !errrec ffff9504607db8f8
===============================================================================
Common Platform Error Record @ ffff9504607db8f8
-------------------------------------------------------------------------------
Record Id : 01d3d82fd3842962
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 4/19/2018 22:43:29 (UTC)
Flags : 0x00000002 PreviousError

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffff9504607db978
Section @ ffff9504607dba50
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : BUS error
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000600f20
Processor ID : 0x0000000000000000

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffff9504607db9c0
Section @ ffff9504607dbb10
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000000
CPU Id : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ ffff9504607dbb10

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffff9504607dba08
Section @ ffff9504607dbb90
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
Status : 0xf600000000070f0f
Address : 0x00000000d0001dc0
Misc. : 0x0000000000000000

Now most of this is just gibberish to me but I read somewhere that "BUSLG_GENERIC_ERR etc." is a bugcheck called by the CPU for what could be a number of reasons (memory, power, etc.) but as for what specifically is the cause I have yet to find out. Any help getting a specific diagnosis is much appreciated. Also, I don't overclock and never have, I'm current on all windows updates and everything, and as far as I'm aware, this suddenly started occurring out of the blue, crashing during games that I have been able to run no problem for years without this issue and with the exact hardware and setup I have right now. I'm not sure if this means it's more likely to be failing hardware or not, and I have yet to run Memtest (as I haven't yet taken the time to figure out how to actually run it since there's no easy .exe for a monkey like me) but will update this as soon as I run that as well. If you could explain any suggestions as to what and how to diagnose something in a rather basic way so that someone without much hardware/software experience could understand it, I would really appreciate it. Thanks!

 

[Colif]

See the answer here and follow some of the suggestions - perhaps not the win 7 troubleshooting as they are likely in different places in win 10 - https://answers.microsoft.com/en-us/windows/forum/all/bsod-wheauncorrectableerror/84a3eafc-dabf-4265-9dca-fae14d26cb38

WHEA = Windows Hardware Error Architecture

Can you copy the minidump file from C]windows\minidump to desktop or docuements folder
Upload the copy from new location toa file sharing web site and share a link here

You can make a USB using memtest and then you boot PC from it. Not often WHEA errors caused by RAM.

 

[CHeinz]

See the answer here and follow some of the suggestions - perhaps not the win 7 troubleshooting as they are likely in different places in win 10 - https://answers.microsoft.com/en-us/windows/forum/all/bsod-wheauncorrectableerror/84a3eafc-dabf-4265-9dca-fae14d26cb38

WHEA = Windows Hardware Error Architecture

Can you copy the minidump file from C]windows\minidump to desktop or docuements folder
Upload the copy from new location toa file sharing web site and share a link here

You can make a USB using memtest and then you boot PC from it. Not often WHEA errors caused by RAM.

Here's a OneDrive link for the .dmp https://1drv.ms/u/s!Ap0RPaQD6QdMaTwjWCzvEBpXT-s
As for that page, I've yet to update the BIOS and chipset drivers as I have to make sure I really know what I'm doing first but will do so as soon as I have the time. Same goes for memtest but I have run the "sfc /scannow" command in the command prompt and it didn't find any errors or missing files. I'll update once I try updating BIOS and chipset drivers as well, thanks for the suggestion.

 

[gardenman]

Hi, you uploaded a shortcut to the file instead of the actual file. To upload the file, open the minidump folder by pressing Win+R to open the Run dialog and type in:
C:\Windows\minidump
Then press OK. The minidump folder should open. Copy the minidump file to your desktop or documents folder and upload it. If you have more than one file, upload the latest 5 or 10 of them. Feel free to compress them into a ZIP file if you want.

 

[Colif]

what motherboard do you have? I can find instructions for flashing bios once I know what you have.

WHEA errors are hardware, sometimes they are drivers as well. SFC just checks files, its not going to fix a WHEA error.

 

[CHeinz]

Hi, you uploaded a shortcut to the file instead of the actual file. To upload the file, open the minidump folder by pressing Win+R to open the Run dialog and type in:
C:\Windows\minidump
Then press OK. The minidump folder should open. Copy the minidump file to your desktop or documents folder and upload it. If you have more than one file, upload the latest 5 or 10 of them. Feel free to compress them into a ZIP file if you want.

That's a big WHOOPS. This should be the file itself here: https://1drv.ms/u/s!Ap0RPaQD6QdMaje1hRz2Fi7qTWo

 

[CHeinz]

what motherboard do you have? I can find instructions for flashing bios once I know what you have.

WHEA errors are hardware, sometimes they are drivers as well. SFC just checks files, its not going to fix a WHEA error.

Oops forgot to include system specs in the initial post.
Motherboard: ASUS M5A78L-M (cheapest board I could find to support AM3+ Processor)
CPU: AMD FX(tm)-6300 Six-Core Processor
GPU: AMD Radeon R9 200 / HD 7900 Series
If there's any other relevant specs that would help let me know, I don't remember off the top of my head my PSU's wattage but I remember it's always been sufficient for probably over 2 years now, gotta get to work but if needed I can open up the case and find out a bit later, as far as I'm aware there's no way to find out through computer's command prompt or any stock functions.
I know I have updated my BIOS once before when I basically rebuilt my whole pc but it was kinda hard to navigate to where I needed to be on their site, my system information says "BIOS Version/Date American Megatrends Inc. 2101, 12/2/2014" I think I flashed it in 2016 though but after the basics of what everything does I start to get a bit lost anyways. I really appreciate the assistance thus far in this!

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/rMRK.html

File: 041718-53671-01.dmp (Apr 17 2018 - 20:11:50)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 08 Sec(s)

Motherboard as you stated: https://www.asus.com/us/Motherboards/M5A78LMUSB3/
The BIOS information was not included in the dump file. This can sometimes mean an older or outdated BIOS is being used. If you decide to try to update your BIOS, read all precautions beforehand and don't do it if you have recently been experiencing power outages.

I can't help you with this. Wait for additional replies. Good luck.

 

[CHeinz]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/rMRK.html

File: 041718-53671-01.dmp (Apr 17 2018 - 20:11:50)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 08 Sec(s)

Motherboard as you stated: https://www.asus.com/us/Motherboards/M5A78LMUSB3/
The BIOS information was not included in the dump file. This can sometimes mean an older or outdated BIOS is being used. If you decide to try to update your BIOS, read all precautions beforehand and don't do it if you have recently been experiencing power outages.

I can't help you with this. Wait for additional replies. Good luck.

I appreciate all the help and effort, thanks a bunch!

 

[Colif]

PC was up for 10 seconds before it crashed, it only had time to load 1 driver - Tpkd.sys which is InterLok driver or PACE Anti-Piracy driver - might be tied into a USB dongle?

It is associated with the PACE Ilok protection system and crashes when I load a specific music plugin that has its license on a USB Ilok dongle.

BIOS Update: Unusual, almost every other Asus motherboard manual launches on their site. this is a download, and it scrolls pages sideways... not really related but odd

Go here and download manual unless you know where it is: https://www.asus.com/au/Motherboards/M5A78LMUSB3/HelpDesk_Manual/
It explains how to update the bios on page 2-2

Most Asus motherboards use same tool - EZ Update 2

Newest bios is number 2101, you may need to download speccy to find out your motherboard bios version now - though it should show in top right corner of bios screen

 

[CHeinz]

PC was up for 10 seconds before it crashed, it only had time to load 1 driver - Tpkd.sys which is InterLok driver or PACE Anti-Piracy driver - might be tied into a USB dongle?

It is associated with the PACE Ilok protection system and crashes when I load a specific music plugin that has its license on a USB Ilok dongle.

BIOS Update: Unusual, almost every other Asus motherboard manual launches on their site. this is a download, and it scrolls pages sideways... not really related but odd

Go here and download manual unless you know where it is: https://www.asus.com/au/Motherboards/M5A78LMUSB3/HelpDesk_Manual/
It explains how to update the bios on page 2-2

Most Asus motherboards use same tool - EZ Update 2

Newest bios is number 2101, you may need to download speccy to find out your motherboard bios version now - though it should show in top right corner of bios screen

Yeah that specific crash was unusual, as it normally only crashes after launching a game or some executable that's a bit more intensive than simply a web browser, that driver is related to Pro Tools software and it's a USB key that I always have plugged in to allow me to run Pro Tools. My BIOS Version in System information says 2101 which should be the newest version of that, then.

Is there any chance that the Anti-Piracy driver and the iLok USB key could be causing the issue? I can't imagine why it would just suddenly start causing these kinds of crashes and the crash reports still say probable cause is "AMD authentic" which I would think would mean something is happening with either my processor or graphics card at some point in the process, and speccy doesn't show my cpu as overheating or anything when I monitor heat.

Any other way to diagnose whether it's failing hardware or a problematic driver?

 

[Colif]

There are those that can get more info out of dumps than I can, but they don't post on a regular basis here so I try to do best I can. You can read the top of this page and post on here, and ask them as well, if you want to - https://www.tenforums.com/bsod-crashes-debugging/ - they have more regular people there who might get to answer faster than I will.

It says AutheticAMD as that is the processor, WHEA errors are called by the CPU but not necessarily caused by it, they can be any hardware and its possible the USB dongles drivers caused the error. Or the USB dongle itself. The only software that can normally cause a WHEA error is overclocking software

I can't see it so I assume motherboard doesn't have AI Suite running, its one bit of Asus software that can cause WHEA errors as it includes overclocking drivers.

 

[CHeinz]

There are those that can get more info out of dumps than I can, but they don't post on a regular basis here so I try to do best I can. You can read the top of this page and post on here, and ask them as well, if you want to - https://www.tenforums.com/bsod-crashes-debugging/ - they have more regular people there who might get to answer faster than I will.

It says AutheticAMD as that is the processor, WHEA errors are called by the CPU but not necessarily caused by it, they can be any hardware and its possible the USB dongles drivers caused the error. Or the USB dongle itself. The only software that can normally cause a WHEA error is overclocking software

I can't see it so I assume motherboard doesn't have AI Suite running, its one bit of Asus software that can cause WHEA errors as it includes overclocking drivers.

Awesome, I started a thread there as well, thanks for the tip! I appreciate all your help. As for the motherboard, as far as I'm aware it does not and has not ever had AI Suite running, and I have zero experience with overclocking and have never gone anywhere near it. In the meantime I'm going to experiment with the USB dongle and see if it has any apparent relation to the crashing.

 

[CHeinz]

Just figured I may as well put this here https://www.tenforums.com/bsod-crashes-debugging/108621-bsod-whea-uncorrectable-error-when-running-games-2.html#post1353373 in case anyone has the same issue, or anyone has any ideas for this ongoing process of diagnosing the issue. This is still an ongoing thing, although at this point not nearly as bad or frequent as it was, so any suggestions or ideas are still appreciated!