SEATOOLS LONG GENERIC FAIL DRIVERS
SEATOOLS LONG GENERIC FAIL OFFLINE
SEATOOLS LONG GENERIC FAIL WINDOWS

it should be obvious that testing a drive puts more stress on it than actual use. It is Ironic that you did the exact oppisite to what you called 'Obvious'. My advice is to turn back time, do the LAST step FIRST, backup your data and then pound your drive with these tests.

If you view its raw value in hexadecimal, it appears to be reporting 22 (= 0x16) timeouts. This suggests that each unit of health corresponds to about 41 sectors (= 2639 / 64).ДЄttribute BC reports the number of Command Timeouts. In other words, your drive has 2639 bad sectors which have been replaced with spares, and the 'health' of this attribute has dropped from 100 to 36. Think of the normalised values as health scores and the raw values as actual data.

SEATOOLS LONG GENERIC FAIL WINDOWS

Tomorrow this value may fall to 35, in which case either your BIOS or Windows may register a SMART failure. Notice that the Reallocated Sector Count attribute is sitting right on the threshold (36). So why could it still be giving me the Windows HD Error and failing the SeaTools Short DST?ДЄ SMART attribute will be reported as 'OK' until such time as its current value falls below the threshold. There seems to be no problems at all according to HDTune. The Benchmark Test brought back the following: The Error Test brought back the following: (C7) Ultra DMA CRC Error Count 200 200 0 0 Ok

SEATOOLS LONG GENERIC FAIL OFFLINE

(C6) Offline Uncorrectable 100 100 0 0 Ok (C5) Current Pending Sector 100 100 0 0 Ok (05) Reallocated Sector Count 36 36 36 2639 Ok As a precaution, I have ordered an external hard-drive to back up my data on. My computer is running fine and I haven't suffered any data loss. I then decided to run one final chkdsk which again returned no problems. I then ran the Read/Write/Read Test which is designed to discover errors and fix them. I ran the Read Test and it discovered no problems. I did a little bit of research and used a tool called HDAT2 for DOS. I then proceeded to run SeaTools for DOS and it performed the Long Test with no problems but then failed right at the end when it tried to run the Short Test. It's mainly used to control your system fans but it also has a section which checks your drives SMART data and issues an online report about the health of your drive.- SeaTools for Windows v1.2.0.8. What's puzzling tho' is the fact that your scan with SeaTools gave it a pass.ДЄ handy little tool is an app called Speedfan.

SEATOOLS LONG GENERIC FAIL DRIVERS

*** ERROR: Module load completed but symbols could not be loaded for win32k.sysДЇollowup: MachineOwnerThe above bugcheck means the Store encountered an exception and looking at your drivers something odd is going on:Дxgkrnl dxgkrnl.sys Tue Apr 24 08:34:26 2029 (6F900902)Дxgmms2 dxgmms2.sys Fri Apr 21 09:13:25 1989 (244EE2A5)ДЇastfat fastfat.SYS Tue May 17 04:56:00 1977 (0DDE8ED0)ДЇilecrypt filecrypt.sys Tue May 28 09:10:59 2030 (719E1813)ДЄs you can see from the small sample i posted, something is amiss with the dates possibly down to corruption?

*** WARNING: Unable to verify timestamp for win32k.sys Use !analyze -v to get detailed debugging information.Д«ugCheck 154,

Seatools long generic fail