Skip to main content

Display driver nvlddmkm stopped responding and has successfully recovered

I've been getting this message in the event log lately, and this happes when I play games on my computer (NVIDIA 8800 GT):
Display driver nvlddmkm stopped responding and has successfully recovered
Lots of forumposts on the internet suggest it's a defect card, old drivers or too small PSU. My findings for my problem was that the fan on the video card actually had malfunctioned. So it was partly a defect card, but just the fan. Which can easily be replaced. Of you don't want to open up your case at first, you could try to check out the temperature of the GPU. I used HWiNFO32. Run it in "Sensor mode" only, and you should find the temperatures at the bottom of the status list you get. Here my 8800GT was hovering around 97 degrees C while going as high as 138 degrees C while playing before it borked.

New fan - problem fixed :)
Labels:

Comments

Post a Comment

Popular posts from this blog

How to configure multiple VLANs on QNAP TS-869U

It's unbelievable that QNAP still doesn't support multiple VLANs on a single bond0 interface via GUI when they now just released the QTS v4.1.0 NAS Operation System for QNAP. The underlying Linux OS (QTS) does support it, and there should at least not be any problems with Intel chipsets. Some are reporting problems with Marvell.. but I haven't tried. I wanted to use the QNAP as a iSCSI storage for my LAB using a second interface while having full redundancy and get max bandwith (2x1GbE) for my ESXi hosts, and I didn't want that interface routed. At the same time I of course need the possibility to manage the QNAP system via the main interface, which is routed. This CLI "hack" will at configure the QNAP for a second VLAN interface that will be persistent during reboots. It's not been verified that it works after an upgrade of the firmware, but I presumed it will. To get this to work I presume you already have the following working: Network onfigured...
5 comments
Read more

Typing @-character is delayed with Asus GPU TweakII and scandinavian keyboard layout (at least norwegian)

After I reinstalled my computer a while back, I noticed that one characters (the @-sign) had a long delay before showing up after I had hit the key on the keyboard. And I noticed it wasn't every time I had turned on my computer it was "slow". Imagine how frustrating it is to write your email address in a normal pace on the keyboard, just to find it spelled firstname1977gma@il.com instead of firstname1977@gmail.com ? Hitting ' @ 'had 0.5 to 1 second delay before it showed up on my screen, while the characters after displayed instantly. The computer in question runs english Windows 10 x64 with an NVidia GTX1070 card from Asus, and using a norwegian/scandinavian keyboard (Logitech G710+, but model isn't the problem). Throubleshooting led me to narrow the problem down to my ASUS GPU TweakII v1.4.0.8 (older version probably have the same problems). When I started the program, which was set to auto-start, I was suddenly no able to type @ as fast and often as ...
Post a Comment
Read more

Upgrade Brocade VDX from USB

Brocade VDX NOS 2.0.x and NOS 2.1.x admin guide and cli ref says this is the command to update the NOS firmware on VDX: firmware download usb directory firmware/nos2.1.0 It's not. Drop the 'firmware/' in the path. Correct and working (from 2.0.0 to 2.1.0 at least) is: firmware download usb directory nos2.1.0 I believe you need to have a Brocade USB. Perhaps it works with other sticks with the same folder layout, I don't know. And by the way, there are no release.plist file in the root of the nos2.1.0 folder. Brocade USB folder layout - one folder 'brocade' in the root and four subfolders: brocade/ config firmware firmwarekey support Updated 20120809.
4 comments
Read more