Good question Lord Reliant, not sure what this post is about or how it was revitalized from Feb 17th. The main patch I think that Stardock Mods are talking about is something that has been around for over 15 months and has been plaguing older chipsets and GPUs that were sold with the ole "Vista-Ready" logo on it. That error is the nvlddmkm.sys, driver has stopped responding error. From what I've read, it has to do with some sort of timing / reading issue between the GPU and either memory bus
StitchedChin
Looks like he tried without SLI. This sounds like something I'm running into as well, though not as bad. Pretty similar specs, M2N32-SLI AM2, 4600+ X2, Vista 64-bit, 7600 GT in SLI, though not SP1, didn't know it was officially released yet. It is almost like something is dragging it down in the background, so I Alt-Tab to the desktop, seems to "catch up", and then I go back into the game and it is good as new for a while. I'll try disabling SLI and see if that helps. See if you can
I'm using the beta 169.28 currently, but still having some issues, so not an end-all fix. I followed the instructions from the ocforum post, booted in safe mode, removed all Nvidia driver remnance, manually if needed and installed a "fresh" driver from 169.28. I had over 12 instances of nvlddmkm.sys all over my system, and now just 3. One in the driver folder, I copied that same file to the system32 folder and then one is stuck in a patch file that I didn't want to delete. Doesn't seem to ha
Yep, should be the same issue we've been having for a long time. Check the "Video Driver Issue causing hangs and bluescreen" post and you'll see everyone has posted attempts at fixing it, including me, but it is a Vista and graphic driver issue. Has been since the get-go of Vista. Nvidia is supposedly going to have a patch coming soon. Underclocking help me with better stability, but I still got the errors, just later on. I get all 3 errors, minidump, nvlddmkm.sys "driver has stopped respon
For curiosity sake, everyone pipe in about your motherboard too as Vista is definitely a major similarity as well as Nvidia's latest driver and the nvlddmkm.sys error. But, I'm wondering if the newer boards, 700s for nForce, are doing okay, just the older ones having the issues. I'm checking Nvidia each day waiting for their latest driver, nothing on there yet. Asus M2N32-SLI 590 AMD AM2
Edit: Crap ignore that, just noticed "XP" 64-bit. ************************ Vista 64-bit has not been the issue as far as guys having crashes and driver issues. It has been more a Vista in general thing along with drivers and hardware. Patches are on the way from Nvidia. If you are running Vista on a newer machine with newer hardware, you should be good to go, but I'd check some of the video error, freeze, crash technical posts and see if anyone has similar hardware to yours on w
Yep, I'm thinking tweaking the system only helps when it is a real hardware issue, but just plain communication/timing issues, we're going to have to wait for the patches. If this Nvidia patch doesn't work, I may have to check with Asus and see if they got something they can do.
Whoops, caught me editing, now I'm below you. Type for RAM Memory is something like DDR2 6400 (800 MHZ), brand OCZ, Corsair, Mushkin, latency is 4-4-4-12? I'm guessing but do you have a Dell? That seems like a lot of VM, not positive if that could be an issue, but I may try Changing it to 1536. Most consensus says 1.5 times your RAM, which is 1 GB. What kind of video card do you have, Nvidia / ATI, 7600 GT, Radeon 1950, etc. You should find this under Device Manager.
Yeah, starting with Vista 64-bit back in Jan '07, I'm constantly looking for BIOS updates all the time from ASUS. I'm on the latest BIOS for my M2N32-SLI AM2 590 AMD. http://dlsvr01.asus.com/pub/ASUS/mb/socket775/P5RD2-VM/e2832_p5vd2-vm.pdf Heres your MB manual. Syntaris, your BIOS should be 1202 available Nov '07. ASUS EZ Flash is, well easy. Just grab the BIN file from the website, put it on a blank flash drive and follow instructions in your manual on page 56. Probably al
Ah the fun of personal computing, everyone has similar issues, but yet there are probably hundreds of different reasons. There's definitely something going on that a patch may be able work around, but isn't really going to fix the underlying problem. Something is having trouble working together between our chipsets, RAM, CPU, GPU, oh and of course, dreaded O/S. I wonder if Devs would have a more efficient/stable time building a game for Linux, oooh bet they cringe at that question. I say if
I'm trying defragging since some guys suggest this and I usually pass over it since Vista was suppose to take this serious and do it in the background on a schedule, so no one had to worry about it. Vista analyzed the drive and said my drive performance was fine and didn't need to be defragged. I ran it anyways and it ran for over 2 hours. I cancelled it and am trying a free trial of diskeeper which at least lets me see the progress. I turned my pagefile to 256 mb last week reading something
Looks like you've checked out most the posts in here. Interesting you have an ATI card with this issue, where most Nvidia guys are waiting for an update hopefully to be released soon. You aren't getting any kind of detailed error from MS? I was thinking passing around saved games or replays of games that this is happening, see if others experience the lock up at the exact same time, but I don't think that would really work since I can reload a game I had a BSOD and get passed the prev
Talking drop you out of multi-player or single? Did it drop you into your desktop or to the main menu? Did you build this PC yourself? Got all the latest updates for Vista? Check to see if you have the 940105 hotfix from MS and read the article to see if it matches your issue. http://support.microsoft.com/kb/940105 I'm trying to look to see what issues a weak power supply has, I always thought it would reboot the whole machine, not sure if it would just shut down a p
Oh yeah, sadistic is definitely the right word, going with Vista 64-bit when it was first available... gotta be crazy. I keep telling myself it is a hobby... The thing I hate it Gametap doesn't support 64-bit and I was just having fun with it, ah well. Try Upshift's fix, if you have the stamina, I like the idea of marking the pagefile.sys down to 50 mb, defrag, and upping it back up to 2 GB. If that doesn't work, check out this issue on the nvlddmkm.sys. http://forums.n
Sebastian, came in here from other forum to get more detail of what problems you've been running into. I think XP would give you the ole, System is Low on Virtual Memory error if you were bumping into that one. Fresh install, I can't imagine defragging would fix much, though always good practice. I did a quick PSU check, you should have at least a 400W power supply, sound about right? Usually a complete reboot happens if PSU is maxed out though, I think I read that somewhere. I think 6800 G
Good to hear Yarlen, thanks! Mine is definitely an interum tweak. Yeah, I'm definitely a rambler, but I was basically underclocking my PC, if you know how to mess around with your bus/clock speeds? You can do it in the BIOS or use nTune if you have it installed. Underclocking has been the most stable for me, not just matching up the memory speeds on the GPU and RAM. I have OCZ Special Ops RAM, DDR2 667 MHZ, I'm getting the best results keeping my RAM clocked at 533 MHZ and bringing
When multiple parties (ATI, Nvidia, Microsoft, Game Devs) all point fingers at each other and things don't get fixed for over a year (not just a SOASE problem) that seems like a collective failure to me. But to the good news, I HAVE A FIX!! Not a complete solution, but has worked for me and hopefully this works for others. This is specific to the nvlddmkm.sys, "graphic driver has stopped responding" error, screen freeze, blank screen, music still playing, and either game resuming or g
You've done well with that hardware playing such demanding games, I'm impressed. Your CPU is 1.67 GHZ, 2000+, single core and you are on DDR 3200? It really looks like your graphics card is what is keeping you in business and maybe you're RAM is high quality, 2-2 latency, and 2 GB is a plus. Since they state minimum CPU is 1.8 GHZ and it works once it gets going, seems to me once it gets loaded and more in the hands of your RAM and GPU, the processor may not have to work as hard, so you are g
I'm thinking the specs on the box are a little optimistic. They recommend 256 MB 7800 or better, but don't say anything about PCI-E or AGP. Not sure if there is a real performance difference in the PCI-E and AGP of the 7600, but I have 2 7600 GT, in SLI and though I run into other issues, I get lag if I go solo GPU and can run decent in SLI on most settings. You are running pretty thin on the minimum requirements aspect as far as processor and maybe even GPU if AGP and PCI-E makes a diff
It is a mix of chipset and Vista. There are system board timing problems that run into conflicts, sort of a collective failure across the game design, graphic drivers and Microsoft. When the game requires extensive calculations, accessing memory, graphics memory, etc., Vista runs into problems, loses it and in most cases can recover even though sometimes it takes up to 10 minutes to recover. There are tons of similar complaints in this forum and this issue needs to be better organized. I thi
I seem to get the BSOD running full tilt, max resolution and settings and if I try to mess around with it too much once it is frozen. I'm on Medium with no effects checked off now on the lowest resolution (1024), and it seems to recover a bit easier, no BSOD. Looks like you've got a much better rig, so according to that Microsoft article, maybe the O/S hasn't given up on your GPU as quickly as it does for mine. I haven't done enough testing between SLI and non-SLI to see if that makes a diffe
Vista 64-bit Ultimate I think this is more of a collective failure, not just Nvidia's, though maybe they can fix their side to work with Microsoft. From everything I've found on the nvlddmkm.sys, graphic driver has stopped responding error, looks to me this is more of a problem running DirectX 9 built games using Vista which uses DirectX 10. Microsoft probably screwed something up on their backward compatability. Here's an article from way back in Nov '06. I'm going to try some of these
Asus M2N32-SLI 590 AM2 64-bit Vista 4600+ AMD X2 4 GB RAM 7600 GT x 2 (Issues in single and SLI) I've been searching around for a fix to this for a while and thought I'd check to see if anyone has seen this from Microsoft? http://support.microsoft.com/kb/938194/en-us This was an update back in August '07 that installed 3 patches which was suppose to vastly improve the performance for Vista, sort of a pre-emptive SP1. The problem I'm having is 2 updates inst