Thread Stuck in Device Driver BSOD (when DotA is opened)

What GPU do you have?

Please provide a new set of logs so I can compare data from the dumps.

Alright,

I was not aware that you enabled driver verifier, good step!

This is what I see, 2 different BSOD error codes with pretty much the same stack.
The 0x1E speaks of a bug in the driver of Avast, the system crashes because this driver is making improper calls.
The single 0x3B speaks of the exact same problem with Avast.
Please remove Avast while troubleshooting.

Code:

3: kd> kb
 # RetAddr           : Args to Child                                                           : Call Site
00 fffff802`e0be0c03 : 00000000`0000001e ffffffff`80000003 fffff802`e0b676b0 ffff8b80`2ad4b848 : nt!KeBugCheckEx
01 fffff802`e0b720e6 : 00000000`ffff0000 ffffb006`00000000 0000000d`00000100 00000011`210a0100 : nt!KiFatalFilter+0x1f
02 fffff802`e0b5124f : fffff80c`474d0000 00000000`00000000 fffff80c`464a2624 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1056
03 fffff802`e0b67ffd : ffff8b80`2ad4e000 ffff8b80`2ad4aa40 00000000`00000000 00000000`00000000 : nt!_C_specific_handler+0x9f
04 fffff802`e0abba31 : ffff8b80`2ad4e000 00000000`00000000 ffff8b80`2ad48000 ffffb006`1e865318 : nt!RtlpExecuteHandlerForException+0xd
05 fffff802`e0aba7e4 : ffff8b80`2ad4b070 ffff8b80`2ad4b570 ffff8b80`2ad4b070 ffff8b80`2ad4b848 : nt!RtlDispatchException+0x421
06 fffff802`e0b6ce02 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x144
07 fffff802`e0b6a473 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
08 fffff802`e0b676b1 : fffff80c`459cb533 ffffb006`1f2b0025 ffffb006`210187c0 ffff8b80`2ad4bad0 : nt!KiBreakpointTrap+0xf3
09 fffff80c`459cb533 : ffffb006`1f2b0025 ffffb006`210187c0 ffff8b80`2ad4bad0 ffffb006`210187c0 : nt!DbgBreakPoint+0x1
0a (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!Mx::MxDbgBreakPoint+0x6 [d:\rs1\minkernel\wdf\framework\shared\inc\primitives\km\mxgeneralkm.h @ 156]
0b fffff80c`45a5994b : 00000000`00737973 ffffb006`21018610 00004ff9`df093f78 fffff80c`48470370 : Wdf01000!FxVerifierDbgBreakPoint+0x43 [d:\rs1\minkernel\wdf\framework\shared\inc\private\common\fxverifier.h @ 97]
0c fffff80c`459ebfef : ffffb006`20f6c080 ffff8b80`2ad4bd02 ffffb006`21018610 ffffb006`20f6c080 : Wdf01000!FxIoQueue::Vf_VerifyForwardRequest+0xcb [d:\rs1\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 1718]
0d (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxIoQueue::VerifyForwardRequest+0x4b963
0e (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxIoQueue::ForwardRequest+0x4b967
0f fffff80c`48464e53 : ffff8b80`2ad4bc18 ffff8b80`2ad4bce0 ffffb006`20f6c080 ffffb006`1f2be360 : Wdf01000!imp_WdfRequestForwardToIoQueue+0x4ba2f [d:\rs1\minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 3130]
10 ffff8b80`2ad4bc18 : ffff8b80`2ad4bce0 ffffb006`20f6c080 ffffb006`1f2be360 ffff9b8c`6275adb0 : aswStm+0x14e53
11 ffff8b80`2ad4bce0 : ffffb006`20f6c080 ffffb006`1f2be360 ffff9b8c`6275adb0 00000000`00000000 : 0xffff8b80`2ad4bc18
12 ffffb006`20f6c080 : ffffb006`1f2be360 ffff9b8c`6275adb0 00000000`00000000 ffff8b80`2ad4bce0 : 0xffff8b80`2ad4bce0
13 ffffb006`1f2be360 : ffff9b8c`6275adb0 00000000`00000000 ffff8b80`2ad4bce0 fffff80c`484653b4 : 0xffffb006`20f6c080
14 ffff9b8c`6275adb0 : 00000000`00000000 ffff8b80`2ad4bce0 fffff80c`484653b4 ffff9b8c`6275ad80 : 0xffffb006`1f2be360
15 00000000`00000000 : ffff8b80`2ad4bce0 fffff80c`484653b4 ffff9b8c`6275ad80 ffff8b80`2ad4bda0 : 0xffff9b8c`6275adb0

Driver verifier watches the selected behaviour of the selected drivers, this could cause a little delay in several things which you notice. This is completely normal.

Yes.