Could you expand a bit more

AndrewC · ‎11-10-2014

I am getting a 100% repeatable BSOD on Windows 7 running Amplifier 2015 Update 1 (build 380310), native code.

Advanced Hotspots ->Hotspots -> NO PROBLEM
Advanced Hotspots ->Hotspots , stacks and context switches ->BSOD after a few seconds.

Suggestions?

Peter_W_Intel · ‎11-10-2014

Thank you to report this with dump file, I have escalated this problem to developer.

Not sure if it will get OK after uninstalling/reinstalling vtss++ driver on your side:

C:\temp>"C:\Program Files (x86)\Intel\VTune Amplifier XE 2015\bin32\amplxe-sepreg" -u
Stopping and removing sepdrv3_15...OK
Stopping and removing VTSS++ driver...OK

C:\temp>"C:\Program Files (x86)\Intel\VTune Amplifier XE 2015\bin32\amplxe-sepreg" -i
Installing and starting sepdrv3_15...OK
Installing and starting sepdal...OK
Installing and starting VTSS++ driver...OK

Vitaly_S_Intel · ‎11-10-2014

Hi vasci_,

Which CPU do you have on this system?

Vitaly_S_Intel · ‎11-10-2014

Found whole system specification in attachment, thanks!

Peter_W_Intel · ‎11-10-2014

Hotspot with stack sampling should NOT be hardware relevant?

>"C:\Program Files (x86)\Intel\VTune Amplifier XE 2015\bin32\amplxe-feedback.exe" -create-bug-report log-file

Vitaly_S_Intel · ‎11-11-2014

They are hardware relevant.

Peter_W_Intel · ‎11-11-2014

Sorry. I didn't see "Advanced Hotspots".

Anyway, try to shutdown/restart VTune drivers first...

AndrewC · ‎11-11-2014

System Report

OS Name   Microsoft Windows 7 Professional
Version   6.1.7601 Service Pack 1 Build 7601
Other OS Description    Not Available
OS Manufacturer   Microsoft Corporation
System Name   BOSE
System Manufacturer   System manufacturer
System Model   System Product Name
System Type   x64-based PC
Processor   Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz, 3701 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. 4701, 8/26/2014
SMBIOS Version   2.7
Windows Directory   C:\Windows
System Directory   C:\Windows\system32
Boot Device   \Device\HarddiskVolume1
Locale   United States
Hardware Abstraction Layer   Version = "6.1.7601.17514"
User Name   Not Available
Time Zone   Pacific Standard Time
Installed Physical Memory (RAM)   32.0 GB
Total Physical Memory   31.9 GB
Available Physical Memory   29.1 GB
Total Virtual Memory   79.9 GB
Available Virtual Memory   77.1 GB
Page File Space   47.9 GB
Page File   C:\pagefile.sys

AndrewC · ‎11-11-2014

Re-installing the vtss++ drivers did not help at all.

Marián__VooDooMan__M · ‎11-11-2014

I had same issue yesterday (same exception string), here it is i7 Haswell, Win 8.1 Pro x64, 4 cores, 8 logical processors, x64 target app.

Marián__VooDooMan__M · ‎11-11-2014

There are more informations about my case:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {18, 0, ffffd001cf980180, 7}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd001cf980180, The PRCB address of the hung processor.
Arg4: 0000000000000007, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  procexp64.exe

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff801`9b34cc88 fffff801`999f9f7f : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd001`cf980180 : nt!KeBugCheckEx
fffff801`9b34cc90 fffff801`998ca165 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xb8cf
fffff801`9b34cd20 fffff801`9982767f : 00000000`00000001 00000000`00000001 fffff801`998739b0 00000000`00000001 : nt!KeClockInterruptNotify+0x785
fffff801`9b34cf40 fffff801`9997076a : fffff801`99873900 fffff801`9998c75b fffff801`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
fffff801`9b34cf70 fffff801`999df62a : fffff801`99873900 00000000`00000001 00000000`00000000 00000000`0002c308 : nt!KiCallInterruptServiceRoutine+0x8a
fffff801`9b34cfb0 fffff801`999dfa0f : 00000000`000003aa fffff801`99b8f180 00000000`00000001 00000000`000003aa : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`23915ed0 fffff801`998bbf38 : 00000000`00000002 fffff801`eb68cb30 00000000`00000000 00000000`00000282 : nt!KiInterruptDispatchLBControl+0x11f
ffffd000`23916060 fffff801`99c53902 : 0000007f`05e34020 ffffd000`23916b80 00000000`00000005 ffffe000`af6520b0 : nt!KeFlushProcessWriteBuffers+0x174
ffffd000`23916160 fffff801`99c632c2 : 00000001`00011d79 00000402`0002c308 fffffa80`0e0cd800 00000000`00000000 : nt!ExpGetProcessInformation+0xe2
ffffd000`23916400 fffff801`99c627e9 : 0000007f`05e34020 00000000`00000000 0000007f`6ce5e030 00000000`00000000 : nt!ExpQuerySystemInformation+0xa86
ffffd000`23916ac0 fffff801`999e99b3 : 00000000`000032d7 00000000`00000000 fffff801`eb68bc5c 00000000`00000000 : nt!NtQuerySystemInformation+0x49
ffffd000`23916b00 00007ffd`420719da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000007f`769fd038 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`420719da


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:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_8_proc_analysis_inconclusive

FAILURE_ID_HASH:  {f60c102e-9b2c-017b-9309-e4af1999e360}

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

Robert_L_Intel1 · ‎11-11-2014

Hi VooDooMan - I happened to notice PROCESS_NAME: procexp64.exe in your debug output. I wonder if process explorer is interfering at the driver level. Do you still get BSOD when you disable process explorer?

Marián__VooDooMan__M · ‎11-11-2014

Bob L. HUD (Intel) wrote:

Hi VooDooMan - I happened to notice PROCESS_NAME: procexp64.exe in your debug output. I wonder if process explorer is interfering at the driver level. Do you still get BSOD when you disable process explorer?

I failed to reproduce it any more, with, or without process explorer running. To the best of my knowledge, process explorer is only querying performance counters, it has no kernel driver, nor it needs to be ran under elevated/administrator account, though I tend to run it so, because it helps me lot when I am debugging my projects, or I need to kill buggy GNU software running under elevated account, like daily backup triggered by task scheduler.

Bernard · ‎11-11-2014

>>>To the best of my knowledge, process explorer is only querying performance counters, it has no kernel driver,>.>

Do you mean Sysinternals ProcessExplorer? If you do so I think that ProcessExplorer has kernel mode driver which is used to read DispatcherReadyList and to read ProcessListHead and ThreadListHead.

I think that this address should be inspected. Try to list all loaded modules and compare if the address pasted below falls into range of ProcessExplorer.

	
				0x00007ffd`420719da

61

Bernard · ‎11-11-2014

@vasci

Can you load kernel memory dump in windbg and run this command !pcrb 1?

I hope that currently executing thread on CPU 1 will be listed.

AndrewC · ‎11-11-2014

Could you expand a bit more on what you want me to do?

install Windows Debugging tools
Load kernel memory dump - do you mean from the .dmp file I sent?
Execute command !pcrb 1?

Bernard · ‎11-11-2014

Sorry for non informative answer.

1) Please install Windows Debugging Tools.

2) Please open full kernel memory dump with windbg.

3) Please execute !pcrb 1 or !pcrb fffff80038a518 and post the output.

AndrewC · ‎11-11-2014

Unfortunately, those commands give the response from WInDbg

0: kd> !pcrb 1
No export pcrb found

The stack is

0: kd> k
Child-SP RetAddr Call Site
fffff880`091e4b58 fffff800`0311ba4a nt!KeBugCheckEx
fffff880`091e4b60 fffff800`030ce6f7 nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`091e4bf0 fffff800`03010895 nt!KeUpdateSystemTime+0x377
fffff880`091e4cf0 fffff800`030c1113 hal!HalpHpetClockInterrupt+0x8d
fffff880`091e4d20 fffff800`030e4302 nt!KiInterruptDispatchNoLock+0x163
fffff880`091e4eb0 fffff800`030e6c98 nt!MiFlushTbAsNeeded+0x282
fffff880`091e4fc0 fffff800`031f5f86 nt!MiAllocatePagedPoolPages+0x4cc
fffff880`091e50e0 fffff800`030e49b0 nt!MiAllocatePoolPages+0x906
fffff880`091e5220 fffff800`031f943e nt!ExpAllocateBigPool+0xb0
fffff880`091e5310 fffff800`033a3ed6 nt!ExAllocatePoolWithTag+0x82e
fffff880`091e5400 fffff800`033a45f6 nt!IopQueryNameInternal+0x66
fffff880`091e54a0 fffff800`0339c2a0 nt!IopQueryName+0x26
fffff880`091e54f0 fffff800`0331eaf3 nt!ObpQueryNameString+0xb0
fffff880`091e55f0 fffff800`0337c98e nt! ?? ::NNGAKEGL::`string'+0x204f4
fffff880`091e5790 fffff800`03399fd9 nt!PspExitProcess+0x4e
fffff880`091e57f0 fffff800`0337eb7d nt!PspExitThread+0x4e9
fffff880`091e58f0 fffff800`030b76fa nt!PsExitSpecialApc+0x1d
fffff880`091e5920 fffff800`030b7a40 nt!KiDeliverApc+0x2ca
fffff880`091e59a0 fffff800`030c3ef7 nt!KiInitiateUserApc+0x70
fffff880`091e5ae0 00000000`00000000 nt!KiSystemServiceExit+0x9c

AndrewC · ‎11-11-2014

Uploaded full windbg transcript

Robert_L_Intel1 · ‎11-11-2014

!prcb :)

AndrewC · ‎11-11-2014

0: kd> !prcb 1
Cannot get PRCB address
0: kd> !prcb fffff80038a518
Cannot get PRCB address

BSOD on Windows 7 using Amplifier 2015 Update 1