Weird Hard Drive Issues

[dhkatz]

Hello everyone, I have recently been having a lot of hard drive issues that are now mostly resolved. However one thing still puzzles me.

 

The pictures below are both of my hard drives. One a WD Black 2TB that is less that 6 months old, and the other an almost 4 year old Seagate 2TB.

 

If you were to just glance, you would think the Seagate was causing the problems. I mean look at those speeds.

 

However, it was the WD giving me the BSOD for the past few days. Yes it is under warranty, but I do not understand how that Seagate can still be going now that I see that benchmark.

 

I mean look at those speeds. 24 MB/s! That is horrible yet the drive has lasted longer than the WD and its speed looks fine.

 

First image: Seagate 2 TB, almost 4 years old

 

 

 

2nd Picture: WD Black 2 TB, less than 6 months old. Causing the BSOD. Will RMA

 

[Enderman]

Have you defragged your seagate drive?

[dhkatz]

Have you defragged your seagate drive?

 

No, not recently. However I just did a frag analysis and it is only 10% fragged.

[Tschloken]

Have you checked the SMART outputs of both drives? The read error rate on the WD drive looks a bit high, but I'm no expert.

 

FYI though, I'm running 5 5-year old HDD's and they are all running fine, a bit loud, but fine.

[dhkatz]

Have you checked the SMART outputs of both drives? The read error rate on the WD drive looks a bit high, but I'm no expert.

 

FYI though, I'm running 5 5-year old HDD's and they are all running fine, a bit loud, but fine.

 

Could you tell me how I would go about doing that?

[Tschloken]

Go here: http://www.howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying/

 

and scroll down to  "Checking S.M.A.R.T. Without Third-Party Tools"

 

Can you then please reply with the output.

[dhkatz]

 

Go here: http://www.howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying/

 

and scroll down to  "Checking S.M.A.R.T. Without Third-Party Tools"

 

Can you then please reply with the output.

 

"Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation.  All rights reserved.

 

C:\Windows\system32>wmic

wmic:root\cli>diskdrive get status

Status

OK

 

wmic:root\cli>"

[Tschloken]

ok, now that is interesting as I'm fairly sure there should be 2 'OK' 's there. One for each drive.I suggest you call WD and see what they say.

[Tschloken]

I got 8 OK messages when I ran it. One OK for each partition.

[dhkatz]

I only have one partition, again this is the Seagate drive. The WD has failed and is being RMA'd. Seagate is out of warranty.

 

Edit: Well just blue screened with this drive that I thought was fine. Although, the reason for blue screen may not be the drive in this case. Here are crash logs:

 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 9/13/2014 6:49:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-31137-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8014E5A300, 0xFFFFFA8014E5A410, 0x4110008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/13/2014 6:49:20 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: winfladrv.sys (WinFLAdrv+0x263C)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8014E5A300, 0xFFFFFA8014E5A410, 0x4110008)
Error: BAD_POOL_HEADER
file path: C:\Windows\SysWOW64\WinFLAdrv.sys
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: winfladrv.sys .
Google query: winfladrv.sys BAD_POOL_HEADER

Edited September 13, 2014 by MCiLuZiioNz

[Enderman]

No, not recently. However I just did a frag analysis and it is only 10% fragged.

That's quite a bit. Defrag it and rerun the speed test.

[PaulKolby]

i think partly its a four year old  drive so it is not as good as a 2014-2013 even if they were both brand new but u should defragment the hardrive anyway

[dhkatz]

i think partly its a four year old  drive so it is not as good as a 2014-2013 even if they were both brand new but u should defragment the hardrive anyway

 

I have drives in another computer that are 6 years old and still running full speed.

 

That's quite a bit. Defrag it and rerun the speed test.

 

I guess I'll try that, I've had drives 25% fragged and run way better.

 

Edit: Defragged and ran SeaTools to do any repairs. Not sure what fixed it but I am back at 150 MB/s speed. Thanks everyone. Still would like to know about my bluescreen though that I posted above. I don't know what that was about.

Edited September 13, 2014 by MCiLuZiioNz