I am currently getting multiple BSODs while playing games, or watching videos on youtube. I see a common problem is the ntoskrnl.exe image not loading properly. If I upload a couple of these dumps, can someone help me pinpoint my issue? Thanks, Mitch
📎 AI Summary:
The thread discusses ongoing BSOD issues, primarily caused by hardware errors related to the AMD processor, with suggestions pointing to overheating, insufficient power supply, or outdated BIOS. The original poster considers that a low-power PSU might be the culprit, given their system specs, and plans to update the BIOS and monitor temperatures. Overall, the contributors recommend checking hardware stability, updating BIOS, ensuring adequate cooling and power, and analyzing dump files for further diagnosis.
The thread discusses ongoing BSOD issues, primarily caused by hardware errors related to the AMD processor, with suggestions pointing to overheating, insufficient power supply, or outdated BIOS. The original poster considers that a low-power PSU might be the culprit, given their system specs, and plans to update the BIOS and monitor temperatures. Overall, the contributors recommend checking hardware stability, updating BIOS, ensuring adequate cooling and power, and analyzing dump files for further diagnosis.
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800e26d028, b0800000, 40151}
Probably caused by : AuthenticAMD
Followup: MachineOwner
---------
Bugcheck 124 is related to a hardware error usually associated with the processor. There are different types of Bugcheck 124 and checking the dump file...
- Joined
- Aug 3, 2010
- Messages
- 1,283
It would appear to point at a processor issue, I would try re-seating your processor and/or memory.
Details below:
6: 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: fffffa800e26d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
SYSTEM_SKU: SKU
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_DATE: 01/06/2014
BASEBOARD_PRODUCT: M5A97 R2.0
BASEBOARD_VERSION: Rev 1.xx
BUGCHECK_P1: 0
BUGCHECK_P2: fffffa800e26d028
BUGCHECK_P3: b0800000
BUGCHECK_P4: 40151
BUGCHECK_STR: 0x124_AuthenticAMD
CPU_COUNT: 8
CPU_MHZ: 10ee
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 2
CPU_STEPPING: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Darksiders2.ex
CURRENT_IRQL: f
ANALYSIS_VERSION: 10.0.10166.9 amd64fre
STACK_TEXT:
fffff880`01feeb88 fffff800`01e21a3b : 00000000`00000124 00000000`00000000 fffffa80`0e26d028 00000000`b0800000 : nt!KeBugCheckEx
fffff880`01feeb90 fffff800`01fe44b3 : 00000000`00000001 fffffa80`0d71f8f0 00000000`00000000 fffffa80`0d71f940 : hal!HalBugCheckSystem+0x1e3
fffff880`01feebd0 fffff800`01e21700 : 00000000`00000728 fffffa80`0d71f8f0 fffff880`01feef30 00000000`00288300 : nt!WheaReportHwError+0x263
fffff880`01feec30 fffff800`01e21052 : fffffa80`0d71f8f0 fffff880`01feef30 fffffa80`0d71f8f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`01feed80 fffff800`01e14e8f : 00000000`00280000 00000000`00000001 fffff880`01feefb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`01feedc0 fffff800`01ecd76c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`01feedf0 fffff800`01ecd5d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`01feef30 00000000`777fe28a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`04bbed2c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777fe28a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
PRIMARY_PROBLEM_CLASS: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_authenticamd_processor_cache
FAILURE_ID_HASH: {8bb1abe1-5cc5-4642-921b-5e3d4790100e}
Followup: MachineOwner
---------
Details below:
6: 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: fffffa800e26d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
SYSTEM_SKU: SKU
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_DATE: 01/06/2014
BASEBOARD_PRODUCT: M5A97 R2.0
BASEBOARD_VERSION: Rev 1.xx
BUGCHECK_P1: 0
BUGCHECK_P2: fffffa800e26d028
BUGCHECK_P3: b0800000
BUGCHECK_P4: 40151
BUGCHECK_STR: 0x124_AuthenticAMD
CPU_COUNT: 8
CPU_MHZ: 10ee
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 2
CPU_STEPPING: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Darksiders2.ex
CURRENT_IRQL: f
ANALYSIS_VERSION: 10.0.10166.9 amd64fre
STACK_TEXT:
fffff880`01feeb88 fffff800`01e21a3b : 00000000`00000124 00000000`00000000 fffffa80`0e26d028 00000000`b0800000 : nt!KeBugCheckEx
fffff880`01feeb90 fffff800`01fe44b3 : 00000000`00000001 fffffa80`0d71f8f0 00000000`00000000 fffffa80`0d71f940 : hal!HalBugCheckSystem+0x1e3
fffff880`01feebd0 fffff800`01e21700 : 00000000`00000728 fffffa80`0d71f8f0 fffff880`01feef30 00000000`00288300 : nt!WheaReportHwError+0x263
fffff880`01feec30 fffff800`01e21052 : fffffa80`0d71f8f0 fffff880`01feef30 fffffa80`0d71f8f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`01feed80 fffff800`01e14e8f : 00000000`00280000 00000000`00000001 fffff880`01feefb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`01feedc0 fffff800`01ecd76c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`01feedf0 fffff800`01ecd5d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`01feef30 00000000`777fe28a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`04bbed2c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777fe28a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
PRIMARY_PROBLEM_CLASS: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_authenticamd_processor_cache
FAILURE_ID_HASH: {8bb1abe1-5cc5-4642-921b-5e3d4790100e}
Followup: MachineOwner
---------
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,163
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800e26d028, b0800000, 40151}
Probably caused by : AuthenticAMD
Followup: MachineOwner
---------
Bugcheck 124 is related to a hardware error usually associated with the processor. There are different types of Bugcheck 124 and checking the dump file further I see that it was a machine check exception.
https://en.wikipedia.org/wiki/Machine-check_exceptionNormal causes for MCE errors include overheating and/or incorrect hardware installation. Specific manually-induced causes include:
Computer software can also cause MCE errors (normally by corrupting data which programs read or write). For example, software performing read or write operations from or to non-existent memory regions can lead to confusion for the processor and/or the system bus.[citation needed] Accessing memory marked off-limits by UEFI may cause MCE errors.[3]
- overclocking (which normally increases heat-output)
- poorly-fitted heatsink/computer fans (the same problem can happen with excessive dust in the CPU fan)
- an overloaded internal or external power-supply (fixable by upgrading)
Check your temperatures whilst gaming, alt-tab out of a game and see what the cpu is at. I used to run an FX series chip and I was surprised at the temps i got whilst gaming.
Another thing that can cause this is not enough power from the psu. Can you post the full spec of your machine including make and model of the psu, thanks.
Saying all this though I've known at least one case where this error was caused by an out of date Flash player. Please ensure your browsers and/or flash player is up to date.
Another thing which may have a bearing is Bios. I notice your Bios is slightly out of date and updates include stability upgrades:
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = M5A97 R2.0
BiosVersion = 2301
BiosReleaseDate = 01/06/2014
Latest version stands at 2601 and is for stability:
https://www.asus.com/uk/Motherboards/M5A97_R20/HelpDesk_Download/
Please ensure I have the correct page for your motherboard.
If your running with a stock cooler and temps are high you may want to consider something after market.
Please post any new dump files.
Oh and thread moved to correct section.
Ok, thanks guys. I cant see it being a CPU overheating issue, as I have the side of the case off and a floor fan blowing extra air into my case. It could be a low power PSU because I had to replace my psu last year, and I have a 400W supply on an fx8350 with a 760 gtx and a few other things plugged into usbs as well. I have the latest bios version downloaded, but I havent installed it yet. I will try these suggestions and let you know how I make out. Thanks again