Nvlddmkm stopped responding is getting VERY OLD...

[ZoLoco]

:thumbdwn: Sigh, so nothing works, eh? Ive tried changing ram, safe mode xdc clean, virus scanner off and almost all tips on the net. Still the same error. And even sendt reports on the latest driver when it was in beta stage.
Still they release it with even worse error rate. When we scroll our menus at start line bug??? Talk about service... :headexplode:

What changes have been made since 158.xx?? Now i cant play my favorite game Armed Assault. All i get is black loading screen. The producers of the game just keep telling me its not made for vista.. Doh!! :(

Also getting a not so usefull tip on the net regarding this error. Dont use Vista they say.. Haha. Using XP then, hah, then the error comes as this:
Nv4_disp.dll has stopped responding.. Rofl... NOT :thumbdwn: :thumbdwn:

How about some fixes soon??? Eh??

Very old indeed, i say.. VERY O L D indeed!! :( :(



Graarrghh!!!!

[Amuro]

It happens in window every few minutes. But try and play a game and all hell brakes loose. It will happen like every 2 seconds and makes it totally unplayable. Even trying to access the menu is almost impossible when in 3d mode. But like I said it is only with the 163.11 drivers. I have never had this issue until now.
I'm experiencing this problem in windows desktop (haven't tried playing games yet) even with the 162.22 official drivers, so it's not just the 163.11.

[Slammin]

Try this. Create two reg files. Name one TdrFixON.reg and put this in the file:

Windows Registry Editor Version 5.00
; ##################
; Created By UserX For Public Use 2007
; ##################
;
; TDR Timout Delay and Debug Fix
; TdrDelay - Effectively the timeout threshold in seconds. Default value is (2).
; TdrDebugMode - The debugging-related behavior of the TDR process. (3) = recovers even if some recovery conditions are not met.
;
; ##################
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers]
"TdrLevel"=dword:00000000
"TdrDelay"=dword:00000010
"TdrDdiDelay"=dword:00000005
"TdrDebugMode"=dword:00000003


Now, to undo the change if you want, create another file called TdrRegFixOFF.reg and put this in it:

Windows Registry Editor Version 5.00
; ##################
; Created By UserX For Public Use 2007
; ##################
;
; TDR Timout Delay and Debug Restore
; TdrDelay - Effectively the timeout threshold in seconds. Default value is (2).
; TdrDebugMode - The debugging-related behavior of the TDR process. (3) = recovers even if some recovery conditions are not met.
;
; ##################
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\GraphicsDrivers]
"TdrLevel"=-
"TdrDelay"=-
"TdrDdiDelay"=-
"TdrDebugMode"=-

This, and disabling Desktop Composistion (Aero) seems to work for most everyone, or at least help quite a bit.

Good luck, or drop back to 158.45 until a better fix comes out, or of course disable Sli too, but I'm not ever planning on disabling Sli.

[MaUiLoCaL]

I was having serious issues at one point with this. The instant I installed a new case fan, and lowered my CPU clock speeds this problem was fixed. It has never come back since.:D

[JimBobb]

Problem here 2x8800GTX@SLI crashed with Aero enabled...Aero off working
Sure a Driverproblem!

[Skinner]

Didnt know that Hl2 ep2 was out ??

Oops, that has te be ep 1.

I can confirm Armed Assault won't work (in Vista 64) anymore :(

[alucard_x]

I was getting errors in ET:QW beta2 with 162.22. I went to 158.45 (or whatever it is) and I haven't had any issues in 2 nights so far.

I don't use SLI, aside from that, what is the differences between the 158.xx and 16x.xx?

[vmsein]

I was getting errors in ET:QW beta2 with 162.22. I went to 158.45 (or whatever it is) and I haven't had any issues in 2 nights so far.

I don't use SLI, aside from that, what is the differences between the 158.xx and 16x.xx?
DirectX 10 support.

[HYBRID]

:thumbdwn: Sigh, so nothing works, eh? Ive tried changing ram, safe mode xdc clean, virus scanner off and almost all tips on the net. Still the same error. And even sendt reports on the latest driver when it was in beta stage.
Still they release it with even worse error rate. When we scroll our menus at start line bug??? Talk about service... :headexplode:

What changes have been made since 158.xx?? Now i cant play my favorite game Armed Assault. All i get is black loading screen. The producers of the game just keep telling me its not made for vista.. Doh!! :(

Also getting a not so usefull tip on the net regarding this error. Dont use Vista they say.. Haha. Using XP then, hah, then the error comes as this:
Nv4_disp.dll has stopped responding.. Rofl... NOT :thumbdwn: :thumbdwn:

How about some fixes soon??? Eh??

Very old indeed, i say.. VERY O L D indeed!! :( :(



Graarrghh!!!!


Same here nothing has helped I do a driver change maybe a few days go by and ban it rears it ugly head, but specific to one game ET which I still play alot.

I've been playing a little ETQwars and havent had it showup, but I play ET for hours one day all good next well.....This needs a fix period.

And no SLI here.

[alucard_x]

Same here nothing has helped I do a driver change maybe a few days go by and ban it rears it ugly head, but specific to one game ET which I still play alot.

I've been playing a little ETQwars and havent had it showup, but I play ET for hours one day all good next well.....This needs a fix period.

And no SLI here.

try 158.45

[Slammin]

Yup, that driver fixes it, but better yet:

http://www.nvnews.net/vbulletin/showthread.php?t=96906

Seems this problem may FINALLY be history.

So far, nothing I do, including enabling Aero causes this ugly error anymore.

Thanks, nVidia!

[vmsein]

Yup, that driver fixes it, but better yet:

http://www.nvnews.net/vbulletin/showthread.php?t=96906

Seems this problem may FINALLY be history.

So far, nothing I do, including enabling Aero causes this ugly error anymore.

Thanks, nVidia!
Now this is the really big news of this driver set if more people report in that this bug is finally gone.

[fasedww]

Now this is the really big news of this driver set if more people report in that this bug is finally gone.
Yep it's fixed

[gizmoy2k]

Another happy customer, Im unable to reproduce this error as i could do before :cool:

[ekovalsky]

I have also confirmed that 163.44 drivers finally fix the Vista Aero and DX10 SLI errors that have been present in all the earlier 16x.xx drivers. I can finally move on from 158.45 :)

Also ntune now allows direct fan control, eliminating the need to use Rivatuner.

[nmgn]

:captnkill: the best news of the year (nana2) lets party

[Muppet]

Yes yes yes. this is almost as good as an orgasm. Finaly drivers that don't go blahhhhhh. :) :captnkill:

[ZoLoco]

WOOT WOOT!!!! What r ye all talking about????? Finally fixed??? :thumbdwn:

NO!!! Had high hopes too for the new driver that arrived yesterday. Yes, i can finally scroll my programs at start menu without error.

BUT!!

When enabled the Vista Ultimate Dreamscene, BANG!! Graphic glitsh, then freeze and ERROR!!!!! NVLDDMKM HAS S T O P P E D RESPONDING !!!!!!!!

GRAAAARGHHHH!!!!!! :( :(

I bet if i put games on maximum itll surely ruin them too. I know dreamscene is not fully released proper yet. But aaargghhh!!!

Tried hotfixes on the net regarding SLI. Even when computer has been off, so no overheating.. Tried lesser ram, Driver cleaner, safe mode installation, and much more solution found on the net... What is the problem with this error? What is it?????? HELP!!!

Did nvidia just fix some stuff just for this new game Bioshock???
Can only nvidia do something when a big company has problems with the driver??
What about the consumers, the users, the buyers of their product????

BAH!!!
:thumbdwn: :thumbdwn:

[nmgn]

:( i think we have party to early
in lot of forms a problems starting again :thumbdwn:

no please lets us party (nana2) (nana2) (nana2) (nana2)
this must be true this must be working

[gizmoy2k]

Try playing any video or tv FULLSCREEN with sli and you wont get far until a crash,

Im glad Aero and games are better though, rarely watch media on my main pc :headexplode:

[DarkOneX]

Wow I can't believe peeps are still having this problem!? Mine did this with like the first 3 drivers that were out for Vista then quit on the 4th release then hasn't ever happened again. What do all of your systems have in common? Anybody gain any ground on the cause? I mean, it's not simply Vista or 8800's because that's what I got and has worked fine since getting past the initial Vista driver releases.

[DRen72]

Wow I can't believe peeps are still having this problem!? Mine did this with like the first 3 drivers that were out for Vista then quit on the 4th release then hasn't ever happened again. What do all of your systems have in common? Anybody gain any ground on the cause? I mean, it's not simply Vista or 8800's because that's what I got and has worked fine since getting past the initial Vista driver releases.Same here. I don't get it. I reboot my PC everyday and have noticed sometimes others don't. Could it be?

[JimBobb]

163.44 fixed this Problem for me with 2x8800GTX :)

[samtroy]

The new 163.44 driver fixed absolutely *nothing* for me!

Still the same 'stopped responding'-crashes in games, especially OpenGL ones.

Even installed my system completely new with all Hotfixes and latest drivers elsewhere...

Vista32, GA-P35-DS3R, D2D6600, 2GB, GF7950GT 512MB

:thumbdwn:

Solution: Back to XP for gaming!

[HYBRID]

Just curious most of us on these boards overclock our systems wheater it be processors, memory GPU.

But does this driver issue occur for some that do not overclock their Rigs just curious more than anything else, and lastly do folks with XP get this error or a similiar related erro or problem or is this just isolated to Vista Iam a little tired of it and my just dual boot?

thanks in advance.