Random and Ongoing BSOD's

zebal said:

Yes, out of 4 dumps, 2 dumps refer to npf.sys and other 2 to audio driver.

If you continue to get bsods for other drivers, not related to above 2 then pointing a finger
at those drivers may be incorrect, and the real reason could be anything.

WinPCap (npf.sys) may be installed by network monitoring tools such as wireshark, nmap etc..

I think i determined that it was installed with Netgear Genie.. which has been removed since i can access the router directly via IP address.. just seemed unnecessary to have the software installed too... I found an updated version of the Audio drivers (Realtek) which will hopefully help with the audio files... I am going to let the system run verifier until tomorrow on the Intel driver and then i will check the audio ones again and see if the new ones hold.. here's to hoping lol

parham93 said:

I am going to let the system run verifier until tomorrow on the Intel driver and then i will check the audio ones again and see if the new ones hold.. here's to hoping lol

Why are you torturing yourself? enable both audio and intel drivers, driver verifier will catch either one in one shot.

Realtek driver most likely isnt the problem but MBfilt64.sys is Audio Driver from Creative Technology Ltd.
realtek drivers have different name.

if you're unsure follow bellow steps:
Windows key + R
msinfo32
File -> Save

copy paste bellow code into elevated powershell hit enter:

Code:

Get-WmiObject -Class Win32_Product | Out-File C:\programs.txt

zip both files and post here.

Unfortunately, they are both examples of a driver that is doing something not recommended (specifying non-paged pool instead of the recommended non-paged pool, non-executable). It's a possible security vulnerability but it's not causing corruption. Also, that is the latest version of MBfilt64.sys from Creative and it's a filter driver for software audio effects - I have the same version on my Haswell system.
Attachment 265317

Driver Verifier results are almost certainly going to be a red herring in this instance. This is most likely a subtle hardware issue - driver corruption isn't likely to cause single bit corruption.

zebal said:

Why are you torturing yourself? enable both audio and intel drivers, driver verifier will catch either one in one shot.

Realtek driver most likely isnt the problem but MBfilt64.sys is Audio Driver from Creative Technology Ltd.
realtek drivers have different name.

if you're unsure follow bellow steps:
Windows key + R
msinfo32
File -> Save

copy paste bellow code into elevated powershell hit enter:

Code:

Get-WmiObject -Class Win32_Product | Out-File C:\programs.txt

zip both files and post here.

I uploaded the 2 files to the google drive

BSOD Files - Google Drive

cwsink said:

I'm not sure I was clear with my question. Has the system ever crashed after it was Restarted and subsequently never gone through a sleep/wake cycle? My Haswell system would work fine after a Restart for hours or even days if I set it to never go to sleep. It only seemed to crash - at some random point - after it had previously gone through a sleep/wake cycle. It would often work fine for days even after multiple sleep/wake cycles. The problem turned out to be a flaky Seasonic PSU for my system. My guess is memory would get corrupted by a strange power situation but I don't know for sure.

So just for an update on this issue... I continued to have BSOD's for another 4 days (files uploaded to the GDrive linked below) at which time i noticed those 4 crashs happened either coming out of sleep or within a min or 2 of coming out of sleep mode. I have since disabled sleep mode and just have it set to turn off the monitor off after 15 min. Since i turned off Sleep mode on 2/6/2020 the system has not suffered a BSOD in the past week...

BSOD Files - Google Drive

Prior Crash Files - Google Drive

I reviewed the dumps that my system was generating and your latest dump almost perfectly matches a 0x12B dump that mine generated. The list of other bugcheck codes I was getting very much line up with those you're getting.

I started with an i7-4770K in an Asus Z87 motherboard. I don't remember how long it took but I eventually started having problems very much like you've described. I replaced the Z87 motherboard with a Z97X Gaming 7 which still had the same problem. I tried new memory - same problem. Updated the BIOS to a beta not available from the Gigabyte product support website - became less frequent but didn't stop. I finally tried a different PSU and the problem stopped. I can't say for certain that yours is the same issue but if you start replacing parts I'd recommend starting with the PSU.

cwsink said:

I reviewed the dumps that my system was generating and your latest dump almost perfectly matches a 0x12B dump that mine generated. The list of other bugcheck codes I was getting very much line up with those you're getting.

I started with an i7-4770K in an Asus Z87 motherboard. I don't remember how long it took but I eventually started having problems very much like you've described. I replaced the Z87 motherboard with a Z97X Gaming 7 which still had the same problem. I tried new memory - same problem. Updated the BIOS to a beta not available from the Gigabyte product support website - became less frequent but didn't stop. I finally tried a different PSU and the problem stopped. I can't say for certain that yours is the same issue but if you start replacing parts I'd recommend starting with the PSU.

Sadly at that point ill just deal with it until the new one is ready... Dont have an extra PS anywhere and dont really see the point in buying one until its time for the new system. Thanks again for all your help.

I don't remember mine crashing with sleep turned off but I'd recommend frequently saving anything important you're working on - just in case. I'm sorry I can't be more definitive about the cause but if you ever do get a chance to try a different PSU and this thread comes to mind, I'd be very curious to know the result. Good luck!