BSOD when copying files from external HDD to external HDD

Long story short, I've purchased a 5TB WD Mypassport USB C HDD to replace my 4tb wd my passport and I'm usding syncback to copy over about 2.8TB of backups and what not

Twice now I've had it crash while running. I've come back to it and found it has restarted. found the following dumps which match up with the times it would have happened using nirsoft BlueScreenView (not sure how useful they are though)

010720-7468-01.dmp 07/01/2020 17:46:26 DRIVER_VERIFIER_DMA_VIOLATION 0x000000e6 00000000`00000026 ffff898a`4a7f8060 00000000`000000a8 00000000`00000006 hal.dll hal.dll+41a7f Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.387 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\WINDOWS\Minidump\010720-7468-01.dmp 4 15 18362 1,470,788 07/01/2020 17:47:16

010620-9265-01.dmp 06/01/2020 23:27:39 DRIVER_VERIFIER_DMA_VIOLATION 0x000000e6 00000000`00000026 ffffbd0b`85df0060 00000000`0000008c 00000000`00000006 hal.dll hal.dll+41a7f Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.387 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\WINDOWS\Minidump\010620-9265-01.dmp 4 15 18362 1,517,420 06/01/2020 23:29:17

any help would be appreciated.

Windows 1909Attachment 262283

Enable Driver Verifier - Enable and Disable Driver Verifier in Windows 10
But in Driver Verifier enable all standard settings and 2 additional settings (force pending i/o request and irp logging)

Cheers, does that give me a report or something?

@mkr10001 You already have Driver Verifier running. Were you aware of this? It should not be on unless you are running driver troubleshooting tests. The purpose of Driver Verifier is to tests drivers and it is designed to cause BSOD events so this might be the reason you are having the problems in the first place.

1) The log collector did not collect any spontaneous BSOD
2) How come Windows driver verifier was on before opening the thread?
3) How did you choose the customized settings?

4) Open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /scanhealth
7) dism /online /cleanup-image /restorehealth
8) sfc /scannow
9) chkdsk /scan
10) wmic recoveros set autoreboot = false
11) wmic recoveros set DebugInfoType = 7
12) wmic recoveros get autoreboot
13) wmic recoveros get DebugInfoType
14) bcdedit /enum {badmemory}

15) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

16) Make sure that there is no over clocking while troubleshooting

17) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


18) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

19) Please turn off Windows driver verifier while running the drive tests
Enable and Disable Driver Verifier in Windows 10

20) Uninstall and reinstall Macrium

I'm up the creek here boys !

I've never seen that driver verifier app before so I can say that's not something I've ever turned on myself. I ran through it, selected the standard things, comp restarted, it told me it was doing some kind of diagnosis. Seemed to finish that and said it couldn't boot so tried to turn off the driver stuff through the advanced startup menus, pressed 7, restarted, cannot boot message, gives me the blue startup options again, try startup repair, cannot fix problems, try system restore and I get some system restore failed to extract the original.copy of the directory from the restore point.
Source: %programfiles%\windowsapps
Destination: appxstaging
An unspecified error occurred during system restore. (0x8007007e)

Which actually is the exact reason I had to do a fresh install before and actually started doing backups with macrium in the first place. And now this same error is screwing me over on a fresh install from the previous time..
I got nowhere trying to solve that last time..

So currently I can't even boot into windows and it can't sort itself out.

- - - Updated - - -

Srttrail.txt says error code 0 for everything apart from

Root cause found:
Unspecified changes to system configuration might have caused the problem.
Repair action:
Result: failed. Error code = 0x32
Time taken = 93ms

Repair action: system restore
Result: failed. Error code = 0x1f
Time taken = 82250ms

Repair action: system files integrity check and repair
Result: failed. Error code = 0x57
Time taken = 1078ms

Then a load more successful tests then eventually..

Startup repair has tried several times but still cannot determine the cause of the problem.

You need get to the recovery menu and select Troubleshoot to boot into the command prompt. Here you can type verifier /reset to turn off Driver Verifier. See the tutorial below for more details and options:

https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html#DDV2

Sorry missed that option for disabling. Ran verifier /reset and it said no settings were changed. Rebooted, back to startup repair menu.

Ran verifier from CMD prompt and everything says disabled. Even ran the bootmode one for good measure and does the same.

mkr10001 said:

Sorry missed that option for disabling. Ran verifier /reset and it said no settings were changed. Rebooted, back to startup repair menu.

Ran verifier from CMD prompt and everything says disabled. Even ran the bootmode one for good measure and does the same.

Instead please try option 3 from the tutorial:
https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html#Disable3

I just want to note that bugcheck 0xE6 does not necessarily mean that Driver Verifier is running. It means that a DMA access violation has been detected, and this can detect both Driver Verifier and IOMMU - Input–output memory management unit - Wikipedia
That's why I advised OP to turn on Driver Verifier and hinted what settings to choose so that you can detect the driver that actually gets DMA the wrong way