[SOLVED] Intermittent BSOD in Win10 - Looking for help

[Tyrlaan]

Hi all,
I built my own PC roughly 2 weeks ago. About one week ago, the BSOD errors began.

The first was a Page Fault in Nonpaged Area, then a Bad Object Header the next day. I got one that was Memory Management as well, otherwise they've been all Page Fault. I had one to two a day for about 3 days then they stopped. I went from the 24th to the 29th with no BSODs, and now they are back.

Here are several of the minidumps. If these links don't work, I'll upload elsewhere.

I've run the Windows provided RAM diagnostic tool (once) with no errors. I did a chkdsk (once) with no errors. I've also uninstalled my graphics drivers with DDU and fresh installed this morning. It's given me a BSOD once since, but I got no minidump from it - the BSOD apparently hung at 0%

Massive thanks in advance to anyone willing to help! I've tried to get help through the Microsoft page but responses went quiet after telling me what info they needed to help...

https://1drv.ms/u/s!AprVK5vSLiJxhmWuMRHEZNJtZixC

https://1drv.ms/u/s!AprVK5vSLiJxhmY4L0zG5ExolRXo

https://1drv.ms/u/s!AprVK5vSLiJxhme7sCygNRvM-rsG

https://1drv.ms/u/s!AprVK5vSLiJxhmmHhzjhb9a0fZmD

 

[Colif]

Is this the system? https://pcpartpicker.com/list/xTCkNQ

Always helps to show specs, lucky I found an older post from 2 weeks ago

have you run MSI LIve update 6? its right here

I can't read dumps but I will ask @gardenman to convert the ones you linked into a format I can read

 

[Tyrlaan]

Is this the system? https://pcpartpicker.com/list/xTCkNQ

Always helps to show specs, lucky I found an older post from 2 weeks ago

have you run MSI LIve update 6? its right here

I can't read dumps but I will ask @gardenman to convert the ones you linked into a format I can read

Indeed - sorry, I should have included that.

I haven't run MSI Live so I'll give that a shot. Although, I may have stumbled on something?...

I was scouring my update history last night because my first crash was perhaps an hour or less after I plugged my phone into the front usb port to charge it. Now... my previous PC (which I also built) had some sort of issue that I was best able to diagnose as a short of some kind initiated by plugging something into the front usb port, which would result in a dead/dying hard drive. I never pinpointed the issue deeper than that so I just put bluetooth receivers in the front ports so I'd stop using them and indeed never lost another hard drive.

That little anecdote makes me superstitious that plugging my phone into the new PC caused this problem. Now as it turns out, in the update history I see a record of an installation of Samsung USB drivers, which makes sense on one hand, but I can't find any evidence of the installation, couldn't uninstall them, etc. Suspecting my superstition might actually be on to something, I chose to chase down and officially install the Samsung USB drivers late last night.

So my current thought is to wait and see if I get another BSOD. I'm also thinking that if I do get another BSOD, I might need to go with a system restore to the date before this driver was "installed". Though if folks think I'm barking up a wrong/insane tree here, I'll jump straight to the MSI Live update.

 

[Colif]

Its your PC, i will still look at files we have and see if it shows anything that might back up your idea. If you want to wait, go right ahead

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/BCQ8.html

Spoiler

File information:	042919-7703-01.dmp (Apr 29 2019 - 08:47:06)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: Discord.exe)
Uptime:	0 Day(s), 0 Hour(s), 49 Min(s), and 59 Sec(s)

File information:	042919-7671-01.dmp (Apr 29 2019 - 01:57:44)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: SetPoint.exe)
Uptime:	4 Day(s), 13 Hour(s), 06 Min(s), and 12 Sec(s)

File information:	042419-7843-01.dmp (Apr 24 2019 - 12:49:50)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: steamwebhelper.exe)
Uptime:	1 Day(s), 0 Hour(s), 05 Min(s), and 19 Sec(s)

File information:	042319-7687-01.dmp (Apr 23 2019 - 11:54:21)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 10 Min(s), and 36 Sec(s)

BIOS information was not included in the first dump file. This can sometimes mean an outdated BIOS is being used.

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

 

[Colif]

wonder why the logitech mouse software crashed. that could have been your phone, others I am not so sure are that easily explained.

might want to run live update anyway, your lan drivers could have caused the 2 of the crashes. It might also explain why mouse drivers crashed as well.

 

[Tyrlaan]

wonder why the logitech mouse software crashed. that could have been your phone, others I am not so sure are that easily explained.

might want to run live update anyway, your lan drivers could have caused the 2 of the crashes. It might also explain why mouse drivers crashed as well.

Okay so I got MSI Live Update and feel silly because I manually updated drivers on the Drivers tab and it seems I could have saved myself a bunch of time if I got this back when I was setting up my PC in the first place

Thing 1 - my LAN drivers are up to date.

Thing 2 - the only driver its listing as not up to date is the AMD Chipset

 

[Colif]

About only motherboard maker who doesn't have a program used to download drivers in Asus (Its unclear if they do or not), its just a shame more people buying the motherboards don't know they exist.

So lan drivers were up to date already or are now?
chipset driver might help, since USB is part of that.

really, only worry about it if you get more BSOD.

 

[Tyrlaan]

Oops, missed the question in your post - LAN drivers were already up to date.

So far, no more BSODs. Not holding my breath though since I had a round of about 4 days without any before... fingers crossed!

 

[Tyrlaan]

Just a BSOD with SYSTEM SERVICE EXCEPTION. It did not create a minidump.

I'll update the chipset drivers now.

 

[Colif]

might want to take this off, it might not be problem but an 9 year old driver could be

Oct 06 2010

GPU-Z.sys

TechPowerUp CPUID GPU-Z driver

everything else is fairly new.
odd it didn't leave a dump file. that can happen if its at startup and windows hasn't had a chance to log in yet.

 

[Tyrlaan]

Okay, will do. I can't remember what made me stop launching it on bootup, but I turned it off. I'll uninstall.

And apparently it crashed again some point within the last couple hours. This BSOD gave me a minidump at least.

https://1drv.ms/u/s!AprVK5vSLiJxhmrv6SwJo_pBll7g

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/xLcu.html

File information:	050419-7609-01.dmp (May 4 2019 - 15:01:44)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	nvlddmkm.sys (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 33 Min(s), and 24 Sec(s)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Edit: I know you said you already tried some of that ^. Maybe try a different driver. Sometimes a slightly older one, or the one provided by Windows Update helps.

Possible Motherboard page: https://www.msi.com/Motherboard/B450M-GAMING-PLUS
The BIOS info was found this time in the dump file, but there is a BIOS update available for your system (version 1.6). You are using version 1.3. 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. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

do as he suggests, try older/different Nvidia drivers

Bios update could help -

seems all I am doing is saying, do what he suggests

 

[Tyrlaan]

Literally just had another BSOD. I think this was the first one to actually reboot afterwards rather than just hang once it reached 100%.

Stopcode was driver_irql_not_less_or_equal and it listed nvlddmkm.sys

https://1drv.ms/u/s!AprVK5vSLiJxhmvLzkWN60d3HREM

Regarding next steps, something else that struck me this morning - I built this PC and I build a second one for my wife. It's all the same parts. She's gotten a total of ZERO BSODs. I don't know if that's all that relevant, but I do know that means her BIOS is not up to date either. She may have an older NVIDIA driver though since I don't think she is as "vigilant" as I am at keeping graphics drivers up to date.

I guess my thought is that perhaps this suggests updating the BIOS won't solve the issue? Or am I barking up the wrong tree?

 

[Colif]

nvlddmkm.sys = Nvidia drivers. same as previous one was.

Try this and instead of downloading latest drivers from Nvidia, run windows update and let it find the card. Microsoft have older Nvidia drivers that are more stable - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

 

[Tyrlaan]

Okay, re-ran DDU and let Windows Update do the work. Definitely an older driver

Fingers crossed!

 

[Tyrlaan]

Made it a full week with no BSODs! So, with some cautious optimism, I'll say this appears resolved.

Thanks all!

 

[Tyrlaan]

Hi all,
Apparently I spoke too soon.

I thought we had beaten the intermittent BSODs that I was getting.

Since then the machine has been quite stable. I had a couple times within the past few days where it behaved weird about recovering from sleep mode. Both times I actually had to power it down, but then on what I thought was a cold boot, it came up like restoring from sleep mode. (side note: tempted to just turn off sleep mode, I never used it on my old PC anyway).

Anyway, a short while ago, I got an actual crash. BSOD said Memory Management.

Here's the minidump: https://1drv.ms/u/s!AprVK5vSLiJxhmw-zJqeC3x4CSRi

Thanks in advance!

 

[Tyrlaan]

And just got another one - this time IRQL Not Less or Equal

Here's the minidump: https://1drv.ms/u/s!AprVK5vSLiJxhm376Vp6ki6nPfHd

 

[onespeedbiker]

It sounds like your computer is having trouble with hibernation/sleep, where Windows keeps the systems files in RAM memory or saves them intact on the HDD/SSD and then dumps them into memory. Another system that does this is Fast startup. If you are having these kind of problems, I would disable sleep, hibernate and Fast start up. Go to Power and Sleep> Additional power settings> Change plan settings, click the box in front of "Put the computer to sleep" and choose Never, than Save changes. Next click "Change advanced power settings". In the Power Settings box, click the cross in front of Sleep. Under Sleep check the boxes in front of Hybrid sleep and Hibernate after. In both cases click on the blue text in front of the headings and choose Never, click Apply. Now Click the back arrow upper left hand corner, back to Power Options >Choose what the power buttons do>"Change settings that are currently unavailable" and unclick the Fast start up box and click Save settings. Exit Power Options and do the same with Power and Sleep. Next restart your computer and see if the changes reduce or eliminate the Blue Screens. If may take longer a little longer to boot, but hopefully your computer will be more stable.

 

[Colif]

hands our medals to all who read 14 lines without a break... Wall of text medal.

Turning off sleep, as suggested above is a work around more than a fix, But if PC is old it is often best solution if the driver has no update. I don't use sleep anyway, PC either off or being used. No middle ground.

its hard to tell what drivers might be to blame for that. It could be the webcam drivers logitech refuse to update

Oct 22 2012	lvrs64.sys	Logitech Kernel Audio Improvement Filter Driver http://support.logitech.com/
Oct 22 2012	lvuvc64.sys	Logitech USB Video Class Driver (WebCam) http://support.logitech.com/

it could be the GPU drivers cause NVIDIA driver quality is suspect.

see what gardenman finds in dumps.

 

[Tyrlaan]

Woke up to a machine that crashed at some point overnight (turned off Sleep Mode... I think).

Here's the minidump: https://1drv.ms/u/s!AprVK5vSLiJxhm6J88vUlgjOQDIT

 

[Tyrlaan]

Had another one this afternoon apparently. To my recollection, this is the first one where the computer actually rebooted after the crash.

Here's this minidump: https://1drv.ms/u/s!AprVK5vSLiJxhm8f1qSnA9U3Lv9A

 

[gardenman]

I wasn't notified of new messages in this thread. The notifications seem to be more and more spotty to me. I ran the dump files through the debugger and got the following information: https://pste.eu/p/teo2.html

Spoiler

File information:	052019-7937-01.dmp (May 20 2019 - 17:38:56)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: Dropbox.exe)
Uptime:	0 Day(s), 10 Hour(s), 05 Min(s), and 32 Sec(s)

File information:	052019-7453-01.dmp (May 20 2019 - 02:04:01)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: Steam.exe)
Uptime:	1 Day(s), 11 Hour(s), 43 Min(s), and 29 Sec(s)

File information:	051819-7921-01.dmp (May 18 2019 - 13:52:53)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 16 Min(s), and 56 Sec(s)

File information:	051819-7796-01.dmp (May 18 2019 - 13:24:53)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	2 Day(s), 16 Hour(s), 32 Min(s), and 11 Sec(s)

File information:	050519-7906-01.dmp (May 5 2019 - 09:50:34)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	nvlddmkm.sys (Process: System)
Uptime:	0 Day(s), 17 Hour(s), 27 Min(s), and 50 Sec(s)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

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