The nvlddmkm error - What is it? An FYI for those seeing this issue

Sora said: try a higher quality cable, or different port on the card.

I have only one display port on my graphic card. My cable is not the culprit. It's the cable given by ACEr for my display (acer xb270hu). if the cable was the culprit, i would have the problem since the buy of my display.

jackbluray said: It's the cable given by ACEr for my display (acer xb270hu)

Try a different cable.

Sora said:

jackbluray said: It's the cable given by ACEr for my display (acer xb270hu)

Try a different cable.

I don't have another cable and I said that the cable is not the culprit.

Buy another cable. What you say and what is reality don't coincide.

Hello guys, On my computer event id 4101, was caused by AIDA64, after 1803 win 10 update. It has since then, been fixed by aida, but users that have not updated their aida64, may still expirience it. Here is the link of the thread: https://forums.aida64.com/topic/4222-aida64-is-freezing-pc-win10-1803-timer-collision/ https://forums.aida64.com/topic/4211-windows-10-spring-creators-update-1803-causing-system-crash-gigabyte-z170x-ud5-th-i7-6700k-gtx1080ti-win10-b17134-win10-1803-timer-collision/ I completely removed AIDA64, and the problem has disappeared. Hope this helps.

I can concur with many, the nvlddmkm error is present on bot my rigs. new cables where install, different monitors where use, both system have different os version, one 1803 and the other one is 1809 (testing) and both use almost similar specs. the erroe is there and is full on the event viewer. both have 1080ti. I do not have aida. I test both with new drivers, the last 399.xx version (is not present all the time maybe 1 every 30 days) on my main rig almost everytime i boot. beside monitors drop to 60hz if i stop expanding the monitors. 1 have the last realtek drivers, the main rig have the LAST drivers. So is not a audio driver. I test with experience install, and with out it. I did test cables, i test the one that comes with monitors, test other cables as well, grab a DP cable that arrive yesterday, and today i boot, is there. I use 3 brands of monitors, NON are gsync, on the control panel i restore settings. NADA. still appears So is windows side or nvidia side. I test psu on both, electrical, drives, ssd. and still the new drivers are the problem. I will make the last DDU as soon i finish these and check back. ---------- The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe206 00000007 00000000 The message resource is present but the message was not found in the message table

Update. Even with DDU, and all new drivers my event viewer is floated with same errors. over and over. and over. What is going on. I am going to format the computer again. and drop to 1803 and 399.xx since is not usable. It is insane. i have drop of fps, i can not oc, is glitch after glitch eve single time. Is not the cable, is not the monitors. since i test 4 more monitors. i did drop to the last 399 driver and all these problems where gone.

Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe208 00000007 00000000 The message resource is present but the message was not found in the message table ------------------- The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000001 000000c0 ff1fe203 00000007 00000000 The message resource is present but the message was not found in the message table

MrAgapiGC said: Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe208 00000007 00000000 The message resource is present but the message was not found in the message table ------------------- The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000001 000000c0 ff1fe203 00000007 00000000 The message resource is present but the message was not found in the message table

thats a uefi support issue in the present driver can work around it with the csm module support.

Sora said:

MrAgapiGC said: Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe208 00000007 00000000 The message resource is present but the message was not found in the message table ------------------- The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000001 000000c0 ff1fe203 00000007 00000000 The message resource is present but the message was not found in the message table

thats a uefi support issue in the present driver can work around it with the csm module support.

I have the exact same issue which shows up in event viewer with event ID 14 everytime I start the pc or restart the pc to boot in windows. @Sora, do you know if this problem is fixed in the Hotfix driver 416.64 or if nvidia developers are already working on fixing it ? I have the RTX 2080 ti, so I have not that much drivers I can install so far. The CSM module support can be enabled in the BIOS, right ?

Sora said:

MrAgapiGC said: Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice

thats a uefi support issue in the present driver can work around it with the csm module support.

I reflash the bios, reinstall all. drivers all the 9th yard. I test UEFI/legacy and with last 2 drivers is present. i test again with normal ssd. csm off, csm on with efi and legacy, uefi only and desible. the problem is there. AS far i test with 4 system. 1080ti, 2080, 2080ti, zotax asus) CSM is not the issue, being csm on or off, the driver have issues. I test z270/z370 with 1080ti asus stix stock and oc, 2080/2080ti stock and wht board oc and stock with csm off and on with uefi/legacy and uefi only and not. and the driver crash. As far these has come from last 3 drivers. I test even leaving the monitors turn off and as soon it turn on boom the issue appears. aside some games also crash. CSM module is not the issue at least in intel platform. I have not tested in amd. even that i have a amd system beside me. i can try since gigabyte board are more simple. I my case I HAVE to use CSM off cause the samsung driver 3.0. I can try using another one that use intel stock drivers from windows 10 but that is for another day. sorry for my long lines. as far my testing goes, the best drivers for 1080ti and below IS the last 399.xx drivers. (even that there is NO performace loss. at least on my side. i do have a frient that he test these on a high end 1080ti gpu and with numbers prove current diference on drivers. new drivers are for 2000 series cars. there is no question about it. i drop to 399.07 and the errors are completely GONE! i test all these with new ime/chipset drivers from intel, also the last ime /chipset drivers from my board 10.1.1.45 chipset and 11.7.0.1045 mei, and the error still there. the rest is 2 weeks testing. a fix is needed. and untill further notice, i am using the last 399 drivers for 1080ti and i did recomend to all to do the same. since is present on all scenarios with csm on or off, on 2080/2080ti, is present also, BUT! in csm on. with csm off using samsung drivers 3.0 for the nvme is not present. with csm in with uefi/legacy is present. With sata is not present or raid using intel RST

Sora said:

MrAgapiGC said: Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe208 00000007 00000000 The message resource is present but the message was not found in the message table ------------------- The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000001 000000c0 ff1fe203 00000007 00000000 The message resource is present but the message was not found in the message table

thats a uefi support issue in the present driver can work around it with the csm module support.

CSM is enabled for me, still I get the occasional hangs. Also the same with the users of Overclock.net.

My CSM is disable for me since it use my own driver for the nvme and not the windows one. For me is a dark territory I read since i start using nvme, that if i use csm disable, so i can use Samsung drivers. I will start reading these. BUT so far errors are flooded again with csm in and off.

Atomfix said:

Sora said:

MrAgapiGC said: Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe208 00000007 00000000 The message resource is present but the message was not found in the message table ------------------- The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000001 000000c0 ff1fe203 00000007 00000000 The message resource is present but the message was not found in the message table

thats a uefi support issue in the present driver can work around it with the csm module support.

CSM is enabled for me, still I get the occasional hangs. Also the same with the users of Overclock.net.

PLease send me link for Overclock.net. so I can read it. is a lot of data in 2 days now. at least 120hz have the issue I will performe a DDU now. but 2 days on clean install??? odd very odd. but I read the paperwork for the driver and maybe, is not prepared for windows 1809

Found a way to replicate the nvidia display driver crash on windows 7 while using 399.24. Launch heaven benchmark then launch furmark with postfx and finally launch aida64 gpu test, all the apps have to run at the same time. Takes about a minute to kill the driver and make it reset. EDIT: Scratch that, launched heaven first then aida64 and in less than 30s driver crash. EDIT: Tested with another GPU, it was fine, its just my gpu is dying. Case Closed.

don't do stupid things and the driver won't crash. Windows 7 is not capable of fine gpu pre-emption where as 8 and later are.

Having the same issue with my RTX 2080 Ti when running BF1. I've tried searching around, but can't find any resolution. It looks like I might just have to wait and hope that the next driver update fixes it? My specs: Latest 417.35 Nvidia driver RTX 2080 Ti Founders Edition i9-9900K 3440x1440 @ 100 Hz - X34 Predator Monitor 16 GB DDR4-3600 1200W PSU Event viewer error log:

 The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
 
If the event originated on another computer, the display information had to be saved with the event.
 
The following information was included with the event: 
 
\Device\Video3
1f65(306c) 84001d9b f65d20a0
 
The message resource is present but the message was not found in the message table 

I'm having 3dmark issues on this new driver 419.17 with a z390 master a i99900k 32gb and a evga xc 2080ti. My frames in time spy are 12fps when before went to 80 and 100fps. I rolled back to drive I have before and problem I'd gone. I used ddu as well.

we don't pay attention to this thread anymore, TDR errors are system by system handled generally.

I was having many of these on my new build, turns out it was the gpu. 2070 gigabyte windforce, pretty much Dead on Arrival, I was troubleshooting for awhile and finally sent it in, after few days of testing I was told I was correct and got a new gpu sent in (should be here by friday).

If that is the case for yout 2070 then my 6 gpus needs to be RMA. since on all machines that i have and has come, have these nvlddmkm error. 8 to 10 per day event viewer pop up with these

Sora said:

MrAgapiGC said: Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe208 00000007 00000000 The message resource is present but the message was not found in the message table ------------------- The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000001 000000c0 ff1fe203 00000007 00000000 The message resource is present but the message was not found in the message table

thats a uefi support issue in the present driver can work around it with the csm module support.

PLease tell me how. CSM support. Mean that on bios need to activate it? also i try and the boot screen change to a weird display?

I've recently been encountering this with my Razer Blade 15 (2019) RTX2070MQ. Seems to have been only occurring when on battery (although last night, when I plugged in my charger it did BSOD instantly - not sure if it was same BSOD issue or something different, because the BSOD screen disappeared too quickly for me to read what the error was). minidumps:

 BugCheck 116, {ffff8902e93a2010, fffff8059c042140, ffffffffc000009a, 4}
 
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvrzi.inf_amd64_0a22d906d95c4221\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ba2140 )
 
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvrzi.inf_amd64_0a22d906d95c4221\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ba2140 )
 
nvlddmkm.sys dated 5/5/2019 Nvidia video drivers. 

That is with the latest Game Ready drivers (430.64). What's weird is that whenever these BSOD occured, I was running software that shouldn't have been using the rtx2070 but should have been using the embedded intel 630 (was just watching videos, browsing on Chrome and using MS Word and Spotify - none of these should have been utilising the rtx2070).

Easy Fix for nvlddmkm.sys Error 14, I discovered that the file itself does not set the users to have FULL CONTROL. Edit the files security to allow the USERS full control of file and not just READ & WRITE. So Far it has worked and I haven't had to revert drivers, or uninstall/reinstall software and drivers. Search: Windows\System32\nvlddmkm.sys Right click, go to Properties Select Security Tab at the top. In "Group or Usernames:" box select Users (Your user name\Users), Select "Edit..." In next Popup Box select: Users (Your user name\Users) Then Below that UNDER Allow, check Full Control. Select Ok! Hope this works for all!

For me, it was Windows Rot, no amount of cleaning or DDU fixed my gpu issues. It starts to get bad after a ~year + version upgrade / card change. Though in my case, the rotten install had seen like been 4 years old, 4-5 version upgrades, 3 mobos/cpus, 2 cards..although incidentally, the problems had only started up after going from a 1080 to 2080 Ti, rather than any of the other radical hw changes...

Updated 24th February 2012: Additional information on potential driver bug triggering TDRs with 28x.xx and 290.xx drivers. EDIT - updated 29th Feb, a number of users reporting 295.73 resolves the issue. More examples of the problem being fixed added Updated Microsoft definitions and links This thread has grown quite lengthy, but hopefully is still useful for people. If you are having 'driver not responding' errors then please read this post so that you understand exactly what the issue is and how varied the causes can be - plus you may find a resolution within. Just as a 'disclaimer' here, this thread is not intended for everyone to post their problems on... The purpose of this thread is to try and help you, but also to prevent multiple topics on the same subject. Lots of people have seen these errors, so hopefully this thread should help you understand exactly what you are seeing before you post. I have seen and responded to a lot of TDR related topics now where people have not made the effort to do any prior searching. The generic error people visit this forum for is: 'Display driver nvlddmkm stopped responding and was recovered.' This is also seen as: 'Display driver atikmdag stopped responding and was recovered.' (AMD/ATI cards) 'Display driver xxxxxxxx stopped responding and was recovered.' (others) Also noted as nvlddmkm.sys, atikmdag.sys, and xxxxxxxx.sys bug-check/BSOD. ________________________________________________________ As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur. If you are having this problem frequently then you will probably find it very frustrating, however be reassured that the problem is normally perfectly solvable, although can take some troubleshooting to resolve. I personally have seen this issue on two separate nVidia builds, and an Intel onboard GPU. How does TDR work?

Timeout Detection and Recovery Windows Vista and later operating systems attempt to detect situations in which computers appear to be completely "frozen". They then attempt to dynamically recover from the frozen situations so that their desktops are responsive again. This process of detection and recovery is known as timeout detection and recovery (TDR). In the TDR process, the operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to reinitialize the driver and reset the GPU. Therefore, end users are not required to reboot the operating system, which greatly enhances their experience. The only visible artifact from the hang detection to the recovery is a screen flicker. This screen flicker results when the operating system resets some portions of the graphics stack, which causes a screen redraw. Some legacy DirectX applications (for example, those DirectX applications that conform to DirectX versions earlier than 9.0) might render to a black screen at the end of this recovery. The end user would have to restart these applications. The following sequence briefly describes the TDR process: 1. Timeout detection The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen. To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play. 2. Preparation for recovery: The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the 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, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.

Limiting Repetitive GPU Hangs and Recoveries

Beginning with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008, the user experience has been improved in situations where the GPU hangs frequently and rapidly. Repetitive GPU hangs indicate that the graphics hardware has not recovered successfully. In these situations, the end user must shut down and restart the operating system to fully reset the graphics hardware. If the operating system detects that six or more GPU hangs and subsequent recoveries occur within 1 minute, the operating system bug-checks the computer on the next GPU hang.

TDR Error Messaging

Throughout the TDR process (that is, the process of detecting and recovering from situations where a GPU stops operating), the desktop is unresponsive and thus unavailable to the end user. In the final stages of recovery, a brief screen flash occurs that is similar to the brief screen flash that occurs when the end user changes the screen resolution. After the operating system has successfully recovered the desktop, the following informational message appears to the end user. The operating system also logs the preceding message in the Event Viewer application and collects diagnosis information in the form of a debug report. If the end user opted in to provide feedback, the operating system returns this debug report to Microsoft through the Online Crash Analysis (OCA) mechanism.

It is possible to disable the TDR service or make changes to the registry in order to increase the timeout period or turn off the service, however please note that this is not recommended nor supported, and in fact doing so is considered a Windows Logo Program violation. For the original Microsoft links to the above quoted information, please see here and here. _________________________________________________________ Now you know what exactly the error is, you probably want to stop it happening. I would like to tell you that there is a one-stop fix that I could recommend, but unfortunately, TDR events can be caused by many different problems. First off though, if your computer has been bough 'off-the-shelf' and is brand new, then you should think about talking to where you bought it from. Common issues that can cause a TDR: Incorrect memory timings or voltagesInsufficient/problematic PSUCorrupt driver installOverheatingUnstable overclocks (GPU or CPU)Incorrect MB voltages (generally NB/SB)Faulty graphics cardA badly written driver or piece of software, but this is an unlikely cause in most casesDriver conflictsAnother possibility that people tend not to like to hear, is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very low FPS, then something graphically complex occurs, the GPU may not be able to respond and a TDR error may occurSome users have experienced TDR errors whilst browsing the web with the 280.xx, 285.xx and 290.xx drivers. Please head to this link to clarify if this is relevant to you - this is quite a specific issue which seems to predominantly affect web browsing as opposed to gaming. Some users have found that changing the power management mode to 'Prefer Maximum Performance' has helped, with many others reporting that 295.73 has resolved the issue. Examples of specific TDR causes: Realtek driver conflict causing TDR errorsOverheatingDriver conflict with Logitech webcam driversUnstable overclock on the graphics cardInsufficient PSURAM problems (faulty, badly seated or not configured correctly)Cleaning out dust resolved issueAMD/ATI cards also have TDR problems Things to check or consider initially in your troubleshooting: Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this here (full credit to DJNOOB for this).If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.If the issue is only with a specific game, check for patches.If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.Check that your RAM is running at the correct settings as defined by the manufacturer.Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically. Additional steps: Run memtest (memtest.org). This should complete with NO errors.If you have just installed a new graphics card, check your PSU ratings. Is it providing enough power, and most importantly enough Amps on the 12V rail.If you are using SLI, try each card separately to see if the fault lies with one.Try graphics card/cards in another computer if you can. _________________________________________________________ As most people who end up reading this will have slightly custom computers in one way or the other, please try to remember that checking things like RAM timings & PSU voltage go hand in hand with modifying or building a computer. A lot of people assume that any hardware they buy and plug in should just work, and any software they then install should be fine also... this is not entirely true. No hardware or software vendor can truly recreate all of the different possible combinations, so do expect some tinkering to be required every once in a while. For those with laptops, I appreciate there are a lot of steps here you cannot complete. However, the confined space of a laptop plus dust and age can mean that overheating is a real possibility. Beyond this you need to look at reinstalling drivers and software, and then you should be looking at potential hardware issues and likely an RMA (assuming of course you have not been overclocking in software or making changes in the BIOS). _________________________________________________________ Programs to use for stress testing CPU: - Prime95 (would advise running for at least a few hours). - Intel Burntest (run at least a few passes) - OCCT (good linpack test for CPU) Programs to use for stress testing GPU: - OCCT - 3DMark Vantage - 3DMark 11 (DX11 GPUs only) - Any of the Crysis series Programs to use for monitoring temperatures: - EVGA Precision (GPU only) - MSI Afterburner (GPU only) - Everest Ultimate Edition (now known as AIDA 64) - CoreTemp (CPU only) - RealTemp (CPU only) - OCCT (stress testing and temp monitoring) I can highly recommend Everest/AIDA64 as this shows you ALL your temperatures, including other GPU components. It is however not free - you can download a trial but it has some functions limited (including some temperatures). At the end of the day, try not to become too frustrated with the issue. Generally a solution can be found. There a lot of topics you can look back on in relation to this issue, and a lot of good people around on this (and other) forums who are happy to help, assuming of course you are willing to take advice! People understand frustration, but they aren't going to help you if you are rude or abusive... an FYI for those who just want a slanging match! If you post a topic regarding this issue, please state you system specs in as much detail as you can, plus anything you have tried so far. Feel free to PM me if you are having no luck and I will do my best to advise. See the 'GeForce GTX & ION Drivers' forum section sticky for the official nVidia response on TDR errors. J