Blue screen on launching anything from Performance Explorer RRS feed

  • Question

  • Hi!

    Whenever I try to launch any application from the Performance Explorer (even if I try "launch without profiling", or try to attach to an already running process), I get blue screen with the message " IRQL_GT_ZERO_AT_SYSTEM_SERVICE ", and my computer restarts.

    VS2008 SP1 (Team System Team Suite), Vista x64 Ultimate, .NET Framework 3.5 SP1

    Things I've tried so far:

    Repaired Visual Studio from control panel - same issue
    Reset all settings - same issue
    Completely uninstalled then reinstalled VS from control panel - same issue
    Uninstalled all add-ons, even uninstalled the whole VMWARE workstation (couldn't remove the VS related stuffs seperately)- same issue
    Uninstalled VGA drivers (very rarely, while debugging a Silverlight-WPF mixed solution, my monitors start flashing a few times then blue screen appears telling me there was a problem with the display driver so Windows shut down the computer to prevent damage to the hardware, so for this reason I hoped maybe it has something to do with the profiler issue as well) - same issue
    Disabled all non-microsoft services - same issue
    Disabled all services that my tablet doesn't run (my tablet runs performance profiler seamlessly- same OS, same VS) - same issue
    Run MemTest - it showed no errors in memory
    Tried ANTS Performance Profiler to see if other profilers generate this issue - it works perfectly (I still would like to use the VS performance profiler)

    Any idea what I could still try to do to be able to run Performance Analysis on my projects?
    It doesn't work for any kind of project I've tried so far (I usually test it on a fresh new Console Application)

    Thank you very much
    • Edited by Herthoren Saturday, January 17, 2009 3:20 AM
    Friday, January 16, 2009 8:10 AM


All replies

  • Hi,

    Can you let me know which processor you are using?


    Daryush Laqab - MSFT ---------------------- To help our tracking, please mark replies as answers if they resolve your issue.
    Friday, January 16, 2009 5:13 PM
  • Intel Core I7 965 @ 3.2ghz (not overclocked)
    Saturday, January 17, 2009 12:43 AM
  • That is a known issue. We are working on a patch to address the issue. I will post an update once the patch is out.


    You can also track a similar thread on this issue, which can be found at http://social.msdn.microsoft.com/Forums/en-US/vstsprofiler/thread/93326568-2635-432c-86d5-848ff2536dc0.


    Daryush Laqab - MSFT ---------------------- To help our tracking, please mark replies as answers if they resolve your issue.
    • Marked as answer by Herthoren Monday, January 19, 2009 9:08 PM
    • Unmarked as answer by Herthoren Saturday, May 9, 2009 10:16 AM
    • Marked as answer by Herthoren Thursday, May 21, 2009 6:46 PM
    Monday, January 19, 2009 7:03 PM
  •  The Patch is ready regarding the blue screens on the Nehalem Intel Processors while profiling as described in this thread. Currently you need to contact microsoft to get the fix at (800) 936-5800 option 3 and request one of the KB numbers listed below. Note hopefully soon we will put the fix on the Microsoft Connect site, https://connect.microsoft.com/default.aspx. As soon as we get it up on the msconnect site I will post again to this site. 


    958840  FIX: A stop error or a crash occurs on the operating system when you profile an application by using Microsoft Visual Studio 2005 SP1




    958842  -Visual Studio 2008 (SP1) Team System Profiler causes Blue screen on Nehalem Intel Processor
    (Note the KB for this fix is not public as of this post, but it can still be requested from Microsoft)

    Johnny Coleman [MSFT] Any code posted to this Forum is [As-Is] With No Warranties
    Monday, February 9, 2009 4:36 PM
  • Please post a downloadable hotfix!

    I have exact same problem on Intel i7 940, Visual Studio 2008 SP1, Vista 64 Ultimate SP1.

    Best regards,
    Bjørn Sigurd Johansen
    Wednesday, February 11, 2009 7:01 PM

    The Profiler hotfixes for the Nehalem processor have been made publically available on Microsoft Code Gallery:

    KB958840 - VS 2005 (SP1) TSP causes Blue screen on Nehalem Intel Processor
    Download  http://code.msdn.microsoft.com/KB958840      
    KB Article http://support.microsoft.com/default.aspx?scid=kb;EN-US;958840


    KB958842 - VS 2008 (SP1) TSP causes Blue screen on Nehalem Intel Processor
    Download   http://code.msdn.microsoft.com/KB958842      
    KB Article http://support.microsoft.com/default.aspx?scid=kb;EN-US;958842
    (note kb article is not public at time of this post but should be available within the week)


    KB959418 - profiling process may crash when using the instrumentation method
    Download   http://code.msdn.microsoft.com/KB959418  
    KB   http://support.microsoft.com/default.aspx?scid=kb;EN-US;959418

    Johnny Coleman [MSFT] Any code posted to this Forum is [As-Is] With No Warranties
    • Marked as answer by Herthoren Thursday, May 21, 2009 6:46 PM
    Monday, February 16, 2009 11:10 PM
  • Well, I did not need to use the performance profiler again until now.

    Downloaded the hotfix from
    It's not installing.
    When I launch the installer I get the message

    None of the products that are addressed by this software update are installed on this computer. Click Cancel to exit setup.

    And can only click cancel.

    Uninstalled Visual Studio 2008 then reinstalled along with freshly downloaded SP1, same message.

    My VS2008TS version is 9.0.30729.146
    The system, just as described above Core I7 965, Vista x64 Ultimate, .NET Framework 3.5 SP1

    Still getting BSOD on performance profiling.
    Saturday, May 9, 2009 10:16 AM
  • I am having the same problem as Herthoren with just a few minor differences in my setup.

    1) OS is Windows Server 2008 x64.
    2) Processor is AMD64 X2.
    3) VS2008 Team System Developer Edition SP1

    I did find this on the Connect site: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=418025&wa=wsignin1.0

    It mentions that there is a known issue with the profiler and Hyper-V running, which I have running on my system as well.  The report just ends with "it's fixed in 2010, and we'll let you know when a fix gets released for 2008."  Is there any updates on a patch to resolve this?

    Saturday, May 16, 2009 1:48 AM
  • Hi Joe,

    The hotfix Herthoren is referring to is specifically for Intel I7 processor. We are trying to figure out why it does not insall for Herthoren. As your processor is AMD64 X2, that hotfix does not apply.

    We are working on an AMD64 specific hotfix to prevent BSOD on Win2K8/x64/Hyper-V systems. The fix, however, will only prevent BSOD. VSTS 2010 has the support for Sample profiling on Hyper-V enabled machines.



    To help our tracking, please mark replies as answers if they resolve your issue.
    • Marked as answer by Herthoren Thursday, May 21, 2009 6:44 PM
    Thursday, May 21, 2009 5:26 PM
  • Formatting the hard drive and reinstalling Vista solved the problem.
    Not sure, but the issue may have been due to Silverlight2 or VMWare Workstation.

    AFAIK those are the only two things that mess with VS and I had them installed prior to the format and not having them now.

    Profiler seems to work fine.
    Thursday, May 21, 2009 6:43 PM
  • I have a Visual Studio Team System 2008 Team Suite edition and this hotfix (KB958842) won't install because it says I don't have any of the components that it fixes. 
    I am getting blue screened when using the profiler with both sampling and instrumentation, so i need the hotfix...
    Wednesday, March 31, 2010 6:16 AM
  • Hi Jordan,

    Please double check that you have VS2008 SP1 installed first.  If you don't, you can download the SP1 update from here.  With SP1 installed, the hotfix should install as well.


    Monday, April 5, 2010 7:30 PM
  • On Windows 7 x64, VS 2008+SP1, I cannot install the patch for the same reason as the next-most-recent poster (nothing to patch). This really is bad -- the bug's been there for well over a year, and the patch didn't fix it.
    Thursday, April 14, 2011 4:58 PM