Windows 8 and 8.1 Forums


Critical Structure Corruption BSOD

  1. #1


    New Hampshire
    Posts : 77
    windows 8 enterprise x64

    Critical Structure Corruption BSOD


    Hello. Attached is a copy of logs/dumps. I believe this is the 3rd time I've had this BSOD. It is completely random as far as I can tell. I wasn't pushing the computer very hard, just a few tabs open in my browser and listening to online radio. Any insight would be greatly appreciated.

      My System SpecsSystem Spec

  2. #2


    Posts : 2,480
    Windows 10 Pro x64


    It appears that your RAM might be the cause. Please test it using this tool: RAM - Test with Memtest86+ - Windows 7 Help Forums Run it for at least eight passes.
      My System SpecsSystem Spec

  3. #3


    New Hampshire
    Posts : 77
    windows 8 enterprise x64


    Hi soft, thanks for the suggestion. I will have to try that over night. I have run 2 shorter tests and both have come back fine. 1 was with an AIO dell diagnostics tool, very quick and the other i used from a hirens boot cd. called prime95. it ran 24 passes in an hour and 20 minutes and that passed as well. I am curious what is pointing you towards this being a ram problem? I googled and yahoo'd all over and everything says "buggy drivers" ? I will report back after the test this evening. Thank you again for your time.
      My System SpecsSystem Spec

  4. #4


    New Hampshire
    Posts : 77
    windows 8 enterprise x64


    *additional info* I ran sfc and it fail. I then did dism restorehealth and that worked. re-ran sfc /scannnow and it passed. Thank you again for your time.
      My System SpecsSystem Spec

  5. #5


    Posts : 2,480
    Windows 10 Pro x64


    I have analysed your minidump, and the results of the analysis have shoen that your RAM might be the cause.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a01f595b785539, b3b72bdfadf70a78, fffff802bbfc3a6c, 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
    ---------
    
    1: 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:
    Arg1: a3a01f595b785539, Reserved
    Arg2: b3b72bdfadf70a78, Reserved
    Arg3: fffff802bbfc3a6c, Failure type dependent information
    Arg4: 0000000000000001, 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
    
    Debugging Details:
    ------------------
    
    
    PG_MISMATCH:  2000
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    FAULTING_IP: 
    hal!HalpAddMcaToProcessorSpecificSection+0
    fffff802`bbfc3a6c 4c8bdc          mov     r11,rsp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0x109
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    STACK_TEXT:  
    ffffd000`bd8cd188 00000000`00000000 : 00000000`00000109 a3a01f59`5b785539 b3b72bdf`adf70a78 fffff802`bbfc3a6c : nt!KeBugCheckEx
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
        fffff802bbfc3ab0 - hal!HalpAddMcaToProcessorSpecificSection+44
        [ d5:95 ]
    1 error : !hal (fffff802bbfc3ab0)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
    
    FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}
    
    Followup: memory_corruption
    ---------
      My System SpecsSystem Spec

  6. #6


    New Hampshire
    Posts : 77
    windows 8 enterprise x64


    I ran memtest over night. I stopped it on pass 8 when I woke, no errors. I checked in my event viewer log and found literally hundreds of the same error occuring 30 seconds apart for the last 3 days. Security SPP Event ID 16385. I googled and yahoo'd all day and finally found a fix on technet. I'm not sure if that is what cause my BSOD, but for now, my computer is running nice and smooth. Thank you again for your time and suggestions.
      My System SpecsSystem Spec

Critical Structure Corruption BSOD
Related Threads
Hello all, I've been experiencing random blue screens on my laptop for a while now. Happens about once a week and only under Windows (Linux works without a problem). It's always the same BSOD: "Critical Structure Corruption (CLFS.sys). My laptop is a ASUS N56VM-S4050V with 8gb 1333mhz ram,...
Hello and thank you, No new behaviors, but my HP pavilion (8 months old-ish) has started throwing BSODs at me. 5 so far with increasing frequency over the past month. I've attached the dump file, but have no idea what caused it or triggers it. Also, it seems I can't even open the dump files? ...
BSOD critical structure corruption in BSOD Crashes and Debugging
Hey guys. I was surfing the internet when i received this Bsod. Lately i have been getting various ones, on startup when its loading the os, i get a bsod sometimes. I was hoping you guys could help me resolve these problems. Thanks
Critical Structure Corruption + otrher BSODs in BSOD Crashes and Debugging
Hi, I am getting BSODs in a 1-year old system. One of the more common errors I get refers to critical structure corruption, although there have been several other ones too. Any advice would be appreciated regarding how to rectify this. Neil P.S. New data dump uploaded dated 27th...
Hello, After some searching on the web and my own troubleshooting, I came here and found some helpful people, so I'm hoping you can help me too! :) History: Win 7 PC working fine. Loaded Win 8 and system crashes. I did find some bad memory (replaced all RAM) reloaded and Win 7 again runs fine,...
Hi All, I just finished installing Win 8.1 update after 2 hours of troubleshooting and with the help from this forum. I thank everyone dearly. My new problem is getting crashed every 5 minutes with the blue screen if death and getting error Critical Structure Corruption on my freshly install...
Hey everyone, got a current screen on blue screen issues, yet it's marked as solved. Because at the time, it was. Anyway as it were, things go from bad to worse, now to give some background - most likely not necessary as the answers may lay in the attached dump file - but none the less. This...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook