Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exploere.exe - Application Error 1

Status
Not open for further replies.

bobo0605

MIS
Dec 4, 2003
71
US
Hi!

I'm working on a windows xp pro machine that had a ton of spyware, trojans, and virus on it. I ran multiple spyware programs ( Spysweeper, Adaware, Spybot, Hijackthis, and microsofts antispyware program). I also ran AVG virus scanner. I'm not receiving any hit with spyware or viruses anymore. But after I deleted all the infection i'm gettign this error when I try to open things like My Computer, Control Panel. The error is " Explorer.exe - Application Error. The instructions at "0x0198d065" referenced at "0x00000000". The memory could not be written." Now if I look in the event viewer there an application error. The error is " Event 1000 Faulting Application DRWTSN32.exe, version 5.1.2600.0, FAulting module dbgkelp.dll. version 5.1.2600.2800, FAulot address 0x0001295." I tried to repair the OS but that didn't work, also if i boot into Safe Mode I have no problems with this explorer problem. Any help or ideas here would be appreciated!!
 
Not from Microsoft.

Start with the instructions in faq608-4650

The issue is that a lot of malware was written in the context of XP and XP with SP1 and the numerous changes of all kinds to IE and OE.

SP2 installs a unique version of both applications. This is a good thing, as later this year those using SP2 will see a huge leap forward with IE 7. It is a bad thing because malware written for pre-SP2 versions of the OS and IE create a lot of odd and annoying problems.

My preference is to have the workstation absolutely as clean as possible of malware prior to installing SP2. It certainly should not be installed on a workstation with virus, malware or hardware issues. It is not a fix, it rather creates a very large magnifying glass on previous unresolved issues.

So my earlier advice was based on that premise: Revert the SP2 install, resolve all issues - OS, malware, hardware --and then install SP2 from an OEM image on a clean machine.

Bill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top