2006-05-22, 05:18 PM
The dw20.exe issue is not just Windows Defender. I googled around some more and it seems that .NET 2.0 is including the link to the Dr. Watson error reporting. 1.1 did not do this. To keep the dw20.exe files from spawning and freezing the system with 100% CPU, you can disable it by:
Open Control Panel/System
Goto Advanced tab
Click Error Reporting button
Disable error reporting
Disable critical error notifications
I got the above message off a .NET developer site so it looks like other developers are having the issue.
I still have it tell me I have a problem, it just doesn't turn into a resource hog to send a list to Billy. I am sure I still have some sort of problem (on the system) but hopefully this will keep things running. I have not seen anything on my logs besides what I already posted. It does not happen all the time, but it still crashes every now and then.
Open Control Panel/System
Goto Advanced tab
Click Error Reporting button
Disable error reporting
Disable critical error notifications
I got the above message off a .NET developer site so it looks like other developers are having the issue.
I still have it tell me I have a problem, it just doesn't turn into a resource hog to send a list to Billy. I am sure I still have some sort of problem (on the system) but hopefully this will keep things running. I have not seen anything on my logs besides what I already posted. It does not happen all the time, but it still crashes every now and then.
[SIZE="1"] Server= Asus M3A78-EM, 4 gigs ram, AMD A64 5200+, Windows 7 home premium 32, 1 HVR-1800, 1 PCH A-100, Test Rig, Biostar 880g+, AMD X2 260, 4 gb ram, Windows, 7 Home Premium 32, 1 DCR-2650 cablecard tuner [/SIZE]
[SIZE="1"][/SIZE]
[SIZE="1"][/SIZE]