Re: Critical Error On Disk (Port SATA 0.0)

Al Kaufmann wrote:
> I am running Vista Home Premium 64 bit and I have started to get
> system error messages - "Access Failure - Critical Error On Disk
> ST380815AS (Port Sata 0.0) Nvidia Stripping ..." It is a parity
> error on one the the hard drives used in my raid setup.
>
> I have used a Seagate DOS utility to test the hard drive and it passed
> all the tests. I have run Windows Checkdsk on the hard drive and
> again, no problem was found. Also I am using the approved latest
> drivers from Nvidia.
>
> If anyone knows what is happening here and the fix, please let me
> know.
> Thanks,
> Al
>


Al, I don't know much about RAID etc but have seen similar "Hardware"
errors caused by failing memory modules. Might be worth leaving memory
test to run for a few hours just to see before taking things apart. Have
at least 2 machines on which bad memory caused all manner of apparently
hardware related errors, maybe because "Timing" is very critical. Sorry
if this does no good, but it's easier than tearing out the drives (and
handfuls of hair)...

Charlie

Al Kaufmann wrote:
> On Sat, 24 Jan 2009 20:57:06 -0600, Charlie Tame <>
> wrote:
>
>> Al Kaufmann wrote:
>>> I am running Vista Home Premium 64 bit and I have started to get
>>> system error messages - "Access Failure - Critical Error On Disk
>>> ST380815AS (Port Sata 0.0) Nvidia Stripping ..." It is a parity
>>> error on one the the hard drives used in my raid setup.
>>>
>>> I have used a Seagate DOS utility to test the hard drive and it passed
>>> all the tests. I have run Windows Checkdsk on the hard drive and
>>> again, no problem was found. Also I am using the approved latest
>>> drivers from Nvidia.
>>>
>>> If anyone knows what is happening here and the fix, please let me
>>> know.
>>> Thanks,
>>> Al
>>>
>>
>> Al, I don't know much about RAID etc but have seen similar "Hardware"
>> errors caused by failing memory modules. Might be worth leaving memory
>> test to run for a few hours just to see before taking things apart. Have
>> at least 2 machines on which bad memory caused all manner of apparently
>> hardware related errors, maybe because "Timing" is very critical. Sorry
>> if this does no good, but it's easier than tearing out the drives (and
>> handfuls of hair)...
>>
>> Charlie
>
> Thanks for that suggestion, I don't think it is my memory but it did
> lead me to another idea. I did check out the memory with Memtest86
> and all is fine there, it is even running slower than rated. The CPU
> is another matter, I have it overclocked from 2.5GHz to 2.7GHz and I
> thought it was running fine at that speed. :-( I set the bios back to
> AUTO and after running a few things, so far so good. Guess I will
> need to bump up the core voltage and run a cpu test program before I
> do that again.
>
> Thanks again for the suggestion.
> Al
>


Good, hope that helps others too. Any idea if the ambient temperature
might have changed and caused the problem to show up? I suppose also
that with the recent weather (Speaking from here in Iowa - no idea where
you are) the load on the electricity supply may have caused the voltage
to vary a little.