Windows 10: BSOD when inserting portable usb hdd

My Hp Notebook automatically starts a BSOD restart cycle when I insert my Seagate 3TB portable hdd. I can't even get to the boot screen, it's just a nonstop cycle. I tried safe mode, that also continued the cycle once the usb was inserted. If I take that hard drive out, and restart the computer, it works fine. I have other portable hdd, they work just fine as well. It will only BSOD once I put in the Seagate 3TB. The hdd itself isn't clicking, overheating or anything else, it was fine until about a week ago when the bsod nonstop cycle began.
Please help, I just want to get the files off it & be done with it. Any suggestions or advice would be greatly appreciated.

:)

 

PAGE_FAULT_IN_NONPAGED_AREA iaStorAV.sys BSOD on boot even with setup drive

BTW checked hdd via bios utility. Says it is OK

 

USB Memory stick problems

I'm having problems with a USB memory stick, 64 Gb.

It is detected when connecting it to my system, but when trying to access it I'm told to insert a disc.

It does not work to format it.

The Disk Management function gets stuck when the USB stick is inserted.

It works though to open it as "Portable device".

I have tried it on a Windows 7 computer and it works fine without having to open it as a "Portable device".

I'm not sure there is a link to this, but I tried to create a backup disc on this device and that did not work.

 

Try KYHI's WinPE rescue disc. Boot it then see if plugging in the 3TB external drive still causes a problem. See here: Windows 10 Recovery Tools - Bootable Rescue Disk from KYHI

Sounds to me like a corrupted file system on that drive. If you can get it to install so you an run chkdsk against it, that might fix the problem.

 

The newest dump is from 5/7.

Definitely a file system problem, from info in teh Stack trace:
Code: STACK_TEXT: ffff8001`9cc35cd0 fffff803`8a64ed10 : 00000000`00000001 ffffffff`024fff82 ffff8001`9cc35dc8 ffff8001`9cc35de0 : nt!CcGetVirtualAddress+0x2ba ffff8001`9cc35d80 fffff803`8aaa54ea : 00000000`7273664c ffff8001`9cc35f40 00000000`00001000 fffff803`8a84d200 : nt!CcPinFileData+0xb0 ffff8001`9cc35e80 fffff804`9491050d : ffffffff`024fff82 ffff8001`9cc35f98 ffff8001`00001000 00001f80`00000001 : nt!CcPinRead+0xea ffff8001`9cc35f40 fffff804`94932d28 : 00000000`00000001 ffffffff`024fff82 00000000`00000000 00000000`00001000 : NTFS!LfsPinOrMapData+0x59 ffff8001`9cc35f90 fffff804`94930b97 : ffffa68a`00000000 ffffb800`416ec898 fffff780`00000001 ffff8001`9cc36401 : NTFS!LfsFindLastLsn+0x78c ffff8001`9cc361e0 fffff804`949302e2 : ffffb800`46568400 00000000`ffff0000 ffffb800`04000000 00000000`04000000 : NTFS!LfsRestartLogFile+0x533 ffff8001`9cc36380 fffff804`9492f375 : 00000000`0016141c 00000000`fffffff8 ffffb800`4ee74890 ffffb800`4c43f6f0 : NTFS!LfsOpenLogFile+0x9e ffff8001`9cc36420 fffff804`9491ce8f : ffffb800`416ec600 ffffb800`416ec898 ffffb800`416ec6f8 ffffb800`416ec6f8 : NTFS!NtfsStartLogFile+0x35d ffff8001`9cc36510 fffff804`9490ed71 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NTFS!NtfsMountVolume+0x11b3 ffff8001`9cc36920 fffff804`94804691 : ffffb800`416ec6f8 ffff8001`9cc36a40 00000000`00000000 fffff803`8a666311 : NTFS!NtfsCommonFileSystemControl+0xa1 ffff8001`9cc36a00 fffff803`8a6696f9 : fffff803`8a9ba100 ffffb800`45ba76c0 ffffb800`416ec768 fffff803`8a9ba280 : NTFS!NtfsFspDispatch+0x281 ffff8001`9cc36b80 fffff803`8a6ba2d5 : ffff8001`995c0180 00000000`00000080 ffffb800`40eda640 ffffb800`45ba76c0 : nt!ExpWorkerThread+0xe9 ffff8001`9cc36c10 fffff803`8a757c86 : ffff8001`995c0180 ffffb800`45ba76c0 fffff803`8a6ba294 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffff8001`9cc36c60 00000000`00000000 : ffff8001`9cc37000 ffff8001`9cc31000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16[/quote] Note all the NTFS entries.

If KYHI's rescue disc doesn't work for you, try a live Linux CD/DVD/flash drive to access your data.