hard drive thrashing

recently, whenever I wake it out of the screen saver, the hard drive goes ballistic, even if no programs are running and continues to thrash constantly until I manually restart it. The whole computer runs like @$$ until I restart it. SMART data gives the drive a good report @ 97%. I turned off the screen saver for now and the problem is gone (duh) but I want to find out the cause of this. Ideas?

I guess I should add that yes, its still OCd, now at 3.7 but i ran Orthos for 7 hours, 3dmark03, some strenuous gaming...the basic stability testing. I did return my memory to stock 400mhz, 2.85v but @ 2.5-3-3-7 timings rather than stock 2-2-2-6. The whole system runs AMAZINGLY unless i let the screen saver load up (its just the standard XP screen saver)

 

Seems like a graphics card problem, as it happens with the screensaver, - is the graphics card getting overheated,- have you got temperature program.
Have you got a front fan, and is there a filter membrane there, as I have found that it needs to be checked for fluff build up under the graphics card, when using a front fan, and then the card plays up.

 

I think you have a paging file problem.

Two options.

First option

start>controlpanel>performance&maintenance>system
advancedtab>performancesettings>virtualmemory>change
select each drive i turn and click no paging file.
click ok ok ok

restart computer.

return to virtual memory box and reset paging file for c drive

restart computer.

secondly

open registry
HKLM\system\currentcontrolset\control\sessionmanager\memorymanagement
change clearpagefileatshutdown to 1
close registry
restart
You can leave this setting for slower shutdown but greater security or change it back.


Studio T

 

baklogic: i just recently reseated my VGA heatsink w/ new paste and i cleaned out the cooler fins and fan. I have 1 front and 1 side intake w/ one exhaust + the PSU exhaust. my CPU is water cooled as well

studiot: i never thought of that, thanks for bringing it up. ill mess around with it and report back in a while

 

That's o.k, viper_boy, I thought it well worth checking.
Studiot thought of the paging file cache, so elimination is my way of going.
That's two .
It will be interesting to see if the paging file does sort it out.

 

ok so i was on my way to edit the paging file and noticed that my memory was set for best performance of system cache! WTF? how did that happen? it has always been set to best performance for programs so i set it back AND reset the paging file and it worked. i dunno which thing fixed it but who cares! Thanks for the help guys

 

Ah, so,
It was to do with cache setting - Studiot was on target.