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!
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!