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

[Layback Bear]

Just a though; if you use any kind of clean up program you could be cleaning out your logs (mini dumps)

 

[dossa51]

Well I have Ccleaner but as far as I know nothing is cleared automatically. Plus the .dmp files are literally not there as soon as I check after a crash. Any cleanup program probably wouldn't clear anything away quite THAT quickly. No crashes since last post - will post when I get next but as things stand, no .dmp will appear

 

[dossa51]

Another crash, still no .dmp

Am happy for someone to remote connect to my system to check things out.

 

[dossa51]

Five crashes in twenty minutes. Couldn't even get on here to post about it. Dusted the inside and outside of machine, ran Windows Update and seems better, but still no codes to report as BSOD doesn't show anymore and no .dmp files are recorded. Really am tearing my hair out over this...

 

[Golden]

OK. I'm stumped. Please run the DM Log Collector Tool again and upload the ZIP file, even if it doesn't contain any .dmp files.

When you get a BSOD again, please make a note of the code as it appears on the blue screen - turn off Automatic Restarts.

 

[dossa51]

Hi again and thanks for continuing support.

Please find attached the latest DM Log Collector ZIP. There are obviously no dumps contained but might be other info that helps.

Have also unchecked the 'automatic restart' box for crashes so should hopefully be able to see the bluescreen and note info on future crashes.

Will let you know.

 

[Golden]

OK.

 

[dossa51]

First crash in almost a week. Thanks to the settings changes you recommended the bluescreen stayed there until I reset the computer manually. This was fortunate as the photo I took is the only evidence of the crash. My computer is STILL not saving .dmp files!

Picture attached - as always any help appreciated.

 

[Golden]

0x109 could be anything, its hard to say at this stage.

Please check in Services and make sure that Windows Error Reporting is set to MANUAL.

View attachment 347228

 

[dossa51]

Just checked - it is.

 

[Golden]

Create a folder on C: called MyCrash, then reconfigure Windows to write the BSOD .dmp files to it, by using this:
http://www.sevenforums.com/tutorials/204214-dump-file-change-default-location.html

Now rerun Driver Verifier to force a crash:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[dossa51]

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

 

[Golden]

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.

 

[dossa51]

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.

 

[dossa51]

Still crashing, still not recording crashes...

 

[dossa51]

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

 

[dossa51]

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!