Question WHEA-18 logger event, black screen rebooting

Lichking2727

Prominent
Aug 28, 2019
9
0
520
1
Since around late September I've been encountering WHEA-logger event 18 and it's not been a daily problem but it causes my system to reboot at random times, usually when just idling/browsing online or playing games. It's a problem I'm hoping to take care of though I have run numerous troubleshooting tips without much success including FurMark, Memtest86, Prime95, Windows built in mem testing, and several others. With WhoCrashed recently I've noticed that the crashes I've had recently have all been coming back to ntoskrnl.exe. I think it could be a driver issue as when I tested the Verifier tool from windows recently it triggered the black screen/reboot event.

This is my most recent crash from WhoCrashed, the black screen rebooting also doesn't seem to save to my .dmp folder and just records itself in my LiveKernelReports.


On Sat 11/14/2020 6:03:17 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\WHEA\WHEA-20201114-1803.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x97EC16)
Bugcheck code: 0x124 (0x0, 0xFFFFCB86B7BA58C0, 0xBEA00000, 0x108)
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.

And this is the latest .dmp file

https://www.dropbox.com/s/jrl3k9nprxoyv73/110920-7171-01.dmp?dl=0


OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-QUU67B6
System Manufacturer Gigabyte Technology Co., Ltd.
System Model B450M DS3H
System Type x64-based PC
System SKU Default string
Processor AMD Ryzen 5 3600 6-Core Processor, 3593 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. F60c, 10/29/2020
SMBIOS Version 3.3
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Product B450M DS3H-CF
BaseBoard Version x.x
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume4
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.488"
User Name DESKTOP-QUU67B6\User1
Time Zone Eastern Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 10.5 GB
Total Virtual Memory 20.7 GB
Available Virtual Memory 11.6 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
 
Last edited:

Lichking2727

Prominent
Aug 28, 2019
9
0
520
1
Had another reboot just a few minutes ago. This has just driven me up the wall because this PC is relatively new and it's just made me miserable trying to solve this problem. The WhoCrashed says the same thing, ntsokrnl.exe. I thought it might be a driver issue but honestly I'm at my limit on this, I just wanted a gaming PC, not a colossal headache.
 

Colif

Win 10 Master
Moderator
I will ask a friend to check the dump file. he will post later but likely only convert file. I will need to look at results and see if anything obvious. His results may show a driver name if you lucky.

WHEA errors always come back with 3 drivers
NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause
PSHED.dll which is also a windows file associated with hardware
and HAL,dll which is the hardware abstraction layer

WHEA = Windows Hardware Error Architecture
Can be caused by over clocking so remove any you have
Can be caused by overclocking software like MSI Afterburner so remove if you have any. AMD Ryzen Master is also an option.
Can be caused by over heating so clean PC
Can be caused by any hardware which always makes it fun.
Can be caused by drivers.
Updating BIOS can fix them.

What are specs of the PC?

CPU - Ryzen 5 3600
Mobo - Gigabyte B450M DS3H
Hdd?
Ram - 16gb what maker? specs?
PSU?
Anything else?
 

gardenman

Admirable
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/r3yLksgc/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:110920-7171-01.dmp (Nov 9 2020 - 22:32:55)
Bugcheck:MANUALLY_INITIATED_CRASH1 (DEADDEAD)
Driver warnings:*** WARNING: Unable to verify timestamp for rspCrash64.sys
Probably caused by:rspCrash64.sys (Process: WhoCrashedEx.e)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 41 Sec(s)

Comment: WhoCrashed driver.

Comment: MANUALLY_INITIATED_CRASH

Did you manually initiate this crash?

Possible Motherboard page: https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-10
I am unable to tell which revision of the motherboard that you have. It appears you have the latest BIOS, version F60c.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
Resplendence Software Projects WhoCrashed Crash Dump Test Driver

I didn't know who crashed could manually initiate a crash. The dump isn't overly helpful to find an actual cause though. As it just blames whocrashed.

maybe remove it and if you crash again,
  1. go to c:/windows/minidump
  2. copy the files from here to another folder
  3. upload copies to dropbox and show link here and we look at that.
 

ASK THE COMMUNITY

TRENDING THREADS