BSOD random (more frequent with games), KMODE_EXCEPTION_NOT_HANDLED

Hi,

I just recently upgraded from Windows 8.1 to Windows 10 and after while it just started to BSOD more or less randomly, it appears to be triggered more often if I have any process open that does accesses the GPU (Browser, Games)

I already ran memtest86 for about 8 hours (over night) with about 6 passes and 0 errors so I figured it is most likely not my memory.

Then I used Driver Verifier to filter out almost anything that isn't really needed there shouldn't be much third party drivers left.

Also I tried to get something out of the crash dumps where the call stack seems consistent however it is not very helpful at all as it always happens in ntoskrnl at the exact same location.

After spending a lot of time trying to figure this out on my own I'm hoping theres someone smarter than me here

Edit: I should mention I also tested my hard drive and it seems fine at least chkdsk claims that.

• XDEV-PC-Wed_08_12_2015_212646_37.zip (613.3 KB, 2 views)

Hi ZehMatt,

I'm very sorry for the delay, there aren't many people in this section.
Are you still requiring help?
If so, please use the tool again and upload a new zip file.

Please fill in your system specs

Please go to this site and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.

How to fill in your system specs:

Hi,

Updated my system information on my profile.

I'm having more recent BSODs lately when using Visual Studio to build a really big project. I tried to investigate the call stack on my own but I'm rather puzzled what it could be, the stack record also seems corrupted?

More recent dump attached.

• XDEV-PC-Fri_12_04_2015_220440_01.zip (708.2 KB, 1 views)

How so does the stack record seem corrupted?

Is a clean install of Windows 10 considered after the upgrade?
Windows 10 - Clean Install - Windows 10 blog

How so does the stack record seem corrupted?

Is a clean install of Windows 10 considered after the upgrade?
Windows 10 - Clean Install - Windows 10 blog

I would rather prefer to avoid reinstalling Windows 10, there has to be a way to pinpoint the issue.

There is a big chance this problem is caused by the upgrade, to pinpoint that down might be very difficult.