locked
Sudden BSOD RRS feed

  • Question

  • Hello,

    This is the first time my system has had a Blue Screen occur and I'm really not tech savvy. I looked at the report given by the system, but I am unsure what any of it actually means.

    This is the entire error, copied from the reliability center.

    Source
    Windows

    Summary
    Shut down unexpectedly

    Date
    ‎12/‎27/‎2011 9:26 AM

    Status
    Report sent

    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7601.2.1.0.768.3
    Locale ID:    1033

    Extra information about the problem
    BCCode:    109
    BCP1:    A3A039D89D42E4F1
    BCP2:    B3B7465EEFC0B40F
    BCP3:    FFFFF80002DCB510
    BCP4:    0000000000000000
    OS Version:    6_1_7601
    Service Pack:    1_0
    Product:    768_1
    Bucket ID:    X64_0x109_0_nt!_imp_NtOpenSymbolicLinkObject+8
    Server information:    2a4e4098-ca20-4c59-a5ae-e13eedf4e41d

    Any help is greatly appreciated.

    Tuesday, December 27, 2011 3:01 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: a3a039d89d42e4f1, Reserved
    Arg2: b3b7465eefc0b40f, Reserved
    Arg3: fffff80002dcb510, Failure type dependent information
    Arg4: 0000000000000000, 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:
    ------------------
    BUGCHECK_STR:  0x109
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c89c40
    STACK_TEXT:  
    fffff880`0c0055d8 00000000`00000000 : 00000000`00000109 a3a039d8`9d42e4f1 b3b7465e`efc0b40f fffff800`02dcb510 : nt!KeBugCheckEx
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt+7cc40
    fffff800`02c89c40 48894c2408      mov     qword ptr [rsp+8],rcx
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  nt+7cc40
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    FAILURE_BUCKET_ID:  X64_0x109_nt+7cc40
    BUCKET_ID:  X64_0x109_nt+7cc40
    Followup: MachineOwner
    ---------
    -------------------------------------------------------------
     This indicates that the kernel has detected critical kernel code or data corruption.
    As I see the corrupted region is a generic one and there is no much information that we can extract from the dump.
    There is possible causes of your issues. It may be hardware failures especially with your RAM. For that, run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support.
    Also, proceed like that:
    • Uninstall all unused programs
    • Update all possible drivers
    • Disable all startup items / services except Microsoft ones
    • Disable all security softwares that you have

    Once done, check results.

    You can also contact Microsoft CSS for assistance.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. 

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by zhen tan Thursday, December 29, 2011 2:52 AM
    • Marked as answer by Arthur Xie Thursday, January 5, 2012 7:09 AM
    Tuesday, December 27, 2011 9:52 PM

All replies

  • Bug Check 0x109 :  http://msdn.microsoft.com/en-us/library/ff557228(v=vs.85).aspx

     

    Please Upload the DMP Files From C:\Windows\minidump into SkyDrive.

     

    Regards,

     


    MCP ✦ MCTS ✦ MCITP
    Tuesday, December 27, 2011 5:56 PM
  • Alright, I uploaded the DMP file to Skydrive. Do I need to place a link, or will it just be read by support?
    Tuesday, December 27, 2011 6:00 PM
  • you should put the Link here 

     

    Regards,

     


    MCP ✦ MCTS ✦ MCITP
    Tuesday, December 27, 2011 6:07 PM
  • https://skydrive.live.com/?cid=1D3C8F9BFD25AAFE&id=1D3C8F9BFD25AAFE!133#cid=A5A0F8DD68DDDCCD&id=A5A0F8DD68DDDCCD!233

    That should be the proper link, thank you!

    Tuesday, December 27, 2011 7:07 PM
  • *******************************************************************************
    *                                                                             *
    *                        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: a3a039d89d42e4f1, Reserved
    Arg2: b3b7465eefc0b40f, Reserved
    Arg3: fffff80002dcb510, Failure type dependent information
    Arg4: 0000000000000000, 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:
    ------------------
    BUGCHECK_STR:  0x109
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c89c40
    STACK_TEXT:  
    fffff880`0c0055d8 00000000`00000000 : 00000000`00000109 a3a039d8`9d42e4f1 b3b7465e`efc0b40f fffff800`02dcb510 : nt!KeBugCheckEx
    STACK_COMMAND:  kb
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner
    ---------------------------------------------------------------------------------------------------------------------------------------------
    Run memtest86+ to check that all is okay with your RAM. If an error was detected then replace the faulty RAM
    Run msconfig and disable all startup items except Microsoft ones
    Update Your Drivers and make sure it's Up to date


    Regards,

    MCP ✦ MCTS ✦ MCITP
    • Proposed as answer by zhen tan Thursday, December 29, 2011 2:52 AM
    Tuesday, December 27, 2011 7:25 PM
  • *******************************************************************************
    *                                                                             *
    *                        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: a3a039d89d42e4f1, Reserved
    Arg2: b3b7465eefc0b40f, Reserved
    Arg3: fffff80002dcb510, Failure type dependent information
    Arg4: 0000000000000000, 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:
    ------------------
    BUGCHECK_STR:  0x109
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c89c40
    STACK_TEXT:  
    fffff880`0c0055d8 00000000`00000000 : 00000000`00000109 a3a039d8`9d42e4f1 b3b7465e`efc0b40f fffff800`02dcb510 : nt!KeBugCheckEx
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt+7cc40
    fffff800`02c89c40 48894c2408      mov     qword ptr [rsp+8],rcx
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  nt+7cc40
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    FAILURE_BUCKET_ID:  X64_0x109_nt+7cc40
    BUCKET_ID:  X64_0x109_nt+7cc40
    Followup: MachineOwner
    ---------
    -------------------------------------------------------------
     This indicates that the kernel has detected critical kernel code or data corruption.
    As I see the corrupted region is a generic one and there is no much information that we can extract from the dump.
    There is possible causes of your issues. It may be hardware failures especially with your RAM. For that, run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support.
    Also, proceed like that:
    • Uninstall all unused programs
    • Update all possible drivers
    • Disable all startup items / services except Microsoft ones
    • Disable all security softwares that you have

    Once done, check results.

    You can also contact Microsoft CSS for assistance.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. 

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by zhen tan Thursday, December 29, 2011 2:52 AM
    • Marked as answer by Arthur Xie Thursday, January 5, 2012 7:09 AM
    Tuesday, December 27, 2011 9:52 PM
  • As recommended, you may want to check your memory, I wrote a post on
    exactly how to do this,
     
     

    -- Mike Burr
    Technology
    Wednesday, December 28, 2011 7:23 AM