K
KrB
Whenever my HD becomes active, my cpuload goes skyhigh ...
What can i do about that?
What can i do about that?
P
peterk
When your HD comes active you are running a program
This program uses CPU cycles
These Cycles cause your load to increase
Find out what else is running(background?) and decrease the load
peterk
This program uses CPU cycles
These Cycles cause your load to increase
Find out what else is running(background?) and decrease the load
peterk
K
KrB
Every program I start,takes the cpu to 90+%. When it's started, cpu goes
back to normal.
Writing a cd brings the cpu to 50+%, downloading something same thing ...
So it has nothing to do with many programs running in the background,
it's has to be something else. I mean, notepad wouldn't bring my cpu
load from 5% -> 95% in normal circumstances, would it?
KrB
back to normal.
Writing a cd brings the cpu to 50+%, downloading something same thing ...
So it has nothing to do with many programs running in the background,
it's has to be something else. I mean, notepad wouldn't bring my cpu
load from 5% -> 95% in normal circumstances, would it?
KrB
B
Brian Cryer
KrB said:
Aside from the issue PeterK has raised, that it may be the application which
is running, other ideas:
1. is your disk compressed? For example, if your system folder were
compressed then Windows would need to uncompress on the fly any dlls it
might need to load. Thus even loading notepad would take longer.
2. Take a look in your event log , specifically the system event log. You
will find this under "Administrative Tools > Event Viewer". If you were
having hardware/disk related problems then this might account for your
problem (although I would expect it just to be slow without necessarily any
cpu hit), but if this the problem then there should be entries in the System
event log indicating a problem.
Can't think of anything else.
Brian.
www.cryer.co.uk/brian
K
Kerry Brown
KrB said:
What CPU? How much RAM? What type of hard drive, PATA, SATA, SCSI?
Kerry
K
KrB
Kerry said:
CPU Type Intel Pentium 4A, 2666 MHz (5 x 533)
512 MB - Apacer Tech. (PC2700 DDR SDRAM)
256 MB - Samsung M3 68L3223DTL-CB3
Seagate ATA 120 Gig - ST3120023A (3KA0MNA1)
KrB
K
Kerry Brown
KrB said:
I just tried some file operations on a similar system. With several windows
open, downloading newsgroup headers, copying files, starting programs all at
the same time. Neither CPU (Hyperthreaded) showed above 60% except for brief
spikes to 75%. Most of time both were below 10%. Do you have the motherboard
chipset drivers installed? In the device manager Expand IDE ATA/ATAPI
controllers. In the properties for the Primary IDE Channel (I'm assuming
that's where your drive is hooked up) what is the current transfer mode?
Kerry
K
KrB
Kerry said:
Yup, I have the latest chipset drivers installed on my system.
Transfermode of my prim IDE is at 'DMA when possible', but it's
currently at PIO.
Hmmm ... Can this be the problem?
Thx for your time in advance!
K
Kerry Brown
KrB said:
That is most likely it. See the following links:
http://support.microsoft.com/default.aspx?scid=kb;en-us;817472
http://www.microsoft.com/whdc/device/storage/IDE-DMA.mspx
http://www.michna.com/kb/WxDMA.htm
Kerry
K
KrB
Oh yeah baby
IDE Chan 1 is now back at UDMA mode ... Things are fixed now.
If I can do anything to thank you, please let me know
There's one thing I don't quite get yet, I read the causes ...
But I don't understand it, what could cause such CRC timeouts? A bad cdrom?
Thank you again very much!
KrB
K
Kerry Brown
KrB said:Oh yeah baby
IDE Chan 1 is now back at UDMA mode ... Things are fixed now.
If I can do anything to thank you, please let me know
There's one thing I don't quite get yet, I read the causes ...
But I don't understand it, what could cause such CRC timeouts? A bad
cdrom?
Thank you again very much!
KrB
Look through the event logs for errors over the last little while. It could
be a bad CDROM, bad hard drive, loose cable, bad cable, bad ram, bad m/b
controller. The most likely cause is from trying to read a bad CD. If it
keeps happening then it's worth pursuing further. For now I'd just monitor
it.
Glad you got it fixed.
Kerry