Dying 150GB Raptor?

[JBNimble]

How about software slowdown?

If you have Zone Alarm, for example, shut it down and see what happens. If this makes you nervous, first disconnect from the Internet.

[Baud]

With the WD diagnostic tool, you have more tests than the smart status one.
I had trouble with a raptor 150 too, and while the smart status test was OK, the quick test revealed a read error. So I got my disk exchanged by the vendor.

Test Option: QUICK TEST
Model Number: WDC WD1500ADFD-00NLR5
Unit Serial Number: WD-WMAP41967563
Firmware Number: 21.07QR5
Capacity: 150.04 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 06-Quick Test on drive 3 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 65 (Error Log Test) SMART self-test did not complete on drive 3!
Test Time: 12:29:34, July 15, 2008

[sammy2066]

Originally Posted by Baud

With the WD diagnostic tool, you have more tests than the smart status one.
I had trouble with a raptor 150 too, and while the smart status test was OK, the quick test revealed a read error. So I got my disk exchanged by the vendor.

Test Option: QUICK TEST
Model Number: WDC WD1500ADFD-00NLR5
Unit Serial Number: WD-WMAP41967563
Firmware Number: 21.07QR5
Capacity: 150.04 GB
SMART Status: PASS
Test Result: FAIL
Test Error Code: 06-Quick Test on drive 3 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 65 (Error Log Test) SMART self-test did not complete on drive 3!
Test Time: 12:29:34, July 15, 2008

I did the WD Diagnostic ... but I did not get any errors on the Quick Test.

[sammy2066]

Bummer ... My Raptor was 34c .. and now suddenly it has jumped to 41c.

I need help on imaging my drive. How should I proceed?

[ctal]

Originally Posted by sammy2066

Bummer ... My Raptor was 34c .. and now suddenly it has jumped to 41c.

I need help on imaging my drive. How should I proceed?

Install the Hitachi as a second hard drive; format it if necessary; read the thread I linked to that talks about imaging programs; select one; and go to it, creating the image on the second drive!

Regards,
-- Al

[sammy2066]

Al,

I just noticed something weird. CPU-Z and Everest were reporting the CPU Voltage as 2.240v! In the BIOS it was set to Auto. But now I manually set it to 1.2v.

Windows Explorer is opening INSTANTLY now. All the symptoms seem to have disappeared! How could this be?

EDIT:

Everest still shows CPU vCore as 2.24v and so does CPU-Z. *** is going on??

And for some reason, Everest is not showing my CPU temps!

[ctal]

Originally Posted by sammy2066

Al,

I just noticed something weird. CPU-Z and Everest were reporting the CPU Voltage as 2.240v! In the BIOS it was set to Auto. But now I manually set it to 1.2v.

Windows Explorer is opening INSTANTLY now. All the symptoms seem to have disappeared! How could this be?

EDIT:

Everest still shows CPU vCore as 2.24v and so does CPU-Z. *** is going on??

And for some reason, Everest is not showing my CPU temps!

Not sure. Did CPU-Z and Everest provide reasonable readings in the past, or did you just start using them since the problem appeared? What kind of mobo and cpu do you have?

-- Al

[sammy2066]

Originally Posted by ctal

Not sure. Did CPU-Z and Everest provide reasonable readings in the past, or did you just start using them since the problem appeared? What kind of mobo and cpu do you have?

-- Al

Yeah, the readings were fine with Vista. I have a Striker Extreme with the latest BIOS and an Intel C2D E6600. Everything is running at stock. I have the vCore manually set to 1.20v. I'm soo bummed. The thing just crashed again sometime back. I'm soo bummed. ActiveSMART says the HDDs are fine.

[ctal]

I'm thinking that the 2.24V indication might have been just a reporting/monitoring problem, that was an additional symptom of whatever the underlying problem is. You could try going back to auto, verifying that you again see 2.24V, and checking the core temperature to get a rough feel for what Vcore is really doing.

I'm thinking also that the problem could be unrelated to the cpu, but somehow still sensitive to cpu voltage (which would have subtle effects on waveforms and timings of signals on the fsb, for instance). Did you run Memtest86+ to check your memory, as I suggested? If not, Google that term and you'll quickly find it. It runs from a bootable cd or floppy.

-- Al

[sammy2066]

Originally Posted by ctal

I'm thinking that the 2.24V indication might have been just a reporting/monitoring problem, that was an additional symptom of whatever the underlying problem is. You could try going back to auto, verifying that you again see 2.24V, and checking the core temperature to get a rough feel for what Vcore is really doing.

I'm thinking also that the problem could be unrelated to the cpu, but somehow still sensitive to cpu voltage (which would have subtle effects on waveforms and timings of signals on the fsb, for instance). Did you run Memtest86+ to check your memory, as I suggested? If not, Google that term and you'll quickly find it. It runs from a bootable cd or floppy.

-- Al

Well, it was on auto and the voltage was wrong. It's still wrong.

[ctal]

Originally Posted by sammy2066

Well, it was on auto and the voltage was wrong. It's still wrong.

Yes, but what is the core temperature when you are reading 2.24V? If it's a reasonable number, then it tells us that the reporting/monitoring of the voltage is wrong, and the actual voltage is probably ok. Although if it is ok, it could be a little different than what you manually set to, and that difference could be bringing out the real problem which could be unrelated to the cpu (such as memory).

-- Al

[sammy2066]

Well, Everest is not showing the CPU temperature for some reason. What else can I use to monitor CPU temps?

[sammy2066]

SpeedFan Output .... Bummer ...

[ctal]

Real Temp - CPU temperature monitoring (monitors core temps)

SpeedFan - Access temperature sensor in your computer (monitors case temp and core temps, but may not be as accurate as realtemp without configuration/calibration)

Core Temp (I haven't used it)

Also, the bios probably provides an indication of temperature, which I think would be case temperature (which is not as significant as core temperature).

-- Al

[ctal]

Originally Posted by sammy2066

SpeedFan Output .... Bummer ...

Yes, SpeedFan typically needs to be configured to what and how the specific mobo reports. Without configuration it will report all kinds of nonsense values, as explained in their faq. I suspect that the Temp 1 and Temp 2 readings are legitimate core temp values, which look reasonable. See if Realtemp agrees, and if so I think you could conclude that there is nothing grossly wrong with Vcore.

-- Al