Question Plagued by BSODs

badsoup

Reputable
May 15, 2016
34
0
4,530
I’ve been given several different error codes for why my system crashed and I’ve had no luck with fixing them. Before I made this thread I ran memory diagnostic tool and automatic maintenance tool, and there have been no issues brought up. I also did DISM.exe and sfc /scannow in powershell and found no issues there. I’ve noticed it tends to crash when I restart after I hit sleep.

Using BlueScreenView, the last 3 minidump files say my system crashed for the following reasons:

SYSTEM_SERVICE_EXCEPTION - files highlighted in red: Ntfs.sys, ntoskrnl.exe
DRIVER_IRQL_NOT_LESS_OR_EQUAL - files highlighted in red: Netwbw02.sys, ntsokrnl.exe, wfplwfs.sys
SYSTEM_SERVICE_EXCEPTION - files highlighted in red: ntoskrnl.exe
 
The only thing that is common is the ntoskrnl. My guess is that you have some corrupted drivers on your computer and will need to go through and update each driver.
I would not recommend using the driver scan tool that is in the link, but the link at least gives you an idea of how to fix the issue.
 

Colif

Win 11 Master
Moderator
Firstly, NTOSKRNL is so common above as its the windows kernel, it is in the middle of almost all actions on PC involving programs and hardware.

NETwbw02.sys = Intel Wifi driver. Try updating drivers?
wfplwfs.sys = Windows 8 CP - WFP NDIS 6.30 Lightweight Filter Driver (probably Win 10 as well, they share parts).
ntfs.sys = New Technology File System = The file system Windows has used since XP

If updating Intel Wifi drivers isn't enough,

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 

badsoup

Reputable
May 15, 2016
34
0
4,530
Firstly, NTOSKRNL is so common above as its the windows kernel, it is in the middle of almost all actions on PC involving programs and hardware.

NETwbw02.sys = Intel Wifi driver. Try updating drivers?
wfplwfs.sys = Windows 8 CP - WFP NDIS 6.30 Lightweight Filter Driver (probably Win 10 as well, they share parts).
ntfs.sys = New Technology File System = The file system Windows has used since XP

If updating Intel Wifi drivers isn't enough,

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

here's a link to 5 minidumps I've collected.

https://1drv.ms/u/s!Am9WlWp_gAG9cbBhox3oTjV0jDs?e=cLVTj2
 

gardenman

Splendid
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://westernmosttonight.htmlpasta.com/
File information:011020-36625-01.dmp (Jan 10 2020 - 10:35:18)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for Netwbw02.sys
Probably caused by:Netwbw02.sys (Process: System)
Uptime:1 Day(s), 10 Hour(s), 30 Min(s), and 28 Sec(s)

File information:010820-42265-01.dmp (Jan 8 2020 - 02:05:06)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for Netwbw02.sys
Probably caused by:Netwbw02.sys (Process: System)
Uptime:5 Day(s), 8 Hour(s), 58 Min(s), and 32 Sec(s)

File information:010820-34187-01.dmp (Jan 9 2020 - 00:04:16)
Bugcheck:FAULTY_HARDWARE_CORRUPTED_PAGE (12B)
Probably caused by:ntkrnlmp.exe (Process: MemCompression)
Uptime:0 Day(s), 12 Hour(s), 52 Min(s), and 11 Sec(s)

File information:010220-36109-01.dmp (Jan 2 2020 - 17:06:04)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: HandBrake.exe)
Uptime:2 Day(s), 21 Hour(s), 02 Min(s), and 54 Sec(s)

File information:123019-34578-01.dmp (Dec 30 2019 - 20:02:41)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 4 Hour(s), 36 Min(s), and 26 Sec(s)
Comment: The overclocking driver "XtuAcpiDriver.sys" was found on your system. (Intel Extreme Tuning Utility)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/GA-H97-D3H-rev-10
There is a BIOS update available for your system (Version F7). You are using version F3. 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.
 

badsoup

Reputable
May 15, 2016
34
0
4,530
Hi, I ran the dump files through the debugger and got the following information: https://westernmosttonight.htmlpasta.com/
File information:011020-36625-01.dmp (Jan 10 2020 - 10:35:18)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for Netwbw02.sys
Probably caused by:Netwbw02.sys (Process: System)
Uptime:1 Day(s), 10 Hour(s), 30 Min(s), and 28 Sec(s)

File information:010820-42265-01.dmp (Jan 8 2020 - 02:05:06)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for Netwbw02.sys
Probably caused by:Netwbw02.sys (Process: System)
Uptime:5 Day(s), 8 Hour(s), 58 Min(s), and 32 Sec(s)

File information:010820-34187-01.dmp (Jan 9 2020 - 00:04:16)
Bugcheck:FAULTY_HARDWARE_CORRUPTED_PAGE (12B)
Probably caused by:ntkrnlmp.exe (Process: MemCompression)
Uptime:0 Day(s), 12 Hour(s), 52 Min(s), and 11 Sec(s)

File information:010220-36109-01.dmp (Jan 2 2020 - 17:06:04)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: HandBrake.exe)
Uptime:2 Day(s), 21 Hour(s), 02 Min(s), and 54 Sec(s)

File information:123019-34578-01.dmp (Dec 30 2019 - 20:02:41)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 4 Hour(s), 36 Min(s), and 26 Sec(s)
Comment: The overclocking driver "XtuAcpiDriver.sys" was found on your system. (Intel Extreme Tuning Utility)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/GA-H97-D3H-rev-10
There is a BIOS update available for your system (Version F7). You are using version F3. 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.

Thank you so much. And that is the correct motherboard!
 

Colif

Win 11 Master
Moderator

badsoup

Reputable
May 15, 2016
34
0
4,530
Last 2 BSOD still blaming the INtel network driver, did you update it?

Apr 17 2016Netwbw02.sysIntel Wireless WiFi Link driver
this would be latest - https://downloadcenter.intel.com/download/29258?v=t

You are on original Bios (version F3), the latest is F7. It might help - this shows how - https://www.gigabyte.com/MicroSite/121/flashbios_qflash.pdf

It could be all caused by same driver, the 1st 3 bsod are inconclusive. So update it before looking at BIOS.

I tried your link but it told me that the software package couldn’t be installed on my system. So I tried this one instead and no luck: https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10 .

Just in case it’s important:
CPU: Intel Core i5 4460 @ 3.20GHz
Wifi Card: ASUS PCE-AC55BBT dual band wireless-AC1200

I can’t name my previous wifi card, but I got BSODs back then as well. Since then I installed this new one.

New minidump after latest crash:
https://1drv.ms/u/s!Am9WlWp_gAG9cgeHeD-Te8Y6b84?e=mV3ckF
 

gardenman

Splendid
Moderator
I ran the new dump file through the debugger and got the following information: https://perfervidfail.htmlpasta.com/

File information:011120-36906-01.dmp (Jan 11 2020 - 14:08:44)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: RuntimeBroker.)
Uptime:1 Day(s), 3 Hour(s), 32 Min(s), and 51 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

Win 11 Master
Moderator
Sigh, the paste file is borked, the webpage gardenman used is dead... I could guess its likely the network driver

Did you try this one? https://www.asus.com/us/Networking/PCE-AC55BT/HelpDesk_Download/ although it is only 6 months older and could in theory be what you have installed now. Asus have a tendency of changing driver numbers and dates.

I don't suppose you can use ethernet and see if BSOD stop?
 

badsoup

Reputable
May 15, 2016
34
0
4,530
Sigh, the paste file is borked, the webpage gardenman used is dead... I could guess its likely the network driver

Did you try this one? https://www.asus.com/us/Networking/PCE-AC55BT/HelpDesk_Download/ although it is only 6 months older and could in theory be what you have installed now. Asus have a tendency of changing driver numbers and dates.

I don't suppose you can use ethernet and see if BSOD stop?

I'm not sure what you mean by 6 months older since the latest driver available for download is from 2016, which probably means I already have it installed since I replaced my wifi card and installed it in 2018/9 via disc.

Unfortunately I'm not able to use ethernet right now.
 

Colif

Win 11 Master
Moderator
Dump file link was glitched yesterday, it works now. Alas dump isn't really pointing at any driver name.

Asus change driver dates.
the newest driver on site is dated - 14 Dec 2016
THe driver on your PC is dated 17th April 2016

I would expect the disc also has same driver, so yes, you have it.

Dates on driver packages don't always match the driver dates, some companies still use drivers from 2012 and include it in their 2019 driver packs.
 

badsoup

Reputable
May 15, 2016
34
0
4,530
Dump file link was glitched yesterday, it works now. Alas dump isn't really pointing at any driver name.

Asus change driver dates.
the newest driver on site is dated - 14 Dec 2016
THe driver on your PC is dated 17th April 2016

I would expect the disc also has same driver, so yes, you have it.

Dates on driver packages don't always match the driver dates, some companies still use drivers from 2012 and include it in their 2019 driver packs.

I uninstalled my old wifi driver and installed the latest one and things seemed to be going well. I restarted my computer a few times after I put it to sleep and no BSODs happened but then I got a BSOD right before I tried to update windows 10. I did successfully update windows 10 though.

New minidump: https://1drv.ms/u/s!Am9WlWp_gAG9c1teYDHsu-3L_1A?e=JYmBlA
 

gardenman

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

File information:011620-36437-01.dmp (Jan 16 2020 - 20:41:36)
Bugcheck:FAULTY_HARDWARE_CORRUPTED_PAGE (12B)
Probably caused by:ntkrnlmp.exe (Process: MemCompression)
Uptime:1 Day(s), 5 Hour(s), 41 Min(s), and 27 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

Win 11 Master
Moderator
I ran memory diagnostic tool

I should have thought of this before
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.

Last BSOD was in compressed memory, so it was in ram. The errors moving around enough that it could be ram causing it. Worth a look.
 

badsoup

Reputable
May 15, 2016
34
0
4,530
I should have thought of this before
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.

Last BSOD was in compressed memory, so it was in ram. The errors moving around enough that it could be ram causing it. Worth a look.

I tested both ram sticks at the same time and found no errors after 4 passes. I didn't really expect there to be errors though since I upgraded my ram over a month ago.
 

badsoup

Reputable
May 15, 2016
34
0
4,530

Colif

Win 11 Master
Moderator
I said drives, as in SSD or HDD :)
the corrupted page could be on the drive, not ram.

Gardenman is asleep and I am meant to get storms all day tomorrow so unsure when I will get a chance to read his results. I don't use PC when storms around, I can't afford the unnecessary repairs.
 

badsoup

Reputable
May 15, 2016
34
0
4,530
I said drives, as in SSD or HDD :)
the corrupted page could be on the drive, not ram.

Gardenman is asleep and I am meant to get storms all day tomorrow so unsure when I will get a chance to read his results. I don't use PC when storms around, I can't afford the unnecessary repairs.

Oh! I use Western Digital drives. The main one is a 1tb drive that I've been using since I first started getting BSODs. Here let me take this from Speccy.

1863GB Western Digital WDC WD20EZAZ-00GGJB0 (SATA (SSD))
931GB Western Digital WDC WD10EZEX-00BN5A0 (SATA )
931GB Western Digital WDC WD10EZEX-08WN4A0 (SATA )

I updated my BIOS btw. And I'll wait for you until after the storms are finished. I appreciate you trying to help me so much!
 

gardenman

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

File information:011920-31265-01.dmp (Jan 19 2020 - 02:16:10)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:ntkrnlmp.exe (Process: RuntimeBroker.)
Uptime:1 Day(s), 13 Hour(s), 57 Min(s), and 20 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.
 

badsoup

Reputable
May 15, 2016
34
0
4,530

I couldn't get the first link to detect my SSD, thankfully I was able to scan all drives with the second link and found no issues.

I actually originally made this account to fix my BSODs. I definitely appreciate you helping me and this is the most anyone has consistently tried to help me with this issue, but this is getting so frustrating for me. Is it normal for the cause of BSODs to be so well-hidden? I don't know how many more methods I have left to identify what the problem is with my PC.
 

gardenman

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

File information:012020-33031-01.dmp (Jan 20 2020 - 14:24:50)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:ntkrnlmp.exe (Process: Microsoft.Phot)
Uptime:0 Day(s), 11 Hour(s), 31 Min(s), and 24 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.