Thread: OT Scandisk ?
View Single Post
  #4   Report Post  
Old September 26th 05, 09:05 PM posted to uk.sci.weather
Alan Gardiner Alan Gardiner is offline
external usenet poster
 
First recorded activity by Weather-Banter: Jul 2003
Posts: 1,138
Default OT Scandisk ?




XP ~ thanks for that, I try to avoid doing such things until it becomes
necessary, but of course when the time comes around I've forgotten what I
did.

I know the more times it crashes the more likely it is to do more damage
to either the OS or the hardware. I doubt it's overheating of the CPU as I
have a 120mm Heatsink on the Athlon 3400 which looking at 'Motherboard
Monitor' rarely gets hotter than 50°c, atm is 45°c

I ran Scandisk (Check disk) for my 'C' drive, as this is the main one with
the operating system on, it didn't appear to throw up any errors, unless
it corrected them in the background, it often does a quick Scan when it
reboots after a crash and does find error and currupt files everytime it
runs. I'll see how it goes for now.

I don't think I've installed anything apart from Firefox 1.0.7 upgrade,
which I find quite often crashes. I sometimes get the blue screen/reboot
when I try to attach a file or grab something from my 'slave' disk. I read
about the blue screen/driver issue, the next step if it happens again is
to put the XP disk in and do a install/repair as it maybe possible some
files have got corrupted. It was a thought that there maybe some bad
clusters whre the swap files are which prompted me to run a scan disk.

Again thanks for your help
--
Keith (Southend)

'Weather Home & Abroad'
http://www.southendweather.net



The most probable cause of sporadic blue screens, lockups etc is a buggy
device driver. Windows XP has a Driver Verifier Manager utility. To use this
type verifier at the command prompt and select create standard settings. In
the next dialog box select the type of driver you want to verify - unsigner
drivers are almost certainly the problem. If your computer stops with ablue
screen on the next start up you will see which is the offending driver
together with an error code.

To resolve the problem boot into safe mode (press F8) and disable or
uninstall the offender.

To disable the verifier run verifier and select delete existing settings or
type verifier/reset at the command prompt. If you haven't got rid of the
driver then this will have to be done in safe mode.

This information has been taken from Windows XP inside out which is a
Microsoft publication. More information is available at the Microsoft
website so if you feel like running this utility it might be worth going
there first at http://www.microsoft.com/whdc/DevToo.../Verifier.mspx.

Your problem may be elsewhere but this will at least eliminate any buggy
drivers if they exist.

Alan


Alan