閱讀992 返回首頁    go windows

Win 10經常出現藍屏

Win 10經常出現藍屏：

以下是使用Debugging Tools提提取的數據 希望非常專業的人給予幫助！

希望及時回複 謝謝！

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


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

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`b2082000 PsLoadedModuleList = 0xfffff801`b23ce5c0
Debug session time: Fri Aug 25 12:27:55.795 2017 (UTC + 8:00)
System Uptime: 0 days 1:13:38.514
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 656e6f4e, 4020010, ffff950eb4366110}

*** WARNING: Unable to verify timestamp for PassGuard_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for PassGuard_x64.sys
fffff801b2463358: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
Probably caused by : PassGuard_x64.sys ( PassGuard_x64+1c95 )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 00000000656e6f4e, Pool tag value from the pool header
Arg3: 0000000004020010, Contents of the first 4 bytes of the pool header
Arg4: ffff950eb4366110, Address of the block of pool being deallocated

Debugging Details:
------------------

Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B85-HD3

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F2

BIOS_DATE:  07/04/2014

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B85-HD3

BASEBOARD_VERSION:  To be filled by O.E.M.

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: 7

BUGCHECK_P2: 656e6f4e

BUGCHECK_P3: 4020010

BUGCHECK_P4: ffff950eb4366110

POOL_ADDRESS: Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
 ffff950eb4366110

FREED_POOL_TAG:  None

BUGCHECK_STR:  0xc2_7_None

CPU_COUNT: 8

CPU_MHZ: d40

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  KEVIN

ANALYSIS_SESSION_TIME:  08-25-2017 13:34:25.0133

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER:  from fffff801b2302f87 to fffff801b21ee560

STACK_TEXT: 
ffffd000`fe06d238 fffff801`b2302f87 : 00000000`000000c2 00000000`00000007 00000000`656e6f4e 00000000`04020010 : nt!KeBugCheckEx
ffffd000`fe06d240 fffff80e`aeac1c95 : ffff950e`b4366110 ffffd000`fe06d490 ffff950e`b6dc08b0 ffff950e`00000000 : nt!ExFreePoolWithTag+0xf67
ffffd000`fe06d340 ffff950e`b4366110 : ffffd000`fe06d490 ffff950e`b6dc08b0 ffff950e`00000000 00000000`00000000 : PassGuard_x64+0x1c95
ffffd000`fe06d348 ffffd000`fe06d490 : ffff950e`b6dc08b0 ffff950e`00000000 00000000`00000000 ffffd000`fe06d600 : 0xffff950e`b4366110
ffffd000`fe06d350 ffff950e`b6dc08b0 : ffff950e`00000000 00000000`00000000 ffffd000`fe06d600 00000000`00000000 : 0xffffd000`fe06d490
ffffd000`fe06d358 ffff950e`00000000 : 00000000`00000000 ffffd000`fe06d600 00000000`00000000 00000000`00000000 : 0xffff950e`b6dc08b0
ffffd000`fe06d360 00000000`00000000 : ffffd000`fe06d600 00000000`00000000 00000000`00000000 ffff950e`b00d7950 : 0xffff950e`00000000


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  587a0bc8c9d8b85b2853eb6ac32f0b72ad423ef8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  485bd797f74e3586247169a5fa933fc7bf8516be

THREAD_SHA1_HASH_MOD:  e0abbc36b9472a0f5ceaad7fe95327c9cdb895df

FOLLOWUP_IP:
PassGuard_x64+1c95
fffff80e`aeac1c95 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  PassGuard_x64+1c95

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PassGuard_x64

IMAGE_NAME:  PassGuard_x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  525f9a4c

BUCKET_ID_FUNC_OFFSET:  1c95

FAILURE_BUCKET_ID:  0xc2_7_None_PassGuard_x64!unknown_function

BUCKET_ID:  0xc2_7_None_PassGuard_x64!unknown_function

PRIMARY_PROBLEM_CLASS:  0xc2_7_None_PassGuard_x64!unknown_function

TARGET_TIME:  2017-08-25T04:27:55.000Z

OSBUILD:  15063

OSSERVICEPACK:  540

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-08-01 09:23:25

ANALYSIS_SESSION_ELAPSED_TIME:  575

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc2_7_none_passguard_x64!unknown_function

FAILURE_ID_HASH:  {5161bdd4-ccb0-3d6b-9f6a-b1678c3b03dc}

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

最後更新：2017-08-25 14:02:24

  上一篇：go Windows10專業版運行速度太慢怎麼解決？
  下一篇：go Why winodw10 system special character dispaly very small