Hard drive tools (Spinrite, HD Tune, Seatools) showing different size than Explorer

Zach_57 · Apr 11, 2017

I am running three drives on a fresh Windows 10 install: an internal SSD, a 2 TB WD external USB drive, and a 3 TB Seagate USB drive. I've started installing games to the 4 TB drive, and noticed that the few I've tested have a tendency to crash, including inducing a couple BSODs. That lead me to investigate to see if there are hard drive or memory problems.

Memtest shows there are no issues with the ram.

Spinrite shows an error, invalid partition for drive size for the Seagate.

HD Tune shows that 100% of the blocks on the Seagate drive are damaged, has a read error when attempting to benchmark, and indicates the drive capacity is only 375 GB.

Seatools tests all run fine, but the information shows that the Seagate drive only has a capacity of 375GB.

Meanwhile, all of the Windows system tests (Disk Check, explorer error checking) come back clean, Explorer shows the proper capacity of 3TB, all of the files I test seem to work. Looking at it in Diskpart shows the proper disk size and partition size. The partition table shows Partition 1 is Reserved, is 128 MB and has an Offset of 24 KB, Partition 2 is Primary, the Size is 2794 GB (same size as drive) and the Offset is 129 MB.

My searches have come up empty and I'm completely stumped on this one, and would greatly appreciate any feedback.

UPDATE: Looking back in Seatools, it shows four drives when there are only three. A SAS-SCSI labeled Expansion (this is what the Seagate USB drive is labeled), the SSD, the WD, and then an unlabeled USB drive showing (the Seagate) showing the correct capacity.

Colif · Apr 12, 2017

i would be inclined to believe the tools over windows, so I would suggest backing up anything on 3tb drive before you lose anything.

can you share some screenshots of seatools results? SMART scores might be a good place to start.

Do you remember what BSOD you got? download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do

Zach_57 · Apr 12, 2017

Colif :

Thanks for your help! Here is a link to some Seatools screens - http://imgur.com/a/VutRu? Unfortunately it doesn't give detailed results of tests, just shows that it passed.

Here is some more info I was able to dig up. 1) I updated the BIOS, that isn't it. 2) I noticed in the BIOS that the Seagate does not appear as a bootable drive, but it is listed in the USB list as one of the mass storage devices (along with the 2TB drive and a flash drive I had in). The SSD, flash drive, and 2TB USB all appeared as bootable drives. 3) This drive is roughly three years old. I read in other forums (such as: http://www.tomshardware.com/forum/274015-32-external-usb3-drive-shows-devices) that there were problems back then with drives of this size and the way they were formatted (MBR v UEFI). It's been three years since I initially formatted it, so I can't recall what tool I used or what parameters, and it all shows up as a single drive in Windows 10, but could that be a potential problem?

and for good measure here is the WhoCrashed log. I already updated the network driver that the report flags.

On Tue 4/11/2017 10:09:20 PM your computer crashed
crash dump file: C:\Windows\Minidump\041117-4328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xC2 (0x7, 0x206C644D, 0xD0017, 0xFFFFBA870D6D1CE0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 4/11/2017 10:09:20 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rtwlanu.sys (rtwlanu+0x43487)
Bugcheck code: 0xC2 (0x7, 0x206C644D, 0xD0017, 0xFFFFBA870D6D1CE0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\rtwlanu.sys
product: Realtek WLAN Wireless USB 2.0 Adapter
company: Realtek Semiconductor Corporation
description: Realtek WLAN USB NDIS Driver 42899
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: rtwlanu.sys (Realtek WLAN USB NDIS Driver 42899, Realtek Semiconductor Corporation ).
Google query: Realtek Semiconductor Corporation BAD_POOL_CALLER

On Mon 4/10/2017 6:23:56 PM your computer crashed
crash dump file: C:\Windows\Minidump\041017-4171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xDA (0x302, 0xFFFFB403E5730000, 0x1, 0xFFFFFFFD603E5730)
Error: SYSTEM_PTE_MISUSE
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 page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 4/9/2017 5:58:23 PM your computer crashed
crash dump file: C:\Windows\Minidump\040917-5000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xA (0xFFFF908ACFB3F042, 0x2, 0x0, 0xFFFFF800225D29DA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 4/8/2017 2:16:58 PM your computer crashed
crash dump file: C:\Windows\Minidump\040817-4156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xC2 (0x7, 0x206C644D, 0x40D0086, 0xFFFFB587EA276870)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Colif · Apr 13, 2017

All the bsod appear to be driver errors

rtwlanu.sys is only file listed that isn't windows, its part of Realtek Wireless Lan drivers. This is likely a driver off your motherboard so go have a look on website for motherboard and see if you have the latest drivers. I would be surprised if its related to the hdd problem.

I would check all motherboard drivers, Sata might help.

if fixing wireless lan drivers don't fix it all, Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

Zach_57 · Apr 13, 2017

I've updated all relevant drivers, but still have the same problems when looking at hard drive tools.

I have been unable to replicate the BSOD, but I remember the last time was the IRQL_NOT_LESS_OR_EQUAL error.

There were also times when the game I had installed on that drive would crash but not force a BSOD. I've re-installed the game onto my SSD and, so far, haven't had any issues. Of course, it took a day or two to start noticing crashes when it was on the other drive as well.

As an aside, I ran a system file scan from the command line and found no problems.

Absent replicating the BSOD, any other suggestions for diagnosing (and hopefully repairing) the 3TB drive?

Colif · Apr 13, 2017

i think you can create a minidump now of the errors you have already had, DOn't need to wait for another BSOD.

You can't fix drives, if its reporting 375gb to tools I would think about backing up stuff on it and replacing it, I will tag thread as storage and see if you can get another opinion on that or someone may have another idea whats going on.

Zach_57 · Apr 13, 2017

Colif :

Here is the dumplog: http://www.mediafire.com/file/skzw7tnunup1i62/mini_dump.zip

I'm hoping to at least get a diagnosis for this drive before replacing. It passes all tests in Seatools, only error is that it displays as two drives, one with 375GB capacity and one with the correct 3TB.

Search

Hard drive tools (Spinrite, HD Tune, Seatools) showing different size than Explorer

Zach_57

Prominent

Colif

Win 11 Master

Zach_57

Prominent

Colif

Win 11 Master

Zach_57

Prominent

Colif

Win 11 Master

Zach_57

Prominent

TRENDING THREADS

Latest posts

Moderators online

Share this page