Solved BSOD Multiple Times

[Jorediej]

Hi there,
I received a BSOD multiple Times and I don't know what cased it.
Can you please help me out?

 

[Boozad]

There is only one dump in your logs, that is showing a STOP 0x109 which denotes a Critical Structure Corruption.

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

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89d408697, b3b7465eefbec4f9, fffff8800336f640, 3}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

It's showing that there's corruption to the Global Descriptor Table which more than likely is down to a failing RAM module.

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89d408697, Reserved
Arg2: b3b7465eefbec4f9, Reserved
Arg3: fffff8800336f640, Failure type dependent information
Arg4: 0000000000000003, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

View attachment 353131

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Post back with the results.

 

[Jorediej]

Thanks for your reply.
I did the full test (8 passes) and it didn´t came up with any errors.
What else could it be?

 

[Boozad]

As there's only one dump in your logs (which isn't giving anything away at all) I'm doing a bit of guesswork here.

Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Enable Driver Verifier but only enable these options:
Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

   Warning

Make a System Restore point before enabling Driver Verifier.

   Note

Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

If you do receive any more BSODs with DV enabled, run the DM Log Collector again and upload the new logs.

 

[Jorediej]

I´ve followed your instructions and enabled the Driver Verifier and restarted my computer.
As soon as I did, I immediately received a BSOD and had to restore my computer to an earlier point.
After that I ran the dm log collector again and this is the log I got.

Besides this log I also found another log which I made earlier, maybe this contains a bit more information.
I've put them both in the attachments. I also noticed that this BSOD appears after I installed and used the software Bluestacks, maybe this causes the problem?

 

[Boozad]

Unfortunately the latest log is completely empty so there's nothing new to investigate. Can you run the log collector again to see if it catches the latest dumps.

 

[Jorediej]

Here´s the newest log.

 

[Boozad]

Finally something has given.

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

Use !analyze -v to get detailed debugging information.

BugCheck C2, {9b, 0, 10, fffff880018c2503}

[COLOR=Red][B]*** WARNING: Unable to verify timestamp for Neo_0091.sys
*** ERROR: Module load completed but symbols could not be loaded for Neo_0091.sys
Probably caused by : Neo_0091.sys ( Neo_0091+116d )[/B][/COLOR]

Followup: MachineOwner

This belongs to SoftEther VPN. I recommend uninstalling that software and testing the system.

Also I missed this first time round.

Uninstall Daemon Tools, a proven cause of BSODs.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and perform the following steps.
3. Double click the executable to open it.
4. Click the button shown below.

View attachment 353338

If the button it is grayed out as shown in the image, there is no more SPTD installation on your system and you can just close the window.

 

[Jorediej]

I did all that. However, there wasn't a checkbox when installing the SPTD.
I still keep getting those BSOD's.
Here's the log.

 

[Boozad]

Do you still have Driver Verifier enabled?

 

[Jorediej]

Yes, when I enabled it I immediately get another BSOD (just like the first time).
After that I had to restore my PC again.
No new log was found for the dm collector.
I'm kind off lost at the moment..

 

[Boozad]

If you've uninstalled DaemonTools and SoftEtherVPN, disable Driver Verifier and test the system for stability.

 

[Jorediej]

Unfortunately it´s not fixed yet.
Here´s the newest log.

 

[Jorediej]

It's been 4 days now since I posted my last message and haven't heard back from you. I still experience the same issues. I'm getting the feeling that the problem is hardware.

 

[Boozad]

There's nothing in the last .zip at all, it's completely empty. I do apologise for not getting back sooner but I've been doing other things as well as trying to help numerous other people in my spare time.

 

[Jorediej]

The PC hasn´t created any new minidumps since the 23th. I tried enabling the minidump again (http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.htm) but didn't receive any new dump yet. I will check again tomorrow and will let you know if it has created one.

 

[Jorediej]

Nope.. I still receive BSOD's but I can't find any new logs.
Here's the log collector file.

 

[Boozad]

Yeah there are still no new dumps unfortunately. Have a quick read through this http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html to check to see if your system's set to write dumps when BSODs occur.

 

[Jorediej]

As I stated in my post of yesterday I already followed this procedure althought no new log's found. I checked it again using all the different methods and the computer says that Small memory dump is enabled. Could there be another reason the PC doesn't give any BSOD logs?

 

[Boozad]

Try this:

Follow these steps:

1. Configure Windows to create minidumps:
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

2. Set the paging file on C: to be the same size as the physically installed RAM:
Virtual Memory Paging File - Change

3. Set the Windows Error Reporting service to MANUAL:
http://www.sevenforums.com/tutorials/2495-services-start-disable.html

4. Test to see that dump files are created:
- Open Windows Task Manager
- Navigate to the Processes tab
- Right-click on explorer.exe, and click Create Dump File

- Note the location of the saved file

- Check that location and confirm that explorer.dmp exists