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

dossa51 · 07 Dec 2014

Hi all,

A friend built me a gaming computer three years ago (most of the specs should be in my profile) and it crashes every so often. Sometimes a few times in a single day, sometimes once a month.

This can happen in the middle of a game, when browsing the Internet or when the computer is simply sitting idle. I have not noticed any correlation at all over the years in terms of what causes it.

I am a relative novice and my research into the problems led me to bluescreenview and the analysis of the BSODs for any correlation within the codes themselves, but this goes far beyond my capability and I'm hoping that there are people on here who might be able to scrutinize my dump files and help me out. All I have learned from looking at the data is that most crashes are 109s with the occasional 3b and the crash address seems to always be at ntoskrnl.exe+75bc0.

I have run both memtest and the Windows memory diagnostics several times over the years and my RAM has passed every time.

Although this is something I can live with, a friend reminded me the other day that I don't have to, and that computers should never crash.

Any help would be most appreciated - I will co-operate in any way possible. I followed the instructions on the sticky thread at the top of this forum so all of the relevant information should be attached.

Thanks.

Golden · 07 Dec 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d898c46a09, b3b7465eeb423947, fffff80003400920, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

I realise you've run some memory tests, but to thoroughly test RAM you need to do it as follows:

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Reference this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+

Try that first. If it comes back clean, we can go hard-core and try soemthing different.

dossa51 · 08 Dec 2014

Thanks for the quick reply.

I'll run memtest overnight tonight and post the results tomorrow.

dossa51 · 09 Dec 2014

As much as I would have liked the relatively simple solution of corrupt memory, after 18 hours and 16 passes nothing had been flagged by Memtest (please see attached image). What should I try next?

Thanks

Golden · 10 Dec 2014

Please do the following:

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

dossa51 · 15 Dec 2014

Hi again,

I followed the instructions you posted, which were very clear and easy to follow by the way.

I ran the program from 4pm yesterday until just now (25 hours total) and no crash occurred. The commercial program linked to verifier.exe did a garish popup that suggested 18 drivers were "out of date or corrupt" but this was Tweakbit Driver Updated rather than verifier.exe, so I assume this is irrelevant.

What do you suggest next?

dossa51 · 15 Dec 2014

Ha ha that's more like it. Less than an hour later and I hear a crash (the speakers were on) while I'm out the room. Oddly it didn't get picked up by bluescreenview but is hopefully in this dump.

dossa51 · 15 Dec 2014

And another, they're coming thick and fast now... joy! I was at the screen this time. It was my old friend the 109. Log attached.

dossa51 · 03 Jan 2015

I can't find the forum rules regarding 'bumping' but as I have followed all instructions thusfar and fairly promptly at that, I hope it's ok to 'bump' this post after two weeks with no reply.

Lots of people post on this forum and posts disappear quickly. Regardless, most issues are solved, whilst mine remains unsolved.

Any further help would be appreciated.

Thanks :)

Golden · 03 Jan 2015

Sorry that your thread slipped through the cracks - it happens sometimes due to the volume of BSOD threads.

dossa51 said:

The commercial program linked to verifier.exe did a garish popup that suggested 18 drivers were "out of date or corrupt" but this was Tweakbit Driver Updated rather than verifier.exe, so I assume this is irrelevant.

Hold on a minute - there is no commercial software linked to Driver Verifier. Driver Verifier is a Microsoft program, not 3rd party one, so I'm not sure what you ran to get that.

Never install any drivers recommend by 3rd party programs, unless specifically advised to do so.

I'll look at your .dmp files shortly, but for now ensure that there are NO 3rd party driver programs, tune-up utilities etc. installed.

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

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

Memtest results