Question Locked

Help with temp & hung ap error messages in Windows XP after desktop crashed

0 helpful
38 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My desktop (Windows XP running 2000)crashed and I have reinstalled the software, updated drivers, etc. but am experiencing some glitches, including hung aps and the inability to us MSWord. Can someone point me in the right direction for fixing this? THANKS!

BELOW ARE SOME OF THE ERROR MESSAGES:

C:\DOCUME~1\COMPAQ~1\LOCALS~1\Temp\634b_appcompat.txt

--------
c:\dOCUMEN 1\COMPAQ 1\ LOCALS\TEMP\WER652D.DIR00\ACDSEE11.EXE.MDMP
c:\dOCUMEN 1\COMPAQ 1\ LOCALS\TEMP\WER652D.DIR00\APPCOMAT.TXT

saAppName: ACDSee11.exe szAppVer: 11.0.108.0 szModName: hungapp szModVer: 0.9.0.0 offset: 00000000

--------
MSWord error #1

C:\DOCUME~1\COMPAQ~1\LOCALS~1\Temp\WER1c61.dir00\WINWORD.EXE.mdmp

C:\DOCUME~1\COMPAQ~1\LOCALS~1\Temp\WER1c61.dir00\appcompat.txt

MSWord error #2

c:\docume 1\compaq 1\locals 1\temp\WER83be.dir00\WINWORD.EXE.mdmp

...dir00\appcompat.txt

szAppName: WINWORD.EXE szAppVer: 9..0.0.3822 szModName: hungapp szModVer: 0.0.0.0 ofset:0000000

38 replies

by the scummy one

then perform a chkdsk /f and reboot. After that I would clean out temps and run the disk cleanup wizard.

Post back if the problem remains

by tldemay

Thanks for the help! Ran chkdsk /F etc. Rebooted and ran chkdsk and chkdsk /F and it appears there is still a problem. Suggestions about what to do very welcome!

SEE BELOW:

chkdsk is verifying files (stage 1 of 3)
file verification completed
chksdsk is verifying indexes (stage 2 of 3)
index verification completed
chkdsk is recovering lost files
chkdsk is verifying security descriptors (stage 3 of 3)
security descriptor verification completed.
chkdsk discovered free space marked as allocated in the master file table (MFT) bitmap
chkdsk discovered free space marked as allocated in the volume bitmap.
windows found problems with the file system
run chkdsk with the /f (fix) option to correct these

by older mycroft

So - WHAT is the problem now?

Is it exactly the same as before?
If not, how has it changed?

Clearly chkdsk found and repaired various inconsistencies with the system files. How has it improved your situation? Any improvement? None?

Are all the same apps still hanging?

by w2ktechman

I ran into this a few weeks ago (the last time at least). However, for me chkdsk /f fixed them.

It looks like you may need a utility program to fix it. However, me being the type that I am, would erase everything and reload.
However, I would have also backed up my data by now (I hope you did).

I just looked on MS site, and for file system troubles, they suggest a defragment :0
before this though, I highly recommend to backup data

by seanferd

Did it say this after you ran chkdsk /f, or just chkdsk?

If after chkdsk /f, the fix part didn't take.
Perhaps chkdsk /x

edit:
Or chkntfs /c

by w2ktechman

the chkdsk /f is in a loop because it cannot fix the dirty bits properly. (if I am understanding correctly). When this happens, a stronger disk check/fix utility is needed, or, wipe the drive and rebuild it.

by seanferd

chkntfs /c was supposed to take care of that.

Doesn't surprise me one bit if something slightly more functional is needed, though.

by w2ktechman

hmmm, looking at the command, yes, that appears to be what it does. It sets the dirty bit so that chkdsk /f will run on the next boot.

by rob miners

chkdsk c:/r as it will run through all 5 stages. Just type it in the Run box and restart the System.

by tldemay

After backing up data, running disk clean up and defragging, I ran CHKNTSF, then ran CHKDSK with THE FOLLOWING RESULTS:

chkdsk is recovering lost files.
Recovering orphaned file 71769 (8271) into directory 55966
Recovering orphaned file 21567 (24337) into direcotry file 55975

chkdsk i sverifying security descriptors (stage 3 of 3)
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap
Windows found problems with the file system
Run Chkdsk with the /f option to correct these
----------
Ran chkdsk c:/r then rebooted with THE FOLLOWING RESULTS:

Chkdsk is verifying files
File verification completed
chkdsk is verifying indexes
Index verifcation completed
chkdsk is verifying security descriptors
Security descriptor verification completed
CORRECTING ERRORES IN THE VOLUME BITMAP
WINDOWS FOUND PROBLEMS WITH THE FILES SYSTEM.
----------
Running chkdsk /f again after rebooting the machine does not resolve the issue.

ANY OTHER SUGGESTIONS?
WHAT UTILITY PROGRAMS WOULD YOU SUGGEST/RECOMMEND?
Thanks for everyone's help!

by rob miners

a disk cleanup to remove Tempory files and Defragment your drive. How much space is left on the drive.

How to locate and correct disk space problems on NTFS volumes

http://support.microsoft.com/kb/303079

1. Open My Computer, right-click Local Disk, and then click Properties.

2. On the General tab, click the Disk Cleanup button. Disk Cleanup will spend a few minutes examining your disk.

3. The Disk Cleanup dialog box will open and you can make your selections.

4. Select the desired check boxes in the Files to Delete list including Temp files.

5. Select ?Disk Clean Up and other options?. In the ?Other options? press on ?Clean? for ?System Restore", and then click OK

6. If you have more than one hard disk, repeat this process for each hard disk listed in My Computer.

You can use the Hard Drive Makers Testing Utility to Test the Drive

Hitachi / IBM - DFT "Drive Fitness Test"

http://www.hgst.com/hdd/support/download.htm

Works with all manufacturers

Western Digital "Data Lifeguard"

http://support.wdc.com/download/index.asp#dlgtools

Works with WD drives only

Fujitsu "FJDT"

http://www.fel.fujitsu.com/home/drivers.asp?L=en&CID=1

Works with fujitsu models only

Samsung "hutil"

http://www.samsung.com/Products/Hard...ties/hutil.htm

Compatability unknown...

Seagate "Seatools"

http://www.seagate.com/support/seatools

Works with Seagate drives only

by seanferd

I'd still try chkdsk /v /x

If you can get a defragmenter to run, have it do a surface scan. It will take forever, but it will mark any bad blocks on the disk, hopefully avoiding future problems.

It could be that the disk is getting ready to die. I'd definitely back up whatever is important, and look into getting another disk, just in case.

Will look into other utilities. I'll bet Jacky Howe knows some good ones.

by rob miners

Did you run the drive makers tools to rule out a bad hard drive. Was there any references in chkdsk to do with BAD Sectors.

Check for the presence of the Zobot virus. Symantec has a removal tool.

http://www.symantec.com/security_response/writeup.jsp?docid=2005-081615-4443-99&tabid=3

Download and install CCleaner to tidy up your Registry. Backup the Registry as you go along, rescan again and again saving as you go until there are no errors left.

Cleaner: Windows

When you first open Ccleaner you will have an option to Analyze or Run Cleaner, after checking the left Pane and making your choices. Delete all Temp Files. If you scroll down you will see a greyed out box that has Advanced next to it. Left click on it and keep pressing OK to all of the responses. I normally Untick Windows Log Files and Memory Dumps as they may come in handy.

You don't have to install all of the add ons or shortcuts just the one to the Desktop.

http://www.ccleaner.com/download

Try running chkdsk c:/r again.

by tldemay

After trying the above and rebooting and running chkdsk again I received the following message (again):

Chkdsk discovered free space marked as allocated in the master file table (MFT) bitmap.
Correcting errors in the volume bitmap.
windows found problems with the file system.
run chkdsk /f to correct these

0 kb in bad sectors.
---
I also ran fsutil dirty c: and
diskmgmt.msc without any negative findings...

by rob miners

Follow the steps below with the System started in Safe Mode with Networking.

Removing malware from System Restore points
To remove the malware, you must first disable System Restore, then scan the system with up-to-date antivirus software - allowing it to clean, delete, or quarantine any viruses found. After the system has been disinfected, you may then re-enable System Restore. The steps for disabling System Restore vary, depending on whether the default Start Menu or the Classic Start Menu is being used.

Default Start Menu
If using the default Start Menu, click Start | Control Panel | Performance and Maintenance | System. Select the System Restore tab and check "Turn off System Restore".

Classic Start Menu
If using the Classic Start Menu, click Start | Settings | Control Panel and double-click the System icon. Select the System Restore tab and check "Turn off System Restore".

After scanning the system and removing the offending malware, re-enable System Restore by repeating the steps, this time removing the check from "Turn off System Restore".

Click Start, Run type msconfig and press Enter.

Now if you have the Configuration Utility open.
Configure selective startup options
In the System Configuration Utility dialog box, click the General tab, and then click Selective Startup.
Click to clear the Process SYSTEM.INI File check box.
Click to clear the Process WIN.INI File check box.
Click to clear the Load Startup Items check box. Verify that Load System Services and Use Original BOOT.INI are checked.
Click the Services tab.
Click to select the Hide All Microsoft Services check box.
Click Disable All, and then click OK.
When you are prompted, save the settings and restart the PC.
When the System is disinfected re-run the Configuration Utility and in the System Configuration Utility dialog box, click the General tab, and then click Normal Startup.

Download Malwarebytes Anti-Malware, install it and update it.
Click this linkmalwarebytes

http://download.bleepingcomputer.com/malwarebytes/mbam-setup.exe

* Double-click mbam-setup.exe and follow the prompts to install the program.
* At the end, be sure a checkmark is placed next to Update Malwarebytes' Anti-Malware and Launch Malwarebytes' Anti-Malware, then click Finish.
* If an update is found, it will download and install the latest version.
* Once the program has loaded, select Perform Quick Scan, then click Scan.
* When the scan is complete, click OK, then Show Results to view the results.
* Be sure that everything is checked, and click Remove Selected.

I would keep scanning with it until it is clean by closing out and rebooting and running it again.

Just to be on the safe side when you finish do an online scan with Bitdefender. Or Google for an online scanner.

http://www.bitdefender.com/scan8/ie.html

If you can't access the internet to update MBAM try the instructions below to clear a path to the internet to be able to run MBAM.

From another PC download and install Spybot, update it and copy the the installed folders to a USB Stick.

Restart the PC in Safe Mode, navigate to the USB stick and run Spybot.

Download Spybot - Search & Destroy and install it. Update it. http://www.safer-networking.org/en/download/index.html

With the new strains of Virus that have been created you may find it necessary to rename the executable files so that they will work. Rename mbam-setup.exe and then navigate to the install folder and rename mbam.exe. Do not change the files extension from .exe. Do the same with Spybot.

Also run this Rootkit Revealer GMer
http://www.gmer.net/index.php

FAQ
http://www.gmer.net/faq.php

BleepingComputer
http://www.bleepingcomputer.com/malware-removal/page

by seanferd

Vagaries of antivirus apps and stuff.

I was mano a mano in a battle royale with this one box to get any of these things to work. The ultimate goal was a boot-time defrag with Diskeeper. Even when the chks would run, some repairs weren't made. Even after everything was cleaned up, Diskeeper kept reporting that the dirty bit was still set, and wouldn't run. Argh.

by seanferd

and he shall appear. :D

Thanks for proving me right. :)

(I didn't see your post until I submitted mine.)

by rob miners

be the drive failing but it seems more like the amount of free space isn't adding up properly. It will be interesting to find out if there are any BAD Sectors on the drive. If that is the case I would be replacing it.

If not I would use DBAN to erase the drive and do a reinstall. These things don't happen regularly. Then again I've seen Win98 Systems that have ran for four years without a Scandisk and Defrag.

{Edit}

Darik's Boot and Nuke.

http://dban.sourceforge.net/

by tldemay

chkdsk is verifying indexes
index verification completed
DECTECTED MINOR INCONSISTENCEIES ON THE DRIVE. THIS IS NOT A CORRUPTION.
heckdsk is verifying security descriptiors
CLEANING UP 1 UNUSED INDEX ENTRIES FROM INDEX $SII OF FILE 9
CLEANING UP 1 UNUSED INDEX ENTRIES FROM INDEX $SDH OF FILE 0
CLEANING UP 1 UNUSED SECURITY DESCRIPTIORS
Security descriptor verification completed
correcting errors in the volume bitmap
windos found problems with the file system.
Run chkdsk with the /f option to correct these.

suggestions for utilities to use?

by seanferd

"Chkdsk discovered free space marked as allocated in the master file table (MFT) bitmap.
Correcting errors in the volume bitmap.
windows found problems with the file system.
run chkdsk /f to correct these"

And does it still say "windows found problems with the file system" if you run it again? It seems like you need to keep running this until the problem is fully resolved, or something is messing with the file system, like malware.

by tldemay

yes, if I understand your question. Anytime I run any variant of chkdsk and then reboot so the process can run, and rerun chkdsk, the same message appears.

by rob miners

Right click on My Computer, select Properties, select Advanced, under Performance select Settings, left click on advanced and under Virtual memory select Change.

If System managed size is ticked, tick No paging file. Click on Set and then OK, you will get an alert saying that you have to restart the PC. Close out of there and restart the PC.

run chkdsk c:/r and and follow the prompts, restart the System and see if it will run through properly. If it does do the steps below to turn it back on.

Follow the above steps to get back to Virtual memory select Change, make sure that c: is highlighted and click on System managed size, click set and OK. Close out and hopefully you will have a new Pagefile.

by tldemay

This is the outcome of taking the above steps....

Changed virtual memory selection and restarted machine.
Ran chkdsk c:/r with the following results:

Chkdsk is recovering lost files
Recovering orphaned file tmp.edb (93982) into directory file 5076.
Chkdsk is verifying security descriptors (state 3 of 3)...
Security descriptor verification completed.
Correcting errors in the master file table's (MFT) bitmap attribute.
Correcting errors in the volume bitmap
windows found problems with the file system
run chkdsk with the /f option....

Rebooted machine
Ran chkdsk c:/f

Chkdsk is recovering lost files
Chkdsk is verifying security descriptors (state 3 of 3)...
Security descriptor verification completed.
Chkdsk discovered free space marked as allocated in the master file table bitmap
correcting errors in the folume bitmap
windows found problems with the file system

Went back and reset virtual memory settings
Reboted system
Ran chkdsk (read only)

Chkdsk is verifying files
File verification completed
chkdsk is verifying indexes
deleting index entry Dc36.url in index $130 of file 52348
Index verification completed
Errors found. Chkdsk cannot continue in read-only mode.

Reran chkdsk c:/r

Chkdsk is verifying files
File verification completed
chkdsk is verifying indexes
Index verification completed
Chkdsk is recovering lost files

Chkdsk is verifying security descriptors (state 3 of 3)...
Security descriptor verification completed.
Chkdsk discovered free space marked as allocated in the master file table bitmap
correcting errors in the volume bitmap
windows found problems in the file system.

by rob miners

yesterday that was displaying these symptoms. I went through the processes that have been posted here to no avail. I ran the hard drive testing utility and it found no problems. I then backed up the users data and did a fresh install. Problem solved.

by seanferd

by tldemay

I haven't had a chance to try the most recent suggestions, but I will tomorrow...

I was poking around on Microsoft's website and came across this information and was wondering if this could be part of the problem?

Your thoughts?

http://support.microsoft.com/kb/315688

Thanks again for all your expertise. I'll check in again tomorrow after I try your most recent suggestions...tld

by tldemay

ran malwarebytes ap which turned up a few things, followed by MS rootkit detctors which turned up the following:

HKLM\SECURITY\Policy\Secrets\SAC* 6/24/2005 4:52 PM 0 bytes Key name contains embedded nulls (*)
HKLM\SECURITY\Policy\Secrets\SAI*6/24/2005 4:52 PM 0 bytes Key name contains embedded nulls (*)

Tried to run the regdelnull utility, but I don't believe I'm entering the string correctly.. (Went to http://technet.microsoft.com/en-us/sysinternals/bb897448.aspx)

by rob miners

were probably added by something that was installed years ago. Try IOLO and if that doesn't work wipe the drive with DBAN and start fresh. The System has been running for a long time now and corruption is enevatable.

by rob miners

you deserve a Thumb. I put it down to a corrupt registry and the best way to fix that is a reinstall as you earlier suggested.

I wasn't going to waste any more time mucking around trying to repair the system.

by w2ktechman

after about 4 hours without coming up with any progress.
If it aint getting better, it gets rebuilt.
However, I have swayed from that from time to time.

by skdtech

Having read everything already posted and considering the effort already expended I would recommend a backup of your data, disk wipe and clean format and install.

But this is all dependent on how much further effort you want to expend on this problem.

by tldemay

...since I've never had to do this (wipe a disk), I was assuming (hoping?) that problems could be identified and fixed so I could avoid this, but it's not looking good...

This discussion is closed to new replies.