oneAPI Registration, Download, Licensing and Installation
Support for Getting Started questions related to download, Installation and licensing for Intel oneAPI Toolkits and software development tools.
1258 Discussions

vtss.sys caused Windows 11 bluescreen DPC_WATCHDOG_VIOLATION

Ayka
Novice
1,584 Views

Hi,

When the installation of Intel oneAPI Base Toolkit, v. 2022 (version 2022.1.2.154) 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 fileand 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 (part):

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 had some errors. After that, the installer could not be started after showing the icon.

0 Kudos
1 Solution
Soumya_M_Intel
Moderator
1,528 Views

Hi Ayka,


Sure! Thanks for your update on the thread. We have shared your feedback with our internal team. They are working to fix the issue in the upcoming release that would be available in a few weeks. You may keep an eye on the download website.


Intel® oneAPI Base Toolkit Download Link: https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html


Please let us know if you have further concerns or if you would like to close this thread. Looking forward to your update.


Regards,

Soumya


View solution in original post

0 Kudos
7 Replies
Ayka
Novice
1,549 Views

Sorry for opening multiple posts but previous posts are mis-marked as spams so I have to shorten my post...

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

Visual Studio version: 17.1.0

More of dump file analysis result:

nt!KeBugCheckEx:
fffff807`4be16220 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbc00`b631a9f0=0000000000000133
2: kd> !analyze -v
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:
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
0 Kudos
Soumya_M_Intel
Moderator
1,544 Views

Hi Ayka,


Thanks for posting your concern on the forum. Please note, our recent investigation has shown that on Microsoft* Windows*, the installation of Intel oneAPI Toolkits versions 2022.1 and 2022.1.2 and standalone components will fail using Microsoft* Visual Studio* 2022 version 17.1.x.

 

There are 2 possible workarounds, prior to installing an Intel oneAPI toolkit or component:

 

·      Uninstall Visual Studio 2022 version 17.1.x and install the older version 17.0.6 from here Visual Studio 2022 Release History | Microsoft Docs.

·      Replace Microsoft.VisualStudio.Setup.Configuration.Native.dll with same dll from a Visual Studi0 2022 17.0.x release. For example, from version 17.0.6 https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-history

 

We are striving to provide a new release in the weeks ahead to address this installation issue. However, please let us know if you have any other queries about this. Do let us know if the issue persists even after following one of the workarounds.


Regards,

Soumya


0 Kudos
Ayka
Novice
1,533 Views

Hi Soumya,

I'll wait for new releases and keep an eye on this issue, thanks!

0 Kudos
Soumya_M_Intel
Moderator
1,529 Views

Hi Ayka,


Sure! Thanks for your update on the thread. We have shared your feedback with our internal team. They are working to fix the issue in the upcoming release that would be available in a few weeks. You may keep an eye on the download website.


Intel® oneAPI Base Toolkit Download Link: https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html


Please let us know if you have further concerns or if you would like to close this thread. Looking forward to your update.


Regards,

Soumya


0 Kudos
Soumya_M_Intel
Moderator
1,511 Views

Hi Ayka,


Kindly let us know if you have other queries or if you would like to close this thread. Looking forward to your response.


Regards,

Soumya


0 Kudos
Ayka
Novice
1,491 Views

Hi Soumya,

It's OK to close this thread

0 Kudos
Soumya_M_Intel
Moderator
1,474 Views

Hi Ayka,


Thanks for getting back to us with the update on the post. Proceeding further we are closing this thread. However, if you need any additional information, please feel free to post a new question as this thread will no longer be monitored by Intel®. 


Have a wonderful day ahead!


Regards,

Soumya


0 Kudos
Reply