MSI 660 TI PE Display Driver crashes

First, here is my system.
i5-2500k Processor (http://www.newegg.com/Product/Product.aspx?Item=N82E16819115072) (Processor is overclocked to 4.3ghz, temp on it never goes over 45-50°C though)
MSI Geforce GTX 660TI PE Video card (http://www.newegg.com/Product/Product.aspx?Item=N82E16814127696)
Asus P8Z68-V Pro\Gen 3 Motherboard (http://www.newegg.com/Product/Product.aspx?Item=N82E16813131790)
Corsair HX series HX650 Power Supply (http://www.newegg.com/Product/Product.aspx?Item=N82E16817139012)
4x4GB of G.Skill Ram (http://www.newegg.com/Product/Product.aspx?Item=N82E16820231314)
When my old MSI P67A-GD55 Motherboard bricked a month ago, instead of waiting on RMA I went ahead and got the Asus board, at the same time I went ahead and upgraded my old Asus GTX 560TI card to the MSI GTX 660TI card. Since the upgrade, I am constantly getting display driver crashes "Display driver nvlddmkm stopped responding and has successfully recovered." when playing games. Guild Wars 2 and Starcraft 2 are the only ones I've had time to try, but both consistently give driver crashes after awhile (sometimes as soon as 15-20 mins, sometimes takes several hours of gameplay).
Here is the list of things I've already tried:
-First, I tried the most recent Nvidia drivers. Still crashes.
-Second, I tried running driver sweeper, removing all old drivers and reinstalling. Still crashes.
-Third, I tried disabling TDR in the Win7 registry. Still crashes.
-Fourth, I really ramped up the auto fan speeds. So far it hasn't crashed while doing this, but I can't do it for too long because the fans get so loud that it annoys me greatly.
-Fifth, I thought it might be an old Motherboard driver conflict of some sort, so I completely formated my OS hard drive and reinstalled Windows 7. Still getting crashes.
-Sixth, I used driver sweeper again and rolled back to the last official MSI drivers (the ones from October). Still getting crashes.
I really don't think the card is overheating. The most recent crash happened tonight after playing Starcraft 2 for about 20 minutes, and the temperature of the card never got over 60°C. That's why even with the extremely ramped up fan speeds I tried, I think if I used them long enough, the driver would still crash.
The power supply is the same as what I used with the 560TI and it didn't have these issues. And from my understanding, the 560TI consumed more power than the 660TI.
At this point, I'm at my wits end. The only thing else I know to try is swapping out the old 560TI in with the new motherboard or waiting for my old motherboard to come back from RMA and trying the 660TI in it. Though that means rebuilding the case, uninstalling the new mobo drivers and installing the old mobo drivers and authenticating Windows. Doing all of that is going to kill most of a day and I really only want to do that if I absolutely have to.
I've had such limited time for troubleshooting the card, that I'm regrettably past the 30day limit on RMA replacements to Newegg. So unfortunately that means I'm looking at an RMA directly to MSI and that takes about a month. Before I do that, does anyone have any advice on something to try that might be the cuplrit or can help determine the culprit? I can't find any details in the Event Viewer as to what caused the driver crash. Just that it has stopped responding and has recovered. I wish it could tell me if there was a loss of power, or anything. Power Management Mode is set to prefer maximum performance btw.
Btw, as a brief description of what happens. The screen goes black, and then comes back and the game is running very slowly. There will also usually be a popup above the taskbar saying that the driver had crashed. I keep the MSI Afterburner info window open in my second monitor and Power usage never goes over 80%, GPU Usage is usually around 95-99%. Core Clock and Memory clock drop to about 324mhz (which is what it idles at) temporarily during the crash. GPU Usage of course dips to very low levels while the driver is crashing, as well.
Oh and in an added twist, I've run Kombuster several times. Burn-in test DirectX 11 1920x1600 8xMSAA as long as five hours, and the display driver has never crashed. I'll probably turn it on, and disable the computer's sleep and display off tonight and let it run for about 8-9 hours and see what happens. That's one thing that throws me off, if it's a hardware defect, wouldn't Kombuster cause it to crash?
edit-Here is a screenshot of the Afterburner monitor during a crash while playing Starcraft 2. The huge dip in the bars that I have the cursor over is when the crash occured.

Well with the Power% limited to 75%, I just had another crash in Starcraft 2. Temp was only at 56°C just before the crash.
Here is a shot of the Afterburner Hardware Monitor when it crashed:
Unfortunately I do not have another PC to test the card in. And I don't know anyone around here with a system that the card could work in.
If I swapped out the 660TI with my old 560TI and I do not get any crashes, wouldn't that indicate it's the 660TI's fault and I'd need to RMA since the 560TI is a more power hungry card?

Similar Messages

  • Intel display driver crashes on S1 Yoga running 64-bit Windows 8.1

    Whenever my machine comes out of suspend mode, the display driver crashes.  It goes to a black screen for about 8 seconds then I get the error "display driver intel hd graphics drivers for windows 8 (r) stopped responding and has successfully recovered".   The black screen is consistent but the error is occasional.  I also got the error when performing a right click on the desktop to enter the display properties. I am running the most current driver for my graphics card and the most current BIOS version.  After researching this problem online it appears that it is a known issue but the fixes I saw posted all included using an older driver from another manufacturer.  Is there a better fix from Lenovo out there?

    Hi @curtisa, @guigs2 and @rmcguigan,
    Thanks for your responses.
    I managed to get eWallet working correctly for 24 hours approx. by uninstalling Firefox, running CCleaner, deleting all Mozilla references on my system drive, scanned for virus using Win Defender, SuperAntiSpyware, and SpyHunter, (nothing reported) then again downloading and installing the current version of FF to "Program Files (x86)".
    However next morning, it had failed again.
    I checked the Windows event log and it shows an error with a Source of .NET Runtime. The application is eWallet.exe, Framework Version V4.0.30319, Exception Info SystemAccessViolationException.
    I'm not sure what that all means, and would welcome any further suggestions.
    Cheers
    Steve

  • When I have firefox open, it crashes at the same time as my display driver crashes (Crash signature: kernelbase.dll@0xb9bc)

    The screen turns black (audio remains normal if I'm playing music) and then flickers back on. I get a message that says "Nvidia display driver stopped responding and has recovered successfully." This happened before and Firefox wouldn't always crash, but the last few days it happens several times a day and Firefox always crashes at the same time as the display driver.

    No, they aren't working on the same files. All 3 employees are working on different files.
    They are all on Dell Optiplex GX745 with 4 Gb of RAM.
    The crashes are at different times, not all 3 crashing at the same time. Therefore, I don't believe network is the cause of the issues. Also, it didn't crash on CS5, but now it does on CS6.
    What I'm looking for are possible settings within Illustrator CS6 that I can tweak to make it a more stable program.
    Thanks

  • AT2020 Not Working & AMD Display Driver Crash

    My AMD display drivers crash every time I try to start a skype call. I have the newest beta build, what driver version should I use? (I have the r7 260x)
    Another issue I have is that if I have a call that does work, my AT2020 will not have sound input for skype. It works perfectly fine with other programs and windows. (I use an AT2020 XLR and a PreSonus Audiobox USB)
    I just want to record games and talk to friends. Please help!

    If you use beta builds of drivers (If I understand you correctly), you should expect crashes and incompabilities. For general stabillity, the latest WHQL driver should normally be the best bet (not allways offcourse).
    You can allways run a dxdiag and post it here, Winkey + r > dxdiag, save it and zip it (rightclick > send to ziped folder), and post the zip version, there might be other issues.

  • Satellite Pro A100-080: NVidia display driver crashing during 3D Games

    Hello,
    i have some problems with the display driver since i've bought the notebook 9 month ago. I've tried to install every new driver published on the toshiba homepage but no driver is running stable on my system.
    The problem is that my notebook is crashing with bluescreen during playing 3d games and my windows vista tells me its the display driver causing the crashes.
    I had the previous version of the driver installed several month ago and i feel it was more stable than the current version. But unfortunately i've lost the files for that one, but i would prefer any functional driver for this notebook.
    My Notebook
    Satellite Pro A100-080
    Modelno. PSAASE-00G004GR
    Manufactured on 2007-02-20
    Thank you all in advance for yr assistance
    bgrds
    Robert

    Hi,
    below you will find a small list of games i've tried on my system.
    Supreme Commander
    Halflife 2 (including several mods)
    World in Conflict Demo
    Warhammer - Mark of Chaos
    Warhammer - Dawn of War
    X3
    I've also tried to play the older games on compatibility mode, but this doesnt run. At least one of those games should run properly on my system, but none is running.

  • 870A-G54 - Possible overheating caused by too much ram? Display driver crashes

    Greetings, I have a 870A-G54. I've had multiple issues with several video cards prompting me with a "display driver has stopped responding and has recovered" error. Each video card having it's own unique fix. I've come to the conclusion that it's another piece of hardware in my system that is the root of the problem; and not the video cards. I've noticed that the CPU during "the crash" hits about 60c; usually when playing video games. After a reboot, I can play games for a couple more hours before getting the error again. I'm running 16gb of ram on Windows 7 ultimate. Yesterday I decided to remove 8gb of ram to see if the CPU got "hot" again (only leaving the sticks in bay 3 and 4 in). I had a 4 hour session of gaming and it didn't crash. Note, I have the latest bios installed and a Power Supply that shouldn't have issues powering the whole thing; 850w gold rated PSU. I'm currently running a 6950 video card, and all of the settings are stock; no over clocking in any way. I have a hardware monitor installed that shows with my 16gb of ram that my cpu idles at 41-43c. During a intense gaming session going up to 60c. Yesterday after removing the other 8gb (two sticks of 4gb), it never went above 50c. My CPU is well ventilated. I've contemplated water cooling the CPU if that would resolve the issue. But I'd hate to fork over more money to an already expensive system if I don't have to. I've also wondered if it's just a bad ram stick, or bad ram bay on the motherboard. :\
    Any suggestions here would be appreciated! Thanks!

    So, I conducted several tests over the last couple of days. Now, I understand that mismatching ram could (and probably is) potentially causing the overheat problem. But... I kind of started looking at fundamentals. I have to sets for DDR3. One pair is Patriot sector 5 ram, the other is a set of Dominator ram. Now, I've noticed that I've seem to always have this driver crash issue. But I had always thought it was the video card. Only until recently I started seeing/noticing that the cpu was getting very hot when the driver would crash. On Wednesday I removed the ram in slots 1 and 2 (the Dominator ram), and only ran with the ram in 3 and 4 (Patriot). It ran fine all night. I then ran some heat tests, with the same ram in bays 1 and 2. When the Patriot ram was in those two slots, it ran cooler. When the Dominator was in, it ran hotter. The Dominator's builtin heat-sinks pretty much rest right next the CPU's heatsink (and restrict air flow). It re-arranged the ram so the Dominators are in 3 and 4. And the Sector 5 are in 1 and 2. It worked all night yesterday, CPU didn't get any hotter that 48c while having multiple programs running. Looking at it now, the design of this MB is pretty bad, there should be a little more space between the CPU and the ram. In any case, I will follow up if it continues to crash due to heating issues. I know it's probably cheaper to get new ram, but I'm playing with the idea of just getting a better heat-sink for the CPU (WATER COOLED)!

  • Firefox can't recover after my display driver crashes

    My display driver is garbage, it crashes multiple times a day. It always has (I got this laptop second-hand).
    I'm used to it. I've tried reinstalling drivers, editing the registry, reinstalling windows, switching browsers, etc etc etc
    It's fine, I guess I can live with it crashing throughout the day, it flicks back on in a second or two.
    HOWEVER, I can not live with it shutting down my browser EVERY TIME. Chrome and IE can recover from this, but apparently Firefox can't. Firefox just goes blank and won't respond- I lose all my pages. Chrome and IE will bounce back with the pages and tabs that were open when the display crapped out on me.
    I guess my question is, how do I prevent this from happening?
    Or can you fix firefox so that it can recover from this? I really hate using chrome. Help me out, firefox

    Did you already disable hardware acceleration in Firefox?
    *https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    Make sure that you do not run Firefox in permanent Private Browsing mode (Never remember history).
    *https://support.mozilla.org/kb/Private+Browsing
    *Tools > Options > Privacy > Firefox will: "Use custom settings for history"
    *Deselect: [ ] "Always use Private Browsing mode"

  • W701ds Nvidia display driver crashes frequently

    Hello, I have a W701ds with 16gb of ram running Win7 Pro 64bit.  Using preinstalled OS.  My display driver keeps crashing (about once an hour or so) with an error message that the display driver recovered from an error.  The screen goes black for a few seconds and then returns.  This generally happens when I am watching a video or working in Powerpoint, Adobe After Effects, etc.  All drivers are up to date.  Has anyone else experienced this problem, and do you have any recommendations as to how I can resolve this?  Thanks all.

    Been a couple months since the video card was replaced. Happy to say I am ROCK solid now!! Absolutely zero display crashes even running heavy applications!

  • Display Driver crashes in Windows 8.1 on late 2013 macbook

    I have been able to install Windows 8.1 on my new 15 inch MacBook with Mavericks and Nvidia GPU. I installed windows along with the bootcamp drivers. The issue I am having now is that the machine complains that "Display driver stopped responding and has recovered".
    This is happening every 30 seconds at its worst. When I have tried installing windows 8.1 earlier, rebooting resulted in windows booting to a black screen.
    I have tried running windows updates but the same thing happens and after restarting the machine, windows just boots to a black screen. I have tried installing windows but not running any updates and the same thing happens. This is now my 3rd attempt in which I tried installing nvidia drivers direct from the nvidia website (331.65-notebook-win8-win7-64bit-international-whql) but the installer complains about incompatible hardware.
    Is there any way to get windows to behave?
    For refrence, I installed windows the following way:
    Creating an iso from my windows 8.1 dvd on a windows machine.
    Use bootcamp assist to create a bootable usb from the iso, allowing it to download boot camp drivers.
    Splitting the hardrive into 2 partitions inside bootcamp assist.
    After the computer reboots to install windows, I then rebooted back into OSx and went into disk utility. I reformatted the bootcamp partition. I also added 2 more partitions that I later plan to put linux on.
    Restarted the notebook, booting from the bootable usb. Followed the windows 8.1 install prompts including formatting the bootcamp partition. Machine rebooted many times.
    Allow the installer to install bootcamp drivers.
    Restart and windows 8.1 was installed.

    The Solution
    The section about installing nvidia drivers worked flawlessly!
    Download the latest nvidia driver.
    Unpack/run it on your local harddrive(note where!), it won't install at this point"You need a modified .inf file to make the installer work"
    Go to: www.laptopvideo2go.com - Windows 8 Nvidia 314.22 WHQL .inf File
    Locate the inf file for the driver version you downloaded in step 1. Save the inf file locally
    "Copy the downloaded .inf file into the Nvidia installer folders at: C:\NVIDIA\DisplayDriver\314.22*\Win8_WinVista_Win7_64\International\Display.Dri ver (when asked if you want to replace the file say yes)." *note that driver version may differ
    Run C:\NVIDIA\DisplayDriver\314.22*\Win8_WinVista_Win7_64\International\setup.exe
    You are probably done by now!
    If problems still occur, go to Device Manager
    Locate Monitors -> Generic PnP Monitor
    right click and choose disable
    My Problem
    My screen went black on startup. I think some kind om Windows 8 update, was the cause.
    Anyhow, uninstalling the nvidia drivers in safe mode* "solved" the black screen problem.
    *Getting into safe mode was the most terrible part since shift + F8 wouldn't work for me at all(were I too slow?).

  • Satellite A500-1GL - Display driver crashes

    Hi!
    I have a *Toshiba Satellite A500-1GL*, which always crashes the video driver. Always comes "The driver has been restored after a failure," or something like that.
    Have the unit in March 2010 purchased new.
    What can I do about it?
    Please help!
    Thanks in advance!
    psp

    Hi psphc11,
    If you would use the forum search, your question would be already answered.
    Did you use the forum search?
    Here are some results of forum search they are useful for you:
    http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=53955
    http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=51062
    Check this!!!

  • GTX580 Twin Frozr II OC : Display driver crashing in DX11

    I have two GTX 580 Twin Frozr II OC in SLI. nvlddmkm.sys seems to crash and restart after about 10 -15 mins on gameplay on DX11 games (I have seen it happen in F.E.A.R. 3 and Crysis 2 DX11). I have not had any issues with other games (I haven't played any other DX11 games), and surprisingly, it hasn't occured on Heaven benchmark (DX11) either, for some reason.
    Config:
    Core i7 2600K @ 4.5Ghz (Vcore:1.35V | Mult: 45)
    Corsair Dominator GT 8GB @ 1600Mhz, 2 DIMMS (1.6V, 9/9/9/24)
    ASUS P8P67 Deluxe
    Corsair HX 1000W
    2 x GTX580 Twin Frozr II OC (not overclocked above the factory overclock)
    300GB Intel 320 SSD
    500GB WD Black Caviar
    Windows 7 Ultimate x64
    Single Monitor
    The BIOS for the cards is up-to-date, so are all drivers.
    The voltage for both the cards was 1025mV. I upped the voltage to 1050mV (using Afterburner) and I haven't had any issues since (played Crysis 2 DX11 for a couple of hours). Could that have been the issue? If so, how do I permanently set the voltage to that value? And why am I having to do this in the first place?
    Thanks!

    Quote from: TripShock on 16-July-11, 10:30:54
    Also, do you know how to flash a new BIOS with different default values? I rather not have to set Afterburner to autostartup...
    - download NiBiTor v6.0 or above
    - save your bios by GPU-Z
    - open saved bios in NiBiTor and go to Tools/Fermi Voltage
    - change voltages Setting 2 and 3:0 from 1,0250 to 1,0500
    - change voltages Setting 2 and 3:1 from 1,0750 to 1,0880
    - klick Apply
    - save bios named gtx580.rom
    - than you must flash this bios on the card, you need bootable usb disk - try GOOGLE
    - if you have bootable usb and have copied right files for nvflash, restart pc, and get to boot from usb
    - in DOS mode write these commands: nvflash --protectoff for unlock security before flashing and the second command is nvflash gtx580.rom (name of saved bios)
    - watch in progress and at the succeed end, restart PC
    - finally in windows, reinstall driver for card
    Hope this manual was helpfully for you. Sorry for my english
    Regards

  • Firefox 4 crashing display driver

    I am using acer aspire4741G with an NVIDIA GEFORCE GT330M' driver version 8.16.11.8886'(ForceWare 188.86). when i browse using firefox the display driver crash and show me one message like (the display driver has stopped working and recover successfully). Firefox is the best browser with the perfect extensions but this problem make me sad

    Hi every buddy its me again.I just successfully solve my previous problem. How? its so easy' just update your firefox browser. I think this problem happen only in the firefox 4 beta 7 and 8. The new version of the firefox 4 beta 9 to12 and 4RC is much batter than before. Thanks everyone and run the fox as you wish....

  • R400/T400/T500/W500: display driver "amdkmdap" crashes

    Executive summary: All current Lenovo ThinkPads with switchable graphics (R400, T400, T500, and W500) have usability issues in connection with Vista and the use of external monitors. For more than half a year, users were plagued by frequent Windows crashes. During that time frame, Lenovo did not comment on the various available reports and complaints. By the end of April 2009, Lenovo resolved many issues by releasing a new official driver. Though several problems, including severe ones, remain as of today. Lenovo has said to be actively working on the remaining issues (without outcomes so far).
    Important information for affected users: If you're having one of the issues reported here, then Lenovo advises you to call your local Lenovo Support. Demand that a case is submitted to hardware engineering. In particular, you should ask for "a CMVC case to be created and escalated". Using these "code words" ensures that your case is properly addressed.
    Old problem description
    On Vista 32 and Vista 64, the ATI display driver "amdkmdap" crashes when an external monitor was active before OR an application (game) using DirectX technology is used. The user typically receives a couple of so-called "Timeout Detection and Recovery" (TDR) messages from Vista:
    (Click here for an explanation of the message from Microsoft)
    Sometimes, amdkmdap crashes several times in a row. Then Windows crashes with a so-called "BSOD", likely resulting in data loss. Typically, Windows detects "atikmpag.sys" as the crashing driver. Sometimes, also an instantaneous reboot happens independent of prior TDR crashes. In such a case, no BSOD is displayed.
    The following movie illustrates the phenomenon: http://www.youtube.com/watch?v=LBX9QsCmrpY
    This behavior above has been confirmed for the following ThinkPad models: R400, T400, T500, and W500 (see below). Problem reports indicate that the symptoms are often related to playing games and/or the notebook being docked and the external monitor being connected via DVI.
    Though, the presence of these two conditions is not necessary to trigger the driver crash:
    There are reports where no dock was involved and the external monitor was connected directly to the notebook's VGA port.
    Furthermore, there are reports where the notebook was docked and an external monitor was connected to the DVI port.
    So far, there has been no report relating to a monitor being connected to the Display Port which is available on some models. (Possibly because this port is not used.)
    There are a few reports where neither a dock nor an external monitor was involved.
    Playing certain games reliably triggers the crash.
    Steps to reproduce
    While intially (around September 2008 - October 2008) the crash could be triggered easily, the situation is now (December 2008) more complex. The crashes do still occur, though there is no clear pattern anymore. According to various reports, the display driver crash can be triggered as follows:
    Resuming from standby
    Watching a DVD.
    Playing one of these games: Fallout 3, Bioshock, Team Fortress 2, Knights of the Old Republic.
    Arbitrarily during normal work. On a normal working day, the problem occurs at least once.
    Further issues
    Here are more issues which seem to be related. More information can be found in other posts of this thread:
    The notebook display and/or the external monitor runs at a low resolution after resuming from standby.
    After the login both monitors flicker while adjusting the resolution of the monitor.
    The external monitors cannot be activated using Presentation Director.
    The external monitor is blank after docking or undocking.
    There are some reports about display driver crashes on machines running Windows XP.
    The switchable graphics drivers limit the useable RAM under Vista 32 to 2.5GB (i.e. 500MB-1GB less than usual).
    Workarounds
    Lenovo has released a new "tip" document which provides a link to a new driver. Get it here but be sure to read the instructions!
    (Old tips follow below the line. Consider them as obsolete.)
    Here are some tips which might make the problem occur less often. I have not tried all of them. Though, A. and B. have improved the situation for me; your mileage may vary.
    A. If you do not have to use an external monitor, then switch to Intel graphics for time being.
    Otherwise:
    B. Make some changes to your system:
    Disable Aero.
    Create a new profile in the power manager with the following setting: When running on AC, turn off the monitor after 40 minutes. (Thereby, the notebook goes less often to standby.)
    Install the newest graphics drivers.
    Install the newest BIOS.
    Install the newest Hotkey utility.
    Install the newest drivers.
    C. Disable the switchable graphics in the BIOS setup and install modded drivers from ATI (see zilla's post in this thread for instructions).
    The last workaround (C.) has been confirmed to work reliably by several users. Though, thereby you use drivers which have not been tested by Lenovo. It's possible (but not very likely) that damage results by doing so. Also, it might be difficult to install a future Lenovo driver which resolves the issues reported here. Finally, you cannot use the power-saving Intel graphics. Thus, you should only use this workaround if you know what you are doing.
    The programs can be downloaded from the following locations. Notice that System Update does not always offer you immediately the lastest versions.
    R400 and T400 users: Go here.
    T500 and W500 users: Go here.
     User opinions
    "Is there any chance this will be fixed, or should I just get used to my "workstation-class" machine crashing regularly?"
    "I [am] thinking about to sell my w500 if this problems won't be fixed in the next weeks."
    "I've got a T400 w/ Vista 64 and I'll say the Switchable drivers on it S[**]K bad."
    "Unfortunately for Lenovo, our IT Manager is at the point of a awarding a new and rather substantial Enterprise Agreement for our whole organization's PC's, which included a rollout of many new PC's for 2009. The contract was going to go to Lenovo. He mumbled something about HP when I asked him about the state of affairs with my PC... [O]ur firm's IT Manager decided to return all the faulty Lenovo's for a refund and would replace them with HP's."  
    "Is someone from Lenovo paying attention[?]"
    "i'm getting angry with ati and lenovo."
    "there are no new drivers and no ETA for a fix."
    "ThinkPads are supposed to be good, so you'd think there wouldn't be a problem like this."
    "honestly it is completely unacceptable for lenovo to have done nothing this long. I paid extra to get the ATI card, and now I can't hook up my laptop to an external monitor without it crashing. I will probably end up selling the laptop soon since using an external monitor is extremely important to me and lenovo doesn't seem to care about fixing the situation."
    Update:
    - Lenovo support has informed me today (2008-10-24) that they are working on the problem.- changed subject (was: Major troubles with DVI-port and a T400) to reflect new information.- changed message body to reflect new information
    - See MIGR-70490 (dated 2008-09-21) for an official statement from Lenovo.
    - 2008-11-15: The problems are still present and there is still no ETA for a fix.
    - As expected, also R400 models are affected. See below for reports.
    - 2008-11-26: Still no word from Lenovo when the problem will be fixed. Added information on (partial) workarounds.
    - 2008-12-03: Lenovo updated MIGR-70490. Though, problems persist.
    - 2008-12-13: Updated problem description on the basis of new reports.
    - 2008-12-16: Updated problem description on the basis of new reports.
    - 2009-01-07: Updated problem description on the basis of new reports. Still no word from Lenovo. I called Lenovo's customer service in the Netherlands and was promised to receive a callback. Though, so far they didn't (want to) get back to me.
    - 2009-01-08: Updated workaround description on the basis of new reports.
    - 2009-01-10: Updated executive summary on the basis of new reports.
    - 2009-01-14: Updated problem description on the basis of new reports (movie).
    - 2009-01-19: Updated workaround section.
    - 2009-01-21: Happy birthday MIGR-70490! It's now 4 months. Updated workaround section. I called Lenovo's customer service in the Netherlands again.
    - 2009-01-22: Added section "User opinions"
    - 2009-01-23: Updated problem description on the basis of new reports.
    - 2009-01-24: Small updates.
    - 2009-02-02: Small updates.
    - 2009-02-03: Changes to section "Executive summary". Added section "Important information for affected users".
    - 2009-02-04: Update to section "Credits".
    - 2009-02-19: Update to section "Credits".
    - 2009-02-27: Quick update to "Executive summary" and "Workarounds".
    - 2009-03-10: Quick updates to section "Executive summary" and "Important information for affected users".
    - 2009-03-21: Quick update to "Executive summary"
    Credits
    Workaround "Aero off": Bubbi, TonyK
    Workaround "Modded ATI drivers": jtull89,  zilla
    Thanks to Mark_Lenovo and Confederate for their work behind the scenes 
    Thanks to feedback from: ajgiordano, Andy_7575, ben2e, brettgri, bri0831, Brimstar, Bubbi, CodeNameSly, cpueschner, dandill, diablo2man, ewilansky, gaccounts, gan, gandalf7, golffreaksi, Homer, hubertlam, Jiraiya, johnsonjf, jordan_moss, jmark, jtull89, kbarina, lenardg, lukest, misitmichaelf, mlb, MMetts, ojisan, pendaluent, Qot, rmccallen, sarnil, shaofengsd, Snakecharmed, StephanK, tarzan23, Texas1040, TheNewNumber2, TonyK, trickyDick, vedman, Vitalus, Waschbecken, xpnet, xrafx, zilla, ZPrime
     (Please don't expect that this list is complete. I am not paid to keep it accurate and complete and, actually, I have a life besides writing about Lenovo's problems. )
    Original post
    Hi there!
    I have major troubles using a Dell 2709W monitor with my T400. 
    The notebook is attached to a Advanced Mini Dock to which the monitor is connected via DVI.
     The problems are as follows.
    A. Activating the external monitor often fails
    Steps to reproduce:
    1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T40
    2. Start Windows and make sure that the T400 is running on the ATI card.
    => Dell monitor enters power saving mode because no signal is coming.
    3. In Windows use either the Presentation Director, Windows, or the ATI tools to activate the Dell monitor.
    Expected result: The Dell monitor is activated and the Windows desktop is shown on it.
    Actual result: It takes 1-3 seconds for the Dell monitor to display something. The monitor shows the Windows desktop for a short period. Then it's black again and the monitor returns to the power saving mode .
    Analysis: It seems that the Presentation Director, Windows, or the ATI tools (or more aptly, I guess, the ATI driver) expect a quick response from the DVI-port that a monitor is present. If they do not receive the response, the DVI-port is deactivated again. Since the monitor is too slow to respond and enters the power saving mode too quickly, the monitor can hardly ever be activated.
    Suggested change: Change these tools (or the ATI driver) so that they wait longer for a response on the DVI-port.
    B. Resuming from monitor sleep causes Windows to fall back to a low resolution if the Dell monitor was activated before
    Steps to reproduce:
    1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T400
    2. Start Windows and make sure that the T400 is running on the ATI card.
    3. Select the Energy Star profile
    4. Activate the Dell monitor
    5. Don't use Windows until the notebook display and the Dell monitor are set to sleep by Windows.
    6. Wake up the displays (e.g. by pressing some keys)
    Expected result: Both displays are run in the display mode as before.
    Actual result: The Dell monitor still sleeps. The notebook displays is run at a lower resolution (I guess 800x600). The Windows login prompt is not visible and it has to be guessed that it is shown. Though the typical Windows login background is visible. If the password is entered, then Windows can be used again. Though, the resolution is still low and the Dell monitor still sleeps.
    Analysis: It seems that by sending the Dell monitor to sleep, the monitor deactivates the DVI-interface or enters a low-power interface mode. This seems to disturb some component in Windows (the Presentation Director, Windows, the ATI tools, the ATI driver) in a way that Windows only activates the notebook display when it resumes from "monitor sleep".
    Suggested change: Change these tools (or the ATI driver) so that they can cope with the situation that the DVI-interface is deactivated and wait longer for the interface to be in a useable state. Reactivate an external monitor even if it "sleeps very deeply".
    Relevant system information
    - T400 2767-CTO (T9400, 2x2GB RAM, ATI, WXGA+ LED)
    - Advanced Mini Dock
    - Vista 32 Business (German) - fully updated
    - All Lenovo updates via System Update are installed- Dell 2709W
    - The system runs the ATI graphic card in the described scenarios
    Message Edited by Izmi on 05-21-2009 10:34 AM
    Message Edited by Izmi on 06-29-2009 03:13 PM
    Solved!
    Go to Solution.

    Lenovo support made me reinstall presentation director to rule out this component as a factor. After the reinstallation, the amdkmdap-problem is still present. Letting Windows go to standby and waking the system up afterwards, is a reliable method in my case to reproduce the problem on condition that an external monitor was active. The problem does not occur if no external monitor is present.
    A web search for "amdkmdap", "atikmpag","BSOD" with one of the ThinkPad-series names (like "T400") shows that other persons also have this problem with R400s, T400s, T500s, and W500s:
    - t400: Display driver crashes
    - W500 Display Driver
    - My W500
    - T400 Display driver stopped working...
    - T500 Video/Video Driver Issues (2056-4SU)
    - NUS T400 issues
    - T400 Display Driver Issue
    - Vista64 + 4GB RAM + External Display = BSOD
    - R400 problem report (in Chinese)
    - T500 problem report (in Chinese)
    - Bioshock keeps crashing (seems related)
    -  Vista x64, ATI graphics, dock + external LCD = bluescreens? (a report by a W500 user)
    - many problems with lenovo w500
    - another R400 problem report (in Chinese)
    -  Vista BSOD on Lenovo T500 with new Switchable Graphics
    - switchable graphics and external monitor through port replic
    - Problem with Lenovo T500 notebook & external LCD
    - Lenovo ThinkPad T400 - some impressions.
    - T400 freezes with graphics Intense programes
    - Standard Laptop mit ein paar Macken (in German)
    Some possibly related Non-Lenovo cases: 
    - Why Vista crashes so often when dual display is enabled?
    - Vista and 7.3 Display driver atikmdag stopped responding error
    - 4870 vista x64 multi-mon = atikdmag BOOM
    In the cases in which people observe the "amdkmdap"-problem and describe the circumstances, the use of an external monitor is always a factor. These other reports also indicate that it is likely not an issue with the hardware of my notebook (or then a general problem for many batches of these machine types). For it happens a) on many systems and b) on different kinds of systems.
    If others want to contribute to the problem solution, then we should provide Lenovo and ATI a good problem description. So, please add your description.
    Message Edited by Izmi on 02-03-2009 11:53 AM

  • Skype keeps crashing on log in "display driver stopped working and has recovered"

    HiI have ati radeon 260x OC with the lattest cataclyst driver from AMD site. When I log in on skype display driver crashes but sometimes all system is not responding (freeze) and I have to restart. How can I resolve this? I use lattest skype version and windows 8.1. Thank you!DxDiag loghttp://pastebin.com/6aBX0Hd8

    It seems that the latest Skype versions don't work with AMD Radeon R7 200 Series graphic card. Try to uninstall the currently installed version and install the 6.14.0.104 version using the download links provided here: http://community.skype.com/t5/Windows-desktop-client/ASUS-USB2-0-Webcam-not-recognized-by-Skype-6-18​... Make sure to disable automatic updates:Tools -> Options -> Advanced -> Automatic updates ->Turn off automatic updates

  • Severe driver-crashes with N580GTX Lightning! [v3xx series]

    Hello everyone!
    i just registered here after a while of scouring the forum a bit. i'll try to present info about the issue in accordance with the posting guidelines as far as possible, as well as try to be concise in it.
    my system-specs can be seen in my sig below. following is about the occurrence(s):
    1. i got my system built in Aug./Sept. 2011, the GPU being bought at the same time. since then, i have played games a lot less (unjustifiably). in fact, very rarely in 2012. the last games i remember playing were BF3, skyrim, hard reset, & limbo, all at their respective default graphics-settings. the GPU has NEVER BEEN overclocked, nor MSI's applications been used at any point of time.
    2. two months back, in november, i started noticing that the display-driver crashed intermittently. this was a never-seen-earlier issue for me, and it being far random & infrequent in nature, i neglected it as some random occurrence. the display-driver must've been from 3xx series then, but i can't say surely. i was till then using drivers downloaded from MSI's website after it used to notify me about the same. this was probably the 1st time i had downloaded drivers from nvidia's website though.
    3. a little later, with time, nvidia started showing me updates about driver-releases every now & then, and i started downloading & installing all of them.
    4. now, at the time i am writing, i had downloaded v310.70, and the crashes, with the passage of time within these 2 months, have gone from worse to berserk! i booted up my PC 2 days back after a gap of a week, and for a few hours it behaved normal, but after an overnight operation the next day, the driver showed it's true worth again! since then, in the past 2 days, the v310.70 driver is behaving madly, and the system kept restarting on this driver after continuous crashes! i was also notified about v310.90 being available for download, but i skipped that understandably.
    5. today, i tried clean installation of earlier drivers as well, till v280.26, using 'driver fusion', but to no avail. the most 'stable' version seems to be v306.97, as it crashes only when:
     - i boot up the PC. it then crashes 3-4 times continuously, and then everything's normal again.
     - same behaviour when i put the PC off 'sleep' mode, though not consistent.
     - when i watch a youtube video; crash occurs very randomly.
    thankfully, with v306.97, the PC isn't restarting (yet!).
    6. i was contemplating writing to MSI India for a probable fault with the card after such crashes & after going through nvidia forums (where nvidia hasn't bothered to respond properly), but then thought of 1st posting it here after going through this forum.
    please note that i have NOT overclocked the GPU at any point of time ever, played games very less, games used to run flawlessly till sometime back (and i haven't played any after this issue showed up, but i know what could be the result of doing so).
    S/N of the card is: 602-02SB11098062
    am not able to test the card in any other PC, as i don't have one, and nor do i have friend(s) here close-by. also, should i update MSI Afterburner? i read in a thread that it solved the issue with one. nevertheless, i know i should, obviously 
    also, i keep my PC turned ON frequently over the nights (if that is of any help here).
    Please let me know if any additional info is reqd., as well as what could be done. i don't have much idea about intricacies of the topic like changing voltages, BIOS flashing, etc., but you could just let me know what should be done & i have the searching-ability as well as Mr. Google to assist me too
    Thanks in advance!
    UPDATE: so the system had its 1st restart now on v306.97 driver, after i started gtalk. a momentary hang, and zap! also, am using the DVI port on the card to connect it to the monitor, if that's of any use here.

    I have this same problem and have been scouring forums for months on end to no avail. Previously using the older version of the drivers it would crash often when running intensive games such as BF3 and Hitman Absolution whereas since the recent update it crashes regularly with pretty much any game on high settings. By crash I mean lots of small green square shaped artifacts all over the screen then the machine reboots.
    I have reported this problem to Scan computers where I purchased the card from and travelled 2 hours to get to their base only to have them test the card for 20 mins on BF3 and report that they found no issue with it. The problem I have is also that it could sometimes run for a couple of hours before having sudden spate of crashes so it wasn't really guaranteed to show a problem with the way they tested it.
    Scan at least understood that I was frustrated and replaced all the mem sticks in my machine - this didnt help either as the problem persists and I am very very frustrated with the card - so much that I am thinking I might chuck it in the bin and buy a 680GTX from a different manufacturer because it costs me more to take time off travelling to Scan that it would do buying a new card (petrol and losing pay as I am self employed).
    I have tried the following to resolve the issue;
    1) Complete rebuild of machine - remove clean and reassemble all parts and reinstall OS from scratch more than once
    2) Run with different driver versions - some are more flakey than others but all are unstable
    3) Replace all the memory
    4) Ran with memory in different slots
    5) Changed mem timings from auto to XMP to manual etc
    6) Ensured no area of the system was overclocked in bios
    7) Running different versions of motherboard bios
    8) ensured electricity supply wasnt at fault by changing the sockets used, 4 way gangs used, tried dedicated socket - I also moved house during this period and still get the same issue at the new house
    9) Rewired the graphics card to different ports on the PSU in case those were at fault - all give the same result. PSU is also a 750w corsair pro series so has enough juice to run a single card that hasnt been overclocked in my opinion. I also dont have any other add-in cards that might be drawing power.
    I notice that sometimes when it crashes to desktop and doesnt reboot the system it states that the driver stops responding and also that the graphics card can no longer be detected.
    I had at one point thought this might be an overheating issue however sometimes I can boot up my machine from cold and there is white lines all across the screen in POST and upon booting into windows it goes into the default vga driver mode stating that the graphics card cannot be detected - the msi afterburner software also states that it cannot detect any compatible hardware.
    If I then reboot my machine anything up to 10 times the graphics card then starts working and the white lines in POST dissapear and everything might run fine for a few hours. Having said that it actually used to sometimes crash in VLC player whilst watching a movie which is hardly what I would call intensive use.
     All in all very frustrating and whilst I used to seriously rate MSI products this has left me feeling a bit cold because SCAN were not interested in the many screenshots i sent them or the video of the problem occurring - they eventually relented and said send in the card for testing which would equate to them having it for up to 2 weeks during which time i dont know if they will just test it with bf3 for 20 mins again and declare it perfectly fine.
    Also I have to add, if I enable the on-board graphics chip on the motherboard and run with that then the system is completely stable which again points me back to the GPU being at fault.
     

Maybe you are looking for