Presario V5000 crawling & won't system restore

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
Two month old V5000 is suddenly a mess.
It's crawling.  Takes 3-5 mins to boot up or shut down.
Mouse is delayed & applications run slower than snot.
Audio & video (CD/DVD/Windows XP chimes) breaks up.
During minutes long shutdown I get dialog boxes "ccAPP", and "alm.exe"
not responding and have to click "end now" boxes.
Tried system restore feature, but none of the supposedly acceptable
(BOLD date calendar) restore points would load (I have 12% of 48GB HDD
allocated to system restore).
Ran the full boat Norton's Anti-virus scan, all 161,000 files and found
nothing at all.
Disabling Norton's when attempting restores had no effect.
About the only thing on it is iTunes - rest is all standard stuff that
came w/it.
Daughter's computer at school so I'm not positive about what's been
done w/it, but directories, programs, etc. all look pretty clean.  Any
ideas what's up here? At wits end now.

Re: Presario V5000 crawling & won't system restore

reglarnavy wrote:
Quoted text here. Click to load it

Right click My Computer - Properties - click Hardware - Device Manager
- IDE ATA/ATAPI Controllers, right-click Primary IDE Channel,
Properties, Advanced Settings, Device 0 - what does it say in "Current
Transfer Mode" ? (Should be Ultra DMA Mode 5).

There's a problem in XP whereby the computer can get stuck in PIO mode
after repeated hibernate/resume cycles. This was SUPPOSEDLY fixed, but
I've still seen it happen since the fix propagated.

Re: Presario V5000 crawling & won't system restore

Thanks for the response: here goes -
Device 0 transfer mode = "DMA if available".  The only other choice
(unselected) is "PIO only"
Current transfer mode = PIO wrote:
Quoted text here. Click to load it

Re: Presario V5000 crawling & won't system restore

reglarnavy wrote:
Quoted text here. Click to load it

Then you have the problem I described. The problem is that on resume,
you sometimes get a checksum error. Windows "gives up" on DMA mode
after a certain number of attempts and there is no simple UI way to fix
this. Run Regedit.


Set "MasterIdDataCheckSum" = 0

Do the same thing in

Reboot. Look in Device Manager again and you should see it now says
"UDMA Mode 5". System should also start faster and be much more

Re: Presario V5000 crawling & won't system restore

Have to admit zwsdotcom, you're right on the mark with what I'd find so
far - sure enough, both checksums big hexidecimal values.  Reset both
to zero and rebooted, but no change in the system, and the PIO status
didn't change.  Did find some info on the Compeq website about the
"ccAPP" issue - related to temp files in Nortons.  Don't have the
laptop w/me anymore, daughter took it back to school - better than
nothing at all right now.  Many thanks for assistance. wrote:
Quoted text here. Click to load it
Quoted text here. Click to load it
Quoted text here. Click to load it

Re: Presario V5000 crawling & won't system restore


Quoted text here. Click to load it

Argh. Well, at least you know why your system is slow - just not the
reason why it is in PIO mode.

Did you make sure that in Control Panel it still says "DMA if
available" in the drop-down list?

The registry change I told you forces Windows to rescan the devices for
DMA capabilities on boot (as long as you've got "DMA if available"
selected). Essentially what it does is perform a data transfer in DMA
mode 5, check the result, if it's bad then it goes down to mode 4, etc.
etc. until it falls all the way down to PIO mode.

The checksum that's in there is actually a hash of the IDE Identify
results for the attached drive. Changing the checksum makes it no
longer match the info reported by the drive, forcing Windows to reset
all its internal attempt counters for the drive. Basically what it does
is simulate swapping the hard drive out for a different unit.

If things are still failing into PIO on the rescan, sterner measures
are necessary. The first thing I'd try - AFTER backing up anything
important on the system - is to delete the IDE controller in Device
Manager and let Windows redetect it and reinstall the driver. That

Did you recently install some software that tries to hook the drive
APIs at a low level? Antivirus software, encryption software, special
partitioning software, special drive management software, or anything
of the sort?

Site Timeline