[SOLVED] I need help with BSOD

Status
Not open for further replies.
Sep 18, 2020
10
0
20
0
Hello everyone, I've been having quite a few BSOD recently and it's really getting on my nerves, I'm hoping one of you guys can help me.

My computer tends to bluescreen either on startup, or when playing games and it's really annoying, i get the error code WHEA_UNCORRETABLE_ERROR. Below is an image of the crash dump file
View: https://imgur.com/a/CInW20v
I don't know what else to say, i'm not a very technical person so i really hope some of you can help. If you need more information i will try to find it. Thanks
 
Last edited:
Sep 18, 2020
10
0
20
0
I might have narrowed the search down a bit. I ran BurnInTest and everything passed. I also ran Windows Memory Diagnostic and past, but when i ran Furmark i got the BSOD. Does this mean that it is the GPU, and is it guaranteed to be a hardware problem, or could it be a faulty or missing driver? Any help is much appreciated :D
 

Colif

Win 10 Master
Moderator
Can you go to c:/windows /minidump folder, copy the files from here to another folder. Upload the files from the new folder to a file sharing website and show the link here, and I will get someone to convert them.
If you get a BSOD running a test on the GPU it is probably a clue.
WHEA stands for Windows Hardware Error Architecture. It is an error called by the CPU but not necessarily caused by it.
Dumps may show more.
Can be caused by heat so have you cleaned inside case recently?
Can be software too.
 
Last edited:
Sep 18, 2020
10
0
20
0
Hey thanks a lot for the answer. I should probably say that this issue started appearing shortly after changing a bunch of parts in my pc. I changed the cpu, gpu, motherboard, psu and put in a new ssd. I don't know if this is relevant but thought I would say it anyways just in case. About the temperatur, I have had OpenHardwareMonitor open for a while, also just before a BSOD and the gpu never get above 70C, so I don't think this is an issue. Here is a link to the dump files. The computer have crashed way more than two times, but for whatever reason I only have two dump files. https://1drv.ms/u/s!ArFG_R_Nf7dDb_7TXdBdh_2vWzM?e=pCZbsu
 

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/k45Lpwmy/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:101520-7968-01.dmp (Oct 15 2020 - 12:40:27)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 19 Hour(s), 05 Min(s), and 32 Sec(s)

File information:101120-7968-01.dmp (Oct 11 2020 - 10:28:02)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 1 Hour(s), 23 Min(s), and 17 Sec(s)
Possible Motherboard page: https://www.gigabyte.com/Motherboard/X570-GAMING-X-rev-10#kf
You are using BIOS version F11. If you are using Revision 1.0 of the motherboard, there are BIOS updates available. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

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
what nvme drive do you have in the PC?

Both errors mention
storport!.sys which is part of the windows storage drivers.
stornvme.sys - Microsoft NVM Express Storport Miniport Driver

So most makers of nvme have their testing software. I would suggest testing the nvme drive

. The computer have crashed way more than two times, but for whatever reason I only have two dump files.
if the problem is the nvme it won't be recording dumps after it crashes.
 
Sep 18, 2020
10
0
20
0
Thanks for the responses guys. The link does indeed link to the correct motherboard, but since I've heard many horror stories with updating the BIOS I rather not do it unless it's 100% certain that it will help. My nvme drive is called WD_BLACK 720. What would be the best way to test it?
 

Colif

Win 10 Master
Moderator
the stack, below, is sorted in First in, last out order, which means the things on top happened after the ones below
Error 1 (just a portion)
ffffc28874b255a0 fffff8065c240fe5 : 0000000000000000 ffffc28874b257c0 ffffc807d94661a0 ffffc807d9457de0 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffc28874b25600 fffff8065c23a450 : 0000000000000000 ffffc807d94661a0 ffffc807d946b1a0 0000000000000000 : storport!StorpWheaReportError+0x9d
ffffc28874b25690 fffff8065c220b90 : fffff80659d24440 0000000000000000 0000000000000000 0000000000000001 : storport!StorpMarkDeviceFailed+0x358
ffffc28874b25920 fffff8065c1cc9c6 : ffffc807d9421020 ffffc807d9421020 0000000000000000 0000000000000000 : storport!StorPortNotification+0x139a0
ffffc28874b259f0 fffff8065c1cd1c4 : ffffc807d9421020 ffffc807c1000002 ffffc807ee6f8100 0000000000000003 : stornvme!NVMeControllerInitPart2+0x226
now just ignore all the codes and just look at the text at the end.

that too me looks like its the nvme, even though its passing the tests

Error 2( very similar)
fffff5051a64c570 fffff80054bb60a5 : 0000000000000000 0000000000000062 ffffba0359bb9710 ffffba0355075000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
fffff5051a64c5a0 fffff80056840fe5 : 0000000000000000 fffff5051a64c7c0 ffffba034a2651a0 ffffba034a258de0 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
fffff5051a64c600 fffff8005683a450 : 0000000000000000 ffffba034a2651a0 ffffba034a26a1a0 0000000000000000 : storport!StorpWheaReportError+0x9d
fffff5051a64c690 fffff80056820b90 : fffff80055324440 0000000000000000 0000000000000000 0000000000000001 : storport!StorpMarkDeviceFailed+0x358
fffff5051a64c920 fffff800567cc9c6 : ffffba034a213020 ffffba034a213020 0000000000000000 0000000000000000 : storport!StorPortNotification+0x139a0
fffff5051a64c9f0 fffff800567cd1c4 : ffffba034a213020 ffffba03c1000002 ffffba03553ffe00 0000000000000003 : stornvme!NVMeControllerInitPart2+0x226
fffff5051a64ca70 fffff800567cc0bf : ffffba034a213020 ffffba034a265050 ffffba03553ffee0 ffffcc000c000180 : stornvme!NVMeControllerReset+0x124
they are pretty much same thing, the NVME controller seems to be causing the problem. The controller is on the NVME. I don't know if the WD software would see a bad controller

Now lets look at software.
Update your bios, you on F11 and there are 4 since though 2 are just updates to let motherboard use more CPU. Might still help.
install newest chipset driver
nvme looked after by CPU so not any software I can offer.
 
Sep 18, 2020
10
0
20
0
Thanks for the quick response. I have updated the BIOS to version F31b and updated the chipset driver, however the issue persists. Should I try to put the NVME in another m.2 slot on the motherboard, or will it be useless?
 

Colif

Win 10 Master
Moderator
if the problem is the nvme controller, and that is on the nvme, where you put drive won't really fix it.

We used to have WD reps who I would ask right now what they thought but they don't exist anymore.

I would maybe ask Western digital - you can contact them here via the Ask a question box via email. and perhaps link to this post and see what they say about the errors. https://support.wdc.com/contact.aspx
 
Sep 18, 2020
10
0
20
0
Hello again. I contacted WD, but sadly the response I got was something along the lines of; "From the screenshots you provided us, it seems like you drive is working fine" not exactly the response I was hoping for, he also recommended putting the drive into another machine, but sadly this is not an option, as I do not have access to another machine to try it on. I honestly have no idea what to do from here. I'm kinda lost.
 

Colif

Win 10 Master
Moderator
I wonder if I am wrong. I would suggest you ask on here, follow their posting instructions and just see if they think its the NVME as well.


you can link to this thread if you like, some of them over there come here too sometimes.

updating BIOS might still help but see what they say. I haven't given up but I want a 2nd opinion from people who know how to read dumps.
 
Sep 18, 2020
10
0
20
0
Haha. Don't worry I think they figured it out :tearsofjoy:. I showed them the same screenshots that I have posted in here and the dump files, as well as some report thing from their desktop app (Dashboard).
 
Sep 18, 2020
10
0
20
0
It seems like uninstalling a bunch of Logitech drivers did the trick. I have no idea why they were such a problem, but for whatever reason they were. Thanks you so much for your help Colif.
 
Status
Not open for further replies.

ASK THE COMMUNITY