Page 5 of 5 FirstFirst ... 345
  1.    23 Sep 2017 #41
    Join Date : Apr 2016
    Posts : 53
    win 10 64 bit home
    Thread Starter

    Hi, here you go :

    CCleaner enclosed. Did not run, just a screenshotCCleaner screenshot Sept 23.docx
    Memory dump file : Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
    Who crashed file :Who crashed Sept 23.docx
    HWInfo screenshot :HW Info Sept 23.docx

    Thanks for everything as usual
      My ComputerSystem Spec
  2.    23 Sep 2017 #42
    Join Date : Apr 2017
    Posts : 8,834
    windows 10 professional version 1607 build 14393.969 64 bit

    For Whocrashed were you able to perform a crash dump test?

    Please post an image of current startup and recovery settings:
    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 > post an image into the thread
    Perform another crash dump test > analyze > post results into thread.

    In post #27 there is a Dell link. The bios is 2010 and the current bios is 2014.
    When possible please update the bios.
      My ComputerSystem Spec
  3.    23 Sep 2017 #43
    Join Date : Apr 2016
    Posts : 53
    win 10 64 bit home
    Thread Starter

    Yes, WhoCrashed doesnt seem to show the BSOD on Friday. Latest log enclosed.Crash Dump Analysis Sept 23.docx
    System setting screenshot enclosed. (Hop[efully you can see the screenshot below)
    Re BIOS. I've updated the latest one which is A04 several times, and it seems I ahve the latest one. Not sure why show 2010 vs 2014

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	556.2 KB 
ID:	154737
      My ComputerSystem Spec
  4.    23 Sep 2017 #44
    Join Date : Apr 2017
    Posts : 8,834
    windows 10 professional version 1607 build 14393.969 64 bit

    For startup and recovery settings:
    1) un-check automatic restart (this will give you unlimited time to view the stop code, and sometimes the misbehaving is displayed when using windows driver verifier)
    2) change the dump file to automatic so that it displays memory dump

    3) perform a whocrashed test dump now (tools > crash dump test > type: ACCEPT
    4) then click Analyze to see the result of the crash dump test
    5) post the whocrashed results into the thread
    6) post a new zip into the thread:
    BSOD - Posting Instructions - Windows 10 Forums
      My ComputerSystem Spec
  5.    24 Sep 2017 #45
    Join Date : Apr 2016
    Posts : 53
    win 10 64 bit home
    Thread Starter

    Hi, here you go :

    WhoCrashed results:WhoCrashed Sept 24.docx
    Diag Zip file :DAD-PC-24_09_2017_131923_60.zip

    Thanks as usual
      My ComputerSystem Spec
  6.    24 Sep 2017 #46
    Join Date : Apr 2017
    Posts : 8,834
    windows 10 professional version 1607 build 14393.969 64 bit

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

    There are 3 methods that are used to turn off Windows driver verifier and they are all done using the Windows advanced troubleshooting menu.
    After each BSOD you will view the window with stop code typically driver verifier detected violation. Sometimes it will display the misbehaving driver. If you see a driver displayed in the form *.sys record that driver and post it into the thread.
    Once there has been a BSOD there is typically a mini dump created that is later debugged to find the misbehaving driver.
    The first 2 methods for turning off Windows driver verifier will maintain the mini dump.
    The third method typically leads to a loss of the mini dump and little progress is made in the troubleshooting.

    These are the 3 methods:
    1) windows advanced troubleshooting > select startup options (not startup repair) > select #6 safe mode with command prompt > allow restart > type:
    verifier /reset
    2) windows advanced troubleshooting > select command prompt > opens Administrator X:\Windows\system32.cmd.exe > type:
    verifier /bootmode resetonbootfail
    3) windows advanced troubleshooting > restore

    The commands above should always be used in the order above. Only moving from one to the other if the command fails to turn off windows driver verifier.

    Windows driver verifier may cause some sluggishness of the computer while in use.

    Once there are no longer any BSOD windows driver verifier will be run for an additional 36 hours while the computer is used under typical use. If there are no more BSOD then troubleshooting will be completed and windows driver verifier will be turned off.

    Use the settings in this link to customize the testing parameters:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Use this link to learn the 3 methods to turn off windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

    Download and install Bluescreenview:
    Blue screen of death (STOP error) information in dump files.

    After each BSOD you will view both Whocrashed and Bluescreenview.
    Then uninstall and reinstall the misbehaving driver.

    Post a new zip into the thread and we will guide you through the process:
    BSOD - Posting Instructions - Windows 10 Forums
      My ComputerSystem Spec
  7.    27 Sep 2017 #47
    Join Date : Apr 2016
    Posts : 53
    win 10 64 bit home
    Thread Starter

    Thanks all, have marked it as solved.
      My ComputerSystem Spec

 
Page 5 of 5 FirstFirst ... 345


Similar Threads
Thread Forum
BSOD issues while in general use, Error: KMODE_EXCEPTION_NOT_HANDLED
I've been having very frequent BSOD's for the past 4-5 months now, I have tried as much as possible to pin-point the problem, but they still persist. I am going to take a wild guess, and say it might be memory related, although I wanted to come here...
BSOD Crashes and Debugging
BSOD KMODE_EXCEPTION_NOT_HANDLED igdkmd64.sys ERROR MESSAGE
I've been experiencing random crashes on my computer over the last couple of weeks, I believe it has something to do with my graphics card drivers (igdkmd64.sys) but the update/rollback attempts didn't help nor did completely uninstalling and...
BSOD Crashes and Debugging
Solved Kmode_exception_not_handled bsod
Hi everyone, This is my first post in this forum. I have a problem with multiple BSODs on my computer. I tried to solve the first couple of BSODs but with no luck at all. I then decided to reinstall Windows 10 on my computer but the BSODs kept...
BSOD Crashes and Debugging
KMODE_EXCEPTION_NOT_HANDLED (ETD.sys) Error
Hi Ten Forums, From past couple of days i faced an issue KMODE_EXCEPTION_NOT_HANDLED (ETD.sys) error and it restarts, after restart most of my installed software will be missing, almost will be like new user profile it look likes. Need Any...
General Support
kmode_exception_not_handled
Intermittently hitting this error on boot up. I initially got it when I upgraded from Windows 7 to Windows 10. I got the BSOD on bootup a few times and during normal use; system would go to BSOD then would reboot to desktop fine until it finally...
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 13:53.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums