Random BSOD

[hitman052]

My laptop occasionally got into BSOD for no reason, even sometime using browsers would get into BSOD, they mostly shows CRITICAL_PROCESS_DIED, WHEA_UNCORRECTABLE_ERROR and SYSTEM_SERVICE_EXCEPTION.

I tried using sfc scan and dism fix and both doesn't solve the problem, RAM checked with windows tools and said both ram were ok, CPU checked with Intel Processor Diagnostic Tool and said it passed, chkdsk said ok too.

I can't run the BSOD Collection Application after I ran the first time, since most of the information displayed in other language that might hard for you guys to read/translate. So I decided to use another log collector and change back to English, hope it will help to identify the problem of my laptop. I added extra dmp files too, hope it can help to find what actual causing my laptop crashing. Thanks!

 

[ubuysa]

Hello and welcome to the forum!

The CRITICAL_PROCESS_DIED and WHEA_UNCORRECTABLE_ERROR bugchecks are very commonly caused by hardware, so you were wise to test your RAM and CPU. However, I think your hardware problem may lie elsewhere.

The 0x124 bugcheck has an argument 1 value of 0x10...

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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000010, Error Source Type
Arg2: ffff84876cd0b028
Arg3: ffff848756fdab2c
Arg4: ffff848756f691a0

That indicates that the error was caused by a device driver, or by the device that it manages. If we look at the call stack we can see what device this likely was...

1: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffc188`eba76ea8 fffff807`7a01753b     nt!KeBugCheckEx
01 ffffc188`eba76eb0 fffff807`7a018063     nt!WheaReportHwError+0x37b
02 ffffc188`eba76f80 fffff807`7a018185     nt!WheaHwErrorReportSubmitDeviceDriver+0xf3
03 ffffc188`eba76fb0 fffff807`7c950188     nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
04 ffffc188`eba77010 fffff807`7c9498c3     storport!StorpWheaReportError+0xb8
05 ffffc188`eba770a0 fffff807`7c92c46a     storport!StorpMarkDeviceFailed+0x3ff
06 ffffc188`eba77350 fffff807`7ca6da68     storport!StorPortNotification+0x1f37a
07 ffffc188`eba77420 fffff807`7ca6e3dd     stornvme!NVMeControllerInitPart2+0x2a8
08 ffffc188`eba77520 fffff807`7ca682fa     stornvme!NVMeControllerReset+0x145
09 ffffc188`eba77630 fffff807`7c9377fc     stornvme!NVMeHwResetBus+0x1a
0a ffffc188`eba77660 fffff807`7c9616bc     storport!RaidAdapterResetBus+0x18c
0b ffffc188`eba777c0 fffff807`7c9607aa     storport!RaidUnitHierarchicalReset+0x108
0c ffffc188`eba77880 fffff807`79c13f30     storport!RaidHierarchicalResetWorkRoutine+0x8a
0d ffffc188`eba778d0 fffff807`79c176a5     nt!IopProcessWorkItem+0x100
0e ffffc188`eba77940 fffff807`79d249f7     nt!ExpWorkerThread+0x155
0f ffffc188`eba77b30 fffff807`79e35b64     nt!PspSystemThreadStartup+0x57
10 ffffc188`eba77b80 00000000`00000000     nt!KiStartSystemThread+0x34

The storport.sys driver is the Windows high-level storage driver and stornvme.sys is the Windows NVMe SSD driver. Neither of these drivers are at fault because they are Microsoft drivers. Notice the function call stornvme!NVMeControllerReset, this is where an NVMe drive was reset because of a failure. Later on we see the storport!StorpMarkDeviceFailed function call, indicating that a storage device (an NVMe device of course) has failed. This dump then suggests a problem with one of your NVMe drives.

There are a couple of 0x3B bugchecks with an exception code of 0xC0000006 in argument 1...

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the bugcheck
Arg2: fffff804148c2e82, Address of the instruction which caused the bugcheck
Arg3: ffff930075c2cac0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

A 0xC0000006 exception code indicates that there was an I/O error during a page-in operation. Your paging file will be on the system drive typically (C:) and that's your 477GB Gigabyte NVMe SSD. This is almost certainly the drive that the 0x124 bugcheck failed on too.

There is also a 0x135 bugcheck (which is not that common) which also has a 0xC0000006 exception code in argument 1...

REGISTRY_FILTER_DRIVER_EXCEPTION (135)
This bugcheck is caused by an unhandled exception in a registry filtering driver.
This bugcheck indicates that a registry filtering driver didn't handle exception inside
its notification routine. One can identify the driver by the 3rd parameter.
Arguments:
Arg1: ffffffffc0000006, ExceptionCode
Arg2: ffff818b4bcdd9a0, Address of the context record for the exception that caused the bugcheck
Arg3: fffff8052998eab0, The driver's callback routine address
Arg4: ffffe6885edf62c0, Internal

The problem in this bugcheck was during a registry operation and the registry hives are stored on your system drive - the 477GB Gigabyte NVMe SSD.

I think there's enough detail here to suspect the Gigabyte NVMe drive as the cause of these BSODs. Unfortunately I can't read your error logs, perhaps next time you could change the system language to English before running the data collector app?

I would suggest in the first instance simply removing and re-seating that NVMe drive. I've seen many niggly problems solved by re-seating an M.2 drive. If that doesn't help then download the Gigabyte SSD Toolbox and run a full diagnostic on the drive from there.

Also, I've just realised from looking up a Gigabyte G5/ME that this is a laptop. Did it come with the additional Samsung 970 EVO SSD installed or did you add that yourself? If you added it yourslef it might be worth testing with that drive removed. Some laptops have problems running two NVMe drives.

 

[hitman052]

Wow, thank you so much for your time and effort to dig deep into my case, very professional and easy to understand!

I have actually been suspecting the C drive (Gigabyte SSD) is the cause of the BSOD, since event log shows alot of disk checking and said "healthy", I am not so sure about it until it finally showed something that could justify it.

You are right about the Samsung 970 EVO SSD, I added it by myself. Before I added that ssd, the BSOD problem exists already. I tried re-seating the Gigabyte SSD long ago. Apparently, it doesn't work.

I'm going to see what I can do with the Gigabyte SSD Toolbox first, thank again.

 

[ubuysa]

If you suspect the Gigabyte SSD drive at all be sure to regularly backup anything on there that's irreplaceable. When an SSD fails the data on it is not recoverable.