最近经常遇到蓝屏，导出的日志是这样的，可以帮我分析瞎什么问题吗

Question

最近经常遇到蓝屏，导出的日志是这样的，可以帮我分析瞎什么问题吗

匿名

Loading User Symbols Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8073c1f71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffca81651b5e20=0000000000000133

锁定的问题。此问题已从 Microsoft 支持社区迁移。你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。

0 个注释

4 个答案

Answer 1

DaveM121 888K 独立顾问

您的 PC 上是否有 USB 音频设备？

如果你这样做了，那就是你需要重新安装的驱动程序和软件

0 个注释

Answer 2

匿名

我该怎么找到这个驱动呢

0 个注释

Answer 3

Hi kunkun008

I am Dave, I will help you with this.

Your printout indicates it is a driver named artusbaud.sys that is causing the crashes, that is a driver associated to some USB audio device you have installed on our PC, you should remove those drivers, then restart your PC and re-install the latest version of the USB Audio drivers.

嗨 kunkun008

我是戴夫，我会帮你解决这个问题。

您的打印输出表明是一个名为 artusbaud.sys 的驱动程序导致崩溃，该驱动程序与您在我们的 PC 上安装的某些 USB 音频设备相关联，您应该删除这些驱动程序，然后重新启动您的 PC 并重新安装最新的 USB 音频驱动程序的版本。

Answer 4

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

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`3be00000 PsLoadedModuleList = 0xfffff807`3ca2a270
Debug session time: Wed Oct 20 22:18:29.791 2021 (UTC + 8:00)
System Uptime: 0 days 4:35:01.531
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`3c1f71b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffca81`651b5e20=0000000000000133
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: fffff8073cafb320, 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                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4171

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 51177

    Key  : Analysis.Init.CPU.mSec
    Value: 671

    Key  : Analysis.Init.Elapsed.mSec
    Value: 53870

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 89

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8073cafb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffffb06e17b8830 -- (.trap 0xfffffb06e17b8830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffff978d51fcd6f8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8073c0d79cc rsp=fffffb06e17b89c0 rbp=0000000000000dc8
 r8=0000000000000000  r9=0000000000000001 r10=fffff8073c122a80
r11=ffffba7979400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KxWaitForSpinLockAndAcquire+0x2c:
fffff807`3c0d79cc 488b07          mov     rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffca81`651b5e18 fffff807`3c21f57e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`3cafb320 : nt!KeBugCheckEx
ffffca81`651b5e20 fffff807`3c016953     : 000035fe`4e9970c8 ffffca81`6519c180 00000000`00000000 ffffca81`6519c180 : nt!KeAccumulateTicks+0x2063ce
ffffca81`651b5e80 fffff807`3c01643a     : ffff978d`51add600 fffffb06`e17b88b0 ffff978d`5f6e6100 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffffca81`651b5f30 fffff807`3c0de055     : ffff978d`51add600 fffff807`3c152447 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffffca81`651b5f60 fffff807`3c1f8c5a     : fffffb06`e17b88b0 ffff978d`51add600 00000000`00000200 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffca81`651b5fb0 fffff807`3c1f91c7     : 00000000`b4b8e8b0 ffffa90c`698b0020 ffff978d`649036f0 fffff807`3c007b00 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb06`e17b8830 fffff807`3c0d79cc     : 00000000`00000000 00000000`00000000 00000000`00000001 ffff978d`51fcd5a0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb06`e17b89c0 fffff807`3c0d7998     : ffff978d`51fcd6f8 ffffca81`6519c180 00000000`00000000 00000000`00000082 : nt!KxWaitForSpinLockAndAcquire+0x2c
fffffb06`e17b89f0 fffff807`49e17b55     : ffff978d`5fa5cb20 ffff978d`51fcd660 00000000`00000000 fffff807`3cb25440 : nt!KeAcquireSpinLockRaiseToDpc+0x88
fffffb06`e17b8a20 ffff978d`5fa5cb20     : ffff978d`51fcd660 00000000`00000000 fffff807`3cb25440 fffff807`3cb25440 : artusbaud+0x7b55
fffffb06`e17b8a28 ffff978d`51fcd660     : 00000000`00000000 fffff807`3cb25440 fffff807`3cb25440 00000000`00000200 : 0xffff978d`5fa5cb20
fffffb06`e17b8a30 00000000`00000000     : fffff807`3cb25440 fffff807`3cb25440 00000000`00000200 ffff978d`51fffb50 : 0xffff978d`51fcd660

SYMBOL_NAME:  artusbaud+7b55

MODULE_NAME: artusbaud

IMAGE_NAME:  artusbaud.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  7b55

FAILURE_BUCKET_ID:  0x133_ISR_artusbaud!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b9e398ba-2854-832c-39d7-9afd9f83657a}

Followup:     MachineOwner
---------

通过

最近经常遇到蓝屏，导出的日志是这样的，可以帮我分析瞎什么问题吗

4 个答案