none
Windows 7 blue screen 0x00000109 RRS feed

  • 问题


  • Hi

    I am running windows 7 ultimate 64BIT

    My system is as follows
    CPU: intel core i5 2400
    Motherboard: Gigabyte Z68A D3H-B3
    Video Card: Leadtek winfast gtx 550ti oc
    Sata Hard Drives seagate st2000dl003 2tb
    memory Corsair 2X 4GB DDR3 1333 CMX4GX3M1A1333C9

    I am using an external wireless usb internet adaptor. Both the processor graphics and discrete graphic card are in use and Virtu is employed to manage the two graphic card.

    The system crashes irregularly. The error code is always 0x00000109.

    I have uploaded two of my memory dumps at request site.

    https://skydrive.live.com/?cid=e3ddbce6604261c6&sc=documents&id=E3DDBCE6604261C6%21121

    Can someone look at this and let me know why my system is constantly crashing?

    My MS debugger doesn't work.

    I really appreciate any and all help.

    Chunli

    • 已移动 Alexis ZhangMVP 2011年8月14日 5:24 与主题更相符 (发件人:微软硬件)
    2011年8月13日 4:54

答案

  • Hi,

     

    Your dump file analyze:

    *******************************************************************************

    *                                                                             *

    *                        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: a3a039d8988a6805, Reserved

    Arg2: b3b7465eeb07375b, Reserved

    Arg3: fffff80004a3336b, 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:

    ------------------

     

     

    BUGCHECK_STR:  0x109

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  CODE_CORRUPTION

     

    PROCESS_NAME:  System

     

    CURRENT_IRQL:  0

     

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

     

    STACK_TEXT: 

    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

     

     

    STACK_COMMAND:  kb

     

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

        fffff80004a3346b - nt! ?? ::NNGAKEGL::`string'+42eb0

                    [ 24:20 ]

    1 error : !nt (fffff80004a3346b)

     

    MODULE_NAME: memory_corruption

     

    IMAGE_NAME:  memory_corruption

     

    FOLLOWUP_NAME:  memory_corruption

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

     

    MEMORY_CORRUPTOR:  ONE_BIT

     

    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

     

    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

     

    Followup: memory_corruption

    ---------

     

    About bugcheck 109, you can refer this article:

    http://msdn.microsoft.com/en-us/library/ff557228(v=VS.85).aspx

     

    That seem your memory card may corrupted, please contact the manufacturer to check if memory card broken.

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • 已标记为答案 liuchunli 2011年8月17日 2:29
    2011年8月15日 9:07
    版主

全部回复

  • Hi,

     

    Your dump file analyze:

    *******************************************************************************

    *                                                                             *

    *                        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: a3a039d8988a6805, Reserved

    Arg2: b3b7465eeb07375b, Reserved

    Arg3: fffff80004a3336b, 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:

    ------------------

     

     

    BUGCHECK_STR:  0x109

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  CODE_CORRUPTION

     

    PROCESS_NAME:  System

     

    CURRENT_IRQL:  0

     

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

     

    STACK_TEXT: 

    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

     

     

    STACK_COMMAND:  kb

     

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

        fffff80004a3346b - nt! ?? ::NNGAKEGL::`string'+42eb0

                    [ 24:20 ]

    1 error : !nt (fffff80004a3346b)

     

    MODULE_NAME: memory_corruption

     

    IMAGE_NAME:  memory_corruption

     

    FOLLOWUP_NAME:  memory_corruption

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

     

    MEMORY_CORRUPTOR:  ONE_BIT

     

    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

     

    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

     

    Followup: memory_corruption

    ---------

     

    About bugcheck 109, you can refer this article:

    http://msdn.microsoft.com/en-us/library/ff557228(v=VS.85).aspx

     

    That seem your memory card may corrupted, please contact the manufacturer to check if memory card broken.

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • 已标记为答案 liuchunli 2011年8月17日 2:29
    2011年8月15日 9:07
    版主
  • Thank you very much.

    I cheched the memory with Memtest. One of the memory stich had some errors and has been sent back for warranty. Thanks again.

    Kind regards.

    Chunli

    2011年8月27日 2:25