阅读916 返回首页    go iPhone_iPad_Mac_apple


win10经常死机然后重启没有蓝屏.

dump文件是这样的、

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


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

Symbol search path is: SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.1176.amd64fre.th2_release_sec.170913-1848
Machine Name:
Kernel base = 0xfffff803`e1c88000 PsLoadedModuleList = 0xfffff803`e1f65c70
Debug session time: Mon Jan  8 15:00:56.923 2018 (UTC + 8:00)
System Uptime: 0 days 0:29:23.679
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........................
Cannot read PEB32 from WOW64 TEB32 0000de12 - Win32 error 0n30
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a01f59c3cab6b5, b3b72be0164b6886, ffffe001254e3780, 1c}

Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )

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

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

2: 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: a3a01f59c3cab6b5, Reserved
Arg2: b3b72be0164b6886, Reserved
Arg3: ffffe001254e3780, Failure type dependent information
Arg4: 000000000000001c, 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:  2

BAD_PAGES_DETECTED: de12

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff803e1dca900

STACK_TEXT:  
ffffd001`3a1ecfb8 00000000`00000000 : 00000000`00000109 a3a01f59`c3cab6b5 b3b72be0`164b6886 ffffe001`254e3780 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  PAGE_NOT_ZERO

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO

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

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



您好!

 

感谢您联系微软技术支持。

 

我了解到您遇到系统死机重启的问题 。

 

请您在电脑重启之后,上传minidump文件到百度网盘,然后提供链接,文件默认路径在C:\Windows\Minidump(不需要进行压缩操作)。

 

您可以通过以下方案收集您的dump日志文件:

 

1)打开控制面板>>系统>>高级系统设置>>高级>>启动和故障恢复>>设置;

 

2)写入调试信息>>选择“小内存转储(256KB)”,路径选择默认,确定并重启您的计算机;

 

3)再次蓝屏后,前往C:\Windows\Minidump提取即可。

 

希望以上的信息可以帮助到您。



最后更新:2018-01-09 12:04:20

  上一篇:go Windows10更新不了
  下一篇:go Win7无法安装 .net framework 4.6.2