Windows 10: Random BSOD even with fresh reset, can't find the cause

Each Drive testing software has a different algorithm.
They either find problems with the drive or attempt to predict future problems.
So one software may display pass while another displays problem areas.
When there are findings from any of the drive testing software we advise backing up the drives.
The Macrium imaging is useful in case the computer is not longer bootable.
If you have data backed up you can always clean install and don't have to use Macrium as you have other options.
Most of the threads don't have the backup discipline that you have.

 

Alright!
So I'm still not sure what was the cause, but no blue screen so far for the moment... I'll consider this is a solved case until the next crash *Wink
Thank you very much for your help, I should have come here months ago.

Have a great day!

 

You are welcome. Glad to help. The windbg found the misbehaving wireless card as the cause of the BSOD. The drive problem was discovered in the workup of the event viewer reports. The set up you have should serve you well in case there are any drive problems.
Let us know if you have any future issues.

 

Hi again,

Maybe I spoke too fast! The problem came back as soon as I have upgraded from build 1703 to build 1709.
Here is a new dump:
ANTOINE-POULET-Mon_10_30_2017_144517_04.zip

I wanted to investigate the issue by following your tutorials about WinDbg. I installed it but I'm quite lost. I couldn't even manage to find a driver issue in the first dump I submitted to you.

The Intel driver is up to date. Also, previously to the update, I was "stable" on prime95 (I just tested 2 hours) regardless of the Wi-Fi driver version. Now it crashes again in dozens of minutes.

I suspect something else than the Intel driver...

 

Some of the Windbg commands are not working during this Windows upgrade period.
There was no definitive misbehaving driver identified in the latest dumps.
If there are more dumps it may be possible to find the misbehaving driver with the limited commands.

1) Please read these links on Windows driver verifier.
2) Backup all files to another drive or to the cloud.
3) Create a backup image using Macrium:
Macrium Software | Macrium Reflect Free
4) Place the backup image onto another driver or into the cloud.
5) Make a brand new restore point

Windows driver verifier is designed to repetitively produce BSOD until misbehaving drivers are fixed or until the tool is turned off.

To turn off Windows driver verifier you will navigate in the Windows advanced troubleshooting menu to:
1) startup options (not startup repair) > restart > #6 safe mode with command prompt > type: verifier /reset
If step #1 fails to turn off Windows driver verifier move to step #2
2) command prompt > Administrator X:\Windows\system32\cmd.exe > type:
verifier /bootmode resetonbootfail
If step #2 fails to turn off Windows driver verifier move to step #3
3) system restore
This method typically leads to the loss of the mini dump and little progress is made in the troubleshooting.

4) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > in startup and recovery click settings > make sure automatically restart is un-checked and write debugging information is automatic memory dump.

5) Open administrative command prompt and type or copy and paste: shutdown /r /o /f /t 00
This will reboot to the windows advanced troubleshooting menu where you can practice the above 3 methods to turn off windows driver verifier.

6) When you have backed up files, made a brand new restore point, and are comfortable with the 3 methods to turn off windows driver verifier you can turn it on.
The computer may be sluggish when windows driver verifier is on and this expected.
7) The BSOD windows typically displays the bug check driver verifier detected violation and sometimes displays the misbehaving driver in the form *.sys. If you see the misbehaving driver please report it into the thread.
8) Download and install:
Blue screen of death (STOP error) information in dump files.
Resplendence Software - WhoCrashed, automatic crash dump analyzer
9) After each BSOD run both software programs and then uninstall the misbehaving driver.
10) You can either reinstall a new driver immediately after uninstalling the driver or you can restart Windows driver verifier and look for the next misbehaving driver. Then you can install new drivers after all misbehaving drivers have been removed and there are no longer any BSOD. The end result should be the same.

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials


Code: 10/30/2017 9:22 AM Windows Error Reporting Fault bucket 0x1a_41792_nt!MiDeleteVirtualAddresses, type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 41c23f59-ef64-49be-8dec-dd6be9dd7d4d Problem signature: P1: 1a P2: 41792 P3: ffffe0814c73be00 P4: 5f0000 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-10484-01.dmp \\?\C:\WINDOWS\TEMP\WER-12468-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4074.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4083.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4094.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_95fec27165ff8ee84202c81787af7ddb8f20d9_00000000_cab_0e48bc7a Analysis symbol: Rechecking for solution: 0 Report Id: 32eba8e3-001d-449f-bd22-c244ace57b2e Report Status: 268435456 Hashed bucket:10/30/2017 9:22 AM Windows Error Reporting Fault bucket 0x1E_c0000005_R_ntfs!NtfsCommonCleanup, type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 62e73fa8-1a10-4b5e-acda-245a1b42f3eb Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8023f507323 P4: 0 P5: 170018 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-11046-01.dmp \\?\C:\WINDOWS\TEMP\WER-22890-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A52.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A62.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A73.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_4484dedc24fc7c8e1e8cbecefaa4875c39d69a4_00000000_cab_0e488685 Analysis symbol: Rechecking for solution: 0 Report Id: 2fe3551d-5d2c-4509-b50f-3bd351537c05 Report Status: 268435456 Hashed bucket:10/30/2017 9:22 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 1a P2: 41792 P3: ffffe0814c73be00 P4: 5f0000 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-10484-01.dmp \\?\C:\WINDOWS\TEMP\WER-12468-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4074.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4083.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4094.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_95fec27165ff8ee84202c81787af7ddb8f20d9_00000000_cab_034c4093 Analysis symbol: Rechecking for solution: 0 Report Id: 32eba8e3-001d-449f-bd22-c244ace57b2e Report Status: 4 Hashed bucket:10/30/2017 9:05 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8023f507323 P4: 0 P5: 170018 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-11046-01.dmp \\?\C:\WINDOWS\TEMP\WER-22890-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A52.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A62.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A73.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_4484dedc24fc7c8e1e8cbecefaa4875c39d69a4_00000000_cab_03486a72 Analysis symbol: Rechecking for solution: 0 Report Id: 2fe3551d-5d2c-4509-b50f-3bd351537c05 Report Status: 4 Hashed bucket:[/quote]

 

Yes this is strange...
Maybe I should wait for other BSODs that might show misbehaving drivers ?

 

If you wait it may take a while to find the misbehaving driver.
If you use windows driver verifier there will be multiple mini dumps to debug.

 

Hello,

It's unfortunately not a closed case...
I ran the driver verifier for one month with the recommanded parameters from your forum, and I got absolutely no BSOD.
I stopped the driver verifier since, and the laptop is moderately stable. It means that I rarely get a BSOD (maybe once a week), but as soon as I stress it with prime95 it crashes.
So I didn't get any lead with the driver verifier.
Do you have any idea of what I could look for now?

 

1) Please post a new zip now and whenever there is a BSOD:
Language - Add, Remove, and Change in Windows 10 General Tips Tutorials
BSOD - Posting Instructions - Windows 10 Forums
2) Also post a share link with memory dump file:
C:\Windows\MEMORY.DMPUse file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

 

Personally, if it lets you reset the unit and BSOD's after then it gotta be something installed.

Are you installing any programs at all after install?

If it a store brought unit it will have loads and loads of preinstalled garbage including anti virus programs and old drivers so best to start there.

 

Hello!

So here are new results.
First, I did a fresh install through Windows 10 menu: delete the application, but keep the files and Windows metro apps & settings. I did get a BSOD. You can get here the zip and the memory dump:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Then I did a full reset of the laptop, again using the Windows 10 settings: delete all applications and files, reinstall from scratch. No 3rd party drivers or anything. I just copied Prime95 and your tool in order to post the BSOD I still have with a really fresh install:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

I didn't expect to get a BSOD with a new Windows install...

I didn't install anything special. I did install Windows 10 from a Microsoft iso, then I installed the Lenovo system update app which helps getting important updates (especially BIOS and critical updates). This laptop got a few useless with Windows 7 but Lenovo tends to use less bloatware than before (at least on their professional laptops range).

 

Please run this version of the log collector and post a zip into the thread for troubleshooting:
log collector v2-beta08.zip


Update this driver: igdkmd64.sys
Intel Graphics driver igfx




Updating a driver: Updating a driver. - Microsoft Community


igdkmd64.sys
Intel Graphics driver
Drivers & Software




Code: igfx igfx igfx Kernel Manual Running OK TRUE FALSE 20,480 5,287,936 0 9/29/2016 4:43:27 PM C:\WINDOWS\system32\DRIVERS\igdkmd64.sys 8,192[/quote]
Code: Name Intel(R) HD Graphics 4600 PNP Device ID PCI\VEN_8086&DEV_0416&SUBSYS_220E17AA&REV_06\3&B1BFB68&0&10 Adapter Type Intel(R) HD Graphics Family, Intel Corporation compatible Adapter Description Intel(R) HD Graphics 4600 Adapter RAM 1.00 GB (1,073,741,824 bytes) Installed Drivers igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll Driver Version 20.19.15.4531 INF File oem70.inf (iHSWM_w10 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 60 hertz Bits/Pixel 32 Memory Address 0xF0000000-0xF03FFFFF Memory Address 0xE0000000-0xEFFFFFFF I/O Port 0x0000FFC0-0x0000FFFF IRQ Channel IRQ 4294967288 Driver c:\windows\system32\drivers\igdkmd64.sys (20.19.15.4531, 7.61 MB (7,974,896 bytes), 11/23/2016 12:41 AM)[/quote]

 

Hi Zbook,

As requested I ran your log collector version several times:

• 12h59: a BSOD just happened with the previous Intel driver
• 14h22: Intel driver uninstall + restart, then a new BSOD
• 14h46: New Intel driver installed, then a new log collector run (no BSOD yet)

You can find them in the post attached zips.

Have a nice day,

 

There was 1 misbehaving hardware driver:
Netwbw02
Netwbw02.sys Tue Oct 31 09:45:40 2017 (59F88C94)
NETwNb64 ___ Pilote de carte In ___ 10/31/2017 3:45:40 PM C:\WINDOWS\system32\drivers\Netwbw02.sys

Please update this driver.
If there are no BSOD in the next 36 hours then turn off windows driver verifier.

Code: Name [00000002] Intel(R) Dual Band Wireless-AC 7260 Adapter Type Ethernet 802.3 Product Type Intel(R) Dual Band Wireless-AC 7260 Installed Yes PNP Device ID PCI\VEN_8086&DEV_08B2&SUBSYS_C2708086&REV_83\4&2252D3DE&0&00E1 Last Reset 2/3/2018 2:44 PM Index 2 Service Name NETwNb64 IP Address 192.168.1.11, fe80::2d0b:db43:6fdd:2024, 2a01:cb1c:7c3:4e00:ac32:8c0a:70b0:2779, 2a01:cb1c:7c3:4e00:2d0b:db43:6fdd:2024 IP Subnet 255.255.255.0, 64, 128, 64 Default IP Gateway 192.168.1.1, fe80::8e10:d4ff:fe7d:ef9c DHCP Enabled Yes DHCP Server 192.168.1.1 DHCP Lease Expires 1/2/1970 1:00 AM DHCP Lease Obtained 1/1/1970 1:00 AM MAC Address ‪90:2E:1C:33:E8:8E‬ Memory Address 0xF0400000-0xF04FFFFF IRQ Channel IRQ 4294967293 Driver c:\windows\system32\drivers\netwbw02.sys (18.33.11.2, 3.36 MB (3,521,032 bytes), 10/10/2017 8:03 PM)[/quote]