Display driver NVIDIA Windows Kernel Mode 260.89 stopped responding and has succesfully recovered. - General Hardware - Desktop - Dell Community

Display driver NVIDIA Windows Kernel Mode 260.89 stopped responding and has succesfully recovered.


Desktop computer Forums (Audio, General Hardware, Video)

Display driver NVIDIA Windows Kernel Mode 260.89 stopped responding and has succesfully recovered.

This question has suggested answer(s)

HI all. I would like to ask for help, maybe someone had the same problem and was able to fixed it. I have Dell XPS One A2420 desktop with Windows 7 installed. We have never used this computer with Vista, when we got it I have installed Windows 7 32-bit at once. Since the beginning we have got this message -" Display driver NVIDIA Windows Kernel Mode 260.89 stopped responding and has succesfully recovered". I do not play any games, just check emails, watch some videos and browse.First the screen goes black and it appeares again and this message about display driver occures.Yesterday screen went black, then mouse did not respond, the computer shutted down itself. When it started there was a black screen with some white and green tiles in the bottom half of the screen. Then everything worked normally. I have tried to install few different drivers from Nvidia website, but the problem is still there, I have just updated BIOS, but no luck. The same problem occures. I asked for help from NVIDIA, but never got response. I will be looking for more solutions from other websites, but I would really appreciate some suggestions from dell users.

Thank you calgal

All Replies
  • 260.89 is not the off the DVD driver.

    Install the Directx June 2010 patch.

    DirectX Redist (June 2010) - Microsoft Corporation


    Extract into Directory call it DX90C

    Run Dxsetup.exe

    System Requirements

    • Supported Operating Systems:Windows 7;Windows Server 2003;Windows Server 2008;Windows Vista;Windows XP Service Pack 3
    Directx should be installed BEFORE the latest driver.

    Report Unresolved Customer Service Issues here
    I do not work for Dell. I too am a user.
    The forum is primarily user to user, with Dell employees moderating
    Contact USA Technical Support

    Get Support on Twitter @DellCaresPro

  • Hi Speed Step. Thank you for your response. I have already done what you suggested, but I just notice that you wrote that Directx should be installe BEFORE the latest driver. Does it mean I need uninstall directx, the the driver and do it all again in the correct order? Otherwise it won`t work , is that right? Excuse me the question, but I want to make sure that I did understand it your directions.

    Have a nice day. Calgal


    This error can mean that Your GPU or CPU overheated. Sometimes there will be BSOD problem.

    It's a Microsoft "feature" called Timeout Detection and Recovery   or TDR. It's a WDDM function that

    resets the driver if it thinks the framerate has slowed down so much that it's crashing.

    A  registry setting might solve the problem:



    Timeout Detection and Recovery

    Windows attempts to detect these problematic hang situations and recover a responsive desktop dynamically. In this process, the Windows Display Driver Model (WDDM) driver is reinitialized and the GPU is reset. No reboot is necessary, which greatly enhances the user experience. The only visible artifact from the hang detection to the recovery is a screen flicker, which results from resetting some portions of the graphics stack, causing a screen redraw. Some older Microsoft DirectX applications may render to a black screen at the end of this recovery. The end user would have to restart these applications. (Game)

    The following is a brief overview of the TDR process:

    1.Timeout detection: The Video Scheduler component of the Windows Vista graphics stack detects that the GPU is taking more than the permitted quantum time to execute the particular task and tries to preempt this particular task. The preempt operation has a "wait" timeout—the actual "TDR timeout." This step is thus the "timeout detection" phase of the process. The default timeout period in Windows Vista is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout, then the GPU is diagnosed as hung.

    2.Preparation for recovery: The operating system informs the WDDM driver that a timeout has been detected and it must reset the GPU. The driver is told to stop accessing memory and should not access hardware after this time. The operating system and the WDDM driver collect hardware and other state information that could be useful for post-mortem diagnosis.

    3.Desktop recovery: The operating system resets the appropriate state of the graphics stack. The Video Memory Manager component of the graphics stack purges all allocations from video memory. The WDDM driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As mentioned earlier, some older DirectX applications may now render just black, and the user may be required to restart these applications. Well-written DirectX 9Ex and DirectX 10 applications that handle "Device Remove" continue to work correctly. The application must release and then recreate its Microsoft Direct3D device and all of its objects. DirectX application programmers can find more information in the Windows SDK.

    Registry Keys

    The following registry keys are documented for testing purposes only. These registry keys should not be manipulated by any applications outside targeted testing or debugging.

    The TDR-related registry keys are located under HKLM\System\CurrentControlSet\Control\GraphicsDrivers.
    • TdrLevel: REG_DWORD. The initial level of recovery. The possible values are:
    •    TdrLevelOff (0). – Detection disabled.
    •    TdrLevelBugcheck (1) – Bug check on detected timeout, for example, no recovery.
    •    TdrLevelRecoverVGA (2) – Recover to VGA (not implemented).
    •    TdrLevelRecover(3) – Recover on timeout. This is the default value.
    •    TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold. The default value is 2.
    •    TdrDdiDelay: REG_DWORD. The number of seconds that the operating system allows threads to leave the driver. After a specified time, the operating system bug checks the system with the code VIDEO_TDR_FAILURE (0x116). The default value is 5.
    •    TdrTestMode: REG_DWORD: Internal test usage.
    •    TdrDebugMode: REG_DWORD: The debugging-related behavior of the TDR process.
    •    TDR_DEBUG_MODE_OFF (0) breaks to kernel debugger before the recovery to allow investigation of the timeout.
    •    TDR_DEBUG_MODE_IGNORE_TIMEOUT (1) ignores any timeout.
    •    TDR_DEBUG_MODE_RECOVER_NO_PROMPT (2) recovers without break into the debugger. This is the default value.
    •    TDR_DEBUG_MODE_RECOVER_UNCONDITIONAL (3) recovers even if some recovery conditions are not met (for example, recovers on consecutive timeouts).
    •    TdrLimitTime: REG_DWORD (Windows Vista SP1 and later versions only): The default time within which a "TdrLimitCount" number of TDRs are allowed without crashing the system.
    •    TdrLimitCount: REG_DWORD (Windows Vista SP1 and later versions only): The default number of TDRs (0x117) that are allowed in "TdrLimitTime" without crashing the system.

    Directx Is like Windows Media player.  It can be installed and updated but not removed.

    The Directx Drivers are Cumulative and they patch it  hundreds of times year after Year.

    Many people commonly say I dont need XXXX because I have XP/VISTA/7  but in fact they do need

    the Patches because they come out sometimes more than 1 time per month.

    Thats why there is a June 2010 release.

    If you look in the folder that you run DXSETUP from the Drivers have many years of patches.

    The 290 driver from nvida is a WHQL release.

    You should uninstall any Nvidia drivers.

    Install directx and reboot.

    Then install the WHQL drivers from NVIDIA.

    The current drivers are 10/25/2010

    New in Release 260.99

    • Increases performance vs. v260.89 drivers in the following PC games: Civilization V (SLI), Fallout 3, Final Fantasy XIV, and Formula 1 Racing (DX11).
    • Adds SLI profiles for the following PC games:
      • Need for Speed: Hot Pursuit
      • Star Wars: The Force Unleashed II
      • Fallout: New Vegas
    • Improves compatibility for Fallout: New Vegas with antialiasing enabled.
    • Improves Alt-Tab compatibility for several PC games.
    • Added the following 3D Vision game profiles: Call of Duty: Black Ops and Tom Clancy's HawX 2.
    • With Release 260 drivers, the installation process for 3D Vision has changed. Please view this knowledgebase article for more information on the changes.

    Additional Information

    • Installs HD Audio driver to version
    • Includes PhysX System Software to version 9.10.0514.
    • Supports the new GPU-accelerated features in Adobe CS5.
    • Supports GPU-acceleration for smoother online HD videos with Adobe Flash 10.1. Learn more here.
    • Supports the new version of MotionDSP's video enhancement software, vReveal, which adds support for HD output. NVIDIA customers can download a free version of vReveal that supports up to SD output here.
    • Supports DirectCompute with Windows 7 and GeForce 8-series and later GPUs.
    • Supports OpenCL 1.0 (Open Computing Language) for all GeForce 8-series and later GPUs.
    • Supports OpenGL 3.3 for GeForce 8-series and later GPUs.
    • Supports OpenGL 4.1 for GeForce 400 series GPUs.
    • Supports single GPU and NVIDIA SLI technology on DirectX 9, DirectX 10, DirectX 11, and OpenGL, including 3-way SLI, Quad SLI, and SLI support on SLI-certified Intel X58-based motherboards.
    • Supports GPU overclocking and temperature monitoring by installing NVIDIA System Tools software.
    • Users without US English operating systems can select their language and download the International driver here.




    260.99 WHQL

    Release Date:


    Operating System:

    Windows 7, Windows Vista


    English (U.S.)

    File Size:

    96.3 MB

    Report Unresolved Customer Service Issues here
    I do not work for Dell. I too am a user.
    The forum is primarily user to user, with Dell employees moderating
    Contact USA Technical Support

    Get Support on Twitter @DellCaresPro

  • As the prior person mentioned, you could have a problem with your GPU. I just replaced my 8800GTX due to getting BSOD with a message indicating the tthe driver reset did not work.


    Since installing a new GTX 470 I no longer have any problems with BSOD due to video driver related items. If your system is new, you should be good to go with warranty support replacing your GPU. You'll just have to go through some troubleshooting steps with Dell support.



  • Hi again.  Thank you for all the suggestion and clear and professional explanation what is happening to my computer. I am not very tech savvy, but I was able to understand it.

     I did as you suggested- I unistalled NVIDIA driver, installed Directx according to your directions and from the link you have provided, then again I installed NVIDIA driver 260.99. Unfortunately after a while the same problem occured, display driver has stopped and recovered.  Is there something else what I need to check or do, or just call Dell support and do the repair  upon my warranty.

    Thanks calgal

  • Hi Eric. Thank you for your response and suggestion. The computer is still under warranty, so I guess I can request GPU  replecement, but shipping this computer will be painfull. It is big and heavy. Also I have a one more question. Originaly there was Windows Vista on this computer,but  I installed Win 7.Do you think they can void my warranty?

    Keep well. Calgal