Latitude E6410 drive error

mididoc

Well-Known Member
Hi Martin,

hope you're well.

I have a problem with my Dell Latitude E6410.

I use HWinfo64 v5.06-2640.

In System Summary I see a red mark beside the Sata drive, which is a Western Digital WD 2500BEKT.
If I use Western Digital own diagnostic tool, they report no error.

I use intel rapid storage driver, which caused also problems in my other computers in older HWinfo versions.
But this was successfully repaired from you.

So this could also perhaps be the problem here in the dell computer.
just an idea.

btw.
also in the sensor window i see red Yes beside Smart / Drive failure column.

thanks for your advice.

cheers
 
Please locate the drive in the main HWiNFO window (might need to disable Sensors-only mode if enabled) and post a screenshot of the SMART section.
 
Hi Martin,

thanks for your reply.

attach screenshot

cheers

[attachment=1776]
 

Attachments

  • Bild1.jpg
    Bild1.jpg
    239.3 KB · Views: 4
Hi Martin,

understand.

attach screenshots.

cheers

[attachment=1778]

[attachment=1779]

[attachment=1780]
 

Attachments

  • Bild1.jpg
    Bild1.jpg
    278.5 KB · Views: 2
  • Bild2.jpg
    Bild2.jpg
    290.4 KB · Views: 2
  • Bild3.jpg
    Bild3.jpg
    335.7 KB · Views: 5
Here the other programs.

cheers

[attachment=1781]

[attachment=1782]
 

Attachments

  • Bild1.jpg
    Bild1.jpg
    196 KB · Views: 3
  • Bild2.jpg
    Bild2.jpg
    202.3 KB · Views: 3
As you can see, the "G-Sense Error Rate" parameter has crossed the critical threshold value - actual value is 1, but the threshold set it 50 (lower means worser).
So it seems the drive experienced a strong shock that exceeded the design limits. That's why HWiNFO reports this as a failure.
Those other tools probably don't evaluate particular parameters. You might try to check with CrystalDiskInfo for example or in the WD Data LifeGuard check detailed SMART information.
 
this is smart from western digital lifeguard diagnostics.

cheers

[attachment=1787]

[attachment=1788]
 

Attachments

  • 1.jpg
    1.jpg
    120.8 KB · Views: 3
  • 2.jpg
    2.jpg
    122.1 KB · Views: 2
Well, this is interesting. It seems that HWiNFO reads the threshold values wrong and that's why it thinks that parameter is a failure.
Please attach the HWiNFO Debug File for analysis. Also using CrystalDiskInfo please do Copy (Ctrl-C) and paste the data here.
 
Back
Top