none
(windows 7 )電腦已經在檢查錯誤後重新啟動。檢查的錯誤是: 0x00000109

    Question

  • 請問是什麼原因導致重新開機??

     

    電腦已經在檢查錯誤後重新啟動。檢查的錯誤是: 0x00000109 (0xa3a039d897848bc2, 0x0000000000000000, 0xdaecfecfab5fa1dd, 0x0000000000000101)。傾出的資料已儲存於: C:\Windows\MEMORY.DMP。報告識別碼: 092711-14695-01。

    以下是MEMORY.dmp 的內容

    ------------------------------------------------------------------------------------------------------------------------------------
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Acer\Desktop\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: 3: kd> .symfix c:\myCache
    3: kd> .sympath
    Symbol search path is: srv*
    Expanded Symbol search path is: cache*c:\myCache;SRV*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`04209000 PsLoadedModuleList = 0xfffff800`0444e670
    Debug session time: Tue Sep 27 14:16:03.347 2011 (UTC + 8:00)
    System Uptime: 0 days 4:58:54.861
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols

    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 109, {a3a039d897848bc2, 0, daecfecfab5fa1dd, 101}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner
    ---------

    0: 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: a3a039d897848bc2, Reserved
    Arg2: 0000000000000000, Reserved
    Arg3: daecfecfab5fa1dd, Failure type dependent information
    Arg4: 0000000000000101, 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

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80004285c40

    STACK_TEXT: 
    fffff880`04dd5598 00000000`00000000 : 00000000`00000109 a3a039d8`97848bc2 00000000`00000000 daecfecf`ab5fa1dd : 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

    BUCKET_ID:  BAD_STACK

    Followup: MachineOwner
    ---------

    • Edited by issue. _ Tuesday, September 27, 2011 8:08 PM
    Tuesday, September 27, 2011 8:05 PM

Answers

All replies

  • 您好

    Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION

    The CRITICAL_STRUCTURE_CORRUPTION bug check has a value of 0x00000109. This indicates that the kernel has detected critical kernel code or data corruption .

    請做以下步驟

    1. 確認記憶體是否有衝突的問題,如果有雙通道,可以先只插一條記憶體交叉測試一下

    2. 使用記憶體檢測軟體進行檢測,您可以使用 memtest86+ http://www.memtest.org/


    歡迎參觀我的Blog.NET菜鳥自救會
    Tuesday, September 27, 2011 11:51 PM
  • 請問如何確認記憶體是否有衝突的問題?
     
    我我電腦只有一條2GB ram
     
    memtest86+ 應該下載那一個?
     
    Download - Pre-Compiled Bootable ISO (.gz)
    Download - Pre-Compiled Bootable ISO (.zip)

    Download - Pre-Compiled Bootable Binary (.gz)
    Download - Pre-Compiled Bootable Binary (.zip)

    Download - Auto-installer for USB Key (Win 9x/2k/xp/7) *NEW!*
    Download - Pre-Compiled EXE file for USB Key (Pure DOS) *OBSOLETE*

    Download - Pre-Compiled package for Floppy (DOS - Win)

    • Edited by issue. _ Wednesday, September 28, 2011 4:41 PM
    Wednesday, September 28, 2011 4:38 PM
  • 我發現memory.dmp 中的內容顯示 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    這是否表示driver出現錯誤?

    Wednesday, September 28, 2011 9:16 PM
  • 您好

    1. 您最近有自行更新驅動程式嗎? 該情況是在什麼情況下發生的?

    2. 您可以透過 Windows 內建的記憶體診斷工具檢查看看

    http://windows.microsoft.com/zh-TW/windows7/Diagnosing-memory-problems-on-your-computer


    歡迎參觀我的Blog.NET菜鳥自救會
    • Proposed as answer by Kill Apple Thursday, September 29, 2011 10:52 AM
    • Marked as answer by issue. _ Thursday, September 29, 2011 11:30 AM
    Wednesday, September 28, 2011 11:01 PM
  • 假如你有興趣的話可以參考一下這一篇文章,另外MODULE_NAME並沒有明顯指出問題是出現在哪一個模組

    Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION

     

    Thursday, September 29, 2011 2:44 AM
  • 使用Windows 內建的記憶體診斷工具檢查出電腦有有記憶體問題
    Thursday, September 29, 2011 6:03 AM
  • 請問我還需要用 memtest86+進行檢測嗎?
    Thursday, September 29, 2011 11:42 AM
  • 您好

    使用記憶體診斷工具發現問題的話,就可以拿去送修了,不用在使用其他檢測軟體進行檢測


    歡迎參觀我的Blog.NET菜鳥自救會
    Thursday, September 29, 2011 12:19 PM