External HDD cause BSOD Windows 10

[akieez]

Guys, my laptop went BSOD after I plugged in my external HDD. It never happened before, I didn't know what to do. At least I can recover everything inside the HDD is enough for me. I have a 1TB Seagate FreeAgent GoFlex HDD. I've already run Windows Memory Diagnostics and no problem on that. I've already check my driver using DriverBooster and it everything is up-to-date.

Laptop:
Windows 10 64-bit
Acer Aspire VN7-591G
Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz

I use WhoCrashed Home Edition to analyze the minidump file. This is what I get from the minidump.

1) On Wed 20-Jan-16 2:55:07 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012016-27546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x37B03)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800D62C4B03, 0xFFFFD0002185BBC8, 0xFFFFD0002185B3E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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.

2) On Wed 20-Jan-16 2:55:07 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xD9E3E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800D62C4B03, 0xFFFFD0002185BBC8, 0xFFFFD0002185B3E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time

3) On Tue 19-Jan-16 4:35:17 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012016-37218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3927A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018564127A, 0xFFFFD000242FA938, 0xFFFFD000242FA150)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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


Please help me. Thanks in advance!

 

[SuperSoph_WD]

Welcome to the TH community, akieez!

I'd suggest you to try plugging a different external HDD or USB device in your laptop and see if the BSODs will continue. If you have access to another computer, you could also attempt plugging the problematic external drive there and see how the other system would detect it.
Another thing you should try is swapping the USB cable that is connecting the drive with a different one and see if that would improve its behavior.
You definitely need to refer to the HDD manufacturer's website and find their diagnostic tool to test the drive's health and SMART status. Since you are having trouble with Windows when the HDD is connected, I'd recommend you to use the DOS version of their software. It will allow you to test the hard drive without booting into any OS.

Hope it helps you. Keep me posted.
SuperSoph_WD