vtss.sys crash during every Hotspots analysis on Alderlake

cwasser · ‎06-16-2022

On my System running a I7-12700k the Hotspots Analysis using Hardware Event-Based Sampling results in a crash of vtss.sys within the first few seconds of running the profiled application every time (The profiled application also runs extremely slow, if that helps). This time it's a KMODE_EXCEPTION_NOT_HANDLED other times it's a Watchdog timeout that causes the crash. Please let me know what additional information you need to solve this issue.

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 100


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 22000 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff807`3c200000 PsLoadedModuleList = 0xfffff807`3ce29750
Debug session time: Thu Jun 16 13:09:41.234 2022 (UTC + 2:00)
System Uptime: 0 days 2:54:15.845
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000003e`f41e8018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`3c617820 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffa0d`53baea40=000000000000001e
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8073fa86d03, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2062

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5591

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

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

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

    Key  : Bugcheck.DumpVsMemoryMatch
    Value: True

    Key  : Dump.Attributes.AsUlong
    Value: 1800

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8073fa86d03

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  vctip.exe

TRAP_FRAME:  fffff80700000000 -- (.trap 0xfffff80700000000)
Unable to read trap frame at fffff807`00000000

STACK_TEXT:  
fffffa0d`53baea38 fffff807`3c686fa9     : 00000000`0000001e ffffffff`c0000005 fffff807`3fa86d03 00000000`00000000 : nt!KeBugCheckEx
fffffa0d`53baea40 fffff807`3c62a5ce     : fffffa0d`53baf400 ffffdf02`369ee060 fffff807`00000000 00000000`00000001 : nt!KiDispatchException+0x1f05a9
fffffa0d`53baf120 fffff807`3c62618f     : fffffa0d`00000000 00000000`00000000 00000000`000000ff 00000000`00000001 : nt!KiExceptionDispatch+0x10e
fffffa0d`53baf300 fffff807`3fa86d03     : fffff807`3fa85ff4 00000000`00000010 00000000`00040282 fffffa0d`53baf4c8 : nt!KiGeneralProtectionFault+0x30f
fffffa0d`53baf498 fffff807`3fa85ff4     : 00000000`00000010 00000000`00040282 fffffa0d`53baf4c8 00000000`00000018 : vtss+0x16d03
fffffa0d`53baf4a0 00000000`00000010     : 00000000`00040282 fffffa0d`53baf4c8 00000000`00000018 00000000`00000a00 : vtss+0x15ff4
fffffa0d`53baf4a8 00000000`00040282     : fffffa0d`53baf4c8 00000000`00000018 00000000`00000a00 fffff807`3fa7fc93 : 0x10
fffffa0d`53baf4b0 fffffa0d`53baf4c8     : 00000000`00000018 00000000`00000a00 fffff807`3fa7fc93 00000000`00000000 : 0x40282
fffffa0d`53baf4b8 00000000`00000018     : 00000000`00000a00 fffff807`3fa7fc93 00000000`00000000 00000000`00000000 : 0xfffffa0d`53baf4c8
fffffa0d`53baf4c0 00000000`00000a00     : fffff807`3fa7fc93 00000000`00000000 00000000`00000000 00000000`00000000 : 0x18
fffffa0d`53baf4c8 fffff807`3fa7fc93     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa00
fffffa0d`53baf4d0 fffff807`3fa72cf8     : ffff8488`27f10000 00000000`00040282 00000000`0003a2a3 00000000`00040082 : vtss+0xfc93
fffffa0d`53baf5e0 fffff807`3fa73504     : 00000000`00000000 00000000`00000000 00000000`00001927 ffffa47e`90000000 : vtss+0x2cf8
fffffa0d`53baf7d0 fffff807`3c54fb44     : ffff8488`3b6f1080 fffffa0d`53baf869 00000000`00000000 fffff807`3c47f1e1 : vtss+0x3504
fffffa0d`53baf810 fffff807`3c55004b     : 00000000`00000000 00000000`00000000 ffffdf02`11a94a70 fffff807`00000000 : nt!KiDeliverApc+0x314
fffffa0d`53baf8d0 fffff807`3c453f9f     : 00000000`000008a2 ffff8487`feba6090 fffff808`00ad8350 ffff8488`23489bb8 : nt!KiCheckForKernelApcDelivery+0x2b
fffffa0d`53baf900 fffff807`3c86c10d     : 00000000`000008a2 ffff8488`17ba30c0 ffff8488`2e740490 00000000`0000003d : nt!KeLeaveCriticalRegionThread+0x2f
fffffa0d`53baf930 fffff807`3c86b46d     : 00000000`000008a2 ffffdf02`11a94ac0 fffffa0d`53bafaa0 ffff8488`35ae83e0 : nt!PsCallImageNotifyRoutines+0x13d
fffffa0d`53baf9a0 fffff807`3c9bb5e4     : ffff8488`17a1b5a0 00000000`00008664 fffffa0d`53bafb88 fffffa0d`53bafcd8 : nt!MiMapViewOfImageSection+0x7ed
fffffa0d`53bafb40 fffff807`3c9bb8f9     : 00000000`00000000 fffffa0d`53bafea0 000001d1`6f7ad040 00000000`00000000 : nt!MiMapViewOfSection+0x424
fffffa0d`53bafc70 fffff807`3c629e75     : ffff8488`3b6f1080 0000003e`f567d048 0000003e`f567d1b8 00000000`00000000 : nt!NtMapViewOfSection+0x159
fffffa0d`53bafdb0 00007ffe`a3b043b4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000003e`f567d028 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`a3b043b4


SYMBOL_NAME:  vtss+16d03

MODULE_NAME: vtss

IMAGE_NAME:  vtss.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  16d03

FAILURE_BUCKET_ID:  AV_R_vtss!unknown_function

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d1b849af-a6e9-2996-3497-184b2585ea5b}

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

cwasser · ‎07-16-2022

With Windows 11 Build 22000.795 I don't get a bluescreen anymore.
I am still using Vtune version 2022.3, so it must be a Window update.
However program execution is still painfully slow on Alderlake...

vtss.sys crash during every Hotspots analysis on Alderlake

Intel VTune™ Profiler