Community
cancel
Showing results for 
Search instead for 
Did you mean: 
kmarisa
Beginner
54 Views

BSOD while trying to run on Server 2008 R2

Hi, I am seeing the following crash when I run the Vtune Performance Analyzer on Windows Server 2008 R2 X64 Enterprise when I have the HyperV Role installed. I do not see the crash when there is no HyperV Role installed. Any ideas?
1: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: sepdrv
FAULTING_MODULE: fffff8000165d000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a4b9e51
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800016c6c2e to fffff800016ceed0
STACK_TEXT:
fffff880`01c1aa58 fffff800`016c6c2e : fffff880`01c1ab88 fffffa80`539ecb10 fffff880`01c1b1d0 fffff800`016fbe28 : nt!KeBugCheck
fffff880`01c1aa60 fffff800`016f4bed : fffff800`018dbc24 fffff800`01814a3c fffff800`0165d000 fffff880`01c1b978 : nt!KiCpuId+0x41e
fffff880`01c1aa90 fffff800`016fc250 : fffff800`0181cb5c fffff880`01c1ab08 fffff880`01c1b978 fffff800`0165d000 : nt!KeReleaseQueuedSpinLock+0xdd
fffff880`01c1aac0 fffff800`017091b5 : fffff880`01c1b978 fffff880`01c1b1d0 fffff880`00000000 00000000`00000001 : nt!FsRtlLookupLastBaseMcbEntry+0x4c4
fffff880`01c1b1a0 fffff800`016ce542 : fffff880`01c1b978 fffff880`009f010f fffff880`01c1ba20 fffffa80`53dab7f0 : nt!FsRtlInitializeBaseMcbEx+0x42d1
fffff880`01c1b840 fffff800`016cce4a : fffffa80`25e80b10 fffff800`0167682b fffff880`01c1bb0d fffff800`01884910 : nt!KeSynchronizeExecution+0x3e32
fffff880`01c1ba20 fffff880`030fe041 : fffff880`0310bc16 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x273a
fffff880`01c1bbb8 fffff880`0310bc16 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : sepdrv+0x1041
fffff880`01c1bbc0 fffff880`0310c0dd : fffff880`009f0180 00000000`00000000 00000000`00000000 00000000`00000007 : sepdrv+0xec16
fffff880`01c1bbf0 fffff880`03105abc : 00000000`00000000 00000000`00000000 fffff800`0165d000 00000000`00000001 : sepdrv+0xf0dd
fffff880`01c1bc30 fffff880`030ff546 : 00000000`00000000 fffff800`01631652 00000000`00000010 00000000`00000246 : sepdrv+0x8abc
fffff880`01c1bc60 fffff880`030fe8e6 : fffff880`00000000 00000000`00000007 fffff880`009f0180 00000000`00000000 : sepdrv+0x2546
fffff880`01c1bca0 fffff800`016da5dc : 00000004`3df5fab5 fffff880`0001c73a 00000000`00000001 00000000`17233d27 : sepdrv+0x18e6
fffff880`01c1bcd0 fffff800`016d76fa : fffff880`009f0180 fffff880`009fb0c0 00000000`00000000 fffff880`030fe8dc : nt!KeRemoveQueueEx+0xe1c
fffff880`01c1bd80 00000000`00000000 : fffff880`01c1c000 fffff880`01c16000 fffff880`01c1bd40 00000000`00000000 : nt!KeUpdateSystemTime+0x47a
STACK_COMMAND: kb
FOLLOWUP_IP:
sepdrv+1041
fffff880`030fe041 0f30 wrmsr
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: sepdrv+1041
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: sepdrv.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0 Kudos
1 Reply
54 Views

Hello,

The VTune Analyzer's sampling technology is not compatible with the Hyper-V virtualization system. This is because Hyper-V (like other virtualization systems) doesn't virtualize the hardware performance-monitoring registers which the VTune Analyzer uses to gather sampling data.

Best,
-Kevin
Reply