询问者
win10 BSOD
问题
-
win10 version: 17763.379
I didn't pass the test.so I can not put dump file。
WinDbg：
Symbol Search Path ：SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
dump anazly：
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\031819-15718-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: Windows 7 Kernel Version 17763 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff805`11612000 PsLoadedModuleList = 0xfffff805`11a2d9f0 Debug session time: Mon Mar 18 23:36:44.725 2019 (UTC + 8:00) System Uptime: 1 days 6:40:51.481 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............. Loading User Symbols Loading unloaded module list .............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {40920488, 2, 1, fffff8051172d408} Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 101287 instance(s) of page corruption, target is likely to have memory corruption. 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000040920488, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8051172d408, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 0000000040920488 CURRENT_IRQL: 2 FAULTING_IP: nt!KiInsertTimerTable+8 fffff805`1172d408 4154 push r12 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: QQExternal.exe BAD_PAGES_DETECTED: 18ba7 LAST_CONTROL_TRANSFER: from fffff805117d6d69 to fffff805117c55e0 STACK_TEXT: fffff904`cda1d508 fffff805`117d6d69 : 00000000`0000000a 00000000`40920488 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff904`cda1d510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 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 101287 instance(s) of page corruption, target is likely to have memory corruption. 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000040920488, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8051172d408, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 0000000040920488 CURRENT_IRQL: 2 FAULTING_IP: nt!KiInsertTimerTable+8 fffff805`1172d408 4154 push r12 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: QQExternal.exe BAD_PAGES_DETECTED: 18ba7 LAST_CONTROL_TRANSFER: from fffff805117d6d69 to fffff805117c55e0 STACK_TEXT: fffff904`cda1d508 fffff805`117d6d69 : 00000000`0000000a 00000000`40920488 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff904`cda1d510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 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 101287 instance(s) of page corruption, target is likely to have memory corruption. 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000040920488, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8051172d408, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 0000000040920488 CURRENT_IRQL: 2 FAULTING_IP: nt!KiInsertTimerTable+8 fffff805`1172d408 4154 push r12 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: QQExternal.exe BAD_PAGES_DETECTED: 18ba7 LAST_CONTROL_TRANSFER: from fffff805117d6d69 to fffff805117c55e0 STACK_TEXT: fffff904`cda1d508 fffff805`117d6d69 : 00000000`0000000a 00000000`40920488 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff904`cda1d510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 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 101287 instance(s) of page corruption, target is likely to have memory corruption. 3: kd> analyze -v *** WARNING: Unable to verify timestamp for kdcom.dll *** ERROR: Module load completed but symbols could not be loaded for kdcom.dll *** WARNING: Unable to verify timestamp for gdrv2.sys *** ERROR: Module load completed but symbols could not be loaded for gdrv2.sys *** WARNING: Unable to verify timestamp for WeGameDriver764.sys *** ERROR: Module load completed but symbols could not be loaded for WeGameDriver764.sys *** WARNING: Unable to verify timestamp for peauth.sys *** ERROR: Module load completed but symbols could not be loaded for peauth.sys *** WARNING: Unable to verify timestamp for SangforDnsDrv.sys *** ERROR: Module load completed but symbols could not be loaded for SangforDnsDrv.sys *** WARNING: Unable to verify timestamp for SangforTcpDrv.sys *** ERROR: Module load completed but symbols could not be loaded for SangforTcpDrv.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for clipsp.sys - *** WARNING: Unable to verify timestamp for mcupdate.dll *** ERROR: Module load completed but symbols could not be loaded for mcupdate.dll *** WARNING: Unable to verify timestamp for SangforVnic.sys *** ERROR: Module load completed but symbols could not be loaded for SangforVnic.sys *** WARNING: Unable to verify timestamp for RTKVHD64.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys *** WARNING: Unable to verify timestamp for RtkBtfilter.sys *** ERROR: Module load completed but symbols could not be loaded for RtkBtfilter.sys *** WARNING: Unable to verify timestamp for dump_storport.sys *** ERROR: Module load completed but symbols could not be loaded for dump_storport.sys *** WARNING: Unable to verify timestamp for npf.sys *** ERROR: Module load completed but symbols could not be loaded for npf.sys *** WARNING: Unable to verify timestamp for rtwlanu.sys *** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys *** WARNING: Unable to verify timestamp for drmk.sys *** ERROR: Module load completed but symbols could not be loaded for drmk.sys *** WARNING: Unable to verify timestamp for UcmCxUcsiNvppc.sys *** ERROR: Module load completed but symbols could not be loaded for UcmCxUcsiNvppc.sys *** WARNING: Unable to verify timestamp for gmm.sys *** ERROR: Module load completed but symbols could not be loaded for gmm.sys *** WARNING: Unable to verify timestamp for TeeDriverW8x64.sys *** ERROR: Module load completed but symbols could not be loaded for TeeDriverW8x64.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for e1d65x64.sys - *** WARNING: Unable to verify timestamp for nvvad64v.sys *** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys *** WARNING: Unable to verify timestamp for nvvhci.sys *** ERROR: Module load completed but symbols could not be loaded for nvvhci.sys *** WARNING: Unable to verify timestamp for womic.sys *** ERROR: Module load completed but symbols could not be loaded for womic.sys *** WARNING: Unable to verify timestamp for nvhda64v.sys *** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sys *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
全部回复
-
你好,
根据您提供的信息，似乎和qq的组件有关，QQExternal.exe是腾讯公司用来推送内容或广告的程序，随着QQ软件的启动而启动，但是偶尔占用内存太大，导致电脑卡顿死机。关掉QQ，在后台没有其他QQ程序运行的情况下，找到QQ软件安装的根目录，搜索找到QQExternal.exe文件，删除。
希望对您有帮助，如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已建议为答案 Carl FanMicrosoft contingent staff, Moderator 2019年3月22日 1:47
-
你好，
几天没收到你的留言了, 请问问题又什么进展吗？
我正在建议有帮助的答复为 "答案"。请随时尝试一下, 让我知道结果。如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已建议为答案 Carl FanMicrosoft contingent staff, Moderator 2019年4月5日 7:58
