April 2nd, 2012, 22:19
April 3rd, 2012, 3:25
April 3rd, 2012, 11:15
April 3rd, 2012, 13:29

April 3rd, 2012, 13:30
Vulcan wrote:@northwind,
Agreed![]()
@Zimballa,
In order to try to confirm or deny your new WD disk as the cause of these "freezes", I suggest using read benchmark utilities, in a simplified environment (i.e. not in a virtual machine) - ideally with this disk attached temporarily as a secondary disk to another known-working PC.
As well as doing this then, as northwind said, you should collect the SMART data from the disk (ideally including the raw SMART attribute values too, as collected by HDDScan, for example), as this can sometimes show evidence of an underlying problem (although it cannot always show evidence of marginal i.e. slow-reading, areas), hence the need to use read benchmarks too.
April 3rd, 2012, 14:27
Zimballa wrote:I allready run the utility by WD and everything cameback good and i also ran chkdsk and tha came back good too
Powered by phpBB © phpBB Group.