安装COM AddIn后，在Excel中测试连接，出现蓝屏
COM Excel 插件、C#、VS 2008、 Excel COM Addin，在测试虚拟机上测试，工作正常 客户安装后出现蓝屏，不知道原因。 以下是客户得到的。有人可以帮忙吗？我不知道这是什么，是什么原因造成的。 不确定这是由我的插件引起的还是客户电脑上的问题。
感谢
Microsoft (R) Windows 调试器版本 6.12.0002.633 X86 版权所有 (c) Microsoft Corporation。版权所有。
加载转储文件 [c:\windows\minidump\Mini050911-01.dmp] 迷你内核转储文件：仅寄存器和堆栈跟踪可用
警告：无法访问路径：'c:\windows\i386' 符号搜索路径为：srv*c:\symbols*http://msdl.microsoft.com/download/symbols 可执行搜索路径为：c:\windows\i386 Windows XP 内核版本 2600 (Service Pack 3) MP（2 个进程）免费 x86 兼容 产品：WinNt，套件：TerminalServer SingleUserTS 构建者：2600.xpsp_sp3_gdr.101209-1647 机器名称： 内核基础 = 0x804d7000 PsLoadedModuleList = 0x8055d720 调试会话时间：2011 年 5 月 9 日星期一 09:47:22.099 (UTC - 5:00) 系统正常运行时间：2 天 15:09:35.096 加载内核符号 ...................................................... ...................... ...................................................... ………… 加载用户符号 加载已卸载的模块列表 ................................
- *
- 错误检查分析 *
- *
使用 !analyze -v 获取详细的调试信息。
BugCheck 1000007F, {8, 80042000, 0, 0}
* 警告：无法验证 igxpmp32.sys 的时间戳 错误：模块加载已完成，但无法加载 igxpmp32.sys 的符号 无法加载图像 igxpdx32.DLL，Win32 错误 0n2 警告：无法验证 igxpdx32.DLL 的时间戳 * 错误：模块加载已完成，但无法加载 igxpdx32.DLL 的符号 可能由以下原因引起：igxpmp32.sys（igxpmp32+44184）
后续：MachineOwner
0：kd> !analyze -v
- *
- 错误检查分析 *
- *
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) 这意味着陷阱发生在内核模式，并且是一种陷阱 不允许内核拥有/捕获（绑定陷阱）或者 总是立即死亡（双误）。中的第一个数字 bugcheck params 是陷阱的数量（8 = 双错误等） 请参阅 Intel x86 系列手册以了解有关这些内容的更多信息 陷阱是。以下是这些代码的部分： 如果kv显示一个taskGate 在冒号之前使用 .tss，然后使用 kv。 否则如果 kv 显示陷阱帧 在该值上使用 .trap 别的 相应帧上的 .trap 将显示陷阱的拍摄位置 （在 x86 上，这将是与过程 KiTrap 一起使用的 ebp） 恩迪夫 kb 将显示更正后的堆栈。 论据： arg1：00000008，异常_双_故障 精氨酸2：80042000 参数3：00000000 Arg4：00000000
调试详细信息：
BUGCHECK_STR：0x7f_8
CUSTOMER_CRASH_COUNT：1
DEFAULT_BUCKET_ID：DRIVER_FAULT
PROCESS_NAME：EXCEL.EXE
LAST_CONTROL_TRANSFER：从 805362cb 到 80535dc8
STACK_TEXT：
97d0d004 805362cb 97d0d01c 97d0d0d8 8aeec418 nt!ExpFindCurrentThread+0x8 97d0d028 8062c345 8055a1e0 00000001 8063791f nt！ExAcquireResourceSharedLite + 0x51 97d0d034 8063791f 97d0d0d8 8aeec418 97d0d0cc nt!CmpLockRegistry+0x27 97d0d06c 805bfe5b e5eb5708 00000001 97d0d0a4 nt!CmpSecurityMethod+0x17 97d0d0ac 805c01c8 e5eb5708 97d0d0d8 e5eb5704 nt!ObpGetObjectSecurity+0x99 97d0d0dc 8062f28f e5eb5708 8786ddc0 00000001 nt!ObCheckObjectAccess+0x2c 97d0d128 8062ff30 e1036758 003778f0 00000000 nt!CmpDoOpen+0x2d5 97d0d328 805bf488 003778f0 00000000 8786ddc0 nt!CmpParseKey+0x5a6 97d0d3a0 805bba14 00000000 97d0d3e0 00000240 nt!ObpLookupObjectName+0x53c 97d0d3f4 80625696 00000000 8aeec418 00000000 nt!ObOpenObjectByName+0xea 97d0d4f0 8054167c 97d0d810 82000000 97d0d594 nt!NtOpenKey+0x1c8 97d0d4f0 80500699 97d0d810 82000000 97d0d594 nt!KiFastCallEntry+0xfc 97d0d574 805e701e 97d0d810 82000000 97d0d594 nt!ZwOpenKey+0x11 97d0d7e4 805e712a 00000002 805e70a0 00000000 nt!RtlpGetRegistryHandleAndPath+0x27a 97d0d82c 805e73e3 97d0d84c 00000014 97d0dba0 nt!RtlpQueryRegistryGetBlockPolicy+0x2e 97d0d854 805e79eb 00000003 e3fba72c 00000014 nt!RtlpQueryRegistryDirect+0x4b 97d0d8a4 805e7f10 e3fba72c 00000003 97d0d930 nt!RtlpCallQueryRegistryRoutine+0x369 97d0db40 b92f8184 00000005 e5eb4a28 97d0dba0 nt!RtlQueryRegistryValues+0x482 警告：堆栈展开信息不可用。以下框架可能是错误的。 97d0dbe8 b92bd85b 00000005 877fe5f4 877fe6f4 igxpmp32+0x44184 97d0e260 b92b9a7b 8938b358 97d0e290 00000000 igxpmp32+0x985b 97d0e274 b9496729 8938b358 97d0e290 00000a0c igxpmp32+0x5a7b 97d0e338 804ef19f 8938b040 8781d6b8 0000080c 视频！pVideoPortDispatch+0xabf 97d0e348 bf86ebbd 97d0e610 bf6e6cdc 00000014 nt!IopfCallDriver+0x31 97d0e378 bf86ec37 8938b040 00232150 97d0e3f8 win32k!GreDeviceIoControl+0x93 97d0e39c bf376769 8938b040 00232150 97d0e3f8 win32k!EngDeviceIoControl+0x1f 97d0f624 bf3b9f79 8938b040 bf6a593c bf6a5960 igxpdx32+0x8769 97d0f6b8 804fb540 00000002 00000002 97d0f6e8 igxpdx32+0x4bf79 97d0f77c 804fb488 00000000 02d0f818 97d0f7b4 nt!KeFlushSingleTb+0xae 97d0f7a8 805361db 97d0f7c0 bf3ab93b 00000000 nt!KeFlushMultipleTb+0x10e 97d0f7e0 bf3752ae 97d0f898 97d0f8b4 97d0fd28 nt！ExAcquireResourceExclusiveLite + 0x67 00000000 00000000 00000000 00000000 00000000 igxpdx32+0x72ae
STACK_COMMAND：kb
FOLLOWUP_IP： igxpmp32+44184 b92f8184 ?? ???
SYMBOL_STACK_INDEX：12
SYMBOL_NAME：igxpmp32+44184
FOLLOWUP_NAME：MachineOwner
MODULE_NAME：igxpmp32
IMAGE_NAME：igxpmp32.sys
DEBUG_FLR_IMAGE_TIMESTAMP：4b47be93
FAILURE_BUCKET_ID：0x7f_8_igxpmp32+441 84
BUCKET_ID：0x7f_8_igxpmp32+44184
后续：MachineOwner
COM Excel AddIn, C#, VS 2008,
Excel COM Addin, tested on test VM, works fine
Customer installed and got blue screen, have no clue why.
Following is what customer got. Can someone help? I have no idea what's this, what causes this.
not sure if this is caused by my addin or something is wrong on customer's PC.
thanks
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\Mini050911-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon May 9 09:47:22.099 2011 (UTC - 5:00)
System Uptime: 2 days 15:09:35.096
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
...........................
- *
- Bugcheck Analysis *
- *
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
* WARNING: Unable to verify timestamp for igxpmp32.sys
ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
Unable to load image igxpdx32.DLL, Win32 error 0n2
WARNING: Unable to verify timestamp for igxpdx32.DLL
* ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL
Probably caused by : igxpmp32.sys ( igxpmp32+44184 )
Followup: MachineOwner
0: kd> !analyze -v
- *
- Bugcheck Analysis *
- *
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a portion of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: EXCEL.EXE
LAST_CONTROL_TRANSFER: from 805362cb to 80535dc8
STACK_TEXT:
97d0d004 805362cb 97d0d01c 97d0d0d8 8aeec418 nt!ExpFindCurrentThread+0x8
97d0d028 8062c345 8055a1e0 00000001 8063791f nt!ExAcquireResourceSharedLite+0x51
97d0d034 8063791f 97d0d0d8 8aeec418 97d0d0cc nt!CmpLockRegistry+0x27
97d0d06c 805bfe5b e5eb5708 00000001 97d0d0a4 nt!CmpSecurityMethod+0x17
97d0d0ac 805c01c8 e5eb5708 97d0d0d8 e5eb5704 nt!ObpGetObjectSecurity+0x99
97d0d0dc 8062f28f e5eb5708 8786ddc0 00000001 nt!ObCheckObjectAccess+0x2c
97d0d128 8062ff30 e1036758 003778f0 00000000 nt!CmpDoOpen+0x2d5
97d0d328 805bf488 003778f0 00000000 8786ddc0 nt!CmpParseKey+0x5a6
97d0d3a0 805bba14 00000000 97d0d3e0 00000240 nt!ObpLookupObjectName+0x53c
97d0d3f4 80625696 00000000 8aeec418 00000000 nt!ObOpenObjectByName+0xea
97d0d4f0 8054167c 97d0d810 82000000 97d0d594 nt!NtOpenKey+0x1c8
97d0d4f0 80500699 97d0d810 82000000 97d0d594 nt!KiFastCallEntry+0xfc
97d0d574 805e701e 97d0d810 82000000 97d0d594 nt!ZwOpenKey+0x11
97d0d7e4 805e712a 00000002 805e70a0 00000000 nt!RtlpGetRegistryHandleAndPath+0x27a
97d0d82c 805e73e3 97d0d84c 00000014 97d0dba0 nt!RtlpQueryRegistryGetBlockPolicy+0x2e
97d0d854 805e79eb 00000003 e3fba72c 00000014 nt!RtlpQueryRegistryDirect+0x4b
97d0d8a4 805e7f10 e3fba72c 00000003 97d0d930 nt!RtlpCallQueryRegistryRoutine+0x369
97d0db40 b92f8184 00000005 e5eb4a28 97d0dba0 nt!RtlQueryRegistryValues+0x482
WARNING: Stack unwind information not available. Following frames may be wrong.
97d0dbe8 b92bd85b 00000005 877fe5f4 877fe6f4 igxpmp32+0x44184
97d0e260 b92b9a7b 8938b358 97d0e290 00000000 igxpmp32+0x985b
97d0e274 b9496729 8938b358 97d0e290 00000a0c igxpmp32+0x5a7b
97d0e338 804ef19f 8938b040 8781d6b8 0000080c VIDEOPRT!pVideoPortDispatch+0xabf
97d0e348 bf86ebbd 97d0e610 bf6e6cdc 00000014 nt!IopfCallDriver+0x31
97d0e378 bf86ec37 8938b040 00232150 97d0e3f8 win32k!GreDeviceIoControl+0x93
97d0e39c bf376769 8938b040 00232150 97d0e3f8 win32k!EngDeviceIoControl+0x1f
97d0f624 bf3b9f79 8938b040 bf6a593c bf6a5960 igxpdx32+0x8769
97d0f6b8 804fb540 00000002 00000002 97d0f6e8 igxpdx32+0x4bf79
97d0f77c 804fb488 00000000 02d0f818 97d0f7b4 nt!KeFlushSingleTb+0xae
97d0f7a8 805361db 97d0f7c0 bf3ab93b 00000000 nt!KeFlushMultipleTb+0x10e
97d0f7e0 bf3752ae 97d0f898 97d0f8b4 97d0fd28 nt!ExAcquireResourceExclusiveLite+0x67
00000000 00000000 00000000 00000000 00000000 igxpdx32+0x72ae
STACK_COMMAND: kb
FOLLOWUP_IP:
igxpmp32+44184
b92f8184 ?? ???
SYMBOL_STACK_INDEX: 12
SYMBOL_NAME: igxpmp32+44184
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igxpmp32
IMAGE_NAME: igxpmp32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b47be93
FAILURE_BUCKET_ID: 0x7f_8_igxpmp32+44184
BUCKET_ID: 0x7f_8_igxpmp32+44184
Followup: MachineOwner
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
在深入研究实际的调用堆栈之前，我建议进行一些进一步的取证，以确定是否实际上是您的插件导致了 BSOD。英特尔显卡驱动程序因其容易导致 BSOD 混乱而闻名。
Before diving into the actual call stack, I'd advise to do some further forensics as to determine whether it is actually your addin that is causing the BSOD. The Intel Graphics drivers are known for their tendency to end up in a BSOD mess.
它可能是一个坏的视频驱动程序，但这实际上看起来更像是坏的RAM。您的 Excel 加载项只是受害者。
It could be a bad video driver, but this really looks more like bad RAM. Your Excel add-in is just the victim.
您可能还想查看这些链接。您可以通过更新视频或其他驱动程序或卸载此知识库来解决该问题。
http://support.microsoft.com/kb/2393802（请参阅已知问题）
http://blogs.technet.com/b/asiasupp/archive/2011/03/23/stop-error-0x0000007f-or-0x1000007f-after-installing-ms11-011-kb2393802.aspx< /a>
You may also want to look at these links. You can likely resolve the issue by updating the video or other drivers or by uninstalling this KB.
http://support.microsoft.com/kb/2393802 (see Known Issues)
http://blogs.technet.com/b/asiasupp/archive/2011/03/23/stop-error-0x0000007f-or-0x1000007f-after-installing-ms11-011-kb2393802.aspx