Bluescreen in ProBook 6560b caused by display driver Radeon HD 6470M

My computer has crashed every now and then since it was new showing bluesreen caused by a display driver error. My driver is Radeon HD 6470M. It's very disturbing and nowadays when the computer is 2 years old it has begun to crash more often. I'm really surprised of the error that can be possible nowadays in a new computer which cost me about 1000 euros.

Hi @Freedomic
Thank you for your inquiry. To get your issue more exposure you may want to post it in the commercial forum as this is the consumer forum. Commercial Forum
As your Probook is a commercial unit is it outside of support bound but your homepage may help in the meantime.
HP ProBook 6560b Notebook PC
Good Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Similar Messages

NVIDIA OpenGL driver lost connection with the display driver

Alienware M14x Laptop
Windows 7-pre 64-bit
8gb ram
3gb Video: NVIDIA GeForce GT 555M
Intel i7 2760QM
AE CS4
AE keeps crashing. I get the following message while doing something as simple as scrubbing through the timeline, or changing opacity of a layer. in 1080p, I have a picture layer, a solid, some color corrections, and that's it. i just got this new computer and i have never had this problem on my old computer.
this message appears after AE crashes."The NVIDIA OpenGL driver lost connection with the display driver and is unable to continue. The application must close."
this message appears in the taskbar: "Display driver stopped responding and has recovered. Display driver NVIDIA Windows kernel Mode Driver, Version 267.21 stopped responding and has successfully recovered"
any ideas on how to stop AE from causing my display driver to stop working?
Thanks, Ramzi Rebeiz

For anyone picking up this thread (it's probably too late for rrebeiz40 by now!) I have come across a simple but apparently very effective tip that has solved the 'OpenGL driver lost connection' issue for many people using various NVIDIA with various Adobe progs (incidentally a lot of these seem to crop up on Dell machines, especially Notebooks).
(It fixed my issue with Premiere Pro CS4 - GeForce GT 555M on Win 7 Ultimate 64-bit, Dell XPSL702X).
It's posted on http://forum-archive.developer.nvidia.com/index.php?showtopic=5331&st=40 (look for the last post, No 50) as follows:
THIS FIX APPEARS TO WORK...found on an Adobe forum
"This issue led me to this fix: go to NVIDIA Control Panel --> Manage 3D Settings --> Global Settings, and switch "Power Management Mode" to "Prefer Maximum Performance" (the default "Adaptive" setting seemed to be the culprit). And that's it! The key here is changing the "Global" setting, as my individual programs were already set to "Prefer Maximum Performance." I can cause the error to reoccur by changing back to "Adaptive."
Otherwise lots more ideas on this site: http://www.instructables.com/id/How-to-Fix...Nvlddmkm-Error/
My PC has been running for 2 days now. I only put the top fix in for now. Feel happier I have more options if need be though.
Inserted from <http://forum-archive.developer.nvidia.com/index.php?showtopic=5331&st=40>
It worked for me

Latest Windows 7 on latest Mac OS X via Boot Camp = display driver problems

I've just done (with difficulty) a Windows 7 installation via Boot Camp on my hot new Mac Quad. But when I use Photoshop Elements for Windows-- the problem may occur with other Windows applications too but I haven't tried them yet-- I'm getting frequent blackouts and recoveries accompanied by the now slightly infuriating error message, "DISPLAY DRIVER STOPPED RESPONDING AND HAS RECOVERED. Display driver Radeon ATI family stopped responding and has successfully recovered."
I'm also getting frequent spotty screens which suggest compatability problems. What gives? Are other people troubled by this? Seems to me that this is a problem crying out for an Apple software fix. But other people may have an answer now.

Did you uppdate to bootcamp 3.1? To update to 3.1 you need to have installed 3.0 from your Snow Leopard install disc. What version of the display driver are you using.
See this thread that just started too.
http://discussions.apple.com/thread.jspa?threadID=2345677
3.1 solved the "display stopped responding" for me. Of course that introduced other issues.
Check your driver version and read here for other display issues fun...
http://discussions.apple.com/thread.jspa?threadID=2328909
http://discussions.apple.com/thread.jspa?threadID=2307311
http://discussions.apple.com/thread.jspa?threadID=2315531

Win XP Display driver for Satellite Pro P300 PSPCDE requested

After a clean XP installation I cannot install a proper display driver (Radeon 5145).
No driver is offered at Toshiba's website.
Is there any idea what I could do?
Please help - thank you!!

Hi
From my knowledge this graphic card was built in other Toshiba series too.
Satellite L500 PSLS9E
Satellite L505 PSLS9E
Satellite L550 PSLWSE
Satellite L555 PSLWSE
Satellite L630 PSK04E
Satellite L650 PSK1JE
Satellite L650D PSK1SE
Satellite Pro L500 PSLSAE
Satellite Pro L550 PSLWTE
So try the drivers released fort the series listed above.

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)!

"Your system display driver has caused Photoshop to Crash" MacBookPro June 2012 MacOS 10.7.4 Photosh

I am getting this error message when I launch Photoshop -- I just started getting it yesterday, August 28, 2012, when I tried to open a .tif image. Photoshop crashed. What has changed? I don't remember doing any updates to OS or to Photoshop. I am using Photoshop 12.0.4 x64 I've had the new MacBookPro June 2012 laptop for about a month, and Photoshop CS5 has been working fine. Now I'm getting this error message.
What can I do?
thank you!

It's entirely possible for the display driver file to get corrupted, though it's not common.
If you have Applejack, run it now. If you don't know what that is, skip this suggestion for now.
If you have Disk Warrior, or Cocktail or Onyx, run them now.
You might try booting off the install DVD and running Repair Disk with Apple's Disk Utility from there.
If it is indeed a corrupted kext file (the driver), then you can try running the 10.7.4 Combo Update over your existing OS install of that same version. That gives you fresh files as needed.
If none of that works, then you are looking at having to do an Archive and Install of the OS from the DVD, which will put you at 10.7.0, so you'd have to run the 10.7.4 Combo Update again to get you to where you are now (OS version wise).

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

Probook 6560b does not recognize my SSD

hi, i recently purchased a hp probook 6560b and wanted to give it an upgrade by replacing the standard 500gb 7200rpm hdd with a 120gb force gt ssd. but the notebook doesn't recognize the ssd at all, it says no drive is installed. the notebook has the latest bios available and the ssd has the most recent firmware. i know the ssd isn't defective because it works just fine in my desktop pc. hopefully one of you guys can help me out. thanks in advance.

############################################################ Update from January / 2012 # to everyone reading this and having the same issue:# There is a BIOS update F.22 available that fixes the recognition problem! ## Sata-III speeds are still not usable, but it is a big step forward. See page5 and onwards.########################################################### Hello fellow 6560b owners,I decided to enter this support forum to inform you of an important correlation concerning the SSD-Problem I observed: Every non-recognizable SSD-drive mentioned here had a native SATA-III (6Gb/s) Interface.  Every working SSD* had a native Sata-II or Sata-I interface.(*exception: the Crucial M4 mentioned by Slym, which seems to be recognized, but fails on system-level none the less. That does not count as 'working'.) The correlation to recognizion/Sata-II dawned on me after my 6560b did not recognize a brand new Kingston Hyper-X 120GB (Sata-III), but did correctly recognize an OCZ 180GB Agility 2 (Sata-II), which is almost identical to the OCZ Vertex 2/LE. The OCZ drive worked without problems until this week, when it suddently failed without warning. Totally bricked, all data lost. OCZ is aware of that problem, the forums are full of it, but they obviously don't want to start a recall. (Corsair did that with their failed Force3-Series, as well as Intel should do with their 310-Series repeatedly reverting to 8M size.) Which means, I'm back to zero and have to find a new drive that is reliable and recognized in the 6560b. For any SSD-user out there: backups will save you a ton of frustration. Most mayor manufacturers had serious problems with their SSDs dying, so be warned. Some details about my machine: new 6560b, 3 months old (as was the OCZ drive), HW 65 B3 stepping.(->no Intel Sata-chipset failure possible.) Search for explanation / reasons to the 6560b's SSD-problemHWinfo reports 2 Sata-III Ports, which I suppose are those on the main drive slot and the optical drive.The HW 65 as well as the QB67 (which both seem to be very identical according to wikipedia) both reportedly support 2 SATA-III-Ports, which were not affected in the B2-stepping-Sata-II-failure-thing that hit Intel in Jan/Feb 2011.So why should a Sata-III-link from a Sata-III-capable mainboard to a Sata-III-capable drive not work, but a sata-II does?And why can't the Sata-III drives just revert to Sata-II capabilities and work slower, but recogizable? general issues that I can think of:
1) hardware/software-based problem concerning the chipset improbable after that sata-II-issue. I assume they checked everything, and as most Sata-III drives are SSDs, they must have tested our models as well. Oh, and other Sandy-Bridge-notebooks accept Sata-III just fine, don't they?
remaining possibility: the B2-bug-aftermath produced this Sata-III-bug in the 6560b's configuration. That may be a hint to why the Sata-III Corsair M4 worked for the user Switched2HP and his B2-stepping-board, but similar M4-Corsair-SSDs did not work in B3-stepping-6560b notebooks. I'm not convinced of this explanation, though, as Switched2HP had also had problems with the Kingston-HyperX Sata-III drives. Important question @Switched2HP: did you test the Kingston Hyper-X in the same B2-stepping laptop the M4 runs fine in?
2) hardware/software-problem on the SSD sideWith us trying almost every Sata-III drive out there? Which work fine on other Chipsets & notebooks? Almost impossible..
not improbable cause no. 3:- hardware-problem on the electrical link side [eg. bad connectors/cables which prevent Sata-III from working, while not allowing downwards compatibility to Sata-II to jump in] this problem would IMHO only be fixable with complete replacement of the mainboard probable cause no. 4:- bios/HP-hardware-software-based problem concerning the chipset  eg. it's HPs fault because they deactivated/bricked something. See point 1) for B2-stepping-aftermath-scenario.
IMHO quite possible. HP would earn a ton of respect if they manage to solve that problem with a firmware update.  As the 6560b was built to be upgraded in a few minutes, an issue prohibiting modern SSDs and HDDs to work is a complete deal-breaker. As we, the users, have no access to the deeper configuration options, hardware-level-logs or even just knowledge about the inner workings of our chipsets, this would be the perfect time of some expert from HP to join in this thread, which is running for over 3 months now. I'm sorry guys from HP, but this is a serious problem, as soon there will only be Sata-III drives left, so I'm not doing this for fun. The HP Probook is not just any cheap throwaway-laptop.

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.

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?

Photoshop CS6 unable to use due to display driver (Intel) problem

Hi
I am experiencing problems using Photoshop CS6 (not extended version). I have recently installed Design standard and I'm not having this problem with Illustrator.
Each time I run PS, I receive a pop up with "display driver Intel HD graphics drivers for Windows 8(R) stopped responding and has successfully been recovered". PS opens but I cannot use it and I have to force end task in task manager.
I have an Asus Laptop (i7) with Windows 8.1, graphics card Intel HD 4400, it also has an NVIDA Geoforce GT 740M graphic card.
so far:
I have installed the latest driver from Intel (10.18.10.3345).
I have re-booted in Safe Mode and can open PS - I receive the message "Photoshop has encountered a problem with the display driver, and has temporarily disabled enhancements which use the graphics hardware". I can use PS in safe mode. I then re-boot and can use PS normally, however after another re-boot or awakening from sleep the problem reappears.
I have tried switching to 'Basic' or "Normal' in the advanced settings. The problem occurs again.
I connect this laptop by VGA to an external Dell monitor, however it does not just happen when connected to the external.
Any help in resolving this would be very much appreciated!
Here is my help>system info log (retrieved when in safe mode after the warning message) :
Adobe Photoshop Version: 13.0.1 (13.0.1.3 20131024.r.34 2013/10/24:21:00:00) x64
Operating System: Windows NT
Version: 6.3
System architecture: Intel CPU Family:6, Model:5, Stepping:1 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 2
Logical processor count: 4
Processor speed: 2394 MHz
Built-in memory: 8075 MB
Free memory: 6625 MB
Memory available to Photoshop: 7128 MB
Memory used by Photoshop: 60 %
Image tile size: 128K
Image cache levels: 4
The GPU Sniffer crashed on 2014-02-16 at 13:31:01
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 768, right: 1366
No video card detected
Serial number:
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Laura\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
Startup, 372.3G, 316.8G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/06/05-15:16:32   66.507768   66.507768
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/06/26-12:17:19   4.0.95   66.510504
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1654
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   6,0,29,0
   AGM.dll   AGM 2012/06/05-15:16:32   66.507768   66.507768
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/06/05-15:16:32   66.507768   66.507768
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/06/05-15:16:32   66.507768   66.507768
   BIBUtils.dll   BIBUtils 2012/06/05-15:16:32   66.507768   66.507768
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/06/05-15:16:32   66.507768   66.507768
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0.1 (13.0.1.3 x001)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 8.3
   Camera Raw Filter 8.3
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0.1 (13.0.1.3 x001)
   Clouds 13.0.1 (13.0.1.3 x001)
   Collada 13.0.1 (13.0.1.3 x001)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0.1 (13.0.1.3 x001)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Difference Clouds 13.0.1 (13.0.1.3 x001)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0.1 (13.0.1.3 x001)
   Embed Watermark 4.0
   Extrude 13.0
   FastCore Routines 13.0.1 (13.0.1.3 x001)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0.1 (13.0.1.3 x001)
   Measurement Core 13.0.1 (13.0.1.3 x001)
   Mezzotint 13.0
   MMXCore Routines 13.0.1 (13.0.1.3 x001)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0.1 (13.0.1.3 x001)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0.1 (13.0.1.3 x001)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0.1 (13.0.1.3 x001)
   Photocopy 13.0
   Photoshop 3D Engine 13.0.1 (13.0.1.3 x001)
   Picture Package Filter 13.0.1 (13.0.1.3 x001)
   Pinch 13.0
   Pixar 13.0.1 (13.0.1.3 x001)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0.1 (13.0.1.3 x001)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0.1 (13.0.1.3 x001)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0.1
   Shear 13.0
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0.1 (13.0.1.3 x001)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Sumi-e 13.0
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   Underpainting 13.0
   Vanishing Point 13.0
   Variations 13.0.1 (13.0.1.3 x001)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   WIA Support 13.0.1 (13.0.1.3 x001)
   Wind 13.0
   Wireless Bitmap 13.0.1 (13.0.1.3 x001)
   ZigZag 13.0
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE
thanks, Laura

thanks for your reply.
This is because PS turned off the GPU when I opened it in safe mode.
When I can access PS normally, both cards are recognised:
Adobe Photoshop Version: 13.0.1 (13.0.1.3 20131024.r.34 2013/10/24:21:00:00) x64
Operating System: Windows NT
Version: 6.2
System architecture: Intel CPU Family:6, Model:5, Stepping:1 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 2
Logical processor count: 4
Processor speed: 2394 MHz
Built-in memory: 8075 MB
Free memory: 5594 MB
Memory available to Photoshop: 7106 MB
Memory used by Photoshop: 60 %
Image tile size: 128K
Image cache levels: 4
The GPU Sniffer crashed on 2014-02-16 at 13:31:01
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: Intel
Video Card Renderer: Intel(R) HD Graphics 4400
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 768, right: 1366
Video Card Number: 2
Video Card: Intel(R) HD Graphics Family
OpenCL Unavailable
Driver Version: 10.18.10.3345
Driver Date: 20131031000000.000000-000
Video Card Driver: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32
Video Mode: 1366 x 768 x 4294967296 colors
Video Card Caption: Intel(R) HD Graphics Family
Video Card Memory: 2048 MB
Video Rect Texture Size: 16384
Video Card Number: 1
Video Card: NVIDIA GeForce GT 740M
OpenCL Unavailable
Driver Version: 9.18.13.3165
Driver Date: 20131023000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode:
Video Card Caption: NVIDIA GeForce GT 740M
Video Card Memory: 2048 MB
is uninstalling the graphics card the only fix for this? I'm reluctant to try this, and cause more problems..

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

Photoshop GPU and Yoga 2 Pro Display Driver

When I first bought my Yoga 2 Pro, Photoshop’s latest versions (CC and CS6) ran perfectly with their Graphics Processor (aka GPU aka Intel HD Graphics 4400) enabled. However, after an automated update that I didn’t notice, I receive a “display driver stopped working and recovered” message when I open Photoshop. Then I receive an “insufficient memory” message inside Photoshop and Photoshop’s Graphics Processor is disabled. Inside Control Panel-Devices, the Display Driver roll back option is disabled. So I download the latest driver from Lenovo (Intel Video Driver for Windows 8.1 64-bit - Lenovo Yoga 2 Pro, version 10.18.10.3304, ivga136w8164.exe), install it, and Photoshop works with no error messages and its Graphics Processor automatically enabled. A day later, when I open Photoshop I get the same errors. So I reinstall the 3304 driver, Photoshop works fine, and a day or two later the same cycle repeats.
Anyone have a solution, please?
Solved!
Go to Solution.

hi
The guide I Posted Above,
This step stops the updates for the drivers only.
if this is what you did then that's I think is the best way if the current update of the driver is causing you issues.
Spoiler (Highlight to read)
Open the Control Panel
Select System and Maintenance
Select System
Now click Advanced system settings in the left-hand panel (if the UAC is turned on, click Continue to proceed)
Next, click the Hardware tab
Click the Windows Update Driver Settings button
Now you need to select the driver update option you want to use.
The default option will automatically check for drivers and update them. To disable automatic driver updates in Vista, select either the second or third option and click OK.
Open the Control Panel
Select System and Maintenance
Select System
Now click Advanced system settings in the left-hand panel (if the UAC is turned on, click Continue to proceed)
Next, click the Hardware tab
Click the Windows Update Driver Settings button
Now you need to select the driver update option you want to use.The default option will automatically check for drivers and update them. To disable automatic driver updates in Vista, select either the second or third option and click OK.
Regards
Solid Cruver
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

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?).

Multiple Adobe Applications "Missing" Display Driver

I am now using the following system configuration:
2 NVIDIA GeForce GTX 970s
5960X CPU
2 850 Pro SSD drives
32 GB DDR4 RAM
Windows 8.1 Pro
A list of my currently installed applications can be seen here:
1
I am having problems with 4 utterly crucial applications:
Photoshop, Premiere Pro, SpeedGrade and After Effects. They were just installed last night; they are the most recent version.
Here are the error messages that I am receiving for each program:
Photoshop "detected an error in [my] display driver" and won't allow me to use any 3D options or even the either of the graphics cards.
2
Premiere Pro won't even enter the workspace and gives me the following error message: "Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again." After this message it crashes.
34
SpeedGrade won't even launch whenever I try to open it. The cursor begins to spin as if it's doing something and then quits. I've tried opening it several times, even with Administrator Permissions, but to no avail. It just won't open at all and doesn't even bring up the entry loading screen.
After Effects is a whole heap of trouble, with three error messages coming up:
Firstly, "After Effects crashed previously attempting to initialize OpenGL. Consult the manufacturer of your graphics card for a compatible OpenGL driver."
5 Which is followed by:6 and then continued by: 7
After this, After Effects completely crashes and refuses to open (giving the same error message as seen in picture 4).
I've got the crazy notion that it has something to do with my video card drivers (sarcasm). Every message seems to have something to do with the graphics card, and SpeedGrade is the only thing that I can't be sure of since it doesn't even begin to start up whenever I try to open it.
However, here's the catch; I have no idea what. Just now, I manually uninstalled all of my graphics card drivers and did a clean re-install of the newest NVIDIA GTX 970 drivers from here: NVIDIA DRIVERS GeForce Game Ready Driver WHQL
So I have the most updated drivers and most updated adobe software, and certainly have hardware that it's capable of using. I'm not sure what the issue is here.
Another thing that I would like to mention is that, when opening the NVIDIA control panel, I only have the following options:
89
I recall that, on other, older computers that I've used with NVIDIA cards and the NVIDIA control panel, there were many other otptions, such as the ability to control SLI and change 3D settings and whatnot. None of that exists here, and I can't even enable stereoscopic 3D. In fact, whenever I try to change anything in my extremely limited control panel, I just get the message shown in picture 9: "To use this feature, set the color depth to at least 32-bit."
Alright, to sum it all up once and for all:
I'm assuming the problem that all of these applications are having has something to do with the NVIDIA GTX 970 cards
Even with the most updated software, the problem still exists.
A list of all my programs was given in case any of them might, possibly, be interfering with Adobe.
This computer is brand-new, basically, and the SSD drives are all quite empty.
I am running 4 displays, 3 of which on the same GTX 970 and another using this product: JUA310 USB 3.0 VGA Display Adapter
Don't ask why I'm using that J5create product mentioned above, but I'll tell you that I have a feeling that it could, possibly, be interfering considering that it is basically its own graphics driver. I have means to support this display without using it, however, so please mention if I need to stop using it for troubleshooting or because it could be the source of the problems. Also, the other adobe applications seem to be working fine at the moment, but if they do ever have any problems, I might assume them to be caused by the same thing that's messing up all of these programs.
So what should I do?!?

I also forgot to mention a few things:
Windows 8.1 has successfully updated to its most recent version and installed all updates.
I'm using an MSI X99 Gaming 7 Motherboard.
It’s very urgent that I get these programs to work ASAP

Bluescreen in ProBook 6560b caused by display driver Radeon HD 6470M

Similar Messages

Maybe you are looking for