Windows 10 BSOD: WHEA_UNCORRECTABLE_ERROR (MiniDump)

rOost · Jul 6, 2021

Hello,

I am getting a lot of WHEA_UNCORRECTABLE_ERROR's lately.
I attached the latest MiniDump file.

I think its becouse of GenuineIntel (was in the MiniDump), but i ran a full CPU check with the Intel Processor Diagnostic Tool. Ran a Memory check and hardware check but nothing was wrong. Also the tests fisnished all without a BSOD.
I also updated to the latest BIOS and updated other drivers but without any luck.

kemical · Jul 6, 2021

Hi,

the only clue I could find as to a possible issue is stornvme.sys. This is a windows driver so see if running these scans help:

File scans
Open an 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

If you recently uploaded anything new see if it's removal stops the bsod.

Ensure your running the latest chipset drivers.

Post any new bsod's

kemical · Jul 6, 2021

Hi,

the only clue I could find as to a possible issue is stornvme.sys. This is a windows driver so see if running these scans help:

File scans
Open an 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

If you recently uploaded anything new see if it's removal stops the bsod.

Ensure your running the latest chipset drivers.

Post any new bsod's

rOost · Jul 9, 2021

Hello,

Thanks for your help!

I have done the scans u asked but it does not appear anything was wrong. (See attached screenshot)
Altough before the 'sfc /scannow' command i had to do a windows update before i could run the command. Maybe that fixed it already?

I will post if i have another BSOD. (And by that i mean a new MiniDump or MEMORY.dmp becouse i don't get those all the time (BSOD stuck on 0% forever))

kemical · Jul 9, 2021

rOost said:
Hello,

Thanks for your help!

I have done the scans u asked but it does not appear anything was wrong. (See attached screenshot)
Altough before the 'sfc /scannow' command i had to do a windows update before i could run the command. Maybe that fixed it already?

I will post if i have another BSOD. (And by that i mean a new MiniDump or MEMORY.dmp becouse i don't get those all the time (BSOD stuck on 0% forever))

Hi,

just check your settings are for the small minidump:

Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

rOost · Jul 12, 2021

Hello,

I did the steps you told me to. Just had a bluescreen a minute ago but windows restarted instantly and did not get any new MiniDump files. (also no MEMORY.dmp)

The setting where i now have 'small memory dump' was 'automatic' at first.

kemical · Jul 13, 2021

Sometimes there isn't always a dump with that bugcheck.

Do you know which motherboard you have?

rOost · Jul 13, 2021

Hello,

I just had another BSOD without any MiniDump, just instantly restarted.

I attached a .txt file with the report of CPU-Z with all the information. (My laptop is the Huawei Matebook X Pro 2018 i7)

kemical · Jul 13, 2021

Hi, when you updated your drivers did you use the PC Manager? See guide:
Link Removed

Check if you need any updates.

rOost · Jul 13, 2021

No, the bluescreens appeared before i updated BIOS/chipset drivers. PC Manager did not find anything to update altough there were new bios/chipset updates available. I downloaded these through the Huawei Website. But again this was after i got all the BSOD's. The updates did not fix anything unfortunately.

I also updated windows to the latest version but no luck there.

rOost · Jul 13, 2021

rOost said:
No, the bluescreens appeared before i updated BIOS/chipset drivers. PC Manager did not find anything to update altough there were new bios/chipset updates available. I downloaded these through the Huawei Website. But again this was after i got all the BSOD's. The updates did not fix anything unfortunately.

I also updated windows to the latest version but no luck there.

I also had 2 more BSOD's today without any sort of MiniDump or MEMORY.dmp

kemical · Jul 14, 2021

Hi,
at the time bsod were you doing anything in particular or does the bsod happen anytime regardless whats running?

How old is the lappie?

This bsod can be a sign of overheating, make sure any vents are free from dust.

Try stress testing the cpu using prime95

Use HWiNFO64 to monitor temps.

rOost · Jul 14, 2021

BSOD happen regardless of what is running. My laptop is about 2 years old now.

I already opened my laptop and cleared any dust. But there was not a lot of dust. Also i am currently stress testing my CPU with prime95, have been runnig for 10 minutes now (still running at the time of typing), no bluescreen yet. Overheating is not the problem becouse if i use my GPU my laptop gets hot and i don't get bluescreens much then.
I get bluescreens a lot right after startup. I am testing a theory of it being my laptop charger or my motherboard (i had only plugged in my charger and got a BSOD at startup). Now i am letting it unplugged and see if i get any bluescreens then.

rOost · Jul 14, 2021

I was not looking and i got a BSOD again while running Prime95. I got a new MiniDump now! (I can't attach my 2.2MB file becouse "The uploaded file is too large for the server to process." so i made a wetransfer link).

071421-14281-01.dmp

kemical · Jul 14, 2021



ffffe780`a86f7388 fffff802`6cdb61fc     : 00000000`00000124 00000000`00000010 ffffd608`bbcc9028 ffffd608`ab368aac : nt!KeBugCheckEx
ffffe780`a86f7390 fffff802`6cdb6d59 : ffffd608`b43dc210 ffffd608`b43dc210 ffffd608`ab368a80 ffffd608`bb38e128 : nt!WheaReportHwError+0x3ec
ffffe780`a86f7470 fffff802`6cdb6e75     : 00000000`00000000 00000000`00000062 ffffd608`b43dc210 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffe780`a86f74a0 fffff802`700c2365     : 00000000`00000000 ffffe780`a86f76c0 ffffd608`ab3dc1a0 00000000`00000000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffe780`a86f7500 fffff802`700bb7f0     : 00000000`00000000 ffffd608`ab3dc1a0 ffffd608`ab3e51a0 ffffd608`ab4002e0 : storport!StorPortWriteRegisterUshort+0x9295
ffffe780`a86f7590 fffff802`700a1f2c     : fffff802`6d525440 00000000`00000000 00000000`00000000 00000000`00000001 : storport!StorPortWriteRegisterUshort+0x2720
ffffe780`a86f7820 fffff802`7005ca16     : ffffd608`ab321020 ffffd608`ab321020 00000000`00000000 00000000`00000000 : storport!memset+0x61ac
ffffe780`a86f78f0 fffff802`7005d1ac     : ffffd608`ab321020 ffffd608`c1000002 ffffd608`be1f8400 00000000`00000003 : stornvme!NVMeControllerInitPart2+0x226
ffffe780`a86f7970 fffff802`7005c10f     : ffffd608`ab321020 ffffd608`ab3dc050 ffffd608`be1f8430 00000000`00000000 : stornvme!NVMeControllerReset+0x124
ffffe780`a86f79a0 fffff802`700b8f41 : ffffd608`be1f8430 ffffd608`ab3dc050 00000000`00000000 fffff802`6cb415a7 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffe780`a86f79d0 fffff802`6ca748b5     : ffffd608`b7bdebb0 00000000`00000000 00000000`00000000 fffff802`83d55440 : storport!StorPortValidateRange+0x51

Hi,
thanks for the dump file.

Above you can see part of the call stack and the parts outlined point to your nvme.

How full is the drive itself?

Check the drives SMART data for healthyness: How to Check Drive Health and SMART Status in Windows 10

Something else you could try is to recreate the pagefile. This can sometimes become corrupted and this guide will help you in disabling it and to re-enable it again. Don't bother changing the size just let windows manage it automatically.
How to Disable the Pagefile in Windows 10

rOost · Jul 16, 2021

Hello,

i have a Samsung NVMe SSD so i downloaded "SAMSUNG Magician". There i could export a S.M.A.R.T csv (everything was OK btw but attached in anyways).
I also Disabled the Pagefile. After that i rebooted my laptop and Enabled the Pagefile again (to Automatic which it already was before i disabled it). And the reboots went without any errors and no BSOD yet.
Ill try a SSD performance test to check if i get a BSOD later today.

rOost · Jul 16, 2021

I just had another BSOD a minute ago. Just when i was using SSH and watching some Youtube. Don't think that could have anything to do with it but just to let u know.

071621-9031-01.dmp

kemical · Jul 17, 2021



ffffed07`f8a67388 fffff803`573b61fc     : 00000000`00000124 00000000`00000010 ffff990f`e1c56028 ffff990f`d77b4aac : nt!KeBugCheckEx
ffffed07`f8a67390 fffff803`573b6d59     : ffff990f`f63c9a90 ffff990f`f63c9a90 ffff990f`d77b4a80 ffff990f`e120f378 : nt!WheaReportHwError+0x3ec
ffffed07`f8a67470 fffff803`573b6e75     : 00000000`00000000 00000000`00000062 ffff990f`f63c9a90 00000000`00040282 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffed07`f8a674a0 fffff803`5bac2365     : 00000000`00000000 ffffed07`f8a676c0 ffff990f`d77831a0 ffffed07`f8a679ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffed07`f8a67500 fffff803`5babb7f0     : 00000000`00000000 ffff990f`d77831a0 ffff990f`d776c1a0 fffff803`5708d7bb : storport!StorpWheaReportError+0x9d
ffffed07`f8a67590 fffff803`5baa1f2c     : 00000000`4257ff28 00000000`00000000 00000000`00000000 ffff990f`d7788020 : storport!StorpMarkDeviceFailed+0x358
ffffed07`f8a67820 fffff803`5ba5a00d     : 00000000`00000200 ffff990f`d7788020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x1483c
ffffed07`f8a678f0 fffff803`5ba5d192     : ffff990f`c1000002 00000000`00000000 ffff990f`d7788020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffed07`f8a67970 fffff803`5ba5c10f     : ffff990f`d7788020 ffff990f`d7783050 ffff990f`f7cef310 00000000`00000000 : stornvme!NVMeControllerReset+0x10a
ffffed07`f8a679a0 fffff803`5bab8f41     : ffff990f`f7cef310 ffff990f`d7783050 00000000`00000000 fffff803`571415a7 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffed07`f8a679d0 fffff803`570748b5     : ffff990f`f5dc5450 00000000`00000000 00000000`00000000 fffff803`5b2ec5c0 : storport!StorPortWorkItemRoutine+0x41
ffffed07`f8a67a00 fffff803`571411b5     : ffff990f`e9493040 ffff990f`e9493040 fffff803`57074780 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffed07`f8a67a70 fffff803`570f5345     : ffff990f`e9493040 00000000`00000080 ffff990f`d56dc080 72bafdba`00000001 : nt!ExpWorkerThread+0x105
ffffed07`f8a67b10 fffff803`571fe1e8     : fffff803`52f1c180 ffff990f`e9493040 fffff803`570f52f0 c3ba3c7f`37cbeb9a : nt!PspSystemThreadStartup+0x55
ffffed07`f8a67b60 00000000`00000000     : ffffed07`f8a68000 ffffed07`f8a61000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

Hi,
same again regarding the nvme device.

What 3rd party apps are you using?

Remove any software you no longer use.

Open an admin command prompt and type chkdsk /r.

You need to reboot and then a scan will start checking your file system.

rOost · Jul 22, 2021

Hello,

I am sorry for the late reply, i was busy the last few days.
I added the output of the chkdsk /r below in a code block.
I got the output from Event Viewer > Application log > find Wininit.
This is all i got and it does not appear to resolve the issue.

In the following wetransfer are two Bluescreens Minidumps. 1 at startup before i did the chkdsk and 1 after the chkdsk.
072221-10828-01.dmp and 1 more file

Code:

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  1784832 file records processed.                                                         
File verification completed.
 Phase duration (File record verification): 13.76 seconds.
  42660 large file records processed.                                   
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                     
 Phase duration (Bad file record checking): 6.90 milliseconds.

Stage 2: Examining file name linkage ...
  111596 reparse records processed.                                       
  2472698 index entries processed.                                                       
Index verification completed.
 Phase duration (Index verification): 1.30 minutes.
  0 unindexed files scanned.                                         
 Phase duration (Orphan reconnection): 30.21 seconds.
  0 unindexed files recovered to lost and found.                     
 Phase duration (Orphan recovery to lost and found): 270.92 milliseconds.
  111596 reparse records processed.                                       
 Phase duration (Reparse point and Object ID verification): 256.09 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 286 unused index entries from index $SII of file 0x9.
Cleaning up 286 unused index entries from index $SDH of file 0x9.
Cleaning up 286 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 44.94 milliseconds.
  343934 data files processed.                                           
 Phase duration (Data attribute verification): 7.05 milliseconds.
CHKDSK is verifying Usn Journal...
  39836400 USN bytes processed.                                                           
Usn Journal verification completed.
 Phase duration (USN journal verification): 302.22 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  1784816 files processed.                                                               
File data verification completed.
 Phase duration (User file recovery): 8.08 minutes.

Stage 5: Looking for bad, free clusters ...
  5081725 free clusters processed.                                                       
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 177959935 KB total disk space.
 154917720 KB in 1430121 files.
    805664 KB in 343935 indexes.
         0 KB in bad sectors.
   1909647 KB in use by the system.
     65536 KB occupied by the log file.
  20326904 KB available on disk.

      4096 bytes in each allocation unit.
  44489983 total allocation units on disk.
   5081726 allocation units available on disk.
Total duration: 10.14 minutes (608452 ms).

Internal Info:
00 3c 1b 00 7f 93 1a 00 b7 d2 2d 00 00 00 00 00  .<........-.....
56 01 00 00 96 b2 01 00 00 00 00 00 00 00 00 00  V...............

kemical · Jul 23, 2021

Hi,
dump files still point to a dodgy drive or controller. See if running Seatools brings anything up:
How to use SeaTools for Windows | Seagate Support US

Regarding your warranty, is it still active? If so I'd contact them.

rOost · Jul 23, 2021

Hello,

I did a Long Generic test and a Short Generic test and also Drive information (last image). These were all the options available to me.
Here are the results (all passed):

An image from 'BSOD: WHEA_UNCORRECTABLE_ERROR (MiniDump)'. SeaTools shows a Seagate SSD model MZVLB512 passing both long and short tests with detailed info.

Microsoft Defender: No threats detected Today at 2:24 PM Scan details

Windows 10 BSOD: WHEA_UNCORRECTABLE_ERROR (MiniDump)

New Member

Attachments

Essential Member

New Member

Attachments

Essential Member

New Member

Essential Member

New Member

Attachments

Essential Member

New Member

New Member

Essential Member

New Member

New Member

Essential Member

New Member

New Member

Essential Member

New Member

Essential Member

New Member