网友提问：不知道为什么，我的win7系统电脑出现了蓝屏，出现FOLLOWUP_NAME: MachineOwner提示，请问这是什么回事?请分析一下。
以下是蓝屏文件内容：
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\shiwen.li\Desktop\062014-14461-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`0425f000 PsLoadedModuleList = 0xfffff800`044a26d0
Debug session time: Fri Jun 20 14:58:43.358 2014 (UTC + 8:00)
System Uptime: 0 days 0:53:24.794
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa8003f58290, fffffa8003f582c0, 403001b}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!PVOID ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+75b80 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8003f58290, The pool entry we were looking for within the page.
Arg3: fffffa8003f582c0, The next pool entry.
Arg4: 000000000403001b, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Users\shiwen.li\Desktop\windbg\sym\ntoskrnl.exe\51FB06CD5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff8000425f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 51fb06cd
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: fffffa8003f58290
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80004407cae to fffff800042d4b80
STACK_TEXT:
fffff880`047d2388 fffff800`04407cae : 00000000`00000019 00000000`00000020 fffffa80`03f58290 fffffa80`03f582c0 : nt+0x75b80
fffff880`047d2390 00000000`00000019 : 00000000`00000020 fffffa80`03f58290 fffffa80`03f582c0 00000000`0403001b : nt+0x1a8cae
fffff880`047d2398 00000000`00000020 : fffffa80`03f58290 fffffa80`03f582c0 00000000`0403001b 00000000`000000a0 : 0x19
fffff880`047d23a0 fffffa80`03f58290 : fffffa80`03f582c0 00000000`0403001b 00000000`000000a0 fffffa80`03f582c0 : 0x20
fffff880`047d23a8 fffffa80`03f582c0 : 00000000`0403001b 00000000`000000a0 fffffa80`03f582c0 00000000`000007ff : 0xfffffa80`03f58290
fffff880`047d23b0 00000000`0403001b : 00000000`000000a0 fffffa80`03f582c0 00000000`000007ff 00000000`00000000 : 0xfffffa80`03f582c0
fffff880`047d23b8 00000000`000000a0 : fffffa80`03f582c0 00000000`000007ff 00000000`00000000 fffff800`045cce96 : 0x403001b
fffff880`047d23c0 fffffa80`03f582c0 : 00000000`000007ff 00000000`00000000 fffff800`045cce96 fffffa80`045632e0 : 0xa0
fffff880`047d23c8 00000000`000007ff : 00000000`00000000 fffff800`045cce96 fffffa80`045632e0 fffff880`06213110 : 0xfffffa80`03f582c0
fffff880`047d23d0 00000000`00000000 : fffff800`045cce96 fffffa80`045632e0 fffff880`06213110 fffff880`00000000 : 0x7ff
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+75b80
fffff800`042d4b80 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+75b80
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
【编辑分析】根据以上的蓝屏文件日志内容，可以得出导致win7蓝屏，并出现FOLLOWUP_NAME: MachineOwner的原因是硬件驱动不兼容导致的，小编建议：首先更新硬件驱动，然后查看问题是否依然存在。如果问题依然存在，请给小编继续反映情况!
相关阅读：解决win7 蓝屏 错误代码0x000000001e的方法
蓝屏分析工具推荐：Windows蓝屏分析工具
有用
53
