1 Reply Latest reply on Oct 20, 2009 11:05 AM by leiy

    Running xperf while CodeAnalyst is installed bluescreens

    azverkan@hotmail.com

      Running the command below while CodeAnalyst is installed will result in a BSOD on Vista 64.

       

      xperf -on Latency -stackwalk Profile

       

       

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


      Loading Dump File [C:\Windows\MEMORY.DMP]
      Kernel Summary Dump File: Only kernel address space is available

      Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
      Executable search path is:
      Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS
      Built by: 6001.18295.amd64fre.vistasp1_gdr.090721-0152
      Machine Name:
      Kernel base = 0xfffff800`02662000 PsLoadedModuleList = 0xfffff800`02827db0
      Debug session time: Mon Oct 19 22:26:26.272 2009 (GMT-7)
      System Uptime: 0 days 0:06:02.378
      Loading Kernel Symbols
      ...............................................................
      ................................................................
      ................................................................
      .
      Loading User Symbols

      Loading unloaded module list
      ............
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************

      Use !analyze -v to get detailed debugging information.

      BugCheck 1E, {ffffffffc0000096, fffffa6009c12838, 0, 0}

      *** ERROR: Symbol file could not be found.  Defaulted to export symbols for AMPCORE.sys -
      Probably caused by : AMPCORE.sys ( AMPCORE!AmdPcoreAddRecord+f38 )

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

      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: ffffffffc0000096, The exception code that was not handled
      Arg2: fffffa6009c12838, The address that the exception occurred at
      Arg3: 0000000000000000, Parameter 0 of the exception
      Arg4: 0000000000000000, Parameter 1 of the exception

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


      EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

      FAULTING_IP:
      AMPCORE!AmdPcoreAddRecord+f38
      fffffa60`09c12838 0f32            rdmsr

      EXCEPTION_PARAMETER1:  0000000000000000

      EXCEPTION_PARAMETER2:  0000000000000000

      DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

      BUGCHECK_STR:  0x1E

      PROCESS_NAME:  System

      CURRENT_IRQL:  0

      LAST_CONTROL_TRANSFER:  from fffff80002690e67 to fffff800026b6650

      STACK_TEXT: 
      fffffa60`0afcbff8 fffff800`02690e67 : 00000000`0000001e ffffffff`c0000096 fffffa60`09c12838 00000000`00000000 : nt!KeBugCheckEx
      fffffa60`0afcc000 fffff800`026b64a9 : fffffa60`0afcc738 fffffa60`005f6290 fffffa60`0afcc7e0 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x29317
      fffffa60`0afcc600 fffff800`026b508d : 00000000`00000000 fffff800`026205df fffffa80`04975640 00000000`00001000 : nt!KiExceptionDispatch+0xa9
      fffffa60`0afcc7e0 fffffa60`09c12838 : fffffa60`09c0e25b fffffa80`c0010000 fffffa80`04fe8c10 fffffa80`0d082650 : nt!KiGeneralProtectionFault+0xcd
      fffffa60`0afcc978 fffffa60`09c0e25b : fffffa80`c0010000 fffffa80`04fe8c10 fffffa80`0d082650 00000000`00000002 : AMPCORE!AmdPcoreAddRecord+0xf38
      fffffa60`0afcc980 fffffa60`09c11f6b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : AMPCORE!AmdPcoreClearAllEvents+0x16b
      fffffa60`0afcc9d0 fffffa60`09c13030 : fffffa60`0afccc08 fa60005f`00000020 00209b00`00000000 fffffa60`00fa422e : AMPCORE!AmdPcoreAddRecord+0x66b
      fffffa60`0afccb80 fffffa60`0afccc08 : fa60005f`00000020 00209b00`00000000 fffffa60`00fa422e 00000000`00000000 : AMPCORE!AmdPcoreAddRecord+0x1730
      fffffa60`0afccb88 fa60005f`00000020 : 00209b00`00000000 fffffa60`00fa422e 00000000`00000000 fffffa80`05f75190 : 0xfffffa60`0afccc08
      fffffa60`0afccb90 00209b00`00000000 : fffffa60`00fa422e 00000000`00000000 fffffa80`05f75190 fffffa60`0afccc08 : 0xfa60005f`00000020
      fffffa60`0afccb98 fffffa60`00fa422e : 00000000`00000000 fffffa80`05f75190 fffffa60`0afccc08 0000fa80`04467890 : 0x209b00`00000000
      fffffa60`0afccba0 00000000`00010000 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff800`0291fd50 : ecache!EcDispatchReadWrite+0x8a6
      fffffa60`0afcccd0 00000000`00000000 : 00000000`00000000 00000000`00000001 fffff800`0291fd50 fffffa80`0d082650 : 0x10000
      fffffa60`0afcccd8 00000000`00000000 : 00000000`00000001 fffff800`0291fd50 fffffa80`0d082650 00000000`00000000 : 0x0
      fffffa60`0afccce0 00000000`00000001 : fffff800`0291fd50 fffffa80`0d082650 00000000`00000000 00000000`00000000 : 0x0
      fffffa60`0afccce8 fffff800`0291fd50 : fffffa80`0d082650 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
      fffffa60`0afcccf0 fffff800`028dafd3 : 00000000`00000000 fffffa80`04fb1880 00000000`00000080 fffffa80`0d082650 : nt!EtwpLogger+0x1f8
      fffffa60`0afccd50 fffff800`026f0816 : fffffa60`005ec180 fffffa80`04fb1880 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
      fffffa60`0afccd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


      STACK_COMMAND:  kb

      FOLLOWUP_IP:
      AMPCORE!AmdPcoreAddRecord+f38
      fffffa60`09c12838 0f32            rdmsr

      SYMBOL_STACK_INDEX:  4

      SYMBOL_NAME:  AMPCORE!AmdPcoreAddRecord+f38

      FOLLOWUP_NAME:  MachineOwner

      MODULE_NAME: AMPCORE

      IMAGE_NAME:  AMPCORE.sys

      DEBUG_FLR_IMAGE_TIMESTAMP:  49f88bdc

      FAILURE_BUCKET_ID:  X64_0x1E_AMPCORE!AmdPcoreAddRecord+f38

      BUCKET_ID:  X64_0x1E_AMPCORE!AmdPcoreAddRecord+f38

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

        • Running xperf while CodeAnalyst is installed bluescreens
          leiy

          Thanks for reporting this issue.

           

          I think the issue is caused by both CodeAnalyst and xperf are using the performance counter at same time.

          Part of CodeAnalyst installation will start a service to initialize AMPcore driver. It will hook up interrupt table. Since xperf is running and generating interrupt, the interrupt is directed to AMPCore which is not configured with any type of profile.

          We will look at the issue in our next major release.