Nvlddmkm stopped responding is getting VERY OLD...

[Badboy_12345]

Well I am getting the ****ty issues still and now it isnt as warm :thumbdwn:
I think now it started happening after I got 4gb ram and installed Vista x64

Its seriously pissing me off.

Ive tried taking out the ram that I put in again but it doesnt help at all.
And I wont be going back to vista 32-bit

Well its clear now that my next card will be ATI
4870x2 here I come

[$n][pErMan]

Well I am getting the ****ty issues still and now it isnt as warm :thumbdwn:
I think now it started happening after I got 4gb ram and installed Vista x64

Its seriously pissing me off.

Ive tried taking out the ram that I put in again but it doesnt help at all.
And I wont be going back to vista 32-bit

Well its clear now that my next card will be ATI
4870x2 here I come
Join the club! 32-Bit with 4GB no issues.... 64-bit 4GB... issues.

[Badboy_12345]

[pErMan;1749238']Join the club! 32-Bit with 4GB no issues.... 64-bit 4GB... issues.

And people say ATi has crap drivers :mad:

[Ninja Prime]

I just started having this problem too, ffs. I guess start trying random crap, unless theres some magical wonder driver to fix this now?

[Lfctony]

Well I am getting the ****ty issues still and now it isnt as warm :thumbdwn:
I think now it started happening after I got 4gb ram and installed Vista x64

Its seriously pissing me off.

Ive tried taking out the ram that I put in again but it doesnt help at all.
And I wont be going back to vista 32-bit

Well its clear now that my next card will be ATI
4870x2 here I come

Delusions, delusions...
http://www.google.com/search?hl=en&q=atikmdag+errors&btnG=Google+Search

[henrybravo]

Delusions, delusions...
http://www.google.com/search?hl=en&q=atikmdag+errors&btnG=Google+Search

While you're correct pointing out that a similar problem exists on ATI hardware, all that you're doing is showing the problem is significantly less frequent on ATI hardware versus nvidia. Using your little google tactic, if I search for "nvlddmkm errors" there are 14,900 hits. Your google search for "atikmdag errors" yields 3820 hits. That's a margin of nearly 4:1 of nvidia over ati. Not that I agree with your "the proof is in the google" method. Just pointing out that your google link that you have been repeatedly posting paints ATI in a better light which I think is contrary to your goal.

HB

[Lfctony]

The point is ATI cards still get it. To actually think this will be fixed simply by changing to an ATI card... Again, delusions... End of story. I get it when I overclock too much... Is that Nvidia's fault? I've also read about countless users who fixed it by increasing ram voltage, or RMAing their cards etc etc... It's not exclusive to Nvidia cards... That's my point. And no matter how much you twist it and try to change what I've said, it doesn't change the fact that changing to an ATI card to fix this problem without actually knowing what causes it, is plain stupid...

Thank you...

[henrybravo]

<snip>It's not exclusive to Nvidia cards... That's my point.<snip>
Understood. Thank you.

HB

[Muppet]

While you're correct pointing out that a similar problem exists on ATI hardware, all that you're doing is showing the problem is significantly less frequent on ATI hardware versus nvidia. Using your little google tactic, if I search for "nvlddmkm errors" there are 14,900 hits. Your google search for "atikmdag errors" yields 3820 hits. That's a margin of nearly 4:1 of nvidia over ati. Not that I agree with your "the proof is in the google" method. Just pointing out that your google link that you have been repeatedly posting paints ATI in a better light which I think is contrary to your goal.

HB
Well considering that Nvidia cards more than likely outsell ATI at least 4-1. I'd say it makes it about even.

[Badboy_12345]

The point is ATI cards still get it. To actually think this will be fixed simply by changing to an ATI card... Again, delusions... End of story. I get it when I overclock too much... Is that Nvidia's fault? I've also read about countless users who fixed it by increasing ram voltage, or RMAing their cards etc etc... It's not exclusive to Nvidia cards... That's my point. And no matter how much you twist it and try to change what I've said, it doesn't change the fact that changing to an ATI card to fix this problem without actually knowing what causes it, is plain stupid...

Thank you...

Cause = vista x64 nvidia drivers
You can also see by some drivers your getting less BSOD than others

easy isnt it :p

It works perfectly in Vista 32bit and XP

And I dont see a big thread on rage3d about thousends of people having the problem on their ATI cards.

[Lfctony]

Cause = vista x64 nvidia drivers
You can also see by some drivers your getting less BSOD than others

easy isnt it :p

It works perfectly in Vista 32bit and XP

And I dont see a big thread on rage3d about thousends of people having the problem on their ATI cards.

You're choosing to ignore the issue. My stable OVERCLOCKED system in WinXP x64 crashes in Vista x64. If I back down the overclocking, the system is also stable in Vista x64... How is that a fault of the Nvidia drivers? As I said from my previous post, the problem may very well be your system, even if it is stable in Vista 32 and XP... You hope that the problem is the Nvidia drivers, you don't know.

Yet you fail to grasp the simple, obvious signs. You installed 4GB of memory and the crashes began... But it's Nvidia's fault... It's been said many times that Vista stresses the memory subsystem more than Windows XP because of virtualisation. Thus a stable XP system might be unstable in Vista. Did you try backing down your overclocking? Did you try testing in Vista64 with only 2GB of memory? Did you memtest the new sticks to make sure they're not faulty?

The answer is obviously no, and you are quick to point fingers, because you don't understand the problem...

When I first started getting the errors, I was also determined to switch to ATI. A simple google search pointed out that the error exists in ATI cards as well. So it was pretty pointless to switch to ATI if there was the possibility of the same thing...

I understand that, you obviously don't... Anyway, it's your money mate. Do what you want. I'm just saying, you might spend that money for no reason... When you get that 4870x2, loop Crysis in DX10, V.High, overnight. If it doesn't recover etc, then it's a rock solid system. Crysis VH shows the problem extremely quickly...

[slaWter]

All I can say is that I don't get this error with newer drivers and newer cards anymore.
8800GTX was the worst of all cards but even that card was stable with newer drivers.

I still think it's a driver and VGA BIOS related problem, at least on my system.

[Badboy_12345]

You're choosing to ignore the issue. My stable OVERCLOCKED system in WinXP x64 crashes in Vista x64. If I back down the overclocking, the system is also stable in Vista x64... How is that a fault of the Nvidia drivers? As I said from my previous post, the problem may very well be your system, even if it is stable in Vista 32 and XP... You hope that the problem is the Nvidia drivers, you don't know.

Yet you fail to grasp the simple, obvious signs. You installed 4GB of memory and the crashes began... But it's Nvidia's fault... It's been said many times that Vista stresses the memory subsystem more than Windows XP because of virtualisation. Thus a stable XP system might be unstable in Vista. Did you try backing down your overclocking? Did you try testing in Vista64 with only 2GB of memory? Did you memtest the new sticks to make sure they're not faulty?

The answer is obviously no, and you are quick to point fingers, because you don't understand the problem...

When I first started getting the errors, I was also determined to switch to ATI. A simple google search pointed out that the error exists in ATI cards as well. So it was pretty pointless to switch to ATI if there was the possibility of the same thing...

I understand that, you obviously don't... Anyway, it's your money mate. Do what you want. I'm just saying, you might spend that money for no reason... When you get that 4870x2, loop Crysis in DX10, V.High, overnight. If it doesn't recover etc, then it's a rock solid system. Crysis VH shows the problem extremely quickly...

Actually I tried everything that you mentioned. I looked for another cause for days. Because I know other things can influence it as I work as an IT-Tech.

I have run memtest, I have taken out the new sticks of ram, I have turned back my overclocks. And I installed 4gb and installed vista x64. The crashes began after that. So its not that I put in 4gb ram and it started crashing.

So by going by that and that MANY others are having the same problem with the same card I point at the drivers and the card.

So yes nvidias fault.

[Lfctony]

Actually I tried everything that you mentioned. I looked for another cause for days. Because I know other things can influence it as I work as an IT-Tech.

I have run memtest, I have taken out the new sticks of ram, I have turned back my overclocks. And I installed 4gb and installed vista x64. The crashes began after that. So its not that I put in 4gb ram and it started crashing.

So by going by that and that MANY others are having the same problem with the same card I point at the drivers and the card.

So yes nvidias fault.

Since you have tried everything, change that card. Hopefully that will fix it for you. Good luck.

Tony.

[Badboy_12345]

Since you have tried everything, change that card. Hopefully that will fix it for you. Good luck.

Tony.

I will when I get some money (not much over when you have a kid and a partner that is looking for work).. until then I am dual booing with xp so I can play WAR Online when it releases.

I was going to buy the HD4870x2 anyway so its not just because of this problem now.

[nekrosoft13]

Lfctony, i had noticed the samething with AMD 4400+ system that used to run XP, later installed vista64.

4400+ was OC'ed to about 2.7ghz, it was stable with XP but with x64 it used to crash every few minutes. Vista is simply more hardware demanding, and it will expose any weak components in any system. Backed down the OC to 2.6ghz and it was fine then.

[nekrosoft13]

I will when I get some money (not much over when you have a kid and a partner that is looking for work).. until then I am dual booing with xp so I can play WAR Online when it releases.

I was going to buy the HD4870x2 anyway so its not just because of this problem now.

why not just RMA it, if you really think the card is at fault

[Badboy_12345]

why not just RMA it, if you really think the card is at fault

The warranty is long gone.
And I think its the card combined with the drivers

[tisdale36]

The EVGA cards are lifetime warrantied. Just so everyone knows. I bought another 8800 GTX a newer model and plugged it in using the same driver and it works flawlessly. The problem is these cards not the drivers like we've been told. We've been lied to all this time. I was told by EVGA to delete my driver and all traces of the driver and reinstall and so on and so on. This is crap and if EVGA wants return business from me they better do something. I ran my card underclocked all this time waiting for a good driver with confidence and now I find that it is the card and they are telling me that I didnt register my card within 30 days even though I showed the receipt (which should be enough) they are telling me that it is too bad and so sad for me. There should be a factory recall. Has anyone heard of any pending class action suits? If you have an 8800 GTX that is acting up, SEND IT BACK, IT IS NOT THE DRIVER.
I am going to be checking on sueing EVGA and need to know how many people had the EVGA card problem. DO NOT BUY AN EVGA CARD, THEY DO NOT BACK THEIR PRODUCT.
I aint going to fall for no banana in my tail pipe. :captnkill:(nana2):captnkill:

[$n][pErMan]

The EVGA cards are lifetime warrantied. Just so everyone knows. I bought another 8800 GTX a newer model and plugged it in using the same driver and it works flawlessly. The problem is these cards not the drivers like we've been told. We've been lied to all this time. I was told by EVGA to delete my driver and all traces of the driver and reinstall and so on and so on. This is crap and if EVGA wants return business from me they better do something. I ran my card underclocked all this time waiting for a good driver with confidence and now I find that it is the card and they are telling me that I didnt register my card within 30 days even though I showed the receipt (which should be enough) they are telling me that it is too bad and so sad for me. There should be a factory recall. Has anyone heard of any pending class action suits? If you have an 8800 GTX that is acting up, SEND IT BACK, IT IS NOT THE DRIVER.
I am going to be checking on sueing EVGA and need to know how many people had the EVGA card problem. DO NOT BUY AN EVGA CARD, THEY DO NOT BACK THEIR PRODUCT.
I aint going to fall for no banana in my tail pipe. :captnkill:(nana2):captnkill:

I get the error and have an eVGA card... one of the originals with the black PCB.

[tisdale36]

My card is the 768-p2-n835-ar. It aint the driver, it is faulty hardware and EVGA knows it, do an RMA ASAP dont wait like I did because now the ASH-holes at EVGA refuse to honor my warranty because I did not register my card within 30 days of purchase. Also, I will never buy another EVGA card because they are poosies. I hope they go out of business becasuse of these posts.

[tisdale36]

It aint the driver, it is faulty hardware and EVGA knows it, do an RMA ASAP dont wait like I did because now the ASH-holes at EVGA refuse to honor my warranty because I did not register my card within 30 days of purchase. Also, I will never buy another EVGA card because they are poosies. I hope they go out of business becasuse of these posts.
You're choosing to ignore the issue. My stable OVERCLOCKED system in WinXP x64 crashes in Vista x64. If I back down the overclocking, the system is also stable in Vista x64... How is that a fault of the Nvidia drivers? As I said from my previous post, the problem may very well be your system, even if it is stable in Vista 32 and XP... You hope that the problem is the Nvidia drivers, you don't know.

Yet you fail to grasp the simple, obvious signs. You installed 4GB of memory and the crashes began... But it's Nvidia's fault... It's been said many times that Vista stresses the memory subsystem more than Windows XP because of virtualisation. Thus a stable XP system might be unstable in Vista. Did you try backing down your overclocking? Did you try testing in Vista64 with only 2GB of memory? Did you memtest the new sticks to make sure they're not faulty?

The answer is obviously no, and you are quick to point fingers, because you don't understand the problem...

When I first started getting the errors, I was also determined to switch to ATI. A simple google search pointed out that the error exists in ATI cards as well. So it was pretty pointless to switch to ATI if there was the possibility of the same thing...

I understand that, you obviously don't... Anyway, it's your money mate. Do what you want. I'm just saying, you might spend that money for no reason... When you get that 4870x2, loop Crysis in DX10, V.High, overnight. If it doesn't recover etc, then it's a rock solid system. Crysis VH shows the problem extremely quickly...

[FTY]

Frankly this is happening on XP x64 too. There is no error message but the error is just the same for me as in Vista Ultima X64. Any game just freezes at random and the picture gets all messed up, you can still hear the game in the background and well yeah the movement is almost nil, 1 frame per 30 sec or something like that.

It's the exact same stuff that has happened on Vista X64 as said, except that there I got this "driver stopped responding error" which ultimately always resulted me in rebooting the PC, cause the driver wasn't restarted anyway, as when I would run a game after the error, the above written error would just reproduce (freezing, image misshaping, etc.)

Now the same is in Win XP x64, except for that error, when the game freezes, I have to kill it through task manager, and when I start it again, the same problems as above, so a reboot is needed here also. Even if I let XP run few minutes, to let everything cool-down, and start a game, the same ****.

So I guess it's somewhat 64bit related, don't have this problems on 32bit XP. The card is 8800Ultra from MSI.

[FTY]

The EVGA cards are lifetime warrantied. Just so everyone knows. I bought another 8800 GTX a newer model and plugged it in using the same driver and it works flawlessly. The problem is these cards not the drivers like we've been told. We've been lied to all this time. I was told by EVGA to delete my driver and all traces of the driver and reinstall and so on and so on. This is crap and if EVGA wants return business from me they better do something. I ran my card underclocked all this time waiting for a good driver with confidence and now I find that it is the card and they are telling me that I didnt register my card within 30 days even though I showed the receipt (which should be enough) they are telling me that it is too bad and so sad for me. There should be a factory recall. Has anyone heard of any pending class action suits? If you have an 8800 GTX that is acting up, SEND IT BACK, IT IS NOT THE DRIVER.
I am going to be checking on sueing EVGA and need to know how many people had the EVGA card problem. DO NOT BUY AN EVGA CARD, THEY DO NOT BACK THEIR PRODUCT.
I aint going to fall for no banana in my tail pipe. :captnkill:(nana2):captnkill:

Life-Time Warranty, doesn't mean a product is under warranty for eternity. It means It's under warranty for as long as eVGA doesn't stop production of the said product (end of product life-time -> where the phrase "Life-Time Warranty" comes from).

But there's also the normal warranty of one or two years on all those cards anyway, so if you bought one after they should down production, you still have to obligatory product warranty, but I usually return stuff to the store where I bought them and not to the manufacturer directly, and they just give me a new card, or if that model isn't available, the give me options on what I can pick, a card for the same price, or pay additional fee and get a newer better one, if let's say the card I'm returning is almost 2 years old and faulty/dead.

As a side note, this error isn't eVGA exclusive anyway, it happens on ASUS, MSI, XFX, GAINWARD cards just the same as on eVGA.

[Lfctony]

It aint the driver, it is faulty hardware and EVGA knows it, do an RMA ASAP dont wait like I did because now the ASH-holes at EVGA refuse to honor my warranty because I did not register my card within 30 days of purchase. Also, I will never buy another EVGA card because they are poosies. I hope they go out of business becasuse of these posts.

It's an old thread. But, when I said in my post that it's Nvidia's fault, I really meant "You did this blah blah, yet it's Nvidia's fault", which translates to "not Nvidia's fault". Anyways, I believe that the crash no longer happens due to the drivers in 95% of cases. It's most likely the result of too much overclocking, a generally unstable system due to hardware conflicts or just bad hardware... For example, mine was fixed when I backed down from my overclocking. Also, on my other motherboard, overclocking with one video card was fine, with two it crashed with this error in a couple of minutes. Again, bad hardware/overclocking... For me...

Tony.