Need help analyzing crash dump

Question

Hello everyone!

I need some help analyzing a crash dump. Through my online research, I see a couple conflicting suggestions for the same issue. Memory problem or potentially a failing CPU have been two common suggestions along with a less common failing cooling system (I do have liquid but haven't see any BSOD for failing systems in the past - it usually just shut down). It won't even boot to Windows (BSOD before I get that far) and doesn't seem to give me the option to boot to Safe Mode to do any trouble shooting that way. I would rather not replace parts frivolously if avoidable. Any help deciphering the dmp would be greatly appreciated. I currently have the drive in another machine and it runs perfectly so I have (potentially) eliminated a corrupt Windows issue. Not sure how to update (or regress) to a different graphics driver or run MemTest if I can't boot to that PC.

Dropbox link for dmp:

https://www.dropbox.com/s/b6asbpfge5uchvy/053022-20093-01.dmp?dl=0

Specs:

Manuf: Cyberpower

CPU: I9-9900k

Mem: 16GB ADATA XPG DDR4 3000 CL16-20-20

Ordered PC 10% Overclocked by manuf.

OS: Win 10

Thanks in advance for any help. Much appreciated!!

Answer 1

Hi Andrew, there is nothing significant listed on those printouts, please do run that test, when you get time to do that.

Answer 2

Thanks Dave. I'll give those a try. I'm not sure how far back that dmp file goes historically (is there a location where old dmp files are stored??), but I ran WhoCrashed when it first gave me the BSOD (I've been using a spare PC in the meantime until I had time to tackle). Below is the result. Please let me know if this changes anything or if I should run the processes above and see where that gets me.

Thanks again for the help!!

On Wed 10/6/2021 3:27:55 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: netwbw04.sys (Netwbw04+0x2E12F3)
Bugcheck code: 0x124 (0x0, 0xFFFFE0005DD46028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\drivers\netwbw04.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwbw04.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netwbw04.sys Intel Corporation WHEA_UNCORRECTABLE_ERROR

On Tue 8/31/2021 9:36:02 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\083121-17890-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF801996BBA18)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801996BBA18, 0xFFFFD001E9DDAA68, 0xFFFFD001E9DDA280)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 471.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 471.96
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 471.96 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

On Mon 8/23/2021 3:54:36 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082321-16640-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8003A8A4A18)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8003A8A4A18, 0xFFFFD001FD71EA68, 0xFFFFD001FD71E280)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 471.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 471.96
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 471.96 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

On Wed 8/11/2021 1:54:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081121-15515-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80002CC0A18)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CC0A18, 0xFFFFD000B97D0A68, 0xFFFFD000B97D0280)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 471.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 471.96
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 471.96 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

On Thu 8/5/2021 3:28:22 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\080521-14890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0xB9314448, 0xFFFFE001B9314458)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not 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.

On Sun 1/17/2021 4:55:15 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011721-14343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. An illegal page fault occurred while holding working set synchronization.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 1/17/2021 4:36:28 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011721-13906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801777537F3, 0xFFFFD000765C0910, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not 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.

On Sun 1/17/2021 4:34:20 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011721-15187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x50 (0xFFFFF80317744658, 0x0, 0xFFFFF80317E1C6C1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not 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.

On Sat 12/19/2020 1:42:39 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121920-16328-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF800EC73C2F4)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD0002516CDD8, 0xFFFFD0002516C5F0, 0xFFFFF800EC73C2F4)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

Answer 3

Hi Andrew,

I am Dave, I will help you with this.

Your minidump files just indicate memory (RAM) corruption no specific driver is listed

1

Boot your PC into BIOS on your PRIME Z390-P motherboard, if you are overclocking your processor, turn that off

If there is an XMP profile set on your RAM, disable that, set it to default

Save those settings and check if Windows will boot up

2

If not, the best option is to download the widely available free utility MemTest86 onto a USB on the other PC, then run a full 4 pass scan with that to test your RAM for physical errors