BSOD when copying files from external HDD to external HDD

MrPepka said:

Do you still get BSODs after turning off virtualization in the BIOS?

Yes, that is where the last BSOD came from that had IMAGE_NAME: ntkrnlmp.exe in it.

Virutalization completely disabled in the BIOS, including IOMMU, and then this mythical IOMMU detects a DMA violation? Hmm, there are more factors influencing this. Well. Considering the results of one of the earlier analyzes, one of your disks is a problem (it is possible that the one you are copying files from). Of course, you can turn back on virtualization in the BIOS (including IOMMU), turn off Driver Verifier and advise you to look for firmware updates on both drives, or test them with SeaTools

MrPepka said:

Virutalization completely disabled in the BIOS, including IOMMU, and then this mythical IOMMU detects a DMA violation? Hmm, there are more factors influencing this. Well. Considering the results of one of the earlier analyzes, one of your disks is a problem (it is possible that the one you are copying files from). Of course, you can turn back on virtualization in the BIOS (including IOMMU), turn off Driver Verifier and advise you to look for firmware updates on both drives, or test them with SeaTools

Yep there's only one thing in the BIOS that references virtualization (nothing says IOMMU) and it now says disabled.
I think it is the new one I'm copying to. I've never had any issues with my existing on, considering this new one is USB-C, I wouldn't be surprised if half a job had been done on the drivers on both HPs end and WD and they were buggy.

I have tested the new one with SeaTools and it came back pass, I've also tried using WD universal firmware updater to update the new drive but it doesn't even recognise it. I reckon I'll return it and get another of the one I already have.

Please upload new V2 and DM into the thread:
BSOD - Posting Instructions

Was Macrium uninstalled and reinstalled earlier in the thread?

zbook said:

Please upload new V2 and DM into the thread:
BSOD - Posting Instructions

Was Macrium uninstalled and reinstalled earlier in the thread?

No, I didn't get round to doing that. There's a lot of different things to keep track of in here.

I'll run those scripts then reinstall Macrium. It was a syncback job that triggered the BSODs not a macrium backup

- - - Updated - - -

Both log file collections

See post #5, step #20.

The latest BSOD was with 11 customized windows driver verifier customized settings.

The cause was a misbehaving Macrium driver.

Uninstall and reinstall the software.

Restart windows driver verifier.

zbook said:

See post #5, step #20.

The latest BSOD was with 11 customized windows driver verifier customized settings.

The cause was a misbehaving Macrium driver.

Uninstall and reinstall the software.

Restart windows driver verifier.

Yeah that drive wasn't plugged in when I got that particular BSOD, I've reinstalled macrium without CBT as it was mrcbt.sys as the culprit.

Please open a support ticket with Vbox.

Community – Oracle VM VirtualBox

Ask how to troubleshoot these event viewer error messages:

Code:

Event[30748]:
  Log Name: System
  Source: VBoxNetLwf
  Date: 2020-01-11T16:51:45.998
  Event ID: 12
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MICHAEL-10
  Description: 
The driver detected an internal driver error on \Device\VBoxNetLwf.

Ztruker said:

Found this: CBT driver causes BSOD with VMware VM


So this is not a new problem re: Macrium

Is there any evidence any of the first 4 were caused by this?
They were dMA violations and I think the mrcbt.sys one was a page fault

- - - Updated - - -

Had another BSOD after reinstall of Macrium without CBT installed at all

New V2 and DM attached.Attachment 262799Attachment 262798