659      微軟  windows

電腦頻繁藍屏（有藍屏日誌）

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


Loading Dump File [C:\Windows\Minidump\081217-27593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`95885000 PsLoadedModuleList = 0xfffff801`95bd15c0
Debug session time: Sat Aug 12 08:00:54.502 2017 (UTC + 8:00)
System Uptime: 0 days 0:34:27.336
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...............................
Cannot read PEB32 from WOW64 TEB32 00010a01 - Win32 error 0n30
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a39fc1de52d9c845, b3b6ce64a55b2e30, fffff80197c36000, 2}

Probably caused by : memory_corruption

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

 *** Memory manager detected 68097 instance(s) of page corruption, target is likely to have memory corruption.

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 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: a39fc1de52d9c845, Reserved
Arg2: b3b6ce64a55b2e30, Reserved
Arg3: fffff80197c36000, Failure type dependent information
Arg4: 0000000000000002, 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

BAD_PAGES_DETECTED: 10a01

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff801959f1560

STACK_TEXT:  
ffff9482`04daed78 00000000`00000000 : 00000000`00000109 a39fc1de`52d9c845 b3b6ce64`a55b2e30 fffff801`97c36000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff801959f1813-fffff801959f1820  14 bytes - nt!KiRestoreProcessorControlState+33
[ 0f 01 59 66 0f b7 41 70:68 00 c0 69 c4 c7 44 24 ]
14 errors : !nt (fffff801959f1813-fffff801959f1820)

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
---------

 *** Memory manager detected 68097 instance(s) of page corruption, target is likely to have memory corruption.

總是藍屏到底是什麼問題

最後更新：2017-08-14 23:52:27

  上一篇： 同時開啟不同應用，音量大小不一致。

  下一篇： 加入家庭組後為什麼顯示不出同組內的電腦？