閱讀221 返回首頁    go 魔獸

電腦一直藍屏，附上最近一次Windows Debugging Tool

*******************************************************************************
*                                                                             *
*                        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 https://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: a39fe4e58d755622, Reserved
Arg2: b3b6f16bdff3537d, Reserved
Arg3: fffff802bebb4ec8, 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:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff802bebee310

STACK_TEXT:  
ffffc800`a63a3d78 00000000`00000000 : 00000000`00000109 a39fe4e5`8d755622 b3b6f16b`dff3537d fffff802`bebb4ec8 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff802bebb48ae - nt!InitializeListHeadPte+22
[ f6:8f ]
    fffff802bebb4fdf - nt!KiAdjustTimerDueTimes+117 (+0x731)
[ 8d:8f ]
    fffff802bebb56c7 - nt!MiCountSystemImageCommitment+7f (+0x6e8)
[ f6:8f ]
    fffff802bebb5752 - nt!MiCountSystemImageCommitment+10a (+0x8b)
[ f6:8f ]
    fffff802bebb581d-fffff802bebb581e  2 bytes - nt!MiCountSystemImageCommitment+1d5 (+0xcb)
[ 80 fa:00 ef ]
6 errors : !nt (fffff802bebb48ae-fffff802bebb581e)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

最後更新：2017-06-13 21:41:27

  上一篇：go 我的windows10如何獲得“電子郵件程序”
  下一篇：go win10屏幕從睡眠喚醒會先一道強光，屏幕有時會閃屏【一般似乎在打開新的應用時】