Nvlddmkm stopped responding is getting VERY OLD...

[haloeighty8]

']6 passes of Memtest is a joke. Run 25 passes and provide us with results. Last time I got errors in 17th pass for example :(

Hmm.. according to Corsair's tech support anything over 3 passes is overkill, 1-2 passes is fine. 3 they consider the ram in working order.

[LORD-eX-Bu]

I just ran nine passes for the hell of it... 3 for each stick and then three with both on the system... almost 400 errors on one stick :eek2:

****ing corsair, if I send my memory for RMA they'll replace my Micron D9 modules with crap quimoda chips and I'll probably have to wait a month for it since they apparently ran out of 8500C5D memory and refuse to give better memory in return even though they state that they do in their warranty information.

[haloeighty8]

I just ran nine passes for the hell of it... 3 for each stick and then three with both on the system... almost 400 errors on one stick :eek2:

****ing corsair, if I send my memory for RMA they'll replace my Micron D9 modules with crap quimoda chips and I'll probably have to wait a month for it since they apparently ran out of 8500C5D memory and refuse to give better memory in return even though they state that they do in their warranty information.

ouch! that sucks.. when I had to have them replace some ram they took forever. They always seem to be backordered on everything!

[$n][pErMan]

anyone... link for memtest? :)

[LORD-eX-Bu]

memtest.org

[$n][pErMan]

Interesting find.... in WiC on Vista 64-bit I was getting the damn stopped responding BS on a regular basis. Out of curiosity... I disabled the DX10 rendering check box in the game... and now for about a week solid I have not had the error once in WiC in Vista 64-bit. If I get a chance... I might try and uncheck the "Preview DX10" box in FSX and see if that does anything. Not sure if its DX10 related, but it WiC case it seems to be. Note I can play Crysis and Bioshock in DX10 and never get the error.....

[Lfctony]

[pErMan']Interesting find.... in WiC on Vista 64-bit I was getting the damn stopped responding BS on a regular basis. Out of curiosity... I disabled the DX10 rendering check box in the game... and now for about a week solid I have not had the error once in WiC in Vista 64-bit. If I get a chance... I might try and uncheck the "Preview DX10" box in FSX and see if that does anything. Not sure if its DX10 related, but it WiC case it seems to be. Note I can play Crysis and Bioshock in DX10 and never get the error.....

I've discovered that ages ago with my setup. It only happens in DX10 games. Never in Dx9 games. WiC, Crysis, Universe at War. The only game that doesn't suffer from it is Bioshock.

[slaWter]

[pErMan']Interesting find.... in WiC on Vista 64-bit I was getting the damn stopped responding BS on a regular basis. Out of curiosity... I disabled the DX10 rendering check box in the game... and now for about a week solid I have not had the error once in WiC in Vista 64-bit. If I get a chance... I might try and uncheck the "Preview DX10" box in FSX and see if that does anything. Not sure if its DX10 related, but it WiC case it seems to be. Note I can play Crysis and Bioshock in DX10 and never get the error.....

Thanks for the info. What's more important for the frame rate boost that comes with SP2/Acceleration, DX10 mode or general SP2 optimizations? I don't need the DX10 effects because FEX looks much better but I need the performance boost ;)

EDIT:
Just did a 20min test with DX9 in the Vegas and Hawaii area. Good thing is the game didn't crash but unfortunately the DX10 Preview mode is responsible for the nice performance boost after installing Acceleration. So I have to adjust a few scenery/autogen settings to avoid slowdowns to 12FPS :(

[$n][pErMan]

Thanks for the info. What's more important for the frame rate boost that comes with SP2/Acceleration, DX10 mode or general SP2 optimizations? I don't need the DX10 effects because FEX looks much better but I need the performance boost ;)

EDIT:
Just did a 20min test with DX9 in the Vegas and Hawaii area. Good thing is the game didn't crash but unfortunately the DX10 Preview mode is responsible for the nice performance boost after installing Acceleration. So I have to adjust a few scenery/autogen settings to avoid slowdowns to 12FPS :(
Question is though.... did you get the stopped responding error or were you able to play for an extended amount of time?? I can live without the DX10 mode on FSX... it does not appear to add any graphical features to that game and it ran smooth for me before anyway.

Also, Bioshock worked perfect for me but Crysis also did as well. So far WiC and FSX are the only games I get the damn error in... and it looks like I have fixed it for WiC so now its just down to FSX. Oddly too.. only in Vista 64-bit... never had this issue in 32-bit :( I might run some tests on FSX today by disabling the DX10 preview and see if that fixes it.

[slaWter]

[pErMan']Question is though.... did you get the stopped responding error or were you able to play for an extended amount of time?? I can live without the DX10 mode on FSX... it does not appear to add any graphical features to that game and it ran smooth for me before anyway.

Also, Bioshock worked perfect for me but Crysis also did as well. So far WiC and FSX are the only games I get the damn error in... and it looks like I have fixed it for WiC so now its just down to FSX. Oddly too.. only in Vista 64-bit... never had this issue in 32-bit :( I might run some tests on FSX today by disabling the DX10 preview and see if that fixes it.

Just did another ~20min flight in DX9 mode and it was stable. I don't have time for longer flights right now... But so far so good ;)

[$n][pErMan]

Well... FYI... I was just able to fly for about 45min without a single stopped responding BS error ;) Sucks that I cant use the DX10 mode but I suppose being able to fly is better than not being able too. I'll keep you all posted and do some more testing :) I love how nVidia can't code for DX10... unless the issus is much bigger than nVidia's crappy drivers as apperently ATi has the same issue. Might be DX10 code related?

[LORD-eX-Bu]

I don't think it is DX10 related, I am using it fine here.

When I was having the same problems that you were I tried avoiding DX10 and it helped a little but over time the errors got worse.

Have you ran memtest yet?

[$n][pErMan]

I don't think it is DX10 related, I am using it fine here.

When I was having the same problems that you were I tried avoiding DX10 and it helped a little but over time the errors got worse.

Have you ran memtest yet?
Not yet... I might give that a run tomorrow. I dunno how that would be the cause though... I have plenty more games than FSX that push my computer to the max without any issues (I also never saw the error untill moving to 64-bit Vista from 32-bit)... I might give memtest a run though just out of curiosity. BTW... just got done with an hour and a half flight and not a single crash with that DX10 checkbox un-checked. I'll keep everyone posted.

[slaWter]

Thanks for the info. Looks good so far :)

[AdamK47]

I was testing out an overclock by running 3DMark06 demo in loop with my E8400 @ 4050MHz, eVGA 680i @ 450MHz and 4GB (4 x 1GB) Patriot PC6400 at 525MHz (1050 DDR) 5-5-5-15 @ 2.1V. I received the Nvlddmkm Stopped Responding error within 2 hours. I could have clocked the memory down, but I decided to replace the memory with 4GB (2 x 2GB) Corsair PC6400 @ 525MHz (1050 DDR) 5-4-4-12 @ 2.0V. Guess what? No more Nvlddmkm Stopped Responding error. It ran for 8 hours straight until I closed it.

The reason why I bring this up is for those who insist the problem is with nVidia and their drivers. It's not nVidia, it's that the driver is very sensitive to hardware instability and can replicate errors much more readily than most software can. If you get this error, don't be so ready to point your finger at nVidia.

[hell_of_doom227]

Guys motherboard and ram nothing has to do with this error. Simply Nvidia blows at forceware driver sector.

[AdamK47]

Guys motherboard and ram nothing has to do with this error. Simply Nvidia blows at forceware driver sector.

I've been able to reproduce it consistantly.

[hell_of_doom227]

I've been able to reproduce it consistantly.

It's a random thing...

[AdamK47]

It's a random thing...

I've been able to reproduce it consistantly.

[Lfctony]

I've been able to reproduce it consistantly.

Same here. In WiC and Universe at War it happens within minutes of running in DX10 mode. Last time in WiC it was around 5 minutes, in UaW always before the tutorial ended...

[mezkal]

Some people don't seem to get the message. My two cents (for what it's worth) is that DX10 shader processing runs at much higher precision, therefore probably using more memory, than DX9c does. So it could be that DX10 games use much more of the pooled memory resource (ie more system RAM) and the error could be indicative of faulty RAM and/or issues with Vista x64's memory addressing.

[Lfctony]

Some people don't seem to get the message. My two cents (for what it's worth) is that DX10 shader processing runs at much higher precision, therefore probably using more memory, than DX9c does. So it could be that DX10 games use much more of the pooled memory resource (ie more system RAM) and the error could be indicative of faulty RAM and/or issues with Vista x64's memory addressing.

That doesn't explain why it only happens in SOME dx10 games. And one game that doesn't suffer from it is Crysis, which has rather intensive shaders whether in DX9 or 10. What I said in the past though, is that ATI is having exactly the same problem, thus indicating a Vista/DX10 problem.

[mezkal]

Bioshock is neither intensive in terms of textures or shaders by comparison with newer titles. You can easily find whole swathes of screens showing low res bump maps and equally blocky textures throughout the game. Further to this the DX10 support it needs is only for water and alpha processing.

Crysis is an intensive game so it's not as simple to pin down.

My explanation discusses both driver and host OS issues as I believe it's likely to be a combination of both. DX10 is new territory and so is Vista's memory management system, let alone Vista itself.

[slaWter]

I also have a feeling that this problem (in FSX) could be RAM related. I didn't get the error a few months ago with 2x1GB but I get it now with 4x1GB.

[[HeX]]

That problem can be hardware releated. First thing is to check hardware stability (memtest, prime95). If the hardware is fine then there is an problem with OS and/or drivers. In my case for example I was stable in Windows XP 64-bit and I could even overclock my GPU to 628/1454/2000. Not anymore in Vista :( I'm stable in Vista but my GPU has to be at stock settings otherwise it will give me Nvlddmkm message :( Moreover I was getting that error with some versions of Nvidia Forceware drivers with GPU at stock settings.