11-13-2008 06:18 AM
11-13-2008 06:27 AM
Yesterday I update my Bios with system update (I have W500) and after restart I got message the new hardver is found and sucesfully installed. It was Ati v5700 . I'm working today for 5 hour now on docking and I did not have blue screen yet (I had i black screen for 5 sec). I never tried that staff with resume or something because I has blue screen every day at least once when I work with 2 monitors connected to docking).
I let you know next time I face blue screen .
11-14-2008 06:37 AM - edited 11-25-2008 12:20 PM
ATI informed me that Lenovo is responsible to handle my support request...
So, we still don't know whether there is a solution or not.
Ok, quick update. I've downloaded ATI's 08.11 drivers. The ATI Catalyst install manager thought that my display drivers were current, while the Windows device manager reported driver version 08.09. I then installed the drivers manually. The "amdkmdag.sys" driver has now the version 7.01.01.838. Though, the quick "let the system go to standby"-test resulted as before in a amdkmdap crash.
And there seem to be other ATI Catalyst users having this problem with version 08.11. See here.
11-18-2008 04:59 AM
I have problems with turning the computer off while docked then while booting pluging into a external projector. If CCC isn't fully loaded Windows will load it's own graphic manager and total disable CCC from loading. Yet onces you close the graphic popup you are unable to find it in the Controll panal but only able to click the ATI Icon which loads a frozen screen. A reboot is required to change any graphic settings. Happens once every 10 times I say.
Also, amdkmdap still every onces in a while when on battery power hooked to a projector will error out about 5 times in a row until it blue screens. I have a good 20 second warning yet since the 1.9 bios upgrade it has only errored out onces without a blue screen so the problem is getting better still worth reporting.
11-21-2008 11:34 AM
I have the T400 with the same problem, for now I am using the Intel instead of ATI.
I can't believe I paid more the ATI and can't even use it.
Lenovo better come up with a solution ASAP.
You think we can return the unit if this problem is not solved soon.
11-24-2008 11:43 AM
After standby wakeup, it looks fine for about 5 seconds, then freaks out and switches to 640x480. In addition, I seem unable to set my 2nd monitor resolution to anything other than 640x480. If I try, it just flips it back. I'll try the driver updates.
I attempted updating the drivers last night and am pretty sure I was on the right page. Radeon HD 3400 series, but after the exe ran, it errored out with "We found no drivers for your hardware configuration".
11-25-2008 11:44 AM
I had the underlying problem when DELL external monitor was connected extending a desktop (Vista Ultimate, W500). Many times during a day Vista has been crashing to BSOD.
The last time it happened today in the morning. After installing latest updates for Hotkey driver (http://www-307.ibm.com/pc/support/site.wss/documen
11-25-2008 12:15 PM - edited 11-28-2008 03:29 AM
I've also updated the Hotkey driver and can still have the wrong display resolution after the system resumes from standby.
In my case, I've also updated the system bios to version 1.19 and the Ethernet and WLAN drivers.
Update: While the display resolution of the Windows login prompt after the system resumes from standby is still incorrect (something out of proportion; I make some photos if required), I do not get the Windows notification that amdkmdap has been restored. So, the crash seems to be gone. What remains is the wrong display resolution after standby and the display flickering for 20 seconds until it stabilizes. Maybe the presentation direction is trying to change the resolution?
11-30-2008 02:44 AM - edited 12-01-2008 12:14 AM
I had another (non-BSOD provoking) amdkmdap driver crash, this time running on the internal notebook display only.
Update: Another (non-BSOD provoking) amdkmdap driver crash, this time running with the external monitor again after resume from hibernation. So, my trend is: crashes are somewhat less often but still there.