Analyzers
Support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)
4752 Discussions

vtss.sys caused Windows 11 bluescreen when installing DPC++ Compatibility Tool

Ayka
Beginner
260 Views

Hi,

When the installation of Intel oneAPI Base Toolkit, v. 2022 proceeded to Intel DPC++ Compatibility Tool, my Windows 11 system froze and showed a blue screen with error code: DPC_WATCHDOG_VIOLATION. Before Intel DPC++ Compatibility Tool, the offline installer has already installed Intel Advisor, Intel oneAPI DPC++ Library, and Intel VTune(TM) Profiler. I tried to remove the installed components by Windows Install Clean Up and re-installed, however, there was still a blue screen. I viewed the Minidump file under C:\Windows\Minidump and analyzed the generated two dump files by Windbg Preview 1.2202.7001.0 (Administrator) using command `analyze -v`. The two dump files have the same results:

Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff807`4ba00000 PsLoadedModuleList = 0xfffff807`4c629bc0
Debug session time: Wed Feb 23 13:04:13.434 2022 (UTC + 8:00)
System Uptime: 0 days 10:39:20.422
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:
fffff807`4be16220 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbc00`b631a9f0=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: 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: fffff8074c705330, 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: 3187

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 9285

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

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

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


FILE_IN_CAB:  022322-17062-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8074c705330

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbc00`b631a9e8 fffff807`4bcdb5ff     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`4c705330 : nt!KeBugCheckEx
ffffbc00`b631a9f0 fffff807`4bcdb211     : 00001a15`8a6caa8b ffffbc00`b6300180 ffff58e6`318cc154 fffff807`4bd98775 : nt!KeAccumulateTicks+0x20f
ffffbc00`b631aa60 fffff807`4bcd8246     : 00000000`0025761b 00000000`00165426 00000059`50980180 00000000`00000000 : nt!KiUpdateRunTime+0x61
ffffbc00`b631aac0 fffff807`4bcd9552     : ffffab09`bd4ef750 00000000`00000000 fffff807`4c62b380 00000000`00000000 : nt!KiUpdateTime+0x686
ffffbc00`b631aeb0 fffff807`4bcd6e82     : ffffab09`bd4ef750 ffff8002`310aff50 ffff8002`00000000 00000000`00000002 : nt!KeClockInterruptNotify+0x272
ffffbc00`b631af40 fffff807`4bc8d720     : 00000059`50a80a9c ffff8002`310afea0 ffffbc00`b6a93970 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffbc00`b631af70 fffff807`4be17e2a     : ffffab09`bd4ef7d0 ffff8002`310afea0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa0
ffffbc00`b631afb0 fffff807`4be183f7     : 00000000`bb37c832 00000000`00000001 00000000`00000000 fffff807`4bd59e4b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffab09`bd4ef750 fffff807`4bc95e1c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffab09`bd4ef8e0 fffff807`4bc95de1     : fffff807`4c64d118 ffffbc00`b6300180 ffff4fef`3af39304 ffff4fef`00000002 : nt!KxWaitForSpinLockAndAcquire+0x2c
ffffab09`bd4ef910 fffff807`4bf20b89     : 00000000`00000000 00000000`00000000 00000000`0108fda0 00000000`02d2fb34 : nt!KeAcquireSpinLockRaiseToDpc+0xc1
ffffab09`bd4ef940 fffff807`4c28d2b8     : 00000000`00000008 00000000`00000000 00000000`00000000 ffff8002`74aab1c0 : nt!HalpRegisterProfileSourceInterruptHandler+0x19
ffffab09`bd4ef970 fffff807`ac4b1dbc     : ffff8002`736d6d00 ffff8002`5b22c080 00000000`779936e0 00000000`02d2fa0c : nt!HalpSetSystemInformation+0xabae8
ffffab09`bd4ef9a0 ffff8002`736d6d00     : ffff8002`5b22c080 00000000`779936e0 00000000`02d2fa0c 00000000`00d5c000 : vtss+0x1dbc
ffffab09`bd4ef9a8 ffff8002`5b22c080     : 00000000`779936e0 00000000`02d2fa0c 00000000`00d5c000 00000000`00000000 : 0xffff8002`736d6d00
ffffab09`bd4ef9b0 00000000`779936e0     : 00000000`02d2fa0c 00000000`00d5c000 00000000`00000000 00000000`00000000 : 0xffff8002`5b22c080
ffffab09`bd4ef9b8 00000000`02d2fa0c     : 00000000`00d5c000 00000000`00000000 00000000`00000000 fffff807`4be28775 : 0x779936e0
ffffab09`bd4ef9c0 00000000`00d5c000     : 00000000`00000000 00000000`00000000 fffff807`4be28775 ffff8002`724e2080 : 0x2d2fa0c
ffffab09`bd4ef9c8 00000000`00000000     : 00000000`00000000 fffff807`4be28775 ffff8002`724e2080 ffff8002`54e99af0 : 0xd5c000


SYMBOL_NAME:  vtss+1dbc

MODULE_NAME: vtss

IMAGE_NAME:  vtss.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1dbc

FAILURE_BUCKET_ID:  0x133_ISR_vtss!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9bea1b25-7b12-a130-9e47-df6b77a6b755}

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

It seems that the previously installed Intel VTune(TM) Profiler has some errors.

The system information is:

Processor: Intel(R) Core(TM) i7-8750H CPU @ 2.20 GHz  2.21 GHz

Windows version: Windows 11 21H2

Operating system version: 22000. 493

Experience pack version: 1000.22000.493.0

System type: 64-bit operating system based on x64 processor

0 Kudos
0 Replies
Reply