2 u014479626 u014479626 于 2016.04.25 15:48 提问

系统蓝屏symbols could not be loaded for topsecpf.sys

以下是dmp文件

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

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

WARNING: Whitespace at start of path element
Symbol search path is: SRV*C:\mysymbol*http://msdl.microsoft.com/download/symbols; SRV*c:\mysymbol* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.212.amd64fre.th2_release_sec.160328-1908
Machine Name:
Kernel base = 0xfffff8005ca06000 PsLoadedModuleList = 0xfffff8005cce4cd0
Debug session time: Mon Apr 25 14:00:16.636 2016 (UTC + 8:00)
System Uptime: 0 days 0:09:38.532
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 139, {3, ffffd0020017a280, ffffd0020017a1d8, 0}

Unable to load image \??\C:\WINDOWS\sysWOW64\drivers\topsecpf.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for topsecpf.sys
*** ERROR: Module load completed but symbols could not be loaded for topsecpf.sys
Probably caused by : topsecpf.sys ( topsecpf+7370 )

Followup: MachineOwner

3: kd> !analyze -v


  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

Unknown bugcheck code (139)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000003
Arg2: ffffd0020017a280
Arg3: ffffd0020017a1d8
Arg4: 0000000000000000

Debugging Details:

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8005cb532e9 to fffff8005cb48760

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffd0020017a070

STACK_COMMAND: dds FFFFD0020017A070-0x20 ; kb

STACK_TEXT:

ffffd0020017a050 00000000
ffffd002
0017a054 ffffe001
ffffd0020017a058 c565637b
ffffd002
0017a05c fffff801
ffffd0020017a060 3ddb1490
ffffd002
0017a064 ffffe001
ffffd0020017a068 c6d57370
ffffd002
0017a06c fffff801
ffffd0020017a070 c6d57348
ffffd002
0017a074 fffff801
ffffd0020017a078 00000000
ffffd002
0017a07c 00000000
ffffd0020017a080 00000000
ffffd002
0017a084 00000000
ffffd0020017a088 00000000
ffffd002
0017a08c 00000000
ffffd0020017a090 c6d19700
ffffd002
0017a094 fffff801
ffffd0020017a098 5cb53610
ffffd002
0017a09c fffff800
ffffd0020017a0a0 00000002
ffffd002
0017a0a4 00000000
ffffd0020017a0a8 0017a4b0
ffffd002
0017a0ac ffffd002
ffffd0020017a0b0 0000ad13
ffffd002
0017a0b4 00000000
ffffd0020017a0b8 00000000
ffffd002
0017a0bc 00000000
ffffd0020017a0c0 3dfe7b70
ffffd002
0017a0c4 ffffe001
ffffd0020017a0c8 c624f303
ffffd002
0017a0cc fffff801

FOLLOWUP_IP:
topsecpf+7370
fffff801`c6d57370 90 nop

SYMBOL_NAME: topsecpf+7370

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: topsecpf

IMAGE_NAME: topsecpf.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d6da0f2

FAILURE_BUCKET_ID: X64_0x139_topsecpf+7370

BUCKET_ID: X64_0x139_topsecpf+7370

Followup: MachineOwner

3: kd> !analyze -v


  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

Unknown bugcheck code (139)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000003
Arg2: ffffd0020017a280
Arg3: ffffd0020017a1d8
Arg4: 0000000000000000

Debugging Details:

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8005cb532e9 to fffff8005cb48760

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffd0020017a070

STACK_COMMAND: dds FFFFD0020017A070-0x20 ; kb

STACK_TEXT:

ffffd0020017a050 00000000
ffffd002
0017a054 ffffe001
ffffd0020017a058 c565637b
ffffd002
0017a05c fffff801
ffffd0020017a060 3ddb1490
ffffd002
0017a064 ffffe001
ffffd0020017a068 c6d57370
ffffd002
0017a06c fffff801
ffffd0020017a070 c6d57348
ffffd002
0017a074 fffff801
ffffd0020017a078 00000000
ffffd002
0017a07c 00000000
ffffd0020017a080 00000000
ffffd002
0017a084 00000000
ffffd0020017a088 00000000
ffffd002
0017a08c 00000000
ffffd0020017a090 c6d19700
ffffd002
0017a094 fffff801
ffffd0020017a098 5cb53610
ffffd002
0017a09c fffff800
ffffd0020017a0a0 00000002
ffffd002
0017a0a4 00000000
ffffd0020017a0a8 0017a4b0
ffffd002
0017a0ac ffffd002
ffffd0020017a0b0 0000ad13
ffffd002
0017a0b4 00000000
ffffd0020017a0b8 00000000
ffffd002
0017a0bc 00000000
ffffd0020017a0c0 3dfe7b70
ffffd002
0017a0c4 ffffe001
ffffd0020017a0c8 c624f303
ffffd002
0017a0cc fffff801

FOLLOWUP_IP:
topsecpf+7370
fffff801`c6d57370 90 nop

SYMBOL_NAME: topsecpf+7370

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: topsecpf

IMAGE_NAME: topsecpf.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d6da0f2

FAILURE_BUCKET_ID: X64_0x139_topsecpf+7370

BUCKET_ID: X64_0x139_topsecpf+7370

Followup: MachineOwner

3: kd> !analyze -v


  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

Unknown bugcheck code (139)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000003
Arg2: ffffd0020017a280
Arg3: ffffd0020017a1d8
Arg4: 0000000000000000

Debugging Details:

1个回答

CSDNXIAOS
CSDNXIAOS   2016.04.25 15:54
已采纳

The breakpoint will not currently be hit. No symbols have been loaded for this document

1.查看pdb文件有没有更新
2.Debug --- windows -- modules 中对应的库的加载路径是......
答案就在这里:The breakpoint will not currently be hit. No symbols have been loaded for this document
----------------------Hi,地球人,我是问答机器人小S,上面的内容就是我狂拽酷炫叼炸天的答案,除了赞同,你还有别的选择吗?

Csdn user default icon
上传中...
上传图片
插入图片
准确详细的回答,更有利于被提问者采纳,从而获得C币。复制、灌水、广告等回答会被删除,是时候展现真正的技术了!
其他相关推荐
usrlocalliblibz.a could not read symbols Bad value问题解决(64 位 Linux)
usrlocalliblibz.a could not read symbols Bad value问题解决(64 位 Linux).doc
fdk-aac-0.1.2.tar.gz
fdk_aac源代码,开源的aac工具,版本fdk-aac-0.1.2.tar.gz fraunhofer研究所
instantclient_10_2.rar
999 the oracle library oci.dll could not be loaded
slf4j-1.5.2.zip
slf4j-1.5.2.zip 解决了我的org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. 错误
could not read symbols: Bad value
could not read symbols: Bad value,只在64位linux下出现的问题,需要在编译时加上-fPIC
oracle11g x64 oci.dll
oracle library oci.dll could not be loaded ,64位的oci.dll instant client来支持PB调用
windows 7 debug symbols 32位 64位 sp1的symbols是另一个文件
windows 7 debug symbols 不含win7 sp1的symbol If you plan to install symbols manually, it is crucial that you remember this basic rule: the symbol files on the host computer are required to match the version of Windows installed on the target computer. If you are planning to do a kernel mode debug of a Windows XP target from a Windows 2000 host, you need to install the Windows XP symbol files on the Windows 2000 system. If you plan to perform user-mode debugging on the same computer as the target application, then install the symbol files that match the version of Windows running on that system. If you are analyzing a memory dump file, then the version of symbol files needed on the debug computer are those that match the version of the operating system that produced the dump file, not necessarily those matching the version of the operating system on the machine running the debug session.
微软windows操作系统蓝屏分析工具
微软windows操作系统蓝屏分析工具,可以分析操作系统蓝屏而生成的dump文件,将dump文件让此工具读取,可以分析出问题原因,可以分析服务器操作系统和个人操作系统,以下是一个分析实例, Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 1097, e6, fffffa80507b6a00} *** WARNING: Unable to verify timestamp for EdpPcap.sys *** ERROR: Module load completed but symbols could not be loaded for EdpPcap.sys GetPointerFromAddress: unable to read from fffff800018b10e8 GetUlongFromAddress: unable to read from fffff800018b1198 GetUlongFromAddress: unable to read from fffff8000181e210 Probably caused by : EdpPcap.sys ( EdpPcap+2b0b ) Followup: MachineOwner ---------
电脑蓝屏检测软件
软件自动检测电脑蓝屏的代码,检测电脑蓝屏的原因,对蓝屏代码进行分析,得出结论
系统蓝屏错误集合
系统蓝屏错误集合 蓝屏错误分析 蓝屏错误 蓝屏解决办法