F5F Stay Refreshed Hardware Desktop Question Blue Screen of Death (Anyone able to tell me why from Dump file )?

Question Blue Screen of Death (Anyone able to tell me why from Dump file )?

Question Blue Screen of Death (Anyone able to tell me why from Dump file )?

D
dayEric
Member
Find
71
12-19-2024, 08:44 PM
#1
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft ® Windows Debugger Version 10.0.25877.1004 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011424-23046-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 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff801`33800000 PsLoadedModuleList = 0xfffff801`344134a0
Debug session time: Sun Jan 14 00:55:23.896 2024 (UTC + 1:00)
System Uptime: 2 days 13:52:56.218
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`33c16b00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9d00`c952bc90=0000000000000133
2: 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: 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: fffff8013451d340, 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: 530
Key : Analysis.Elapsed.mSec
Value: 11633
Key : Analysis.IO.Other.Mb
Value: 23
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 31
Key : Analysis.Init.CPU.mSec
Value: 77
Key : Analysis.Init.Elapsed.mSec
Value: 32312
Key : Analysis.Memory.CommitPeak.Mb
Value: 102
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x133_DPC_ksUSBa64!unknown_function
Key : Failure.Hash
Value: {8acc3cb8-dd0d-4788-b617-be4381454922}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8013451d340
FILE_IN_CAB: 011424-23046-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
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:
ffff9d00`c952bc88 fffff801`33a12d55 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9d00`c952bc90 fffff801`33a12421 : 00025eea`69f73cf4 00000000`00d98e0d 00000000`00d98e0c 00000000`00000000 : nt!KeAccumulateTicks+0x3d5
ffff9d00`c952bcf0 fffff801`33a104b1 : 00000000`00000000 ffff9d00`ca676a00 ffff9d00`c9511180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
ffff9d00`c952bea0 fffff801`33a0feda : fffff801`3445ff80 ffff9d00`ca676ab0 ffff9d00`ca676ab0 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
ffff9d00`c952bf40 fffff801`33b24b2c : 00000206`b0fc63ff ffffae85`98f45200 ffffae85`98f452b0 fffff801`33c18a5b : nt!HalpTimerClockInterrupt+0x10a
ffff9d00`c952bf70 fffff801`33c18cba : fffff88a`5ae5e770 ffffae85`98f45200 ffffae85`b746b750 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffff9d00`c952bfb0 fffff801`33c19567 : ffffae85`98f108b0 00000000`00000007 ffffae85`c67309a0 ffffae85`c6730e60 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff88a`5ae5e6f0 fffff801`33ae7bff : ffffae85`c67309a0 ffffae85`aa5e5e10 ffffae85`ab103000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff88a`5ae5e880 fffff801`33a13850 : 00000000`000000f0 00000000`00000000 00000000`00000374 ffffae85`db32b290 : nt!KxWaitForSpinLockAndAcquire+0x1f
fffff88a`5ae5e8b0 fffff801`6f09c4b5 : 00000000`00000028 00000000`00000280 00000000`00000001 00000000`00000140 : nt!KeAcquireSpinLockAtDpcLevel+0x20
fffff88a`5ae5e8e0 00000000`00000028 : 00000000`00000280 00000000`00000001 00000000`00000140 ffffae85`b532b000 : ksUSBa64+0x5c4b5
fffff88a`5ae5e8e8 00000000`00000280 : 00000000`00000001 00000000`00000140 ffffae85`b532b000 00000000`00000780 : 0x28
fffff88a`5ae5e8f0 00000000`00000001 : 00000000`00000140 ffffae85`b532b000 00000000`00000780 00000000`c0000001 : 0x280
fffff88a`5ae5e8f8 00000000`00000140 : ffffae85`b532b000 00000000`00000780 00000000`c0000001 fffff801`6f0ad5f8 : 0x1
fffff88a`5ae5e900 ffffae85`b532b000 : 00000000`00000780 00000000`c0000001 fffff801`6f0ad5f8 ffffae85`df98b7f8 : 0x140
fffff88a`5ae5e908 00000000`00000780 : 00000000`c0000001 fffff801`6f0ad5f8 ffffae85`df98b7f8 00000000`000000f0 : 0xffffae85`b532b000
fffff88a`5ae5e910 00000000`c0000001 : fffff801`6f0ad5f8 ffffae85`df98b7f8 00000000`000000f0 ffffae85`dfd25000 : 0x780
fffff88a`5ae5e918 fffff801`6f0ad5f8 : ffffae85`df98b7f8 00000000`000000f0 ffffae85`dfd25000 ffffae85`99010140 : 0xc0000001
fffff88a`5ae5e920 ffffae85`df98b7f8 : 00000000`000000f0 ffffae85`dfd25000 ffffae85`99010140 ffff8e4d`461a1f11 : ksUSBa64+0x6d5f8
fffff88a`5ae5e928 00000000`000000f0 : ffffae85`dfd25000 ffffae85`99010140 ffff8e4d`461a1f11 fffff801`6f11c162 : 0xffffae85`df98b7f8
fffff88a`5ae5e930 ffffae85`dfd25000 : ffffae85`99010140 ffff8e4d`461a1f11 fffff801`6f11c162 00000000`00000000 : 0xf0
fffff88a`5ae5e938 ffffae85`99010140 : ffff8e4d`461a1f11 fffff801`6f11c162 00000000`00000000 fffff801`6f0adf30 : 0xffffae85`dfd25000
fffff88a`5ae5e940 ffff8e4d`461a1f11 : fffff801`6f11c162 00000000`00000000 fffff801`6f0adf30 ffffae85`d1345b00 : 0xffffae85`99010140
fffff88a`5ae5e948 fffff801`6f11c162 : 00000000`00000000 fffff801`6f0adf30 ffffae85`d1345b00 ffffae85`ddac9000 : 0xffff8e4d`461a1f11
fffff88a`5ae5e950 00000000`00000000 : fffff801`6f0adf30 ffffae85`d1345b00 ffffae85`ddac9000 00000000`000000f0 : ksUSBa64+0xdc162
SYMBOL_NAME: ksUSBa64+5c4b5
MODULE_NAME: ksUSBa64
IMAGE_NAME: ksUSBa64.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 5c4b5
FAILURE_BUCKET_ID: 0x133_DPC_ksUSBa64!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8acc3cb8-dd0d-4788-b617-be4381454922}
Followup: MachineOwner
---------
2: kd> lmvm ksUSBa64
Browse full module list
start end module name
fffff801`6f040000 fffff801`6f1ec000 ksUSBa64 T (no symbols)
Loaded symbol image file: ksUSBa64.sys
Image path: ksUSBa64.sys
Image name: ksUSBa64.sys
Browse all global symbols functions data
Timestamp: Wed Jan 6 04:45:02 2021 (5FF5323E)
CheckSum: 001B9B90
ImageSize: 001AC000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
Does anyone know what i got BSOD based on this ?
Reply
Reply
D
dayEric
12-19-2024, 08:44 PM #1

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft ® Windows Debugger Version 10.0.25877.1004 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011424-23046-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 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff801`33800000 PsLoadedModuleList = 0xfffff801`344134a0
Debug session time: Sun Jan 14 00:55:23.896 2024 (UTC + 1:00)
System Uptime: 2 days 13:52:56.218
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`33c16b00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9d00`c952bc90=0000000000000133
2: 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: 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: fffff8013451d340, 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: 530
Key : Analysis.Elapsed.mSec
Value: 11633
Key : Analysis.IO.Other.Mb
Value: 23
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 31
Key : Analysis.Init.CPU.mSec
Value: 77
Key : Analysis.Init.Elapsed.mSec
Value: 32312
Key : Analysis.Memory.CommitPeak.Mb
Value: 102
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 1808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x133_DPC_ksUSBa64!unknown_function
Key : Failure.Hash
Value: {8acc3cb8-dd0d-4788-b617-be4381454922}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8013451d340
FILE_IN_CAB: 011424-23046-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
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:
ffff9d00`c952bc88 fffff801`33a12d55 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9d00`c952bc90 fffff801`33a12421 : 00025eea`69f73cf4 00000000`00d98e0d 00000000`00d98e0c 00000000`00000000 : nt!KeAccumulateTicks+0x3d5
ffff9d00`c952bcf0 fffff801`33a104b1 : 00000000`00000000 ffff9d00`ca676a00 ffff9d00`c9511180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
ffff9d00`c952bea0 fffff801`33a0feda : fffff801`3445ff80 ffff9d00`ca676ab0 ffff9d00`ca676ab0 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
ffff9d00`c952bf40 fffff801`33b24b2c : 00000206`b0fc63ff ffffae85`98f45200 ffffae85`98f452b0 fffff801`33c18a5b : nt!HalpTimerClockInterrupt+0x10a
ffff9d00`c952bf70 fffff801`33c18cba : fffff88a`5ae5e770 ffffae85`98f45200 ffffae85`b746b750 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffff9d00`c952bfb0 fffff801`33c19567 : ffffae85`98f108b0 00000000`00000007 ffffae85`c67309a0 ffffae85`c6730e60 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff88a`5ae5e6f0 fffff801`33ae7bff : ffffae85`c67309a0 ffffae85`aa5e5e10 ffffae85`ab103000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff88a`5ae5e880 fffff801`33a13850 : 00000000`000000f0 00000000`00000000 00000000`00000374 ffffae85`db32b290 : nt!KxWaitForSpinLockAndAcquire+0x1f
fffff88a`5ae5e8b0 fffff801`6f09c4b5 : 00000000`00000028 00000000`00000280 00000000`00000001 00000000`00000140 : nt!KeAcquireSpinLockAtDpcLevel+0x20
fffff88a`5ae5e8e0 00000000`00000028 : 00000000`00000280 00000000`00000001 00000000`00000140 ffffae85`b532b000 : ksUSBa64+0x5c4b5
fffff88a`5ae5e8e8 00000000`00000280 : 00000000`00000001 00000000`00000140 ffffae85`b532b000 00000000`00000780 : 0x28
fffff88a`5ae5e8f0 00000000`00000001 : 00000000`00000140 ffffae85`b532b000 00000000`00000780 00000000`c0000001 : 0x280
fffff88a`5ae5e8f8 00000000`00000140 : ffffae85`b532b000 00000000`00000780 00000000`c0000001 fffff801`6f0ad5f8 : 0x1
fffff88a`5ae5e900 ffffae85`b532b000 : 00000000`00000780 00000000`c0000001 fffff801`6f0ad5f8 ffffae85`df98b7f8 : 0x140
fffff88a`5ae5e908 00000000`00000780 : 00000000`c0000001 fffff801`6f0ad5f8 ffffae85`df98b7f8 00000000`000000f0 : 0xffffae85`b532b000
fffff88a`5ae5e910 00000000`c0000001 : fffff801`6f0ad5f8 ffffae85`df98b7f8 00000000`000000f0 ffffae85`dfd25000 : 0x780
fffff88a`5ae5e918 fffff801`6f0ad5f8 : ffffae85`df98b7f8 00000000`000000f0 ffffae85`dfd25000 ffffae85`99010140 : 0xc0000001
fffff88a`5ae5e920 ffffae85`df98b7f8 : 00000000`000000f0 ffffae85`dfd25000 ffffae85`99010140 ffff8e4d`461a1f11 : ksUSBa64+0x6d5f8
fffff88a`5ae5e928 00000000`000000f0 : ffffae85`dfd25000 ffffae85`99010140 ffff8e4d`461a1f11 fffff801`6f11c162 : 0xffffae85`df98b7f8
fffff88a`5ae5e930 ffffae85`dfd25000 : ffffae85`99010140 ffff8e4d`461a1f11 fffff801`6f11c162 00000000`00000000 : 0xf0
fffff88a`5ae5e938 ffffae85`99010140 : ffff8e4d`461a1f11 fffff801`6f11c162 00000000`00000000 fffff801`6f0adf30 : 0xffffae85`dfd25000
fffff88a`5ae5e940 ffff8e4d`461a1f11 : fffff801`6f11c162 00000000`00000000 fffff801`6f0adf30 ffffae85`d1345b00 : 0xffffae85`99010140
fffff88a`5ae5e948 fffff801`6f11c162 : 00000000`00000000 fffff801`6f0adf30 ffffae85`d1345b00 ffffae85`ddac9000 : 0xffff8e4d`461a1f11
fffff88a`5ae5e950 00000000`00000000 : fffff801`6f0adf30 ffffae85`d1345b00 ffffae85`ddac9000 00000000`000000f0 : ksUSBa64+0xdc162
SYMBOL_NAME: ksUSBa64+5c4b5
MODULE_NAME: ksUSBa64
IMAGE_NAME: ksUSBa64.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 5c4b5
FAILURE_BUCKET_ID: 0x133_DPC_ksUSBa64!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8acc3cb8-dd0d-4788-b617-be4381454922}
Followup: MachineOwner
---------
2: kd> lmvm ksUSBa64
Browse full module list
start end module name
fffff801`6f040000 fffff801`6f1ec000 ksUSBa64 T (no symbols)
Loaded symbol image file: ksUSBa64.sys
Image path: ksUSBa64.sys
Image name: ksUSBa64.sys
Browse all global symbols functions data
Timestamp: Wed Jan 6 04:45:02 2021 (5FF5323E)
CheckSum: 001B9B90
ImageSize: 001AC000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
Does anyone know what i got BSOD based on this ?

Reply
Reply
P
pokesegachao
Member
Find
199
12-19-2024, 08:44 PM
#2
The BSOD resulted from a 'DPC WATCHDOG VIOLATION'. This suggests a Windows utility, the watchdog, which checks for unresponsive programs, is overloaded. It might be due to a conflicting driver, application, or file, especially if they are outdated or not responding properly.
Reply
Reply
P
pokesegachao
12-19-2024, 08:44 PM #2

The BSOD resulted from a 'DPC WATCHDOG VIOLATION'. This suggests a Windows utility, the watchdog, which checks for unresponsive programs, is overloaded. It might be due to a conflicting driver, application, or file, especially if they are outdated or not responding properly.

Reply
Reply
S
SpockyYT
Junior Member
Find
17
12-19-2024, 08:44 PM
#3
It was a Watchdog error during the BSOD, which could indicate many possible issues. That's why I included the dump log for further analysis. If anyone has experience interpreting these logs, they might help identify the specific error. My assumption is that the G6 driver in FAILURE_BUCKET_ID: 0x133_DPC_ksUSBa64!unknown_function is likely involved, though I'm not entirely certain due to limited familiarity with reading such files.
Reply
Reply
S
SpockyYT
12-19-2024, 08:44 PM #3

It was a Watchdog error during the BSOD, which could indicate many possible issues. That's why I included the dump log for further analysis. If anyone has experience interpreting these logs, they might help identify the specific error. My assumption is that the G6 driver in FAILURE_BUCKET_ID: 0x133_DPC_ksUSBa64!unknown_function is likely involved, though I'm not entirely certain due to limited familiarity with reading such files.

Reply
Reply
D
DaNiggaSWAG
Senior Member
Find
539
12-19-2024, 08:44 PM
#4
Does your audio equipment use a Sound Blaster design?
Reply
Reply
D
DaNiggaSWAG
12-19-2024, 08:44 PM #4

Does your audio equipment use a Sound Blaster design?

Reply
Reply