BSODs playing Divinity: Original Sin EE, error 0X0000003b, 0x1000007e

I should also note I ran CHKDSK on all drives with no errors as well as running DISM with no corruption/errors.

Had another BSOD last night during memtest.

Hello Robenger and welcome to TenForums :)

I can see that there was a reference to a driver in the thread that did not load correctly.

Code:

ffffe381`1a3fa790  fffff807`47640000Unable to load image ibtusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ibtusb.sys
*** ERROR: Module load completed but symbols could not be loaded for ibtusb.sys
 ibtusb

Try changing the Intel(R) Wireless Bluetooth(R) Filter Driver - the one installed is quite recent (Timestamp: Sat Apr 08 01:33:50 2017) but there may be others you can try via the Intel drivers website: https://downloadcenter.intel.com/


There was also a reference to the graphics driver too but I can see you have already tried various versions of this driver. It would not hurt to try a different one again.

Code:

ffffe381`1a3fbd78  fffff807`49ccd782Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x6d782

atikmdag driver Timestamp: Wed May 17 21:04:47 2017

philc43 said:

Hello Robenger and welcome to TenForums :)

I can see that there was a reference to a driver in the thread that did not load correctly.

Code:

ffffe381`1a3fa790  fffff807`47640000Unable to load image ibtusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ibtusb.sys
*** ERROR: Module load completed but symbols could not be loaded for ibtusb.sys
 ibtusb

Try changing the Intel(R) Wireless Bluetooth(R) Filter Driver - the one installed is quite recent (Timestamp: Sat Apr 08 01:33:50 2017) but there may be others you can try via the Intel drivers website: https://downloadcenter.intel.com/


There was also a reference to the graphics driver too but I can see you have already tried various versions of this driver. It would not hurt to try a different one again.

Code:

ffffe381`1a3fbd78  fffff807`49ccd782Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x6d782

atikmdag driver Timestamp: Wed May 17 21:04:47 2017

Thank you philc43, I've been a lurker here for years, but only made an account recently.

As to the Bluetooth driver I'll get the new one installed.

On the second point I figured out the issue sort of. I normally install the full software suite from AMD for my Fury but I don't know if its the new destroyer update from Windows or what but something extra I install has been causing all of the issues. Maybe its the Relive streaming software or the HDMI audio driver, but one of them was causing a plethora of issues. Please keep this open while I make sure this is the case.

Using the debugger I somehow am not seeing what you are seeing. It displayed:
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheckWithHint+283 )
Probably caused by : memory_corruption ( nt!MiZeroPageThread+62e )
GetContextState failed, 0x8007001E
How come it is not displaying what you are finding? And how come it is finding things that you did not post?

zbook said:

Using the debugger I somehow am not seeing what you are seeing. It displayed:
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheckWithHint+283 )
Probably caused by : memory_corruption ( nt!MiZeroPageThread+62e )
GetContextState failed, 0x8007001E
How come it is not displaying what you are finding? And how come it is finding things that you did not post?

I'm wondering the same thing lol

zbook said:

Using the debugger I somehow am not seeing what you are seeing. It displayed:
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheckWithHint+283 )
Probably caused by : memory_corruption ( nt!MiZeroPageThread+62e )
GetContextState failed, 0x8007001E
How come it is not displaying what you are finding? And how come it is finding things that you did not post?

Two things are going on here, firstly you are using the latest version of WinDBG which has some issues that MS have not sorted yet, it causes those GetContextState errors. Secondly, I also see those "probably caused by" messages but know that it does not point to the cause. ntkrnlmp is the windows kernel and is always going to be involved in the processes that occur during the operation of Windows 10. Memory corruption is detected but the reason is often due to a bad driver causing the system to crash because the driver has not kept track of the memory addresses and then everything falls apart.

I usually dig deeper into the crash dump thread and then explore the whole stack which is where I found the drivers I highlighted.

You can read a tutorial that goes into a lot of detail on this here: WinDBG - The Basics for Debugging Crash Dumps in Windows 10