Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Valentin_P_
Beginner
95 Views

BSOD when using Advanced hotspots, VTune Amplifier 2017 Update 3

Hello. I'm profiling a c++ desktop application.

After updating VTune from 2016 U4 to 2017 U3 and switching to Visual Studio 2017 every time I launch Advanced Hotspots Analysis after 4-5 seconds I get OS freeze and BSOD 0x101 CLOCK_WATCHDOG_TIMEOUT.  I've tried multiple combinations of settings (basic, with call stacks, with call counts, different sampling intervals) but all cause BSOD.

Basic Hotspots working fine.

My OS is Windows 7 x64 with all updates and Visual Studio 2017 Community. CPU is Intel Core i5 3570K

 

Updated: On my second PC with Win10 (with all major updates) and VS2017 and same CPU. After starting Advanced hotspots system freezing, but still possible to launch Task Manager, but no bsod.

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003565180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0b30a048 fffff800`030d9bf9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03565180 : nt!KeBugCheckEx
fffff880`0b30a050 fffff800`03089d27 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffff8a0`273a6ddc : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`0b30a0e0 fffff800`03600895 : fffff800`03626460 fffff880`0b30a290 fffff800`03626460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0b30a1e0 fffff800`0307c6d3 : 00000000`69bf6f1a fffff800`031fee80 fffff800`031fee80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0b30a210 fffff800`03085020 : fffff800`031fee80 fffff8a0`00000001 00000000`00000000 fffff880`0b30a4a8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0b30a3a0 fffff800`0309fe71 : 00000000`00000000 00000000`00000008 00000000`00000001 fffff800`00000001 : nt!KeFlushMultipleRangeTb+0x250
fffff880`0b30a470 fffff800`030a28e8 : 00000000`00000008 fffff880`0b30a5c0 fffff8a0`1f48b000 00000000`00000001 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`0b30a580 fffff800`031b4f86 : 00000000`00008000 fffffa80`0c6d3000 00000000`00000009 00000000`00000435 : nt!MiAllocatePagedPoolPages+0x4cc
fffff880`0b30a6a0 fffff800`030a05f0 : 00000000`00008000 fffffa80`0c6d3000 00000000`00000009 20206553`03075d6d : nt!MiAllocatePoolPages+0x906
fffff880`0b30a7e0 fffff800`031b844e : 00000000`00000000 ffffffff`11bfd700 00000000`00000000 00000000`00008000 : nt!ExpAllocateBigPool+0xb0
fffff880`0b30a8d0 fffff800`03093585 : 00000000`00000000 00000000`00000009 fffff8a0`015b5060 fffff800`0336eedf : nt!ExAllocatePoolWithTag+0x82e
fffff880`0b30a9c0 fffff800`032e883e : 00000000`00000000 00000000`00008000 00000000`00000000 fffff8a0`22fb02e0 : nt!ExAllocatePoolWithQuotaTag+0x55
fffff880`0b30aa10 fffff800`03344d30 : fffff8a0`22fb02e0 fffff800`00008000 fffff880`0b30ab01 fffff800`03554de0 : nt!PiControlGetInterfaceDeviceList+0x92
fffff880`0b30aa90 fffff800`0307f413 : fffffa80`12a2a060 00000000`01c3e840 fffff880`0b30ab60 00000000`01c3e8c8 : nt!NtPlugPlayControl+0x100
fffff880`0b30aae0 00000000`7718cb8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01c3e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7718cb8a


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_4_proc_analysis_inconclusive

FAILURE_ID_HASH:  {d61e255a-5a6a-8ac9-10f0-973c0c42bda6}

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

 

0 Kudos
6 Replies
Andres_V_
Beginner
95 Views

I've experienced similar problems with an i7-4900MQ, also on 64 bit Windows 7 SP1 (fully patched).

Frazer_C_
Beginner
95 Views

I'm also getting frequent freezes with 2017 U3 and Advanced Hotspots from the command line. Win7 x64 SP1

jimdempseyatthecove
Black Belt
95 Views

On 2017u4, Win7, i7 2600K, x64, run as administrator

Advanced Hotspots with, 1ms, radio button at "Hotspots", Event mode All (no check boxes checked), this runs OK

Advanced Hotspots with, 1ms, radio button at "Hotspots, call counts, loop trip counts and stacks", Event mode All (no check boxes checked), this causes BSOD after about 8 seconds into 30 second test run.

Will try just "Hotspots and stacks"

Jim Dempsey

 

jimdempseyatthecove
Black Belt
95 Views

That fails too, hower system locked up instead of BSOD. Let system hang for ~2 minutes, mouse dead, Ctrl-Shift-Esc would not bring up Task Manager, Alt-Tab inactive, Ctrl-Alt-Del would not respond, rebooted via power button.

Jim Dempsey.

jimdempseyatthecove
Black Belt
95 Views

Installed VTune 2017 update 4 (7 July) and this corrected the problem with Hotspots w/ stack

Jim Dempsey

jimdempseyatthecove
Black Belt
95 Views

On a different thread it was noted that pin.exe has issues running with Antivirus systems. By correcting that issue (Adding to AV exsclusion) this also correction the BSOD. (at least for now).

Jim Dempsey

Reply