Random BSODs, often 109s, usually linked to ntoskrnl.exe

Page 4 of 4 FirstFirst ... 234

  1. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #31

    Create a folder on C: called MyCrash, then reconfigure Windows to write the BSOD .dmp files to it, by using this:
    Dump File - Change Default Location

    Now rerun Driver Verifier to force a crash:

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode
      My Computer


  2. Posts : 25
    Windows 7 Professional 64 bit
    Thread Starter
       #32

    Ok, there's good news and bad news.

    The good news is that Driver Verifier did force a crash. There were a couple that didn't go to blue screens so I simply had to restart the computer and hope for more. I got two just now and photographed them.

    The bad news is that, despite making the changes you suggested, .dmp files are STILL not saving! It was in anticipation of this that I took the photographs. Hopefully these will be more useful than the last one because a driver is actually listed and this might be something we can work with.

    Please let me know what you think
      My Computer


  3. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #33

    OK. So to confirm no .dmp files in C:\MyCrash?

    Please run DM Log Collector anyway and upload the ZIP file, as the other information will help me track down the audio issue.
      My Computer


  4. Posts : 25
    Windows 7 Professional 64 bit
    Thread Starter
       #34

    Well I actually went to D:\MyCrash (my secondary drive), but that shouldn't make a difference, right? And no, there was no .dmp file there post-crash.

    DM Log attached.
      My Computer


  5. Posts : 25
    Windows 7 Professional 64 bit
    Thread Starter
       #35

    Still crashing, still not recording crashes...
      My Computer


  6. Posts : 25
    Windows 7 Professional 64 bit
    Thread Starter
       #36

    Three today now. All 109s, two of them citing CLFS.sys.
      My Computer


  7. Posts : 25
    Windows 7 Professional 64 bit
    Thread Starter
       #37

    Just had a 0x0000024, citing ntfs.sys.

    Logs still not saving, but at least it's a different code/driver.

    Variety really is the spice of life!
      My Computer


 
Page 4 of 4 FirstFirst ... 234

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:15.
Find Us