none
Hyper-V install = Blue Screen - VIDEO_TDR_FAILURE

    Question

  • Ok, I'm starting a new thread on this.

    Background
    First, know that I've already read all the posts related to this issue. Some refer to beta versions, are out of date or are set as answered for the wrong reason. I'm also aware of the post on performance problems for high-end videocards: http://blogs.msdn.com/virtual_pc_guy/archive/2009/01/07/bad-performance-with-high-end-graphics-and-hyper-v.aspx but my problem is a blue screen problem, not a performance problem. And since my processors are i7, I shouldn't have any performance issues if I get my video card to work - which is the real issue this post is about.

    Hardware
    Dell Studio 1747 laptop, i7 processors, ATI Mobility Radeon HD 4650, 8G RAM
    My searches here and on the web seems to indicate that the problem occurs mostly with laptop computers.
    This is wide-spread: I have seen posts involving either Dell or HP laptops and ATI or NVIDIA video cards.

    How to reproduce the blue screen
    Occurs when rebooting after installing the Hyper-V server role in Windows Server 2008 R2, if a high-end videocard driver is used instead than the default VGA driver.

    Why use a high-end video card driver with Hyper-V & laptop
    - To be able to use an external monitor/projector for demos and presentations.
    - To use dual monitors and high resolution while doing software development in an Hyper-V self-contained networked test environment.

    What I know
    (I use my ATI card as an example, but other posts mention the same problem with other videocards.)
    - Running high-res games on Windows 7 with the ATI driver works on the same computer.
    - Running Windows Server 2008 R2 (Standard or Enterprise) in high-res/dual monitors with the ATI driver works.
    - Running Hyper-V with the basic Windows VGA driver works.
    - Booting after the Hyper-V role install causes a blue screen after the progress bar, before the logon screen, when the ATI driver is also installed.
    - Booting in safe mode is ok (ATI driver disabled).
    - Booting without BIOS virtualization option is ok (Hyper-V disabled).
    - Turning off the display driver recovery timeout causes hang (infinite timeout) instead than the blue screen (HKLM\System\CurrentControlSet\Control\GraphicsDrivers - TdrLevel DWORD value of 0).
    - Using basic VGA with the ATI driver (custom boot - BCDEDIT /SET VGA ON) still causes the blue screen.
    - Tried other BIOS/MSCONFIG/ATI options without finding anything usefull.
    - Tried twice from clean OS installs, with and without networking, with and without windows updates, with and without latest drivers (chipsets/videocard) from Dell.
    - The error in the MEMORY.DMP file is VIDEO_TDR_FAILURE (116)

    MEMORY.DMP
    Here's the most important parts of MEMORY.DMP (don't know how/if I can attach the whole file to the forum) - let me know if you need anything else, I'll be glad to help fix this issue, which is driving me crazy - really did spent a lot of time on this one.

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0180a000 PsLoadedModuleList = 0xfffff800`01a47e50
    Debug session time: Sat Jan 23 12:49:33.168 2010 (GMT-5)

    *******************************************************************************
    *                                                                            
    *                        Bugcheck Analysis                                   
    *                                                                            
    *******************************************************************************
    BugCheck 116, {fffffa80014e0010, fffff88002ca71b4, 0, 2}


    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80014e0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88002ca71b4, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.FAULTING_MODULE: fffff8000180a000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a84cf1b

    FAULTING_IP:
    atikmdag+131b4
    fffff880`02ca71b4 48895c2408      mov     qword ptr [rsp+8],rbx

    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

    BUGCHECK_STR:  0x116

    CURRENT_IRQL:  0

    STACK_TEXT: 
    fffff880`040cf9c8 fffff880`03330cbc : 00000000`00000116 fffffa80`014e0010 fffff880`02ca71b4 00000000`00000000 : nt!KeBugCheckEx
    fffff880`040cf9d0 fffff880`033309c6 : fffff880`02ca71b4 fffffa80`014e0010 fffffa80`013d6690 fffffa80`013cf010 : dxgkrnl!TdrResetFromTimeout+0x214
    fffff880`040cfa10 fffff880`02c0ff07 : fffffa80`014e0010 00000000`00000000 fffffa80`013d6690 fffffa80`013cf010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`040cfa40 fffff880`02c39b75 : 00000000`ffffffff 00000000`00000535 00000000`00000000 00000000`00000002 : dxgmms1+0xff07
    fffff880`040cfb20 fffff880`02c382bb : 00000000`00000102 00000000`00000000 00000000`00000535 00000000`00000000 : dxgmms1!VidMmInterface+0x282a5
    fffff880`040cfb50 fffff880`02c0b2c6 : ffffffff`ff676980 fffffa80`013cf010 00000000`00000000 00000000`00000000 : dxgmms1!VidMmInterface+0x269eb
    fffff880`040cfbf0 fffff880`02c37e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0116b6e8 : dxgmms1+0xb2c6
    fffff880`040cfd00 fffff800`01b1f166 : 00000000`00000000 fffffa80`013e4060 fffffa80`003fa9e0 00000000`00000000 : dxgmms1!VidMmInterface+0x265aa
    fffff880`040cfd40 fffff800`0185a486 : fffff880`009b8180 fffffa80`013e4060 fffff880`009c2fc0 00000000`00000000 : nt!PsCreateSystemThread+0x6e2
    fffff880`040cfd80 00000000`00000000 : fffff880`040d0000 fffff880`040ca000 fffff880`040cf310 00000000`00000000 : nt!KeTestAlertThread+0x956


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP:
    atikmdag+131b4
    fffff880`02ca71b4 48895c2408      mov     qword ptr [rsp+8],rbx

    SYMBOL_NAME:  atikmdag+131b4

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: atikmdag

    IMAGE_NAME:  atikmdag.sys

    BUCKET_ID:  WRONG_SYMBOLS


    Martin Lapierre - .NET Consultant
    Wednesday, January 27, 2010 1:57 PM

Answers

All replies

  • Hi Dev,

     

    As you mentioned that you have read all the posts related this issue. So I want to let you know that the we don't recommend that you install the video card acceleration driver on Hyper-V host.

     

    The following post discussed the similar issue, you can refer to:

     

    Conflict between Hyper-V and Intel HD Graphics driver

    http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/155df520-016f-4866-8bb4-1fd526cd6542

     

     

    Best Regards,

    Vincent Hu

     

    • Marked as answer by DevInstinct Thursday, January 28, 2010 2:22 PM
    Wednesday, January 27, 2010 4:34 PM
    Moderator
  • Ok, thank you. I should have said that I've read all the posts with the keyword "blue screen" :)

    I've filled in a bug report at
    https://connect.microsoft.com/WindowsServerFeedback/feedback/ViewFeedback.aspx?FeedbackID=527817

    Couldn't find the way to attach the MEMORY.DMP file however ("attach file" doesn't allow it for me).

    Really hope someone will look more closely at this issue. This is an Hyper-V show stopper for what I'd need to do with it as a consultant (demos, projections, etc.) - at least using my new i7 laptop.


    Martin Lapierre - .NET Consultant
    Thursday, January 28, 2010 2:20 PM
  • Did you get any response or a HOTFIX for this issue, I can't believe that people in MS don't use and or require to have this working for Demonstrations, if they supported Windows 7 64bit with 64Bit Guests then I would use this for demo's but now I have server environments for Development that require 64Bit OS and I don't really want to have to have VMWare but looks like my online choice. Come on Microsoft please let us know how you are going to Proceed.

    My scenario isn't Laptop it is Desktop based with Twin Radeon HD4550 and I7 Core processor and BSOD on boot with Hyper-V Role being installed, works fine in VGA mode but can't support multi screen and correct resolutions which is just not good enough :(

    Fingers crossed has been hotfixed.


    Mike Walker MVP - Visual Developer VSTO - Please mark the best replies as Answers !
    Monday, April 12, 2010 4:31 PM
  • My laptop is HP ProBook 6440B. I have the same issue too.

    I really need to use my laptop with Hyper-V for demostration purpose. If I use standard VGA driver with Hyper-V, everything is fine, but I can not send my screen to projector. For this reason, I install video driver (ATI Mobility Radeon HD 4550), but got BSOD after reboot everytime.

    The video driver works just fine in Windows 7 64 bits edition.

     


    Jimy Cao

    MCP, MCP+I, MCSA, MCSE, MCDBA, MCAD, MCSD, MCTS, MCITP, MCPD, MCT, MVP

    Tuesday, April 13, 2010 12:24 AM
  • No fix yet. Please vote for it at Microsoft Connect.

    https://connect.microsoft.com/WindowsServerFeedback/feedback/details/527817/hyper-v-install-blue-screen-video-tdr-failure


    Martin Lapierre - .NET Consultant
    • Marked as answer by DevInstinct Tuesday, April 13, 2010 3:21 PM
    Tuesday, April 13, 2010 3:21 PM
  • Have done already but you never know if they have done something about it or not.

     


    Mike Walker MVP - Visual Developer VSTO - Please mark the best replies as Answers !
    Tuesday, April 13, 2010 5:33 PM
  • Any heard of a fix on this yet? I just bought a new high powered desktop from dell with 32 Gigs of RAM, Dual displays pushed by an ATI RADEON HD 3450 card. Im stuck in a loop now a Windoes 7 Pro and the WVPC will not support 64 bit. Thought I could install the 2008R2 with Hyper-V on a second layer.

    I have to convert 16 servers from ESX 3.X to the Hyper-V platform and I need this PC acting as a server to test the conversions. Now what am I suppose to do Microsoft?

    If I have to install ESXi to install Hyper-V... I swear I'll consider scratching this entire project. NO IT department will blindly convert without testing!!! if developers and IT professionals cant do thier work then the adoption rate will suffer big time!!!

    Friday, June 04, 2010 9:42 PM
  • Try Windows Server 2008 R2 SP1 Beta.
    • Proposed as answer by Yuhong Bao Tuesday, July 27, 2010 3:19 AM
    • Marked as answer by DevInstinct Tuesday, July 27, 2010 6:59 AM
    Tuesday, July 27, 2010 3:19 AM
  •    Yes, that should work. The Beta needs the manufacturer's video driver for RemoteFX.

     


    Bill
    Tuesday, July 27, 2010 5:40 AM
  • Yes SP1 Beta fixed the Problem for me too.

    Background: I have a MacBook Pro 15" with an Core i7 and the nVidia GT330. I wrote an Post about this under http://www.hyper-v-server.de/hypervisior/hyper-v-auf-apple-imac-und-macbook-pro-mit-core-i7/ (sorry it is in german). When I installed SP1 Beta the problem was fixed. I hope the problem will not reapear when SP1 RTM is out.

    Carsten

    Wednesday, July 28, 2010 8:45 PM
  • Mike,

    Oracle (previously Sun) VirtualBox supports 64-bit guest machines provided the host is running an x64 OS. Works great for me, the only gripe I have is that the guest OS window has to be open all the time when it's running.

    Chris.

     

    Friday, October 01, 2010 7:52 AM
  • Download and install the 64bit version of the Windows 8 Consumer preview.   It has a full implementation of Hyper-v (not Windows Virtual PC) and it supports all the latest graphic drivers.   It's also the same version of Hyper-V that's being prepared for Windows Server 8,  so it has more features than the Windows 2008 R2 version of Hyper-V. 

    Thursday, March 29, 2012 5:15 PM