Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Hard drive Failure?


  • Please log in to reply
5 replies to this topic

#1 panamint

panamint

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:08:26 AM

Posted 30 December 2014 - 09:42 AM

I have been having BSOD and hang ups and browser hijacking and thought it was Malware problem, but after working with the Malware Response Team here he says I might have a hard drive failure. How do I check for that? 

 

HP G71 Laptop running Widows 7 Home Premium 

Drive info WDC-WD3200BEVT 602ZCT1 ATA DEVICE

Thanks

Scott



BC AdBot (Login to Remove)

 


#2 Sintharius

Sintharius

    Bleepin' Sniper


  • Members
  • 5,639 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:The Netherlands
  • Local time:02:26 PM

Posted 30 December 2014 - 09:54 AM

You can use SeaTools for Windows.

I recommend you backing up all important data before testing.

The Long Generic Test is best at determining if your hard drive is on its way out.

The DOS version has the option of attempting to repair the damage - but be warned, if the repair fails it'll destroy your hard drive.

Edited by Alexstrasza, 30 December 2014 - 09:54 AM.


#3 panamint

panamint
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:08:26 AM

Posted 30 December 2014 - 10:09 AM

Can I run it without the repair option to find out if the drive has a problem and keep the data safe.



#4 JohnC_21

JohnC_21

  • Members
  • 24,301 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:26 AM

Posted 30 December 2014 - 10:21 AM

After running the long test, Seatools for DOS gives you the option to skip any repairs. You can run the short test first which does not take that long to get an idea if the drive is failing. It will come up pass or fail. If it passes then you can do the long test. If the short test fails then there is no need to do the long test unless you want to repair any bad sectors.

 

Seatools for DOS tutorial

 

You can also download the portable version of GsmartControl (nothing to install). Download the zip version.  Unzip the files to a folder and double click the exe file. Run the short test and post the logs.

 

info_failing.png



#5 panamint

panamint
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:08:26 AM

Posted 30 December 2014 - 10:48 AM

I hope this is what you wanted

Complete error log:
 
SMART Error Log Version: 1
ATA Error Count: 31635 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
 
Error 31635 occurred at disk power-on lifetime: 37281 hours (1553 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 cf 61 66 40  Error: WP at LBA = 0x006661cf = 6709711
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 01 28 b8 02 9a 00 00      01:42:33.727  WRITE FPDMA QUEUED
  61 20 28 00 2b 36 12 00      01:42:33.726  WRITE FPDMA QUEUED
  60 20 38 c0 e2 09 00 00      01:42:33.719  READ FPDMA QUEUED
  61 07 38 80 75 93 00 00      01:42:33.717  WRITE FPDMA QUEUED
  61 20 38 e0 2a 36 12 00      01:42:33.717  WRITE FPDMA QUEUED
 
Error 31634 occurred at disk power-on lifetime: 37281 hours (1553 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 cf 61 66 40  Error: UNC at LBA = 0x006661cf = 6709711
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 38 80 75 93 00 00      01:42:30.495  READ FPDMA QUEUED
  60 40 30 60 41 a6 03 00      01:42:30.495  READ FPDMA QUEUED
  60 20 28 a0 02 9a 00 00      01:42:30.495  READ FPDMA QUEUED
  60 20 20 e0 e4 10 00 00      01:42:30.495  READ FPDMA QUEUED
  60 00 18 00 61 66 00 00      01:42:30.495  READ FPDMA QUEUED
 
Error 31633 occurred at disk power-on lifetime: 37281 hours (1553 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 cf 61 66 40  Error: UNC at LBA = 0x006661cf = 6709711
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 f8 80 75 93 00 00      01:42:27.178  READ FPDMA QUEUED
  61 13 f0 08 3b a5 00 00      01:42:27.178  WRITE FPDMA QUEUED
  61 20 e8 c0 2a 36 12 00      01:42:27.176  WRITE FPDMA QUEUED
  60 40 e0 60 41 a6 03 00      01:42:27.173  READ FPDMA QUEUED
  61 08 d8 40 41 a6 03 00      01:42:27.172  WRITE FPDMA QUEUED
 
Error 31632 occurred at disk power-on lifetime: 37281 hours (1553 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 cf 61 66 40  Error: WP at LBA = 0x006661cf = 6709711
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 38 50 68 36 66 00 00      01:42:23.834  WRITE FPDMA QUEUED
  61 20 50 c0 29 36 12 00      01:42:23.833  WRITE FPDMA QUEUED
  60 20 48 c0 e8 65 18 00      01:42:23.808  READ FPDMA QUEUED
  61 08 10 08 e6 65 18 00      01:42:23.808  WRITE FPDMA QUEUED
  61 20 10 a0 29 36 12 00      01:42:23.806  WRITE FPDMA QUEUED
 
Error 31631 occurred at disk power-on lifetime: 37281 hours (1553 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 cf 61 66 40  Error: UNC at LBA = 0x006661cf = 6709711
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 70 80 ba e9 01 00      01:42:20.282  READ FPDMA QUEUED
  61 08 68 d0 fd 92 00 00      01:42:20.282  WRITE FPDMA QUEUED
  61 20 60 80 29 36 12 00      01:42:20.281  WRITE FPDMA QUEUED
  60 20 58 20 41 a6 03 00      01:42:20.262  READ FPDMA QUEUED
  61 08 58 00 41 a6 03 00      01:42:20.262  WRITE FPDMA QUEUED
 
 
 
Complete selective self-test log:
 
SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


#6 Sintharius

Sintharius

    Bleepin' Sniper


  • Members
  • 5,639 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:The Netherlands
  • Local time:02:26 PM

Posted 30 December 2014 - 10:52 AM

That would mean read/write error... which indicates that there are problems with your hard drive.

I would recommend you to get a new one, and backup your data regularly if for some reasons you can't get a new HDD right away.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users