BSOD Multiple Times

Page 1 of 4 123 ... LastLast

  1. Posts : 20
    Windows 7 Home Premium x64
       #1

    BSOD Multiple Times


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


  2. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #2

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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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. RAM - Test with Memtest86+

       Note
    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.
      My Computer


  3. Posts : 20
    Windows 7 Home Premium x64
    Thread Starter
       #3

    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?
      My Computer


  4. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #4

    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. Driver Verifier - Enable and Disable

       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.
      My Computer


  5. Posts : 20
    Windows 7 Home Premium x64
    Thread Starter
       #5

    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?
      My Computer


  6. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #6

    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.
      My Computer


  7. Posts : 20
    Windows 7 Home Premium x64
    Thread Starter
       #7

    Here´s the newest log.
      My Computer


  8. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #8

    Finally something has given.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C2, {9b, 0, 10, fffff880018c2503}
    
    *** 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 )
    
    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.

    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.
      My Computer


  9. Posts : 20
    Windows 7 Home Premium x64
    Thread Starter
       #9

    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.
      My Computer


  10. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #10

    Do you still have Driver Verifier enabled?
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 16:03.
Find Us