这是用Winbug分析后得出的代码,
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff801368fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3390
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 9499
Key : Analysis.Init.CPU.mSec
Value: 780
Key : Analysis.Init.Elapsed.mSec
Value: 16674
Key : Analysis.Memory.CommitPeak.Mb
Value: 102
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 081622-52609-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff801368fb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: WeChat.exe
IRP_ADDRESS: 800000023734c788
STACK_TEXT:
ffffc381`063b6e18 fffff801`3602a998 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`368fb320 : nt!KeBugCheckEx
ffffc381`063b6e20 fffff801`35e4b573 : 000009ec`a6bc3f0b ffffc381`0639d180 00000000`00000000 ffffc381`0639d180 : nt!KeAccumulateTicks+0x1dcbc8
ffffc381`063b6e80 fffff801`35e4b05a : ffffda04`52cf6600 ffffec8e`2339e920 00000000`00000000 ffffda04`674cb080 : nt!KeClockInterruptNotify+0x453
ffffc381`063b6f30 fffff801`35ed9405 : ffffda04`52cf6600 00000000`00000000 00000000`00000000 ffff3aa6`5d3a259a : nt!HalpTimerClockIpiRoutine+0x1a
ffffc381`063b6f60 fffff801`35ffa36a : ffffec8e`2339e920 ffffda04`52cf6600 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc381`063b6fb0 fffff801`35ffa8d7 : ffffec8e`2339e588 00000000`000001b1 ffffae04`19dcd5a0 00000000`00000003 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffec8e`2339e8a0 fffff801`35ecf542 : fffff700`00007000 00000000`00000450 ffff15a9`7838a36a ffff8a0c`c41c0000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffec8e`2339ea30 fffff801`35ea29df : ffffec8e`2339e588 00000000`00000000 3d37f364`d74e0682 3d37f364`d74e0682 : nt!KiAcquireKobjectLockSafe+0x22
ffffec8e`2339ea60 fffff801`35ea2139 : 00000000`00000000 ffffec8e`2339ec30 00000001`00000000 ffff8a0c`c41c0000 : nt!KeSetEvent+0x6f
ffffec8e`2339eaf0 fffff801`35eb4aa0 : 80000002`3734c800 ffffda04`00000000 ffffda04`624c6a00 ffffda04`674cb080 : nt!IopCompleteRequest+0x389
ffffec8e`2339ebb0 fffff801`35ffcc50 : 00000000`00000000 00000000`00000000 da046aa4`00000000 00000000`00000000 : nt!KiDeliverApc+0x1b0
ffffec8e`2339ec60 fffff801`35e6cf11 : 00000000`00000114 00000000`00000000 ffff8a0c`c41c0000 00000000`00000000 : nt!KiApcInterrupt+0x2f0
ffffec8e`2339edf0 fffff801`35e2b4eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x231
ffffec8e`2339ef90 fffff801`35e581c5 : 00000000`00000000 00000000`00000000 ffffec8e`2339f1d0 ffffec8e`2339f1b4 : nt!MmCheckCachedPageStates+0x17eb
ffffec8e`2339f160 fffff801`35e5714a : ffffda04`5d308da0 00000000`121094b8 ffffec8e`2339f358 ffffda04`00000000 : nt!CcMapAndCopyInToCache+0x605
ffffec8e`2339f300 fffff801`38fff4ed : 00000000`00000000 ffffec8e`2339f600 ffffda04`5e1f5c68 00000000`00000000 : nt!CcCopyWriteEx+0xea
ffffec8e`2339f380 fffff801`38ffb103 : ffffda04`5e1f5c68 ffffda04`611d9010 ffffec8e`2339f640 00000000`00000000 : Ntfs!NtfsCommonWrite+0x3f7d
ffffec8e`2339f5d0 fffff801`35eabac5 : ffffda04`610f6a20 ffffda04`611d9010 ffffda04`611d9010 ffffda04`5732dd90 : Ntfs!NtfsFsdWrite+0x1d3
ffffec8e`2339f6a0 fffff801`329e70cf : ffffec8e`233a0008 00000000`00000000 ffffda04`611d9010 fffff801`329e70cf : nt!IofCallDriver+0x55
ffffec8e`2339f6e0 fffff801`329e4a03 : ffffec8e`2339f770 00000000`00000000 00000000`00000000 fffff801`35eae0ce : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffffec8e`2339f750 fffff801`35eabac5 : ffffda04`611d9010 00000000`00000204 ffffda04`5c88d320 fffff801`35eabac5 : FLTMGR!FltpDispatch+0xa3
ffffec8e`2339f7b0 fffff801`3621b538 : 00000000`00000001 ffffda04`5c88bed0 00000000`00000001 ffffda04`611d94d0 : nt!IofCallDriver+0x55
ffffec8e`2339f7f0 fffff801`3620a3bf : ffffda04`00000000 ffffec8e`2339fa80 00000000`167ddd64 ffffec8e`2339fa80 : nt!IopSynchronousServiceTail+0x1a8
ffffec8e`2339f890 fffff801`3600a2b5 : ffffda04`00000000 00000000`00001450 00000000`00000000 00000000`120f4fdc : nt!NtWriteFile+0x66f
ffffec8e`2339f990 00000000`77cd1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0559ede8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cd1cfc
SYMBOL_NAME: nt!KeAccumulateTicks+1dcbc8
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1889
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1dcbc8
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
--------- 尊敬的用户您好!欢迎咨询Microsoft本站,我的名字是Li,很高兴能够回答您的问题。当您电脑蓝屏的时候需要.dmp格式的文件进行分析查看并定位蓝屏错误的位置,minidump文件路径:C:\Windows\Minidump如果您的电脑中没有这个文件需要进行一些设置:打开控制面板-系统和安全-系统-高级系统设置-启动和故障恢复打开设置写入调试信息设置成【小内存转储256kb】小转储目录设置成【%SystemRoot%\Minidump】设置完毕后重新启动,电脑在下次蓝屏会生成新的文件,到时您可以把蓝屏文件上传到百度网盘等地方并提供下载链接。
链接:https://pan.baidu.com/s/1B9vdt8tUQPdmP7tjVfoGMw?pwd=4chy提取码:4chy这个是生成的dmp文件,麻烦你了。此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
尊敬的用户您好!