BSODs at random times atikmdag.sys THREAD STUCK IN DEVICE DRIVER

Could you tell us what the 3.3v, 5v and 12v values are according to the BIOS.

Yes.

About a week ago someone who had/has the same BSOD (but different situation). At first it looked like the AMD drivers were causing issues, maybe they did, but the user ran driver verifier which revealed different BSODs with an entirely different cause, Avast.
I haven't heard back from him/her, so I'm not 100% sure if Avast truly was the cause, but since it is almost a week ago..

I don't know if you ran driver verifier, but before blaming the motherboard I would suggest to run driver verifier. Chance exists that it may reveal another driver causing issues.

How to enable driver verifier
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials
I would recommend to run driver verifier with the settings specified in the tutorial, and with the below settings

Code:

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [X] (0x00008000) Power framework delay fuzzing
    [ ] (0x00010000) Port/miniport interface checking
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification
    [ ] (0x02000000) Code integrity checks

    [X] Indicates flag is enabled

Link to thread I'm talking about
Thread Stuck in Device Driver BSOD (when DotA is opened) - Page 2 - Windows 10 Forums

axe0 said:

About a week ago someone who had/has the same BSOD (but different situation). At first it looked like the AMD drivers were causing issues, maybe they did, but the user ran driver verifier which revealed different BSODs with an entirely different cause, Avast.
I haven't heard back from him/her, so I'm not 100% sure if Avast truly was the cause, but since it is almost a week ago..

I don't know if you ran driver verifier, but before blaming the motherboard I would suggest to run driver verifier. Chance exists that it may reveal another driver causing issues.

How to enable driver verifier
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials
I would recommend to run driver verifier with the settings specified in the tutorial, and with the below settings

Code:

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [X] (0x00008000) Power framework delay fuzzing
    [ ] (0x00010000) Port/miniport interface checking
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification
    [ ] (0x02000000) Code integrity checks

    [X] Indicates flag is enabled

Link to thread I'm talking about
Thread Stuck in Device Driver BSOD (when DotA is opened) - Page 2 - Windows 10 Forums

I enabled it and restarted, but it wouldn't turn back on so I forced restarted. It showed Bad Pool Caller and mfesapsn.sys. I uninstalled McAfee Web Advisor as it may have something to do with that?

I've uploaded a new dump, if that helps :)

Please keep driver verifier running, if there are more different BSODs with different drivers then the motherboard can be blamed.