nvlddmkm stopped responding ?

[taltamir]

I actually said that it is most likely a faulty video card OR a faulty motherboard...
Replacing the motherboard will work if it is a faulty motherboard...

If you keep on getting problems with replacement motherboards then it is the BOARD not the chipset...

I had lots of problem with the "nforce400ultra for amd for AM2" aka "nforce500" based abit mobo I bought, I went through three rma's (one will ruin a harddrive every two weeks, one will get ram errors on perfectly good ram, one had some other issue i dont remember).... then I went and bought a gigabyte board with the EXACT SAME chipset. and it worked perfectly without a hitch.

 

[sephra]

You are all forgetting one thing....

is he playing hellgate london.. <---- THIS CAUSES THE CRASH PERIOD.......

@ that guy... if your playing hellgate.. turn off AA/AF, and maybe shaders to high.. that fixed most of my nvidia driver crash issues.. and now im stuck with the memory leak.. for the most part....... Also the first zone in hellgate (hourbour) or however u call it... seems to be the spot you will crash in the most.. generally once you get past that ive noticed crashes diminish... and everytime i zone back.. i crash ~10 mins...



vista is just about perfect in everything i throw at it... there is only 2 issues hellgate london causes the nvida driver to crash sometimes../or it's memory leak tells me im out of memory (sad 8g's of ram doesnt cut it i guess i need to get more ) The only other issue i get is sometimes when swapping levels in CS:S only not tf2 or anything else.. hl2.exe will stop responding.. but others are getting that issue as well.. so dunno


As far as overclocked video cards.. generally if you buy say a BFG8800GTXOC2 like is in my box.. their pretty much going to be fine for the extent of the use... OC'ing may cause harm, may not.. it can go both ways.. clean power/good cooling.. should be more than enough to ensure stable machine...

 

[taltamir]

about the memory leak... Did you try increasing your pagefile size? I remember a game where there was a bug where it accidently addressess a very high pagefile address REGARDLESS of how much ram you have... if you have several gigs of pagefile (4gb seemed good enough) then it doesn't crash, otherwise you get a blue screen.

I have no idea if it is a similar issue in hellgate.. or if it is an honest memory leak... But it is worth a try. (ofcourse, with 8GB of ram your default pagefile should be... beefy.)

 

[chizow]

No offense Taltamir, but I think you're a bit misguided in your opinion on NV chipsets. If you think every case with an NV chipset is due to a bad board, there's a helluva lot of bad NV boards out there. There's just so many different cases where an NV board works fine....until you start adding components or RAM or use Vista and then the board starts flaking out. Not to mention boards from the same makers with Intel chipsets don't exhibit the same problems nearly as often......

In the case of my X-Fi, its not only Creative at fault, as I had the card working fine under XP on the same exact rig. Once I upgraded to Vista and 4GB RAM, I couldn't get the card running at all without crashes/BSODs/etc. Other users reported the latest drivers from Creative fixed Vista problems for a while, until MS released a hotfix that broke the drivers again by creating a memory allocation conflict. The problems with Vista/NV chipsets/Creative aren't just driver related though, as there's just resource allocation problems all over (IRQs, memory addresses etc). I'm sure some of it is just a pissing contest between MS/NV/Creative but the end-result is a massive headache.

And I did end up replacing my board and eating the cost since Newegg/Asus don't let you "return" it. It took 3 kits because the rig was perfectly stable a few months at a time and I had no choice but to run 1 kit while the other was out on RMA until my new board came in. If I had to do it all over again, I would've just gotten an Intel chipset, probably wouldn't have had to go through 3 RMAs and I'd be able to use my X-Fi.

 

[taltamir]

Originally posted by: chizow
No offense Taltamir, but I think you're a bit misguided in your opinion on NV chipsets. If you think every case with an NV chipset is due to a bad board, there's a helluva lot of bad NV boards out there. There's just so many different cases where an NV board works fine....until you start adding components or RAM or use Vista and then the board starts flaking out. Not to mention boards from the same makers with Intel chipsets don't exhibit the same problems nearly as often......

In the case of my X-Fi, its not only Creative at fault, as I had the card working fine under XP on the same exact rig. Once I upgraded to Vista and 4GB RAM, I couldn't get the card running at all without crashes/BSODs/etc. Other users reported the latest drivers from Creative fixed Vista problems for a while, until MS released a hotfix that broke the drivers again by creating a memory allocation conflict. The problems with Vista/NV chipsets/Creative aren't just driver related though, as there's just resource allocation problems all over (IRQs, memory addresses etc). I'm sure some of it is just a pissing contest between MS/NV/Creative but the end-result is a massive headache.

And I did end up replacing my board and eating the cost since Newegg/Asus don't let you "return" it. It took 3 kits because the rig was perfectly stable a few months at a time and I had no choice but to run 1 kit while the other was out on RMA until my new board came in. If I had to do it all over again, I would've just gotten an Intel chipset, probably wouldn't have had to go through 3 RMAs and I'd be able to use my X-Fi.

actually I KNOW it is because of a bad board... You want chipset problems, use via or sis boards for years... now those are crappy chipsets... and even then the board has ALOT to do with it.. I have seen companies make perfectly stable boards with via and sis... they just need to do the right things with the bios.
And I am greatly amused by your intel comment... It kind of goes against most reviews I have read.

What exactly makes me an NV defender? I say, and rightly so, that most of the times if you have serious flaking it is a defective board / board DESIGN. SOMETIMES there are actual chipset problems. But 1. Those are rare. 2. Those are not unique to a few individuals. 3. Those are nothing like the problems reported here... all problems I have seen before and have traced to a single defective board...

And yes there are alot of defective boards out there... I personally worked at companies who shipped parts with 30+% failure. The explanation? "it is better then not shipping it at all"

 

[ZK2007]

Originally posted by: chizow
No offense Taltamir, but I think you're a bit misguided in your opinion on NV chipsets. If you think every case with an NV chipset is due to a bad board, there's a helluva lot of bad NV boards out there. There's just so many different cases where an NV board works fine....until you start adding components or RAM or use Vista and then the board starts flaking out. Not to mention boards from the same makers with Intel chipsets don't exhibit the same problems nearly as often......

In the case of my X-Fi, its not only Creative at fault, as I had the card working fine under XP on the same exact rig. Once I upgraded to Vista and 4GB RAM, I couldn't get the card running at all without crashes/BSODs/etc. Other users reported the latest drivers from Creative fixed Vista problems for a while, until MS released a hotfix that broke the drivers again by creating a memory allocation conflict. The problems with Vista/NV chipsets/Creative aren't just driver related though, as there's just resource allocation problems all over (IRQs, memory addresses etc). I'm sure some of it is just a pissing contest between MS/NV/Creative but the end-result is a massive headache.

And I did end up replacing my board and eating the cost since Newegg/Asus don't let you "return" it. It took 3 kits because the rig was perfectly stable a few months at a time and I had no choice but to run 1 kit while the other was out on RMA until my new board came in. If I had to do it all over again, I would've just gotten an Intel chipset, probably wouldn't have had to go through 3 RMAs and I'd be able to use my X-Fi.

Vista, X-Fi, high end Nvidia chipset video cards CAN run together flawlessly. My Nvidia chipset m/b I tried running with and without the xfi board installed.. nothing different. Crash every second or 2 seconds. Intel chipset board was my fix.

Taltamir... One of the most stable boards i owned were MSI boards back on VIA chipsets.. never ever had a problem. EVER. Ran rock solid for me up until I was ready to jump aboard the PCI-E/C2D/Vista/DDR2 train with the rest of the crew. I was going to go with MSI again, and one of my friends was like "OMG u gotta go asus! asus rocks!" So, reluctantly, I gave 'em a try and did the NF590 board.. waited on backorder for 3 months, only to have the 680 boards released a MONTH after I got my system finally built. I chalked it up as experience and realization technology doesn't wait and is forever changing and u're only "top of the line" for mere weeks, even if u have yet to open the box the thing came in. I had absolutely nothing but trouble with my Asus board. After months of troubleshooting every possible thing, doing everything everyone told me to. unintall, reinstall, stand on my head when i press Start, etc.. nothing but heartache and rage beyond belief. I gave up and bought Abit IP35 Pro. Perfect! Enuff said. All these folks, with the exception of Garfield3d.. have nvidia boards that are having the nvidia driver issue that i've seen. Freak occurance perhaps, but i'm willing to put my money on the fact that nvidia based boards do NOT play well with Vista and it's drivers for nvidia hardware. Why else would everything that wouldn't work, including the EXACT same drivers in my nvidia board now work flawlessly in an intel board? Weird, huh.

*steps off soapbox*

 

[taltamir]

If you look at my posts you will see I listed msi and gigabyte as two of the three best motherboard makers.

AND I said that it is perfectly possible to make a good via or sis mobo if you have quality bios and a well designed board... which MSI does.

That is really my whole point. If a board is flaking it is either defective, or crappily designed... it is not a case of "OMG nvidia/ati/intel/via/sis suxorsss, OLOLOLO?!"

 

[chizow]

Originally posted by: taltamir

Originally posted by: chizow
No offense Taltamir, but I think you're a bit misguided in your opinion on NV chipsets. If you think every case with an NV chipset is due to a bad board, there's a helluva lot of bad NV boards out there. There's just so many different cases where an NV board works fine....until you start adding components or RAM or use Vista and then the board starts flaking out. Not to mention boards from the same makers with Intel chipsets don't exhibit the same problems nearly as often......

In the case of my X-Fi, its not only Creative at fault, as I had the card working fine under XP on the same exact rig. Once I upgraded to Vista and 4GB RAM, I couldn't get the card running at all without crashes/BSODs/etc. Other users reported the latest drivers from Creative fixed Vista problems for a while, until MS released a hotfix that broke the drivers again by creating a memory allocation conflict. The problems with Vista/NV chipsets/Creative aren't just driver related though, as there's just resource allocation problems all over (IRQs, memory addresses etc). I'm sure some of it is just a pissing contest between MS/NV/Creative but the end-result is a massive headache.

And I did end up replacing my board and eating the cost since Newegg/Asus don't let you "return" it. It took 3 kits because the rig was perfectly stable a few months at a time and I had no choice but to run 1 kit while the other was out on RMA until my new board came in. If I had to do it all over again, I would've just gotten an Intel chipset, probably wouldn't have had to go through 3 RMAs and I'd be able to use my X-Fi.

actually I KNOW it is because of a bad board... You want chipset problems, use via or sis boards for years... now those are crappy chipsets... and even then the board has ALOT to do with it.. I have seen companies make perfectly stable boards with via and sis... they just need to do the right things with the bios.
And I am greatly amused by your intel comment... It kind of goes against most reviews I have read.

What exactly makes me an NV defender? I say, and rightly so, that most of the times if you have serious flaking it is a defective board / board DESIGN. SOMETIMES there are actual chipset problems. But 1. Those are rare. 2. Those are not unique to a few individuals. 3. Those are nothing like the problems reported here... all problems I have seen before and have traced to a single defective board...

And yes there are alot of defective boards out there... I personally worked at companies who shipped parts with 30+% failure. The explanation? "it is better then not shipping it at all"

You seem totally oblivious to problems you don't come across personally, so here's a link to one of many on Creative's forums regarding X-Fi/nForce problems. Its a well-documented issue that nForce users experience regardless of who made their board, so I guess its not just an isolated incident with my board being defective.

You list MSI as one of your preferred board-makers, yet, I still have the same problems with my MSI board as I did with my Asus P5N-E. But at least this MSI board isn't killing my RAM every few months. The X-Fi did actually work with both boards in XP and Vista w/ 2GB, but once I moved to 4GB, problems started up. There's numerous others here on these forums with nearly identical problems and hardware, identifying the common thread being the nForce chipsets. Some have even reported moving to Intel chipsets and their problems are resolved. Even if it is a result of a 30% failure rate for NV board partners, that's a problem endemic of NV boards as Intel boards regardless of maker have always been known to be solid, stable performers at the expense of overclocking/extra features.

As for Via chipsets being crappy, there was a time they were the undisputed best chipset maker for AMD platforms (KT266E or w/e). On the other hand, NV has had what? 2-3 decent chipset amongst 6 generations now? Nforce 2, and 6-series, maybe the 4-series being the only decent performers and you already know my opinon of the 6-series.

 

[taltamir]

I already explained that creative is the plauge and any problem with crative products I consider 100% the responsibility of creative.

I would never recommend to anyone putting a creative disaster is card form into their computer.


And that 30% failure was not mentioned in regards to nvidia. I said I worked at a company that shipped a part with known 30% defect rate... for your information it was the controller board for a home appliance. The POINT was that companies might ship parts despite the parts having insane defect rates.

 

[chizow]

Originally posted by: taltamir
I already explained that creative is the plauge and any problem with crative products I consider 100% the responsibility of creative.

I would never recommend to anyone putting a creative disaster is card form into their computer.


And that 30% failure was not mentioned in regards to nvidia. I said I worked at a company that shipped a part with known 30% defect rate... for your information it was the controller board for a home appliance. The POINT was that companies might ship parts despite the parts having insane defect rates.

Kinda funny, woke up this morning to find some Windows Updates installed.

Looks like another fix for an nForce problem that didn't exist.....a problem I already described here and elsewhere

Problem is, fixes like this give me and other X-Fi/nForce users false hope that compatibility issues are actually resolved. I'm willing to bet nothing was fixed and there's still issues between Vista/X-Fi/nForce.

 

[Akkuma]

I wanted to chime in and and let people know that TDR issues are definitely not just nvidia chipset problems. I am running a Gigabyte 965P-DS3 rev 1 w/what was F5 iirc and now the latest F12 bios. I've had the TDR issue during both of these, so bios update didn't help. On top of this, I have a 7900GTX to make the situation even more different than what most people here have. I recently ran memtest and I discovered a bad memory range, which was giving me errors consistently. I've tried tons of drivers all to no avail, so I am hoping that once I get my ram RMA'd the problem will disappear (as long as there are no errors on the new ram either).

I've seen the explanations on why XP handled this without a problem (ran it for 6 months without any problems on XP) compared to Vista and they make a lot of sense; however, I find this as a failing with Vista in the end if it can't appropriately handle a bad memory range like XP can easily. Vista should be handling the situation even better, instead it has made the situation worse. It traded what seems to be system stability for system performance.

 

[taltamir]

if you have had a bad stick of ram you should reinstall windows... During the installation certain files will get corrupted as they pass through those mem ranges... So even if you have an apperantly stable machine you will still have... issues.

Get new ram, run memtest overnight. And then if has 0 errors after several passes go and reinstall.

 

[chizow]

Important X-Fi Driver Update for those with 4GB+ and Vista 64

Fixes in this driver:

• Resolves an issue for Windows Vista 64-bit systems with 4 GB RAM
• Resolves loud speaker noise when restarting your computer
• Resolves an issue that causes OpenAL games not to respond

This driver may or may not solve the cracking/hissing problems some are seeing with NV chipsets, however, for me it solved the greater problem of not being able to use the X-Fi at all without BSODs, crashes, memory/resource allocation problems etc in Vista 64. Re-installed the X-Fi and haven't crashed yet, although sounds in games still seem a bit off. May need to update the OpenAL wrapper for those games as I previously used onboard Azalia HD.

 

[taltamir]

In other words, the CREATIVE driver no longer causes bsods on vista 64 with 4gb of ram... wow how nice of them to FINALLY get it done... only how long after vista64 came out?

As I said, creative is the plague, and blaming anyone else for their shorcomming is unjustified.

I beleive creative has a team of engineers working on producing impressive hardware... and those exact same engineers are also supposed to program the driver in their "free time" (I have been in a company that did things that way).... Obviously the drivers are downright atrocious.

 

[chizow]

Originally posted by: taltamir
In other words, the CREATIVE driver no longer causes bsods on vista 64 with 4gb of ram... wow how nice of them to FINALLY get it done... only how long after vista64 came out?

As I said, creative is the plague, and blaming anyone else for their shorcomming is unjustified.

I beleive creative has a team of engineers working on producing impressive hardware... and those exact same engineers are also supposed to program the driver in their "free time" (I have been in a company that did things that way).... Obviously the drivers are downright atrocious.

Again, you don't know what you're talking about. Its a Vista problem that Creative ended up working around through their drivers. Like I said, just a pissing contest between MS and Creative. Its really simple though. Vista controls the resources, if they don't want to let Creative's hardware/software use them, there's going to be problems plain and simple.

There's so many examples here and elsewhere that prove this to be the case, but I know you already chose to ignore the link I provided above where Vista had problems with something as simple as USB devices and 4GB. But the simplest proof is that their atrocious drivers work with Vista with 2GB and XP without any issue. Now they work with x64 and 4GB....until MS manages to break them again.

 

[taltamir]

no they don't work with XP without any issues... creative drivers have caused untold damage on many xp machines, often requiring a reformat...

Worse of them all being that between 2000 and 2004 the ONLY way to install the latest driver for creative was to install the original driver that came with the CD rom (and hope the computer doesn't die), and then "upgrade" to the newest driver... because otherwise the driver will give an error about it being software licensed as an upgrade and you must have an older version for it to allow installaiton... then it will REMOVE the older version (you had to hope that doesn't fail) and install the current version... because everyone wants to steal the intellectual property that is the creative DRIVER.

Oh, and you STILL have to go that route for any of the "software" that comes with it... like their advanced control panel software, etc.



Vista has problems, yes. And nivida has problems, and everyone has problems...
But creative has the most problems of them all, most of them are self inflicted or due to neglect.

 

[BLHealthy4life]

Back on topic!..geez

I had this problem with a P35 chipset board 4GB DD@2 Vista X64, definitely not limited to NV chipset boards...

Got rid of that hardware, getting ready for a new build in the coming week with X38 and DDR3..WILL NOT be using Vista x64 this time..going XP X64 instead.

 

[tommo123]

happening to me with latest drivers from nivida and the ones on win update on an intel bad axe mobo on vista x64 with my 7950 gx2

other pc is an asus p5b del - also vista x64 but with an ati 2400xt - no issues.

 

[Puffnstuff]

I kept on getting that error until the most recent drivers. Currently I'm using the 165.29 driver and I haven't had any problems with it.

 

[tommo123]

nvidia have betas on their site so will try them. failing that, i plan on working my way backwards through various drivers. it was crazy last night. went to ign to check a review of some 360 game and the flash content on the site caused TDRs to happen every 30 seconds!

 

[ArchAngel777]

Based on my experience, I will probably say that Vista X64 is just finding problem with cards that were unnoticed with Windows XP.

Someone mentioned on these forums that they had artifacts in ATI Tool at stock speeds on their G80. If that is the case, then it would make sense that you would have this issue as the overclocked cards are prone to getting this message when a card is not stable. It also seems to me that Vista is more sensative to overclocking than XP. I can duplicate these issues by turning fan speed down low and playing a game, or by overclocking the card past a certain point.

 

[Mem]

Originally posted by: ArchAngel777
Based on my experience, I will probably say that Vista X64 is just finding problem with cards that were unnoticed with Windows XP.

Someone mentioned on these forums that they had artifacts in ATI Tool at stock speeds on their G80. If that is the case, then it would make sense that you would have this issue as the overclocked cards are prone to getting this message when a card is not stable. It also seems to me that Vista is more sensative to overclocking than XP. I can duplicate these issues by turning fan speed down low and playing a game, or by overclocking the card past a certain point.

nvlddmkm stopped responding problems can be quite a few things as I meantioned in my previous posts,ie overclocked video cards,ram timings,certain drivers,faulty ram etc.....I know troubleshooting this problem can be a pain...I have seen a few threads on this in XP and Vista,there's no simple one all fix solution for everybody,lots of trial and error as they say.

Latest update on my gaming and Vista x64 is still rock stable(55 games now in Vista x64,still using my underclocked 7800GT OC card,I'll get around to replacing it sometime,oh btw I even installed Starforce drivers and it still did not bat an eye lid).

 

[tommo123]

well, the beta's had no effect at all, so started my way backwards. no TDRs yet though on an older forceware. hoping it will stick.

the annoying thing, is that my other vistax64 PC with an ati 2400XT has none of these problems - at all!. That made my mind up as to which card i plan to get next. Nvidia may be faster at the mo but what use is that if you end up getting TDRs every 30 seconds.

 

[zorrt]

Still nothing on a workaround or fix?

I'm running P35 chipset, 8800gt videocard and I can't get Bioshock to run at all. Just gets the error. Call of duty, world in conflict and crysis seems to be ok but I havent actually played any games longer than 5 mins.

 

[Stangs55]

Got my official Vista x64 SP1 released today...

WoW still crashes like crazy with this bug.

Thanks nvidia!!

Any new news?