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

BSOD Reformat and New Errors


  • Please log in to reply
10 replies to this topic

#1 Legobot90

Legobot90

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:10 PM

Posted 02 December 2015 - 11:31 AM

Hello there.

 

I have a Windows 7 Vaio Laptop, about 5 years old. I swapped out the Hard Drive about 4 years ago, and this has been my primary computer. Every 6-8 months (or if I get a serious virus,) I reformat my computer - clean out junk files, downloads, installs (one-time only for free-ware, which you just redownload.) And I usually have very few problems when reformatting.

 

This time, I have not been so lucky.

Reformatted Nov 23 (about 9 days ago) and proceeded to install all updates, programs, etc that I could.

Starting Thursday night, I had encountered a BSOD. And it would happen every so often if the wireless was on (Bluetooth and wifi.)

Tried reinstalling drivers, until finally I said "screw it, let me reformat  again - maybe there was a glitch."

 

Last night, I reformatted, and I'm installing updates now.

I get a curious notification (never before seen) about a signed driver. Thinking this was maybe the cause of the BSOD, I Googled it (and found you guys!)

 

Of course, by now, I've already exited the screen with the error, but involved "semav6msr64"

 

Googling that, I find this: http://www.bleepingcomputer.com/forums/t/583646/virus-maybe-in-my-recovery-partition/page-3 and skipped a few steps - GSMart Control has already been run, and I provide the report below.

 

It looks different than what was in the forum post, though I don't know by how much.

Is my hard drive about to fail? Or is the BSOD error coming from a different source, like a bad Bluetooth driver (I've had about 30-40 restarts since the BSOD started.)

Am I on the wrong track?

Help is appreciated.

(YES, I'm already backed up completely, as I just did a reformat)

 

 

Edit: I have the Intel Rapid Storage Technology software, and it is saying that my hard drive status is "normal," and is not displaying any system warnings or errors. I don't know if this is a good indicator, just providing as much info as possible.

Edit2: Seeing as I have not had a BSOD since the reformat last night, I don't have those error codes and have not run the program cited in the sticky.

I do remember that it was a USB_Debug_code or something - the same error I had in March, which I thought was caused by Windows update KB3035583 (which I had prvented from installing to begin with on the first round of reformatting.)

 

 

Basic Health Check passed.

Test results completed without error.

Output is as follows:

 

 

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)] (sf-5.43-1)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MK..65GSX
Device Model:     TOSHIBA MK6465GSX
Serial Number:    Z09GB00QB
LU WWN Device Id: 5 000039 2f9901f2d
Firmware Version: GJ002H
User Capacity:    640,135,028,736 bytes [640 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Dec 02 11:11:52 2015 EST
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:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         (  120) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No 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:      ( 186) 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     0x000b   100   100   011    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   005    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   039    Pre-fail  Always       -       1657
  4 Start_Stop_Count        0x0032   100   100   050    Old_age   Always       -       10594
  5 Reallocated_Sector_Ct   0x0033   100   100   051    Pre-fail  Always       -       1680
  7 Seek_Error_Rate         0x000b   100   100   011    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   005    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   074   074   050    Old_age   Always       -       10756
 10 Spin_Retry_Count        0x0033   253   100   051    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       10591
191 G-Sense_Error_Rate      0x0032   100   100   050    Old_age   Always       -       147
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       45
193 Load_Cycle_Count        0x0032   088   088   050    Old_age   Always       -       129559
194 Temperature_Celsius     0x0022   100   100   034    Old_age   Always       -       34 (Min/Max 2/45)
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       133
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   048    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   050    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   002    Old_age   Always       -       23
222 Loaded_Hours            0x0032   079   079   050    Old_age   Always       -       8752
223 Load_Retry_Count        0x0032   100   100   050    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   034    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   038    Old_age   Always       -       250
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 3
    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 3 occurred at disk power-on lifetime: 3453 hours (143 days + 21 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 38 a8 ec de e3  Error: UNC 56 sectors at LBA = 0x03deeca8 = 64941224

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 78 68 ec de e0 00      00:00:18.677  READ DMA EXT
  25 00 78 68 ec de e0 00      00:00:14.421  READ DMA EXT
  25 00 78 68 ec de e0 00      00:00:10.130  READ DMA EXT
  25 00 78 f0 eb de e0 00      00:00:10.130  READ DMA EXT
  25 00 78 78 eb de e0 00      00:00:10.129  READ DMA EXT

Error 2 occurred at disk power-on lifetime: 3453 hours (143 days + 21 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 38 a8 ec de e3  Error: UNC 56 sectors at LBA = 0x03deeca8 = 64941224

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 78 68 ec de e0 00      00:00:14.421  READ DMA EXT
  25 00 78 68 ec de e0 00      00:00:10.130  READ DMA EXT
  25 00 78 f0 eb de e0 00      00:00:10.130  READ DMA EXT
  25 00 78 78 eb de e0 00      00:00:10.129  READ DMA EXT
  25 00 78 00 eb de e0 00      00:00:10.128  READ DMA EXT

Error 1 occurred at disk power-on lifetime: 3453 hours (143 days + 21 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 38 a8 ec de e3  Error: UNC 56 sectors at LBA = 0x03deeca8 = 64941224

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 78 68 ec de e0 00      00:00:10.130  READ DMA EXT
  25 00 78 f0 eb de e0 00      00:00:10.130  READ DMA EXT
  25 00 78 78 eb de e0 00      00:00:10.129  READ DMA EXT
  25 00 78 00 eb de e0 00      00:00:10.128  READ DMA EXT
  25 00 78 88 ea de e0 00      00:00:10.127  READ DMA EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%       684         -
# 2  Short offline       Completed without error       00%         9         -
# 3  Short offline       Completed without error       00%         5         -

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.

Attached Files


Edited by Legobot90, 03 December 2015 - 02:10 AM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:10 PM

Posted 02 December 2015 - 07:41 PM

Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

Should you have problems with the perfmon report, please disregard it (I don't use it very much anyway).

Should the app lock up for more than 15 minutes while searching for Network information (it does this in my copy of W10), go ahead and kill the app. 
Then navigate to the Documents folder and zip up the 18 reports in the SysnativeFileCollectionApp folder - then upload that with your next post.

If that doesn't work, then you can try this new app (from a friend of mine):  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location.
By default it'll be a .zip file located on your Desktop
Simply upload the .zip file with your next post and we'll move on from there.
***********************************************************************************************************

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Legobot90

Legobot90
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:10 PM

Posted 03 December 2015 - 02:08 AM

BSOD just happened, after all of those nice things...
 
For perfmon, "The Data Collector Set or one of its dependencies is already in use."
 
But, I do have a .ZIP for the sysnative app. It is attached to the first post because I'm incompetent, and can't attach the file in this post.



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:10 PM

Posted 03 December 2015 - 05:57 PM

Only 10 Windows Update hotfixes installed.  Most systems with SP1 have 300 or more.  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ArcSoftKsUFilter.sys        Mon May 25 04:27:31 2009 (4A1A5673)
ArcSoft Magic-i Visual Effect}http://www.arcsoft.com/public/download.asp
http://www.carrona.org/drivers/driver.php?id=ArcSoftKsUFilter.sys
 



Analysis:
The following is for informational purposes only.
**************************Thu Dec  3 01:52:38.887 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\120315-46597-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
System Uptime: 0 days 9:52:28.338
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
Probably caused by : usbhub.sys ( usbhub+12a60 )
BugCheck FE, {8, 6, 5, fffffa8006ab3b20}
BugCheck Info: BUGCODE_USB_DRIVER (fe)
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8006ab3b20, TimeoutContext - PortData
BUGCHECK_STR:  0xFE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub+12a60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
Any drivers in RED should be updated or removed from your system. And should have been discussed in the body of my post.
**************************Thu Dec  3 01:52:38.887 2015 (UTC - 5:00)**************************
ArcSoftKsUFilter.sys        Mon May 25 04:27:31 2009 (4A1A5673)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
HECIx64.sys                 Thu Sep 17 15:54:16 2009 (4AB293E8)
SFEP.sys                    Fri Nov 27 00:39:13 2009 (4B0F6601)
SynTP.sys                   Thu Feb 18 22:36:15 2010 (4B7E072F)
Impcd.sys                   Fri Feb 26 18:32:11 2010 (4B8859FB)
iaStor.sys                  Wed Mar  3 21:51:31 2010 (4B8F2033)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
rimssne64.sys               Wed Mar 24 04:39:31 2010 (4BA9CFC3)
WDKMD.sys                   Wed Mar 31 01:19:47 2010 (4BB2DB73)
RTKVHD64.sys                Tue Apr 27 04:20:13 2010 (4BD69E3D)
risdsne64.sys               Tue May 11 22:06:11 2010 (4BEA0D13)
NETwNs64.sys                Wed Jul 14 07:42:54 2010 (4C3DA2BE)
IntcDAud.sys                Tue Aug 23 09:12:57 2011 (4E53A759)
igdkmd64.sys                Tue Jul 31 13:50:01 2012 (50181AC9)
MpFilter.sys                Fri Sep 13 22:17:40 2013 (5233C744)
http://www.carrona.org/drivers/driver.php?id=ArcSoftKsUFilter.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=SFEP.sys
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
http://www.carrona.org/drivers/driver.php?id=Impcd.sys
http://www.carrona.org/drivers/driver.php?id=iaStor.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=rimssne64.sys
http://www.carrona.org/drivers/driver.php?id=WDKMD.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=risdsne64.sys
http://www.carrona.org/drivers/driver.php?id=NETwNs64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 Legobot90

Legobot90
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:10 PM

Posted 03 December 2015 - 10:28 PM

I've installed whatever it had - it kept saying "no new updates." Stupid system :(

 

And yes, I do have the webcam - I didn't realize it had new drivers. Will update.

In the meantime, I'm leaving the wireless disabled for now, and updating over ethernet.



#6 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:10 AM

Posted 03 December 2015 - 11:04 PM

5 Reallocated_Sector_Ct   0x0033   100   100   051    Pre-fail  Always       -       1680

 

 

Count of reallocated sectors. When the hard drive finds a read/write/verification error, it marks that sector as "reallocated" and transfers data to a special reserved area (spare area). This process is also known as remapping, and reallocated sectors are called "remaps". The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future.[3] While primarily used as a metric of the life expectancy of the drive, this number also affects performance. As the count of reallocated sectors increases, the read/write speed tends to become worse because the drive head is forced to seek to the reserved area whenever a remap is accessed. If sequential access speed is critical, the remapped sectors can be manually marked as bad blocks in the file system in order to prevent their use.

 

This number of allocated bad sectors to a spare area is too high already. https://en.wikipedia.org/wiki/S.M.A.R.T.


Tekken
 


#7 Legobot90

Legobot90
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:10 PM

Posted 04 December 2015 - 04:11 AM

ChkDsk says otherwise...

 

Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 166144 file records processed. File verification completed. 196 large file records processed. 0 bad file records processed. 0 EA records processed. 60 reparse records processed.

 

CHKDSK is verifying indexes (stage 2 of 5)... 215884 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered.

 

CHKDSK is verifying security descriptors (stage 3 of 5)... 166144 file SDs/SIDs processed. Cleaning up 378 unused index entries from index $SII of file 0x9. Cleaning up 378 unused index entries from index $SDH of file 0x9. Cleaning up 378 unused security descriptors. Security descriptor verification completed. 24871 data files processed. CHKDSK is verifying Usn Journal... 35943440 USN bytes processed. Usn Journal verification completed.

 

CHKDSK is verifying file data (stage 4 of 5)... 166128 files processed. File data verification completed.

 

CHKDSK is verifying free space (stage 5 of 5)... 141694783 free clusters processed. Free space verification is complete. Windows has checked the file system and found no problems. 614195199 KB total disk space. 47050220 KB in 119375 files. 79228 KB in 24872 indexes. 0 KB in bad sectors. 286615 KB in use by the system. 65536 KB occupied by the log file. 566779136 KB available on disk. 4096 bytes in each allocation unit. 153548799 total allocation units on disk. 141694784 allocation units available on disk. Internal Info: 00 89 02 00 06 32 02 00 86 33 04 00 00 00 00 00 .....2...3...... 71 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 q...<........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

 

No bad sectors, What gives?



#8 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:10 AM

Posted 04 December 2015 - 04:21 AM

Yes, because they were (sectors) already allocated which in turn would not be reported as bad sectors AFAIK. The Hard drive test would most likely also give the HDD a passed as all faulty and bad sectors are successfully remapped or see previous quote on post #6 for a detailed explanation.


Tekken
 


#9 Legobot90

Legobot90
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:10 PM

Posted 04 December 2015 - 05:48 AM

So, with the hard drive remapping, do I have 6 months? Or fail at any time?

What should I be on the lookout for?
(I just followed the steps for resolving SVCHost.EXE taking up too much processing speed, and my Windows Updates are waiting - 257, less the kb3035583 GWX update.)


Edited by Legobot90, 04 December 2015 - 05:49 AM.


#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:10 PM

Posted 04 December 2015 - 05:51 AM

S.M.A.R.T. is a predictive technology.  What this means is that it monitors certain things are known to be associated with an increased risk of hard drive failure.

What that last sentence actually says is that it's guessing that the hard drive is starting to die.

The point of this technology is so that you can replace the hard drive BEFORE it fails.

 

The predictions may/may not be related to problems that you're having with the hard drive - but they are a warning to you.

They do not predict a specific time-span.  The hard drive can die in the next few minutes, or it could be weeks/months/years.

Regardless of what you choose to do, now is the time to ensure that you have ALL of your data backed up.

That way, should the hard drive suddenly die, you'll already have backup copies of most of your data

 

Good luck!


Edited by usasma, 04 December 2015 - 05:52 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 Legobot90

Legobot90
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:10 PM

Posted 04 December 2015 - 06:08 AM

Thanks - I still have everything backed up on the other drives from when I first reformatted, and have moved some of my more sensitive operations to a slower, though hopefully more reliable, system that can access wireless networks without crashing.

 

Unfortunately, though, I couldn't find the software updates for the camera yet - I'm hoping they'll either be in a windows update, or I can find them tomorrow (20 hours no sleep has been a bit much, and its already 6am here.)

 

I'll let the stuff install and try anew in a few hours.

Thank you for your pointers and support.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users