Page 2 of 2 FirstFirst 12
  1.    3 Weeks Ago #11
    Join Date : Oct 2017
    Posts : 10
    Windows 10 build 1709
    Thread Starter

    Hi zbook,
    Thank you for your post.
    I took the time to go through all the steps. Here are all the relevant outputs and screenshots in the attached zip file:
    BSOD troubleshot steps.zip

    What I could see with HDTune is there is a SMART error with my SSD. I don't know if it's related. I remember I hotswaped it a few times with a Sata->USB cable so it might be the explanation.

    You're right memtest86+ is so damn long to run ! I stopped after 11 passes (33 hours of testing), with no error (phew). I only tested with both sticks since there was no visible error. Should I still try each stick separately?

    I also updated the Intel wifi driver. I remember I already did it previously to my first post here. but I was still having the issue. Well, guess what ? Now I can run prime95 for 30min with any driver without BSOD. I didn't change anything else, except a windows chkdsk and having changed the system language from French to English...

    Can you tell me what you think about this report ? In the meantime, I'll let the laptop run prime95 with the new Intel drivers for a few hours...

    Have a nice day!
    Last edited by grospoulet; 3 Weeks Ago at 04:09.
      My ComputerSystem Spec
  2.    3 Weeks Ago #12
    Join Date : Apr 2017
    Posts : 8,627
    windows 10 professional version 1607 build 14393.969 64 bit

    Nice progress.
    How come the C: chkdsk report was in a foreign language and the D: was in English?



    The RAM testing passed with 11 passes 0 errors 16 GB RAM.
    With a pass testing both at the same time there is no need to test them 1 at a time.
    The ST drive looks good.
    The Samsung drive displayed 1 problem in the health report and had corruption on the drive.
    The operating system integrity testing passed.

    Please translate:
    Correction des erreurs dans l’attribut BITMAP de la table de fichiersmaītres (MFT).
    Correction des erreurs dans le carte du volume.

    Has it been 1 or 2 days since you updated the driver?
    If there are any new BSOD please post a new zip.

    During the Windows upgrade period some of our Windbg commands are not working. So the debugging can be incomplete or complete depending on whether the commands can or cannot be processed.

    Use the computer under typical use and see if there are any new BSOD.

    For the drives:
    Make a brand new restore point.
    Download and install Macrium:
    Macrium Software | Macrium Reflect Free
    Make a backup image of each drive and place the backup on another drive or into the cloud.
    Backup all of the files on the Samsung drive.
    Every month revise the Macrium backup image.
    If you add files frequently then update the backup image weekly or more frequently.

    Download and install the Intel Processor Diagnostic Tool


    When the test completes please use the Microsoft snipping tool to post an image into the thread.


    Download IntelĀ® Processor Diagnostic Tool:
    Download IntelĀ® Processor Diagnostic Tool
    The IntelĀ® Processor Diagnostic Tool:
    The IntelĀ® Processor Diagnostic Tool
      My ComputerSystem Spec
  3.    3 Weeks Ago #13
    Join Date : Oct 2017
    Posts : 10
    Windows 10 build 1709
    Thread Starter

    Thanks !

    Actually chkdsk on the C: drive needed to do it during boot, so I guess Windows went back to its default language, which is French on my laptop. Even if I change the system language, some things such as the boot manager won't change.

    In the text file I also put a translation I did myself, I'm not sure if these are the exact words but it should match more or less the English version :

    -------------------------------------------------------------------

    Checking file system on C:The type of the file system is NTFS.
    Volume label is SSD.

    Stage 1: Examining basic file system structure ... 2892288 file records processed. File verification completed. 46544 large file records processed. 0 bad file records processed.

    Stage 2: Examining file name linkage ... 3626232 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.

    Stage 3 : Examining security descriptors ...Cleaning up 24797 unused index entries from index $SII of file 0x9.Cleaning up 24797 unused index entries from index $SDH of file 0x9.Cleaning up 24797 unused security descriptors.CHKDSK is compacting the security descriptor fluxSecurity descriptor verification completed. 366973 data files processed. CHKDSK is verifying Usn Journal... 37892840 USN bytes processed. Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ... files processed. File data verification completed.

    Stage 5: Looking for bad, free clusters ... 272116427 free clusters processed. Free space verification is complete.Correcting errors in the master files BITMAP attribute table (MFT).Correcting errors in the volume card (not sure about the translation ?).Windows has scanned the file system.No further action is required. 486949252 KB total disk space. 238301048 KB in 2290768 files. 919556 KB in 366976 indexes. 0 KB in bad sectors. 3036452 KB in use by the system. 65536 KB ocupied by the log file. 244692196 KB available on disk. 4096 bytes in each allocation unit. 121737313 total allocation units on disk. 61173049 allocation units available on disk.Internal information :00 22 2c 00 4a a4 26 00 30 2c 38 00 00 00 00 00 .",.J.&.0,8.....a4 08 00 00 7d 00 00 00 00 00 00 00 00 00 00 00 ....}...........

    Windows finished verifying your drive.Please wait during computer restart.

    -------------------------------------------------------------------

    For the driver, unfortunately I forgot to update it before running memtest86+. So I updated it this morning right after having stopped memtest86+ and then I was running prime95 (for 2 hours now).

    I just created a restore point. Is the macrium step really required if I don't mind loosing my data ? Actually all my important data on this laptop is replicated using various services (Dropbox, Syncthing), I'm safe if the laptop explodes or gets stolen. I also created a "Windows 7" backup on the SSD just in case, after my fresh install, to avoid loosing time and have an faster recovery process. But this backup is on the SSHD. I'm on a trip and I don't have any other drive with me for now.

    Here is the result with the Intel processor diagnostic tool:

    Click image for larger version. 

Name:	Intel processor diagnostic tool.png 
Views:	1 
Size:	218.8 KB 
ID:	160503

    I'll keep using the computer under typical use and run prime95 when I'm away.
    Last edited by grospoulet; 3 Weeks Ago at 05:27. Reason: chkdsk minimal formatting
      My ComputerSystem Spec
  4.    3 Weeks Ago #14
    Join Date : Apr 2017
    Posts : 8,627
    windows 10 professional version 1607 build 14393.969 64 bit

    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.
      My ComputerSystem Spec
  5.    2 Weeks Ago #15
    Join Date : Oct 2017
    Posts : 10
    Windows 10 build 1709
    Thread Starter

    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
    Thank you very much for your help, I should have come here months ago.

    Have a great day!
      My ComputerSystem Spec
  6.    2 Weeks Ago #16
    Join Date : Apr 2017
    Posts : 8,627
    windows 10 professional version 1607 build 14393.969 64 bit

    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.
      My ComputerSystem Spec
  7.    2 Weeks Ago #17
    Join Date : Oct 2017
    Posts : 10
    Windows 10 build 1709
    Thread Starter

    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...
      My ComputerSystem Spec
  8.    2 Weeks Ago #18
    Join Date : Apr 2017
    Posts : 8,627
    windows 10 professional version 1607 build 14393.969 64 bit

    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.
    http://www.resplendence.com/whocrashed
    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:
    Last edited by zbook; 2 Weeks Ago at 10:31.
      My ComputerSystem Spec
  9.    2 Weeks Ago #19
    Join Date : Oct 2017
    Posts : 10
    Windows 10 build 1709
    Thread Starter

    Yes this is strange...
    Maybe I should wait for other BSODs that might show misbehaving drivers ?
      My ComputerSystem Spec
  10.    2 Weeks Ago #20
    Join Date : Apr 2017
    Posts : 8,627
    windows 10 professional version 1607 build 14393.969 64 bit

    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.
      My ComputerSystem Spec

 
Page 2 of 2 FirstFirst 12


Similar Threads
Thread Forum
Reset vs fresh Reinstall from Media
Hi, What is the difference of doing a reset vs. wiping all partitions and reinstalling from media? Assume it's the reset that does not preserve user files. Of course the user has backed-up important files. Is there a difference in action, or...
Installation and Upgrade
Random BSOD and GPU Driver Crash (go on for 1 year, can'f find a fix)
Hello everybody, I'm struggling for like 1 year with instability of my system. Those are my specs: MOBO:MSI H170 M3 Gaming GPU: GTX 970 EVGA SSC RAM: Corsair Vengance DDR4 2133MHZ 8GBX2 PSU: EVGA G3 650W CPU: Intel i7@6700 + 212 Hyper EVO...
BSOD Crashes and Debugging
fresh win10 x64 pro install random freezing, black screen, no bsod
fresh install of win10 x64 pro from usb using the media creator tool. First off, I upgraded from win7 to win10, and the freezes with black screens started. I reformated, did a fresh install from USB, same thing happened. I assumed it...
BSOD Crashes and Debugging
Win 10 automatically activated on Mac after fresh reset? how?
I had windows 10 activated on my mac (via bootcamp), then I completely deleted the bootcamp partition (to expand it) and reinstalled win 10. Once installed, Windows automatically activated citing "digital entitlement". How does this work? ...
Windows Updates and Activation
BSOD loop on boot from fresh Win 10 upgrade over fresh Win 7 install
This is on an old eMachines M6805 laptop that originally came with XP 32-bit. I put a fresh install of Windows 7 32-bit on it which ran fine. I then upgraded that to Windows 10 32-bit. The first time it booted up I was able to log in but got a...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:05.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums