Tried this, and didn't work. Thanks thou.Dirty Dan wrote:If you're running out of things to try you could run driver sweeper, which does a more thorough wiping of your drivers, then reinstall.
Another person with a similar problem had this advice.http://social.technet.microsoft.com/Forums/en/itprovistahardware/thread/fd499e81-63d9-4ebf-8dcb-4eca24007afc wrote:
1) Go to your device manager and check the date and version of your nvlddmkm.sys file and jot it down.
2) Search your system for files named "nvlddmkm.sy_"
3) If any of those files are newer than the date of your current file, then you are a candidate for this solution. If not... STOP RIGHT HERE, you ARE NOT a candidate for it.
4) Go to your "Windows/System32/drivers" directory and locate the nvlddmkm.sys file.
5) Rename the file to: nvlddmkm.sys.old
6) Now, from the search you did in step 2 above, copy the "nvlddmkm.sy_" file that most matches your system to the "Windows/System32" directory.
7) Click on your start icon, and in the "Start Search" box, type "cmd", and notice the start menu will show you the "cmd.exe" file in the box above the search field.
Right-click the "cmd.exe" program and select, "Run as Administrator", and again tell Windows this is something you really wanted to do!
9) Within the command shell window, navigate to "Windows\System32" if you aren't already there.
10) Type the following command:
expand nvlddmkm.sy_ nvlddmkm.sys
11) It should report back to you that it did something. If it reported the file could not be written, go back to step 8, you didn't *really* tell Windows you were administrator
12) In the command shell window, type "exit" and press enter to close the window.
13) In your file explorer (Windows Explorer), navigate to the "Windows/System32" directory and move the "nvlddmkm.sys" file to the "Windows/System32/drivers" directory.
14) Restart your computer.
Just for reference, here's the Microsoft Knowlegebase info on Event ID 4101. It seems to agree that the driver needs to be replaced. Windows Vista and 7 both keep multiple copies of drivers in various places; it is entirely possible that one of these is being reinstalled without your knowledge.http://forums.nvidia.com/index.php?showtopic=38941 wrote:
I went to the control panel and open up the programs list, where you can uninstall and install progs. I uninstalled my forceware drivers. Now I did NOT restart when it prompted me to.
Next, I did an advanced search on my C:\ drive (or whatever drive contains Vista) and I searched for the driver, "nvlddmkm". Make sure you checked the box where it asks if you want to search hidden files and such.
Several files with that name came up in the search. There were about 8-12 files. They are located in several different places. Many of the files end in ".sy_" and the other few will of course end in ".sys".
Of course some of these files are still being used by Vista because they are the RTM drivers that shipped with Vista. The files that can be deleted, should be deleted. At least this is what I did. I got rid of the nvlddmkm.sys file that seemed to be left over from the uninstall. (Now I know what you are thinking, and let me say that that .sys file that I just mentioned WAS still there even after I restarted to complete the driver uninstall process. The bum file wont go away on its own.)
You can also look at the dates on those files and see exactly which ones are the alleged culprits, because of the recent dates that should appear. Once those were trashed and deleted.
I then deleted all my unpacked driver installation files that I still had on my computer. (Note: Some of those ".sy_" files were located in those installation folders as well, but I got rid of them anyways to be thorough.)
Once I did all of that, I downloaded a fresh copy of the 100.54 forceware drivers.
Once it was on my computer, I went to the properties of My Computer and opened up the Device Manager and then completely uninstalled my video card. I restarted and let Vista install its basic drivers, then I installed those 100.54 drivers I dl'ed and then of course restarted again.
Glad to hear you're tenatively back in business! 
However you said that it happens even when you use minimal settings, so perhaps something else is using up your memory before you even launch TF2? Is that a possibility?What is happening in the game is that your large memory footprint of your graphics card is mapped into the game. Typically this is when your settings are high, because it uses the most memory, which would explain why the game is playable when you use minimal settings. Because your particular graphic card setup uses nearly 2 gig of RAM itself, you quickly force the game to run out of memory space that is addressable.
To fix this, you may be able to play at reduced settings. Lowering your resolution is typically the best way to restrict memory usage, since it exponentially increases RAM use when you increase resolution. You will likely have to play around with various settings. You can open up Task Manager and monitor your WoW game's usage of memory to see where the sweet spot is on keeping your memory under control.
I can't quite make sense of that post. The 64-bit OS should be able to address all RAM and VRAM without an issue. If the 32-bit program is internally addressing all the VRAM before RAM, then it should still be able to address at least a gigabyte of RAM. If the program is running out of memory, then it should crash, not the driver. I can't help but feel that I'm missing something completely logical here. I wish I had a crash dump to debug or something. This problem seems to lie within the interaction between Source and the driver.metacide wrote:
Also I found this:However you said that it happens even when you use minimal settings, so perhaps something else is using up your memory before you even launch TF2? Is that a possibility?What is happening in the game is that your large memory footprint of your graphics card is mapped into the game. Typically this is when your settings are high, because it uses the most memory, which would explain why the game is playable when you use minimal settings. Because your particular graphic card setup uses nearly 2 gig of RAM itself, you quickly force the game to run out of memory space that is addressable.
To fix this, you may be able to play at reduced settings. Lowering your resolution is typically the best way to restrict memory usage, since it exponentially increases RAM use when you increase resolution. You will likely have to play around with various settings. You can open up Task Manager and monitor your WoW game's usage of memory to see where the sweet spot is on keeping your memory under control.
Users browsing this forum: No registered users and 15 guests
