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 being accessed and screen reset every 4-5 seconds


  • Please log in to reply
9 replies to this topic

#1 pastturner

pastturner

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 20 April 2016 - 04:48 PM

I have a Toshiba Portege Z835-P330 that crashed yesterday on a flight when it ran out of power.  Since then, when it starts, every 4-5 seconds, the desktop will disappear, and reappear.  The hard drive is being accessed every 0.5 seconds or so.  If I want to do anything, e.g., access system recovery, run chkdsk, I have that period or 4-5 seconds to either enter the command or click the icons in which to do so, else the screen goes blank and then the desktop reappears.  Once I get into the chkdsk or system restore screens, I can continue to work, although the screen is disappearing and reappearing in the background.

 

When I ran system restore (after repeated attempts), it fails, saying that it "failed to extract the file c:\Program Files(x86)\intel\opencl sdk\2.0\bin\x86\odcpubackend.dll from the restore point. There

 may be bad sectors on the disk.  Run chkdsk /r)

 

Scan disk says there are no errors with the SSD

 

I also periodically get a message when booting up that there was a failure to connect to the group policy client service.

 

Any help would be appreciated.

 



BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,757 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:34 AM

Posted 21 April 2016 - 12:20 PM

You do not want to run chkdsk /r on a SSD.  You should use the /f switch...  chkdsk /f

 

If you have enough time to set up the chkdsk you should have enough time to run sfc /scannow.

 

 
 
Please run sfc /scannow
 
The sfc /scannow command scans all protected system files and replaces corrupted and incorrect versions with correct Microsoft versions.
 
To open the Command Prompt press the Windows keywindowskey_zps092d5c75.png and the X key at the same time.   A menu will open with the option Command Prompt (Admin), click/tap on this.
 
You will see a window similar to the one below.
 
command%20prompt%20w8_zpsxjmewau9.png
 
When the Elevated Command Prompt opens copy and paste in sfc /scannow, then press Enter.
 
This will take a while,  have patience and allow it finish.  Stopping this scan could damage files.  
 
When the scan is finished please post the log of this scan.
 
To find sfc /scannow log, reopen the Elevated Command Prompt using the Windows key windowskey_zps092d5c75.png and the X key method outlined in the instructions above. 
 
When the Elevated Command Prompt opens copy and paste the following in the Command Prompt, then press Enter.  

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 pastturner

pastturner
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 21 April 2016 - 04:35 PM

Thanks, Arachibutyrophobia.  It's running now.



#4 pastturner

pastturner
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 21 April 2016 - 05:04 PM

Would not run.  It says:

 

Verification 35% complete.  Windows Resource Protection could not perform the requested operation.



#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,757 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:34 AM

Posted 22 April 2016 - 09:09 AM

Please download and run SeatTools for Windows.
 
Before the installation begins you will be prompted to either Decline or Accept the terms of the installation, click on I Accept.
 
Once the installation begins you will see an image similar to the one below.
 
seagate3_zps1fa1f71c.jpg
 
1.  SeaTools for Windows will search for HDDs and SSDs on your computer.  Please remove any external storage devices connected via USB ports.
 
2.  Detected Drives will list the HDDs and SSDs found.  Place a check mark in the drive box you want to run the scan on.
 
3.  You will see Basic Tests above Detected Drives, move the mouse pointer over this.
 
4.  A menu will open with options for the different scans, please click on Long Generic Test
 
5.  This will start the scan.  When the scan is complete you will see the result under Test Status , please post the results in your topic.
 
 seatools4_zpsd7balf76.png
 
6.  The test will indicate either Pass or Fail.  Post the results of the scan in your topic.
 
7.  Click on Help, then click on View Log File.  If the scan failed take a screen shot of the Log File and post it in your topic.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 pastturner

pastturner
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 22 April 2016 - 02:33 PM

Unfortunately it failed.  Log is attached

Attached Files



#7 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,757 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:34 AM

Posted 23 April 2016 - 07:54 AM

It looks like we have found the smoking gun, but please do the following to provide more information.

 

Please download GSmartControl and run it.
 
When GSmartControl opens it scans your computer for all mass storage devices.  When the scan is finished it will display all of the drives found.  Double click on the drive which contains your operating system.
 
In the next window that opens the Identity tab is selected which displays all of the data pertaining to your drive.
 
gsmartcontrol1_zps8bkdopna.png 
 
Click on the Perform Tests tab.  When the next window opens select the Short Self-Test, then click on Execute.
 
When the scan has completed it will show that the drive either passed or failed.  If it failed click on the View Ouput.  Copy the text and paste this in your topic.
 
gsmartcontrol2_zpso1blptuk.png

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#8 pastturner

pastturner
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 23 April 2016 - 10:28 AM

First, let me thank you again for your continued help in this matter.  Your persistence is appreciated and admired.

 

The test failed, as the host reset.

 

The output is:

 

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win8(64)] (sf-5.43-1)

Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Device Model:     M4-CT256M4SSD3

Serial Number:    00000000124903578969

LU WWN Device Id: 5 00a075 103578969

Firmware Version: 04MH

User Capacity:    256,060,514,304 bytes [256 GB]

Sector Size:      512 bytes logical/physical

Device is:        Not in smartctl database [for details use: -P showall]

ATA Version is:   8

ATA Standard is:  ATA-8-ACS revision 6

Local Time is:    Sat Apr 23 11:16:45 2016 EDT

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

 

General SMART Values:

Offline data collection status:  (0x80)            Offline data collection activity

                                                            was never started.

                                                            Auto Offline Data Collection: Enabled.

Self-test execution status:      (  32)    The self-test routine was interrupted

                                                            by the host with a hard or soft reset.

Total time to complete Offline

data collection:                        ( 1190) seconds.

Offline data collection

capabilities:                              (0x7b) SMART execute Offline immediate.

                                                            Auto Offline data collection on/off support.

                                                            Suspend Offline collection upon new

                                                            command.

                                                            Offline surface scan supported.

                                                            Self-test supported.

                                                            Conveyance Self-test supported.

                                                            Selective Self-test supported.

SMART capabilities:            (0x0003)            Saves SMART data before entering

                                                            power-saving mode.

                                                            Supports SMART auto save timer.

Error logging capability:        (0x01)   Error logging supported.

                                                            General Purpose Logging supported.

Short self-test routine

recommended polling time:     (   2) minutes.

Extended self-test routine

recommended polling time:     (  19) minutes.

Conveyance self-test routine

recommended polling time:     (   3) minutes.

SCT capabilities:                (0x003d)  SCT Status supported.

                                                            SCT Error Recovery Control supported.

                                                            SCT Feature Control supported.

                                                            SCT Data Table supported.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate     0x002f   100   100   050    Pre-fail  Always       -       455

  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       20480

  9 Power_On_Hours          0x0032   100   100   001    Old_age   Always       -       5701

 12 Power_Cycle_Count       0x0032   100   100   001    Old_age   Always       -       4858

170 Unknown_Attribute       0x0033   100   100   010    Pre-fail  Always       -       5

171 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       0

172 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       0

173 Unknown_Attribute       0x0033   096   096   010    Pre-fail  Always       -       120

174 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       75

181 Program_Fail_Cnt_Total  0x0022   100   100   001    Old_age   Always       -       8353750844735

183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       1

184 End-to-End_Error        0x0033   100   100   050    Pre-fail  Always       -       0

187 Reported_Uncorrect      0x0032   100   100   001    Old_age   Always       -       68071

188 Command_Timeout         0x0032   100   100   001    Old_age   Always       -       0

189 High_Fly_Writes         0x000e   100   100   001    Old_age   Always       -       86

194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       0

195 Hardware_ECC_Recovered  0x003a   100   100   001    Old_age   Always       -       84725

196 Reallocated_Event_Count 0x0032   100   100   001    Old_age   Always       -       5

197 Current_Pending_Sector  0x0032   100   100   001    Old_age   Always       -       0

198 Offline_Uncorrectable   0x0030   100   100   001    Old_age   Offline      -       0

199 UDMA_CRC_Error_Count    0x0032   100   100   001    Old_age   Always       -       0

202 Data_Address_Mark_Errs  0x0018   096   096   001    Old_age   Offline      -       4

206 Flying_Height           0x000e   100   100   001    Old_age   Always       -       0

 

SMART Error Log Version: 1

Warning: ATA error count 0 inconsistent with error log pointer 3

 

ATA Error Count: 0

            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 0 occurred at disk power-on lifetime: 5701 hours (237 days + 13 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

  -- -- -- -- -- -- --

  00 50 40 f0 b4 cc 40   at LBA = 0x00ccb4f0 = 13415664

 

  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 90 40 ca b4 cc 40 00  38d+17:24:50.816  READ FPDMA QUEUED

  ec 00 01 00 00 00 a0 00  38d+17:24:50.816  IDENTIFY DEVICE

  b0 d0 01 00 4f c2 a0 00  38d+17:24:50.816  SMART READ DATA

  ec 00 01 00 00 00 a0 00  38d+17:24:50.816  IDENTIFY DEVICE

  ef 90 03 00 00 00 a0 00  38d+17:24:50.816  SET FEATURES [Reserved for Serial ATA]

 

Error -1 occurred at disk power-on lifetime: 5701 hours (237 days + 13 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

  -- -- -- -- -- -- --

  00 50 40 f0 b4 cc 40   at LBA = 0x00ccb4f0 = 13415664

 

  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 02 40 ca b4 cc 40 00  38d+17:24:50.816  READ FPDMA QUEUED

  ef 90 03 00 00 00 a0 00  38d+17:24:50.816  SET FEATURES [Reserved for Serial ATA]

  ef 02 00 00 00 00 a0 00  38d+17:24:50.816  SET FEATURES [Enable write cache]

  60 00 40 ca b4 cc 40 00  38d+17:24:50.816  READ FPDMA QUEUED

  ef 90 03 00 00 00 a0 00  38d+17:24:50.816  SET FEATURES [Reserved for Serial ATA]

 

Error -2 occurred at disk power-on lifetime: 5701 hours (237 days + 13 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

  -- -- -- -- -- -- --

  00 50 40 f0 b4 cc 40   at LBA = 0x00ccb4f0 = 13415664

 

  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 00 40 ca b4 cc 40 00  38d+17:24:50.816  READ FPDMA QUEUED

  ef 90 03 00 00 00 a0 00  38d+17:24:50.816  SET FEATURES [Reserved for Serial ATA]

  ef 02 00 00 00 00 a0 00  38d+17:24:50.816  SET FEATURES [Enable write cache]

  60 da 40 ca b4 cc 40 00  38d+17:24:50.816  READ FPDMA QUEUED

  ea 00 00 00 00 00 e0 00  38d+17:24:50.816  FLUSH CACHE EXT

 

Error -3 occurred at disk power-on lifetime: 5701 hours (237 days + 13 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

  -- -- -- -- -- -- --

  00 50 40 f0 b4 cc 40   at LBA = 0x00ccb4f0 = 13415664

 

  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 da 40 ca b4 cc 40 00  38d+17:24:50.816  READ FPDMA QUEUED

  ea 00 00 00 00 00 e0 00  38d+17:24:50.816  FLUSH CACHE EXT

  61 02 20 f0 bc 66 40 00  38d+17:24:50.816  WRITE FPDMA QUEUED

  61 02 40 08 1a f9 40 00  38d+17:24:50.816  WRITE FPDMA QUEUED

  61 02 20 60 a7 c6 40 00  38d+17:24:50.816  WRITE FPDMA QUEUED

 

Error -4 occurred at disk power-on lifetime: 5701 hours (237 days + 13 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

  -- -- -- -- -- -- --

  00 50 40 f0 b4 cc 40   at LBA = 0x00ccb4f0 = 13415664

 

  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 02 40 ca b4 cc 40 00  38d+17:24:50.816  READ FPDMA QUEUED

  61 90 08 68 07 eb 40 00  38d+17:24:50.816  WRITE FPDMA QUEUED

  61 02 08 00 74 6c 40 00  38d+17:24:50.816  WRITE FPDMA QUEUED

  ea 00 00 00 00 00 e0 00  38d+17:24:50.816  FLUSH CACHE EXT

  61 00 08 70 bc 66 40 00  38d+17:24:50.816  WRITE FPDMA QUEUED

 

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline       Interrupted (host reset)      00%      5701         -

# 2  Short offline       Interrupted (host reset)      00%      5701         -

 

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.

 

 

Whose hand holds the smoking gun, Monsieur Poirot?

Attached Files



#9 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,757 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:05:34 AM

Posted 23 April 2016 - 11:15 AM

It looks like the drive is failing.  I would backup all of your important data to removable media.

 

If this drive is still under warranty you should contact the manufacturer to get a new drive.

 

If it isn't... time to purchase another drive.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#10 pastturner

pastturner
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:08:34 AM

Posted 23 April 2016 - 03:53 PM

Fortunately I had gotten the important data off the harddrive when it started having problems!

 

Thanks for your help on this.  Helps to know what the problem is caused by.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users