BSOD when entering or exiting full screen game

Jul 8, 2018
2
0
10
BSOD UNEXPECTED_KERNEL_TRAP appeared when I entered full screen games. Problem was solved by right clicking on game icons and checking "Disable fullscreen optimization" and by setting compatibility to Windows 7. This problem only occurs on Windows 10. First time I installed Windows 10 was a year ago and it worked perfectly fine but now this BSOD appears. It also appears if I exit CS:GO. What should I do? Thank you.

BSOD dump file: http://www.mediafire.com/file/j9l0wk45rcu1upf/USER-PC-sub_07_07_2018__163320%2C11.zip

This is from reliability history:
Source
Windows

Summary
Shut down unexpectedly

Date
‎08-‎Jul-‎18 3:27

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
Code: 1000007f
Parameter 1: 8
Parameter 2: 803d8c00
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_17134
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.17134.2.0.0.256.48
Locale ID: 1050
 
Solution
Hi, I guess I may be a little late but hopefully this can shed some light on what was going on with your Win 10 install. I ran the dump files through the debugger and got the following information: https://pste.eu/p/OrUm.html

File: 070718-31625-01.dmp (Jul 7 2018 - 04:30:09)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32kbase.sys
Probably caused by: atikmdag.sys (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 25 Min(s), and 03 Sec(s)

File: 070718-31203-01.dmp (Jul 6 2018 - 18:04:56)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
***...

Colif

Win 11 Master
Moderator
UNEXPECTED_KERNEL_MODE_TRAP

Try running memtest86 on your ram, 1 stick at a time, up to 8 passes. Only score you want is 0, anything higher means ram needs to be replaced/removed

win 10 uses ram differently to Win 7 and its possible it uses more of the sticks than win 7. I won't get ahead of myself as ram might be fine.

I will get someone to convert the dump files into a format I can read.
 

gardenman

Splendid
Moderator
Hi, I guess I may be a little late but hopefully this can shed some light on what was going on with your Win 10 install. I ran the dump files through the debugger and got the following information: https://pste.eu/p/OrUm.html

File: 070718-31625-01.dmp (Jul 7 2018 - 04:30:09)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32kbase.sys
Probably caused by: atikmdag.sys (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 25 Min(s), and 03 Sec(s)

File: 070718-31203-01.dmp (Jul 6 2018 - 18:04:56)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32kbase.sys
Probably caused by: atikmdag.sys (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 23 Min(s), and 35 Sec(s)

File: 070718-29125-01.dmp (Jul 7 2018 - 10:17:48)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
Probably caused by: Ntfs.sys (Process: csrss.exe)
Uptime: 0 Day(s), 5 Hour(s), 47 Min(s), and 12 Sec(s)

File: 070618-36625-01.dmp (Jul 6 2018 - 09:51:20)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32kbase.sys
Probably caused by: atikmdag.sys (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 29 Min(s), and 19 Sec(s)

File: 070618-35125-01.dmp (Jul 6 2018 - 12:33:04)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
Probably caused by: Ntfs.sys (Process: csrss.exe)
Uptime: 0 Day(s), 2 Hour(s), 41 Min(s), and 14 Sec(s)
System: Dell OptiPlex 760

Note: There are many additional diagnostic files included in the OPs original link which can be useful.

I can't help you with this. Wait for additional replies. Good luck.
 
Solution

Colif

Win 11 Master
Moderator
3 were GPU drivers, other two blamed ntfs which is the file system.

parvdm.sys = Parallel VDM driver, part of display drivers. VDM = Visual Display Manager
e1k6332.sys = Intel Gigabit lan driver


possible all BSOD caused by Graphics drivers. If you ever come back to 10, look for newer GPU drivers.