Windows 10 x64 bluescreens after running the "stress test" from CPUz, vtss.sys being the culprit

[Etienne_K_]

Hello,

I have two 33GB memory dumps of this bluescreen which I can gladly supply.

FOLLOWUP_IP: 
vtss+12b72
fffff800`17192b72 c3              ret

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  vtss+12b72

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vtss

IMAGE_NAME:  vtss.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55c4d1c4

STACK_COMMAND:  .cxr 0xffffd00135eb3370 ; kb

BUCKET_ID_FUNC_OFFSET:  12b72

FAILURE_BUCKET_ID:  0x3B_vtss!Unknown_Function

BUCKET_ID:  0x3B_vtss!Unknown_Function

PRIMARY_PROBLEM_CLASS:  0x3B_vtss!Unknown_Function

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_vtss!unknown_function

FAILURE_ID_HASH:  {739a51cd-f64b-01d1-9bcb-25792e387d80}

[Peter_W_Intel]

Thank you for this report. You may try this first, when meet crash again.

>amplxe-feedback -create-bug-report <report archive>
>amplxe-feedback -send-crash-report=<report archive>

[Bernard]

@Etienne

I provided an answer on your second post with  a request to run few windbg commands needed to extract additional bits of information of this frequently occurring BugCheck.