Recently tried to install nVidia Win7 driver update (7/23/09). Uninstalled current driver and rebooted. Login, desktop appears, couple of apps start up then message appears: WerFault.exe - Application Error - Instruction at 0x77923892 reference memory at 0x00000000. Memory could not be read. Note that I have not installed anything yet, all I did was uninstall the current video driver. Clicked OK then get same message for LVCSer64.exe, USerinit.exe, dum.exe, rundll32.exe, sdclt.exe and others, sometimes multiple times for each. Reboot, same problem. Cold boot, same problem. Safe Mode boots OK. Boot repair mode and only one checkpoint shows, made immediately after uninstalling driver. Tried that but it does not restore system. Reboot to repair mode and do full system restore. Everything back to normal. Also all my previous restore points now appear. This morning found computer had rebooted itself overnight with no explanation why. Logged in and immediately received error messages as above even before getting to desktop. After several minutes of clicking OK to these I rebooted. System came up fine and has been running OK for 5 hours. Any idea what is causing this? I am OK with the system in its current state (except for poltergeist re-booting) and do not want to re-install Win7 until the gold code ships in October. Just wondering what would cause such an error in the first place, when all I did was uninstall a video driver. Thanks! SidIntel E6750 OC'd to 2.9GHz - 4GB Corsair XMAS PC-6400 RAM - 80GB Maxtor PATA HD - Corsair 750W PSU - Cyber Snipa Stinger mouse / Saitek Eclipse keyboard - Creative X-Fi Titanium PCIe sound card - Dual EVGA 880GT's in SLI - ViewSonic E90fb monitor - LiteOn external USB DVD/CD burner - Sony internal DVD/CD burner - HP C7280 AIO - D-Link 802.11N router

Hi, unexpected reboots probably caused by corrupted or not properly works drivers (reboot option after BSOD probably turned on). You need to analyse memory dump files from "C:\Windows\minidump" folder.My English is not very well.

It probably seached for the video driver you removed behind your back and reinstalled it eliminating the runtime errors. Automatic updates could be causing reboots.

It probably seached for the video driver you removed behind your back and reinstalled it eliminating the runtime errors. Automatic updates could be causing reboots.

Thanks for the input guys. I tried updating the driver without uninstalling (never the right thing to do) and received the exact same error. A System Restore made everything right again. Then I tried the correct procedure a second time, i.e. uninstalling the driver and rebooting to install the new driver. Same error as before. It's pretty obvious that I am stuck with the original nVidia video drivers, which is OK since everything works correctly. Perhaps I won't have this problem with the Gold Code in October. Again, thanks for the input. If anyone hears of other's having a similar problem please let me know. Perhaps we can all figure it out together. SidIntel E6750 OC'd to 2.9GHz - 4GB Corsair XMAS PC-6400 RAM - 80GB Maxtor PATA HD - Corsair 750W PSU - Cyber Snipa Stinger mouse / Saitek Eclipse keyboard - Creative X-Fi Titanium PCIe sound card - Dual EVGA 880GT's in SLI - ViewSonic E90fb monitor - LiteOn external USB DVD/CD burner - Sony internal DVD/CD burner - HP C7280 AIO - D-Link 802.11N router

Hi Sid,as atemporarily solution you canturn off error reporting service: press Win+R, type services.msc than find Windows Error Reporting service in the services list, right-click on it -> click Properties -> open "Startup type" list and select "Disabled" -> press OK. Check for the problem again. Hope it will be helpfull.I think nVidia will fix this problem after final W7 release.My English is not very well.

sick_ That's a great suggestion, I didn't know you could turn that off. I will try that in the next couple of days and let you know how it works out! SidIntel E6750 OC'd to 2.9GHz - 4GB Corsair XMAS PC-6400 RAM - 80GB Maxtor PATA HD - Corsair 750W PSU - Cyber Snipa Stinger mouse / Saitek Eclipse keyboard - Creative X-Fi Titanium PCIe sound card - Dual EVGA 880GT's in SLI - ViewSonic E90fb monitor - LiteOn external USB DVD/CD burner - Sony internal DVD/CD burner - HP C7280 AIO - D-Link 802.11N router

I believe I found the answer to why the system rebooted - it was the emergency Windows security patch that installed itself and rebooted the system. One mystery solved. But of course, still no idea why uninstalling a video driver makes the system fail. If I can get a free couple of hours I am going to try sick_'s suggestion of disabling the Error Reporting service to see if that makes any difference. SidIntel E6750 OC'd to 2.9GHz - 4GB Corsair XMAS PC-6400 RAM - 80GB Maxtor PATA HD - Corsair 750W PSU - Cyber Snipa Stinger mouse / Saitek Eclipse keyboard - Creative X-Fi Titanium PCIe sound card - Dual EVGA 880GT's in SLI - ViewSonic E90fb monitor - LiteOn external USB DVD/CD burner - Sony internal DVD/CD burner - HP C7280 AIO - D-Link 802.11N router

I have a problem running both Winamp v5.58.1 and AllChars v4.7.321 on my Windows 7 operating system. There is no problem running these two programs on Windows XP nor is there a problem running AllChars without installing Winamp on Windows 7. But if AllChars is loaded in Win7 and Winamp is set to any of its internal browser choices (like Podcast Subscriptions or Add-ons or On-line Services) I get an error message which reads; WerFault.exe - Application Error --------------------------- The exception unknown software exception (0x0eedfade) occurred in the application at location 0x756c9617. On closing the error message window rundll32.exe runs using half the CPU. Killing both WerFault.exe and rundll32.exe allows me to continue with Winamp without further difficulties. But typing anything in the search box in the start menu or opening Outlook 2003 results in another error message. The workaround seems to be not running AllChars and Winamp together. Not very satisfactory. Others have reported similar problems in Windows 7. I suggest using a selective startup with all startups disabled as well as 3rd party services. If the problem dissappears, add in startups until it returns.