anantchowdhary
- 372
- 0
Im sry to say that a tmp file again having an Nmudp initialization function takes over and again the CPU usage shoots up!Pls help!
anantchowdhary said:err...i duno how to check...shud i post another screenshot of TCPVIEW?
thnx
C:\path_to_pskill\pskill.exe C:\path_to_badfile\badfile.tmp
BoredNL said:rename the file in safe mode, then create a blank text file with notepad. Save the file in the directory with the same name as the .tmp file. Right click on the file, and check "read only." Then reboot to see what happens.
You might have gotten some spyware, adware, trojan, or virii which is causing this. I wouldn't know though.
Try downloading "Spybot - Search & Destroy." Run a scan to see if it picks it up. Then you can try "Adaware SE Personal," "Windows Defender," an anti-virus program such as "Avast". I really don't know what this program is.
This would be a lot easier if I could just log into your computer and have a look at it. If you trust me enough, you can get http://www.tightvnc.com/" which you can set up to allow me to remote control your computer (only when you run the program, and you see anything that I'm doing). The only reason why I suggest this is because there's a million things this .tmp file could be and it's a bit tough to have you trying all sorts of things on the forum. If you would like to go for it though, send me a private message and I can give you my AIM or yahoo screen name. (or maybe we could just figure it out on AIM or yahoo sometime)
dimensionless said:I'm not sure that explorer.exe can be stopped. explorer.exe definitely should not be using 60% of your CPU time though. I would suggest verifying that your Windows installation has the most recent updates.

zambamingi said:If you want a faster way to pinpoint the corrupt file, use the Microsoft tool Process Monitor:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
First, recreate the problem causing explorer to use 100% CPU utilization. Then open up the Process Monitor tool and it will show explorer infinitely trying to do a file operation.
It will show you the exact file it's trying to read over and over again.