Random BSOD's at random times on new PC

Page 1 of 2 12 LastLast

  1. Posts : 15
    Windows 7 Ultimate x64
       #1

    Random BSOD's at random times on new PC


    Hello. I built a PC two days ago and today I have had 4 BSOD's so far and I fear there will be more of them.

    Today, the 28th, I've have 4 or 5 bsods and most, if not all, have had the 0x109 stop code.
    Last edited by CrazyGuy158; 28 Oct 2012 at 08:51.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2
      My Computer


  3. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Done.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    OK, let us look ....
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a039d89915a630, b3b7465eeb9375aa, fffff80002e21fa0, 1}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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:
    So we may do two things here ....

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

    2. RAM - Test with Memtest86+
    Run memtest, for at least 8 passes. Preferably6 overnight.

    Let us know the results.
      My Computer


  5. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #5

    How come I didn't come across any errors whilst running the Windows Memory Diagnostic tool?
      My Computer


  6. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #6

    A small update to this matter.

    On the 27 of August, I had four BSOD's, and only one had the 0x109 stop code. Then I mistakenly flashed a bios upgrade where I had picked the latest bios for the rev I don't have. My motherboard comes in two revs, 1.0 and 1.1, and I have rev 1.0 but the bios was for rev 1.1. Anyways, I thought all was smooth sailing from now on, but the day after, which is today, I've had six BSOD's up until 2.57 pm.

    After the last BSOD (at 2.57pm) I cracked my PC open and checked the mobo, to find out that I had another rev than what I had flashed a bios for. I immediately booted up and flashed the right bios (the latest version), did an SFC scan which found a few corrupted files and then I uninstalled Norton.

    I haven't had a BSOD thus far, but I fear this is far from over. I'm not gonna be so quick and blame the RAM until I'm absolutely positive it is the RAM. It can very well be a driver error or some third-party program messing up, couldn't it?
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    Most probably.

    Checking your dumps, I havent got any proof to blame the RAM. It is just the usual cause, so suggested.

    The windows tool is not a very efficient one, whereas memtest is, and it does not harm.

    If it is free from ctashes ATM, wait and observe.
      My Computer


  8. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #8

    Since 2.57 pm (14.57), it's been completely crash-free. I'm going to wait and observe, and see how it is tomorrow. It seems to wanna crash a lot after I've woken up.
      My Computer


  9. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Oh, wow. Four more blue screens and three of them were 109's. I contacted the place I bought the RAM from.
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION

    Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
    ----------------------------------
    So there is other things to blame, too. Not only the RAM.
    Have you ever tried Driver Verifier as suggested in post #4?
    Driver Verifier - Enable and Disable

    It may be simply a device driver, too!
      My Computer


 
Page 1 of 2 12 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 07:39.
Find Us