|
|
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80142105330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
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: 1499
Key : Analysis.Elapsed.mSec
Value: 14397
Key : Analysis.IO.Other.Mb
Value: 10
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 26
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 58932
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x133_DPC_storport!RaidAdapterResetBus
Key : Failure.Hash
Value: {cb87a960-bcb8-103e-455a-147d271692cc}
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80142105330
FILE_IN_CAB: 091423-15343-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9e80`8fbff9e8 fffff801`416db69e : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9e80`8fbff9f0 fffff801`416db121 : 00006454`62cc8dc6 ffff9e80`00000500 00000000`00000297 fffff801`41798325 : nt!KeAccumulateTicks+0x39e
ffff9e80`8fbffa60 fffff801`416d8156 : 00000000`0017f46d 00000000`000e4735 00000039`1cd7b963 00000000`00000000 : nt!KiUpdateRunTime+0x61
ffff9e80`8fbffac0 fffff801`416d9462 : ffffe480`698aee40 00000000`00000000 fffff801`4202b568 00000000`00000000 : nt!KiUpdateTime+0x686
ffff9e80`8fbffeb0 fffff801`416d6d92 : ffffe480`698aee40 ffffd486`12f83950 ffffd486`00000000 00000000`00000002 : nt!KeClockInterruptNotify+0x272
ffff9e80`8fbfff40 fffff801`4168d6a0 : 00000039`1d169f21 ffffd486`12f838a0 00000000`00000001 00000000`00000040 : nt!HalpTimerClockInterrupt+0xe2
ffff9e80`8fbfff70 fffff801`418175ca : ffffe480`698aeec0 ffffd486`12f838a0 00000000`00000000 00000000`00000003 : nt!KiCallInterruptServiceRoutine+0xa0
ffff9e80`8fbfffb0 fffff801`41817b97 : 00000000`00000000 00000000`00000000 00000000`00000000 00001f80`00000200 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffe480`698aee40 fffff801`47045cce : 00000000`0000000b ffffe480`698af060 00000000`00000000 fffff801`4701fda3 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffe480`698aefd0 fffff801`4703d493 : 00000000`00000004 ffffd486`2e279cf0 ffffd486`173d11a0 00000000`00000004 : storport!RaidAdapterResetBus+0xee
ffffe480`698af130 fffff801`416cc394 : 00000000`00000002 00000000`00000001 ffffe480`698af2a9 ffffd486`00000002 : storport!RaidUnitPendingDpcRoutine+0x1ce03
ffffe480`698af1e0 fffff801`416ca984 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`40b529c8 : nt!KiProces**piredTimerList+0x204
ffffe480`698af310 fffff801`4181990e : 00000000`00000000 ffff9e80`8fbe4180 ffff9e80`8fbf0840 ffffd486`2f6c0080 : nt!KiRetireDpcList+0x714
ffffe480`698af5c0 00000000`00000000 : ffffe480`698b0000 ffffe480`698a9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: storport!RaidAdapterResetBus+ee
MODULE_NAME: storport
IMAGE_NAME: storport.sys
IMAGE_VERSION: 10.0.22000.675
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: ee
FAILURE_BUCKET_ID: 0x133_DPC_storport!RaidAdapterResetBus
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {cb87a960-bcb8-103e-455a-147d271692cc}
Followup: MachineOwner
存储端口驱动storport.sys的故障，你是否安装了什么西数的官方驱动之类的东西？你这个系统下还挂了哪些盘？ |
|
310112100042806
发表于 2023-9-14 16:51
草，看到这个帖子，我的7950x也蓝了，故障代码一样
造孽
