sdchange.exe.mui File

Lately my system is requiring a disk check about twice a week or so. When
the check is run it finds errors. Namely the error I seem to see is that the
file sdchange.exe.mui is orphaned. It moves the file from the sector, it
fixes the entry then moves the file back to the sector 7237 of the disk. In
a few days this happens again in the exact same manner. This seemed to start
immediately after SP1 Install for Vista Ultimate.

System Info:
Antec Titan 650 Case and 650W PSU
ASUS P5N-E SLi Motherboard
Corsair XMS2 PC2 8500 Memory Two 1024M Dimms in dual channel mode
Intel E6750 Duo Core 2 Processor
Evga 8800GT 512M SSC Vid Card
Two 250G WD 2500AAKS SATA II Drives in RAID0 on the Nvidia RAID controller
One 160G Maxtor on the Jmircon SATA controller
Windows Vista Ultimate 64 bit SP1 RTM on the RAID
Windows XP SP2 on the standalone Maxtor
MS Intellimouse Explorer 3.0
MS Natural Multimedia Keyboard

System is not experiencing any other issues at this time.
Temps are all well within range.
ACPI Thermal Zone 104 F
Mobo 107 F
Processor 104 F
PSU 77 F
Maxtor 90 F
WDC 1 84 F
WDC 2 84 F
BIOS v. 0901

Hey

Personally, when a drive starts to need disk checks I would replace the
drive. Vista is more thorough when keeping an eye on the disk so it doesn't
mean much if XP didn't tell you about it.

It's always worth moving to a new disk while the old one is still going.

James

"TheShadow" wrote:

Hi James:

Thank you for reading and responding. The disk check happens in Vista
or in XP. The check is not finding a bad block, it's merely moving a file
from a cluster, that results in orphaning the file, then it rescans the
block, verifies the block is ok, then moves the orphaned file back to the
exact same block. This behavior started immediately after Vista 64bit
Ultimate SP1 was installed.
I believe that the SP1 install and this oddity are related. XP's diskchk and
the Vista version of diskchk both do the exact same thing with the problem.

I have made solid backups of my files in Vista in case of hardware failure
is imminent. I suspect this is not hardware related. Typically when a
hardware failure is about to occur the block would be marked bad, then the
file moved to another block. Then another block would fail and get marked
bad. This file is getting moved off of the block and back to the exact same
block repeatedly.

Given the proliferation of other issues with SP1 I'm grateful this is the
only issue I am experiencing.

Should the disk(s) or the RAID array fail or if I find another solution,
I'll post it to this thread.

"jamesvdm" wrote: