- Mar 12, 2021
- 9
- 0
- 510
Hello,
How have you been?
I'm currently having a problem with my computer and I have nowhere else to go now, as I've ran out of solutions.
I've been getting this BSOD for some months now, since August last year or something. I tried to updated all the drivers, the BIOS and everything, deactivated the XMP memory overclocking profile from 3600mhz to 2133mhz (even tho the memory is supposed to run at 3600mhz), did a DDU refresh. I basically did all I could think of in terms of software.
I also tested the memory sticks one by one, and their slots, tested both SSDs, no errors whatsoever. However, the BSOD persisted.
I decided to format Windows entirely in January and things got running smooth again for about 1 month, until it started giving BSOD once again. I'm an IT graduate, so im not entirely a newbie in the field, but im focusing my studies more on visual art and animation, so I'm not the ultimate expert either.
Coincidently, the BSOD reappeared by the time I installed once again the Norton 360 package (paid license), but i cannot guarantee this is caused by Norton, as i've had it in the past on this same computer for months and it didnt give me a single problem.
I've always had problems with my GPU drivers, because being a fresh AMD product, their drivers came with problems, and along came BSODs such as TDR, etc. But as drivers got updated, these errors disappeared and only one came up, a new one, the WHEA Uncorrectable Error. This BSOD is totally random, it doesn't matter whether I'm coding on Visual Studio, or browsing the web on Chrome, and even when the computer goes idle and the monitor switches off, the BSOD can happen. It doesn't matter if the computer is on load or on idle, so it's not temperatures. Most of the times, when this BSOD occurs and the computer restarts, when I get to Windows logon, the CPU fan stops, and I can only get it spinning again by shutting down and starting Windows again. It's a Noctua NF-A12x25 fan with a Big Scythe Shuriken 3 cooler.
One thing I also noticed was that once the BSOD happens, it restarts the computer immediately. So i'm not sure if the minidump ever gets fully created because I don't see the 0% get to the 100%. Not sure if its due to my M2 SSD being fast or not. Also, the BSOD is becoming more and more frequent each time it happens.
MB: AORUS X570 Pro Wifi Mini ITX
BIOS: F6b
CPU: AMD Ryzen 7 3700X
RAM: 2x16GB G.SKILL Trident Z DDR4 3600Mhz CL17 (F4-3600C17D-32GTZKW)
GPU: Sapphire Pulse RX 5700XT 8GB
Current GPU Drivers: 20.12.1
PSU: Seasonic Focus 550W Gold
I ran the only .dmp file on WinDbg and managed to get this:
Loading Dump File [D:\Users\jppbs\Desktop\030921-9203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump does not have process information
Symbol search path is: srv*
Executable search path is:
Unable to load image Unknown_Module_00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802
Debug session time: Tue Mar 9 10:17:17.379 2021 (UTC + 0:00)
System Uptime: 0 days 0:50:25.996
Unable to load image Unknown_Module_00000000
Unable to add module at 00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
For analysis of this file, run !analyze -v
0: kd> !analyze -v
***
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: 0000000000000010, Error Source Type
Arg2: ffffda8bdf70b028
Arg3: ffffda8bc59f292c
Arg4: ffffda8bc871a1a0
Debugging Details:
------------------
* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 0
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on S2K
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 0
Key : Analysis.Memory.CommitPeak.Mb
Value: 42
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 124
BUGCHECK_P1: 10
BUGCHECK_P2: ffffda8bdf70b028
BUGCHECK_P3: ffffda8bc59f292c
BUGCHECK_P4: ffffda8bc871a1a0
CUSTOMER_CRASH_COUNT: 1
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x124_AuthenticAMD
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {12a698bc-58f9-85fa-efc6-5c42d213b271}
Followup: MachineOwner
---------
It's seems to be something AMD related, but I'm not sure what, as the minidump doesn't seem to be so precise. The only AMD stuff I have is the Ryzen 7 3700X CPU and the Sapphire 5700XT.
Any chance to know whether this is an hardware failing (in which case im still in time to activate the warranty) or a software/missing update? I have the F6b BIOS version. I noticed there are a few more updates now, but it's mainly AMD 5000 series now, should i update?
PS: As i was writting this post, my system crashed again, 30 minutes into usage.
After restarting, I had this notification in the AMD Radeon Software: View: https://imgur.com/a/EFxQDSE
There's no new minidump for this crash, so I don't how we'll trace this back. The BSOD happens, and it won't let the percentage complete, it restarts the computer on 0% almost instantly.
Event Viewer events from today:
There's plenty of errors of the same kind: SppExtComObj.exe, but it only comes up on windows start. BSODs happen much later.
There's no real traces of this BSOD right before it happens. It simply happens. Then I get the error "Dump file creation failed due to error during dump creation." There's also a HAL information notice "The iommu fault reporting has been initialized."
Eitherway, I uploaded an events file on both txt and evtx format with the meta data folder, which you can download and view over here: https://drive.google.com/drive/folders/1bAYjEODW133UnJXxgBbFuPbcoNhypIi1?usp=sharing
Hope someone of you can help me figure out what's going on with this. Specially @Colif or @gardenman as I've seen you guys responding to these WHEA errors quite often and often you seem to get to the source.
I have no worries about replacing hardware since it's on warranty, but I want to be sure it's the hardware first, because I need the computer for work and it will take a couple of weeks to get it back together.
Best Regards,
Diablosrouge
How have you been?
I'm currently having a problem with my computer and I have nowhere else to go now, as I've ran out of solutions.
I've been getting this BSOD for some months now, since August last year or something. I tried to updated all the drivers, the BIOS and everything, deactivated the XMP memory overclocking profile from 3600mhz to 2133mhz (even tho the memory is supposed to run at 3600mhz), did a DDU refresh. I basically did all I could think of in terms of software.
I also tested the memory sticks one by one, and their slots, tested both SSDs, no errors whatsoever. However, the BSOD persisted.
I decided to format Windows entirely in January and things got running smooth again for about 1 month, until it started giving BSOD once again. I'm an IT graduate, so im not entirely a newbie in the field, but im focusing my studies more on visual art and animation, so I'm not the ultimate expert either.
Coincidently, the BSOD reappeared by the time I installed once again the Norton 360 package (paid license), but i cannot guarantee this is caused by Norton, as i've had it in the past on this same computer for months and it didnt give me a single problem.
I've always had problems with my GPU drivers, because being a fresh AMD product, their drivers came with problems, and along came BSODs such as TDR, etc. But as drivers got updated, these errors disappeared and only one came up, a new one, the WHEA Uncorrectable Error. This BSOD is totally random, it doesn't matter whether I'm coding on Visual Studio, or browsing the web on Chrome, and even when the computer goes idle and the monitor switches off, the BSOD can happen. It doesn't matter if the computer is on load or on idle, so it's not temperatures. Most of the times, when this BSOD occurs and the computer restarts, when I get to Windows logon, the CPU fan stops, and I can only get it spinning again by shutting down and starting Windows again. It's a Noctua NF-A12x25 fan with a Big Scythe Shuriken 3 cooler.
One thing I also noticed was that once the BSOD happens, it restarts the computer immediately. So i'm not sure if the minidump ever gets fully created because I don't see the 0% get to the 100%. Not sure if its due to my M2 SSD being fast or not. Also, the BSOD is becoming more and more frequent each time it happens.
MB: AORUS X570 Pro Wifi Mini ITX
BIOS: F6b
CPU: AMD Ryzen 7 3700X
RAM: 2x16GB G.SKILL Trident Z DDR4 3600Mhz CL17 (F4-3600C17D-32GTZKW)
GPU: Sapphire Pulse RX 5700XT 8GB
Current GPU Drivers: 20.12.1
PSU: Seasonic Focus 550W Gold
I ran the only .dmp file on WinDbg and managed to get this:
Loading Dump File [D:\Users\jppbs\Desktop\030921-9203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump does not have process information
Symbol search path is: srv*
Executable search path is:
Unable to load image Unknown_Module_00000000
00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000
00000000
Unable to add module at 0000000000000000WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802
71a00000 PsLoadedModuleList = 0xfffff8027262a510Debug session time: Tue Mar 9 10:17:17.379 2021 (UTC + 0:00)
System Uptime: 0 days 0:50:25.996
Unable to load image Unknown_Module_00000000
00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000Unable to add module at 00000000
00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
00000000
Unable to add module at 0000000000000000Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
For analysis of this file, run !analyze -v
0: 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: 0000000000000010, Error Source Type
Arg2: ffffda8bdf70b028
Arg3: ffffda8bc59f292c
Arg4: ffffda8bc871a1a0
Debugging Details:
------------------
* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 0
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on S2K
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 0
Key : Analysis.Memory.CommitPeak.Mb
Value: 42
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 124
BUGCHECK_P1: 10
BUGCHECK_P2: ffffda8bdf70b028
BUGCHECK_P3: ffffda8bc59f292c
BUGCHECK_P4: ffffda8bc871a1a0
CUSTOMER_CRASH_COUNT: 1
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x124_AuthenticAMD
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {12a698bc-58f9-85fa-efc6-5c42d213b271}
Followup: MachineOwner
---------
It's seems to be something AMD related, but I'm not sure what, as the minidump doesn't seem to be so precise. The only AMD stuff I have is the Ryzen 7 3700X CPU and the Sapphire 5700XT.
Any chance to know whether this is an hardware failing (in which case im still in time to activate the warranty) or a software/missing update? I have the F6b BIOS version. I noticed there are a few more updates now, but it's mainly AMD 5000 series now, should i update?
PS: As i was writting this post, my system crashed again, 30 minutes into usage.
After restarting, I had this notification in the AMD Radeon Software: View: https://imgur.com/a/EFxQDSE
There's no new minidump for this crash, so I don't how we'll trace this back. The BSOD happens, and it won't let the percentage complete, it restarts the computer on 0% almost instantly.
Event Viewer events from today:
There's plenty of errors of the same kind: SppExtComObj.exe, but it only comes up on windows start. BSODs happen much later.
There's no real traces of this BSOD right before it happens. It simply happens. Then I get the error "Dump file creation failed due to error during dump creation." There's also a HAL information notice "The iommu fault reporting has been initialized."
Eitherway, I uploaded an events file on both txt and evtx format with the meta data folder, which you can download and view over here: https://drive.google.com/drive/folders/1bAYjEODW133UnJXxgBbFuPbcoNhypIi1?usp=sharing
Hope someone of you can help me figure out what's going on with this. Specially @Colif or @gardenman
as I've seen you guys responding to these WHEA errors quite often and often you seem to get to the source.I have no worries about replacing hardware since it's on warranty, but I want to be sure it's the hardware first, because I need the computer for work and it will take a couple of weeks to get it back together.
Best Regards,
Diablosrouge
Last edited:
Facebook
Twitter
Instagram