New
#1
BSOD (IRQL_NOT_LESS_OR_EQUAL, ntkrnlmp.exe) while playing select games
EDIT 4: Added a new .dmp file with Verifier
EDIT 3: Added SF_Diagnostic Tool package which contains more information
EDIT 2: I have updated the attachment which contains more files (though it does not contain all...it seems very random in what files it includes in the zip file). I will keep updating it if more become available
EDIT: Having some issues with the dm log tools. Please see my post below
Hey everyone,
So, I am at my wits end here. Over the last few months, I have been getting BSODs playing only select games (usually Steam games). What I mean by this, is that some games run perfectly fine with no issues, yet some yield a BSOD.
Games that cause a BSOD:
- Wasteland 2 (most recent)
- Watch Dogs
- Dawn of War II (though not very often)
- Marvel Heroes 2015
- The Sims 3
Games that are perfectly fine:
- World of Warcraft
- Diablo 3
- Hearthstone
- Metro: Last Light
- 3D Mark (sure, not a game, but still hardware intensive)
I've tried all I can to resolve this issue, but I have yet to find the culprit (hoping it's not a hardware issue). You guys are my only hope. I have of course attached all necessary files, and have copy/pasted the log from WhoCrashed(not that it helps much) below with Verifier on. Any help would be immensely appreciated! Thank you!
Crash dump file: C:\Windows\Minidump\091914-21964-01.dmp
Date/time: 9/20/2014 1:21:02 AM GMT
Uptime: 00:27:33
Machine: TK421
Bug check name: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0xA
Bug check parm 1: 0x0
Bug check parm 2: 0xD
Bug check parm 3: 0x1
Bug check parm 4: 0xFFFFF800034941F4
Probably caused by: ntkrnlmp.exe
Driver description:
Driver product:
Driver company:
OS build: Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Architecture: x64 (64 bit)
CPU count: 4
Page size: 4096
Bug check description:
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
Comments:
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Last edited by Sithhlord715; 20 Sep 2014 at 15:00.