Re: After 2gb install, continuous disk check

scott moore wrote:
Kerry Brown wrote:
scott moore wrote:
Kerry Brown wrote:
scott moore wrote:
Hi,

I upgraded my machine from 1gb to 2gb, I heard you get better
performance.

I don't know about the performance, but now my machine performs
"disk checking" on boot -- every time. It never finds any problem,
and everything else is normal.

Thank you.
Test the ram.

www.memtest.org

You added some new hardware. Now Windows is seeing a problem.
Something is not right with the upgrade. If the ram tests OK post
back for more suggestions.

Kerry


May I ask, is Windows actually setting a flag to check the disk if
it sees a ram problem? Why would it not say "there is a ram
problem"? Thanks.

When you write to a disk Windows checks that what was written
matches what is in memory. If it doesn't match the drive is flagged
for a chdsk. Look in your event logs for errors writing or reading
from disk. These are sometimes a symptom of bad ram. It's usually
not a coincidence when you add some new hardware and problems occur.
It is most likely the new hardware. There are certainly other
possibilities - the hard drive started to go bad at the same time,
the hard drive cable came loose when you added the ram and possibly
more causes. I would check the ram before going any farther. If the
ram checks out then it's time to check other possibilities. Kerry



Alright, here's the followup. I pulled the new module, no effect.
Next, pulled the D: disk. Disk D: was put into the system back in
January during a reload of windows due to a windows reboot problem
(this was not common, windows ran for more than a year without
problem before that). It was NTFS formatted, and 300gb in size, and
had a duplicate of the C: drive information. The C: drive in FAT32.

Pulling disk D: stopped the disk checking on reboot.

The event records covering the issue are the same, repeated for every
daily boot:

"The file system structure on the disk is corrupt and unusable. Please
run the chkdsk utility on the volume D:"

Note that (many times) the checkdisk utility was allowed to proceed,
and simply announced the disk was fine. This is a VERY time consuming
procedure on 300gb.

So I am guessing there was some issue with the D: disk, software or
hardware.

Thanks.

Check to see if the dirty bit is set. You could use "chkntfs d:". If it's
set the only way to clear it is to run "chkdsk /f" I usually use "chkdsk /p"
from the recovery console if the drive has been causing problems. If that
doesn't clear it then you are up the proverbial creek. I don't know of any
way to clear it other than a total format. It still seems really odd that
the problem occurred after adding new ram. Personally I would run memtest86+
overnight and also test the drive thoroughly.

Kerry


.

Relevant Pages

  • Re: Windows unable to boot - black screen
    ... suggestion that this could be a hardware issue. ... daughter laptop), but none recently. ... You can if it is a 2.5" disk but not if it is a 3.5" disk. ... blue' started to have problems with booting Windows. ...
    (microsoft.public.windowsxp.general)
  • Re: System Hard Drive RPMs
    ... onto physical resources is another matter. ... Lets limit this to 32 bit Windows. ... You gotta see it the other way around, physical memory - be it disk or ram, ...
    (rec.audio.pro)
  • Re: need to delete my pc, going to buy a new one and sell my old p
    ... All data on the disk should be ... how are you going to reinstall Windows XP? ... Without the installation media, all you have for sale is the hardware. ...
    (microsoft.public.windowsxp.general)
  • Re: Windows Loging off TOO SLOWLY
    ... > i have using Check disk, Disk Defragmenter, Disk cleanup, check knwon ... > november security updates from windows update website. ... Sounds like you checked for hardware issues with the CHKDSK.. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: hard drive impact on overall system performance
    ... If something else accesses the drive (i.e windows system, or swap), ... > What I don't understand is why it slows down at all. ... > using only 200meg of ram, so there's no reason for swapping. ... and keep disk operations off the windows drive as much as possible. ...
    (comp.sys.ibm.pc.hardware.storage)
Loading