Windows 10: Crash/Freeze Seems Random after adding a second USB external NTFS HDD

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 20,975
    windows 10 professional version 1607 build 14393.969 64 bit
       09 Mar 2018 #21

    Windows driver verifier is a tool that stimulates drivers to find misbehaving drivers.
    It will repetitively produce BSOD until misbehaving drivers are fixed or until the tool is turned off.

    When a misbehaving driver is found it will be uninstalled and then the tool will be restarted to find the next misbehaving driver. Drivers can be reinstalled after they are uninstalled or after all drivers have been uninstalled.
    The end results should be the same.

    After each BSOD run the beta log collector and post a new zip for troubleshooting.
    The tool will be run for 48 hours and after the last BSOD for an additional 36 hours.
    If there are no more BSOD the tool will be turned off and that will conclude the use of the tool to find misbehaving drivers.

    During the use of the tool the computer may become sluggish or the boots may be slow.
    If there are problems the number of active tests can be modified to reduce the sluggishness or slower boots.

    Use this link for the customized test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Use this link for the methods to turn off Windows driver verifier:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    All methods to turn off the tool are performed using the Windows advanced troubleshooting menu.
    The methods used to turn off Windows driver verifer should be done in order advancing to the the next step only if the prior step fails to turn off the tool.
    a) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
    verifier /reset
    b) command prompt > Administrator X:\Windows\system32\cmd.exe > X:\Sources> type:
    verifier /bootmode resetonbootfail
    c) system restore
    System restore is used as the last option as very often the dump files are lost and little progress is made in the troubleshooting

    Once you are comfortable with the methods to turn off the tool you can start using it.
    Let us know whether the problem with freezing and crashes gets better, worse, or the same after fixing the misbehaving drivers.
      My ComputerSystem Spec

  2.    09 Mar 2018 #22

    zbook said: View Post
    Windows driver verifier is a tool that stimulates drivers to find misbehaving drivers.
    It will repetitively produce BSOD until misbehaving drivers are fixed or until the tool is turned off.

    When a misbehaving driver is found it will be uninstalled and then the tool will be restarted to find the next misbehaving driver. Drivers can be reinstalled after they are uninstalled or after all drivers have been uninstalled.
    The end results should be the same.

    After each BSOD run the beta log collector and post a new zip for troubleshooting.
    The tool will be run for 48 hours and after the last BSOD for an additional 36 hours.
    If there are no more BSOD the tool will be turned off and that will conclude the use of the tool to find misbehaving drivers.

    During the use of the tool the computer may become sluggish or the boots may be slow.
    If there are problems the number of active tests can be modified to reduce the sluggishness or slower boots.

    Use this link for the customized test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Use this link for the methods to turn off Windows driver verifier:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    All methods to turn off the tool are performed using the Windows advanced troubleshooting menu.
    The methods used to turn off Windows driver verifer should be done in order advancing to the the next step only if the prior step fails to turn off the tool.
    a) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
    verifier /reset
    b) command prompt > Administrator X:\Windows\system32\cmd.exe > X:\Sources> type:
    verifier /bootmode resetonbootfail
    c) system restore
    System restore is used as the last option as very often the dump files are lost and little progress is made in the troubleshooting

    Once you are comfortable with the methods to turn off the tool you can start using it.
    Let us know whether the problem with freezing and crashes gets better, worse, or the same after fixing the misbehaving drivers.
    I started the verifier, checked all boxes as appropriate and rebooted. It did not take long before it blue screened & collected logs for about a minute till 100%, then I rebooted again, and same thing happened. Both times it did not get far enough to get logged on to Windows, so I could not collect any logs to post. Third time, it only gave me an option to repair. Now it is attempting repair, from what I assume is the most recent recovery point. Hopefully it comes back soon...

    lrw
      My ComputerSystem Spec


  3. Posts : 20,975
    windows 10 professional version 1607 build 14393.969 64 bit
       09 Mar 2018 #23

    After each BSOD > open the windows advanced troubleshooting menu > turn off windows driver verifier using the steps in the link startup repair: (verifier /reset ) > return to the desktop > run beta log collector > post zip into the thread

    In the BSOD window it should display a bugcheck. At times it may display the misbehaving driver in the form *.sys
    If you see the misbehaving driver > record it > post it into the thread
      My ComputerSystem Spec

  4.    09 Mar 2018 #24

    zbook said: View Post
    After each BSOD > open the windows advanced troubleshooting menu > turn off windows driver verifier using the steps in the link startup repair: (verifier /reset ) > return to the desktop > run beta log collector > post zip into the thread

    In the BSOD window it should display a bugcheck. At times it may display the misbehaving driver in the form *.sys
    If you see the misbehaving driver > record it > post it into the thread
    I don't think it gave me any option for bug check when I got the bluescreen. I'll take a photo next time but it really dies fast, before any menus or clickable stuff is available. All I could do was power cycle which repeated until the only option was recovery.

    I collected the logs anyway, just in case: LARRY-PC-Fri_03_09_2018_120201_72.zip

    lrw
    Last edited by lrw; 09 Mar 2018 at 15:10. Reason: adding logs
      My ComputerSystem Spec


  5. Posts : 20,975
    windows 10 professional version 1607 build 14393.969 64 bit
       09 Mar 2018 #25

    In the left lower corner search type: system > open system control panel > under startup and recovery > click settings > make sure that automatically restart is un-checked.
    With automatically restart unchecked it should display the BSOD window.
      My ComputerSystem Spec

  6.    09 Mar 2018 #26

    zbook said: View Post
    In the left lower corner search type: system > open system control panel > under startup and recovery > click settings > make sure that automatically restart is un-checked.
    With automatically restart unchecked it should display the BSOD window.
    OK, done. I'll start the process again.

    lrw
      My ComputerSystem Spec


  7. Posts : 20,975
    windows 10 professional version 1607 build 14393.969 64 bit
       09 Mar 2018 #27

    The misbehaving driver was: hecix64.sys

    Update the Intel management engine interface driver: hecix64.sys

    Updating a driver. - Microsoft Community

    Code:
    meix64	Intel(R) Management Engine Interface	c:\windows\system32\drivers\hecix64.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes
      My ComputerSystem Spec

  8.    09 Mar 2018 #28

    I just noticed in the driver verification choices, there's a lot of AVAST drivers. I thought those should have been removed with the remove tool? Click image for larger version. 

Name:	verifier avast.jpg 
Views:	4 
Size:	119.3 KB 
ID:	180219

    lrw
      My ComputerSystem Spec


  9. Posts : 20,975
    windows 10 professional version 1607 build 14393.969 64 bit
       09 Mar 2018 #29

    That indicates the drivers were not uninstalled.
    Please use the uninstall tool :
    Avast Uninstall Utility | Download aswClear for Avast Removal
      My ComputerSystem Spec

  10.    09 Mar 2018 #30

    zbook said: View Post
    That indicates the drivers were not uninstalled.
    Please use the uninstall tool :
    Avast Uninstall Utility | Download aswClear for Avast Removal
    I did use that tool. When my system is back, I'll try it again. Would that be why the verifier dies such an instant death?

    lrw
      My ComputerSystem Spec


 
Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
Read more: In a throwback to the '90s, NTFS bug lets anyone hang or crash Windows 7, 8.1 | Ars Technica
I have a 2TB disk in USB 2 housing which I formatted on my desktop computer as an NTFS volume. It is still recognised by this machine as an NTFS volume even when I plugged it in just now. However on my laptop it is just seen as a raw volume. I...
NTFS vs. ExFAT for external SSD in Performance & Maintenance
Hi, I have a new SSD Drive (128GB) and I was experiencing some poor performance. I read in another older thread about it and I want to post here my findings. Windows has a very good utility to check performance of Drives : Elevated Comand Prompt...
Converting RAW external HDD to NTFS? in Drivers and Hardware
My toshiba 1tb external hard drive currently says it is a raw file system and i cant seem to format it no matter what i do. I dont care for what is inside (only one word file) but i just want to be able to use it again. Is there anyway i can format...
Random Crash/Freeze on Build 10130 in BSOD Crashes and Debugging
Hello everyone. I have been running the Windows 10 preview for the last few months and other than a driver issue here or there, did not experience any real problems. However, with the last update to build 10130, I have been experiencing a random...
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 01:00.
Find Us