[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]

That NVIDIA crash above pre dates when he swapped to the old drivers, so just ignore it. It should be fixed. Something else isn't.

the other 3 are all web based programs.

For some reason the link to the paste file times out today, or I would look to see what might be the cause apart from LAN which we already gone over. I will check it later and see if it comes good.

 

[gardenman]

The HTML version on pste.eu is working for me (but it could have been down earlier, it doesn't seem to be as reliable lately). I've posted the text version if needed.

 

[Tyrlaan]

I don't know if this is helpful info or not, but almost every crash has happened when I go to use my computer after it being idle for a while. I don't recall a single instance of a crash while playing a game, and maybe only one while just web browsing (and this was one of the earlier ones, before addressing the nvidia driver).

 

[Colif]

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Try the 2nd post in this thread - https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/ follow the precautions as they there for a reason. it should give us a driver name. Suspect its something from logitech but thats only based on you having 6 logitech drivers. It will tell me if I am wrong or not.

 

[Tyrlaan]

Okay, cool, will do.

If it's okay for the thread to languish for a few days, I might wait until the weekend to take these steps.

 

[Colif]

Okay, cool, will do.

If it's okay for the thread to languish for a few days, I might wait until the weekend to take these steps.

It is your post, we will be here when you are ready to come back

 

[Tyrlaan]

Memetest came back with no errors on 4 passes (though I just realized I screwed up and didn't isolate my 2 sticks when doing that)

However, it appears we hit paydirt with driver verifier. BSOD triggered by lvrs64.sys on bootup. Broke the bootloop through safe mode no problem.

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

 

[Colif]

lvrs64.sys
logitech webcam drivers

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/

Gardenman may know newer versions, as far as I know there aren't newer drivers available. Its why I ignored them up until now, as I knew they used older drivers but they normally work.

remove it if you don't use it? might need a new one?

 

[Tyrlaan]

I haven't used it in quite some time, honestly, so I'll just remove the driver I think.

I'm on the road right now, so it'll be a few days before I get back, but I'll be sure to update, if for no other reason than to mark the question answered

Thanks!

 

[Tyrlaan]

Apologies if this breaks necro rules but wanted to share this (positive) oddity

So my computer has not had a BSOD since my last post. I still haven't even removed the offending driver though...

 

[Colif]

Don't remind it

that is the desired result, error just stops

 

[Tyrlaan]

So I thought my woes were over, but alas...

What appears to be happening now is that I get a handful of BSODs after each time my computer goes through a Windows update. I'll get somewhere between 2 to 4 BSODs within 24-ish hours after the update and then I'm back to stable... until the next update.

Most of the time it doesn't leave behind a minidump, which is annoying. I got one for the crash that just happened to me overnight however, so sharing it here. It crashed an additional 2 times after that but no minidump (is that because I need to wait longer on the BSOD? I cold boot if I don't see the progress percentage move after a bit).

Generally they are SERVICE EXCEPTION errors, but I've seen others. One today was KMODE EXCEPTION NOT HANDLED, for example.

Anyway, here's the minidump I have: https://drive.google.com/open?id=1StKcQnflNIXUBYGiBbjZMsHSqRUX-3Qd

Thanks in advance!

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pastebin.com/sui7syxZ

File information:	121219-7937-01.dmp (Dec 12 2019 - 07:30:20)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 04 Min(s), and 03 Sec(s)

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]

that one seems pretty obvious to me, Nvidia drivers, try this and see if loading newer drivers fixes it - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

either get drivers from Nvidia or run windows update after ddu

 

[Tyrlaan]

that one seems pretty obvious to me, Nvidia drivers, try this and see if loading newer drivers fixes it - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

either get drivers from Nvidia or run windows update after ddu

Okay, had my first required reboot since posting this and so far no crashes... fingers crossed!

 

[Tyrlaan]

Thought we had it this time - but alas, got another crash this morning. Presumably there was a BSOD, but I didn't see it; when I woke up this morning I just had a black screen.

Here's the minidump: https://drive.google.com/file/d/1StKcQnflNIXUBYGiBbjZMsHSqRUX-3Qd/view?usp=sharing

As always, thanks in advance.

 

[gardenman]

That is the same dump that was previously uploaded with the date/time of:
Dec 12 2019 - 07:30:20

 

[Tyrlaan]

Wow, oops! Apologies.

Here's the right file - https://drive.google.com/file/d/1lYVITHMFlYSsMU_n0kY1R4JXejawHWYo/view?usp=sharing

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://monodiccommonfrog.htmlpasta.com/

File information:	020120-8015-01.dmp (Feb 1 2020 - 02:17:41)
Bugcheck:	KERNEL_MODE_HEAP_CORRUPTION (13A)
Probably caused by:	memory_corruption (Process: iCUE.exe)
Uptime:	0 Day(s), 9 Hour(s), 27 Min(s), and 07 Sec(s)

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.

 

[Tyrlaan]

Hm, just had another crash. Here's the new minidump: https://drive.google.com/file/d/1LsC0fKg8DxvKbnmOaJjXnT4OQOVFWi-s/view?usp=sharing

 

[Tyrlaan]

And two more crashes....

https://drive.google.com/file/d/1hlHQMgAN-ztNclulJudEpZMxRqAyRbyP/view?usp=sharing

and

https://drive.google.com/file/d/1S5MMYZYtCmX28hwaXRXkR5qKN_2c7zOH/view?usp=sharing

 

[gardenman]

Colif was out of town for a few days (and still might be) so I'm not sure when he's going to be able to reply.

Here are the 3 new dump results: https://hoydenishboss.htmlpasta.com/

Spoiler

File information:	020220-8187-01.dmp (Feb 2 2020 - 11:17:22)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 21 Sec(s)

File information:	020220-8156-01.dmp (Feb 2 2020 - 10:30:09)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: Dropbox.exe)
Uptime:	0 Day(s), 2 Hour(s), 20 Min(s), and 42 Sec(s)

File information:	020220-8062-01.dmp (Feb 2 2020 - 08:07:48)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: dwm.exe)
Uptime:	1 Day(s), 0 Hour(s), 26 Min(s), and 33 Sec(s)

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.

 

[Tyrlaan]

No worries. My machine will probably be stable for a while now, until it needs a reboot for some reason. These always seem to happen after rebooting due to some sort of software update.

 

[Colif]

First dump on Sat Feb 1 02:17:41 was caused by GPU drivers - dxgmms2!VIDMM_GLOBAL::CreateOneAllocation+0xc8d - sure looks like a GPU command
first Dump of the last 3 blames Nvidia
last 2 less obvious but given 2 of 4 blame Nvidia, I know who I would blame for all of them...

so um, since I said this in December, did you?

that one seems pretty obvious to me, Nvidia drivers, try this and see if loading newer drivers fixes it - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

either get drivers from Nvidia or run windows update after ddu

Dec 06 2019 nvlddmkm.sys Nvidia Graphics Card driver

I would run DDU and run windows update and let it find your card. They might work better.

 

[Tyrlaan]

I did. And to be precise, I ran DDU and let windows update find my drivers instead of getting them from Nvidia...


What strikes me as odd is that these crashes only seem to happen after I've rebooted my machine due to updating some software. For example, this recent rash of three crashes occurred after doing a clean reinstall of iCue because I got a new mouse and wanted to get rid of the old settings that iCue was holding onto. And the iCue install required a reboot at the end.

I've had no crashes since and don't anticipate any until the next windows update gets pushed down and forces a reboot.