Well I thought this problem was solved when I removed two programs and
did not get any messages from Vista to run CHKDSK due some problem.
All was running fine for six days. However, again this morning Vista
requested that CHKDSK be run due to some file problem. No errors were
reported and I am running ok right now. I am waiting for Western
Digital to send me my replacement for my Raptor 150GB drive. We will
continue as is for now. My plan is to fall back to April 12 image
first and if the problem continues then back to April 4. Those are
two images that I believe were clean before this crazy thing occurred.
I am sure it is not hardware since originally the Raptor was my c
drive. With the Raptor returned to Western Digital I am using a
Seagate 300 GB as my c drive. Due to Western Digital inventory
problems the replacement drive will not be here of another week. I
had filled out an advanced RMA request on April 18.
If anyone has suggestions for the solution of this problem please post
your ideas.
Thanks,
On Sun, 19 Apr 2009 19:34:44 -0700,
wrote:
>Guest or anyone,
>
>Could all of my problems be due to a disc controller problem. I have
>tried now three routines from Microsoft Bootrec.exe tool in the
>Windows Recovery Environment to repair this problem to no avail. My
>initial drive was bad due to a servo problem and is now heading back
>to WD. My c drive is now a Seagate 300GB drive but it is having the
>same CHKDSK problems but not the servo problems from both the WD and
>Seagate diagnostics.
>
>Does anyone have a program that could test the disc controller on the
>MB to see if that is the culprit? If someone has such a program or
>utility could you please post so I can determine if my disc controller
>chip is bad.
>
>My MB is a Gigabyte GA-P35c-DS3R with BIOS Award F11 07/10/2008.
>
>Thanks.
>
>oldman
>
>On Sun, 19 Apr 2009 13:26:31 -0700, wrote:
>
>>Hi guest,
>>
>>I followed your suggestion and ran WD's disk diagnostics program
>>against the drive. The test yielded the following: the short test
>>which checks the SMART data and the servo alignment failed. The long
>>test passed in that all of the data on the drive was ok. I next moved
>>the data from my D drive to my E drive. I then formatted the D drive
>>to ensure it was cleaned off. Next I used Acronis and cloned the C
>>drive to the D drive. Changed the BIOS so that the old D became the C
>>boot drive. I then removed the old C drive. The old C drive is to be
>>RMA 'd back to WD.
>>
>>Now here is what is strange on the next reboot with the bad C removed
>>I got the same error message requesting the run of CHKDSK on the new
>>"C" drive. The CHKDSK procedure finished without finding any errors.
>>As a further check I ran the WD diagnostics on the new "C" drive and
>>the short servo test and the data tests completed ok, no problems. Now
>>the new "C" is a Seagate drive. As a further check I ran Seagate's
>>diagnostics long and short on the drive and both finished ok that is
>>no problems reported.
>>
>>My question is did my cloning copy the problems from the old drive to
>>the new drive relative to the servo positioning? Would it be better
>>to do a full image restore with Acronis?
>>
>>All ideas appreciated. If more info needed please ask. I need to
>>solve this problem.
>>
>>
>>Thanks ,
>>
>>oldman
>>
>>
>>On Sat, 18 Apr 2009 16:33:27 -0500, beauparc <>
>>wrote:
>>
>>>
>>>oldman;1022968 Wrote:
>>>> Here is my situation and I do not know what is the cause.
>>>>
>>>> In the past week four out of five times when I boot up my Vista
>>>> computer after the initial post Vista is invoked. During the boot
>>>> process the program wants to run CHKDSK because it says there is some
>>>> problem on my c drive. Chkdsk goes through all steps and when done
>>>> and reports the status of what it did it reports no bad sectors,
>>>> nothing being repaired. Vista then restarts and then goes as though
>>>> there were no problems.
>>>>
>>>> The next time I boot up if on the same day it will usually not request
>>>> to run chkdsk. However, after the PC has been shut down for a period
>>>> and then booted up CHKDSK will then again be run unless I abort the
>>>> process.
>>>>
>>>>
>>>> Can some one please tell me what might be causing this problem and how
>>>> to permanently fix it. If you need more information to help me please
>>>> respond accordingly.
>>>>
>>>> Thanks,
>>>> oldman
>>>
>>>
>>>Certainly the first thing to do is a complete backup of your drive
>>>preferably to an external HDD, just in case the worst happens.
>>>
>>>Next, go to the disk maker's website and download their disk diagnosis
>>>tool. Run it, see what it says and take it from there.
Similar Threads
Linear Mode
