Solved BSOD (IRQL_NOT_LESS_OR_EQUAL, ntkrnlmp.exe) while playing select games

[Sithhlord715]

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!



[FONT=Courier New, Courier, FixedSys]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: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT]
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. [/FONT]

 

[Sithhlord715]

Well, looks like I'm having issues with the dm log tools...it seems to only generate the files included in this zip (just the .dmp files)...if anyone has any instructions on how to fix this, I would gladly appreciate it

 

[essenbe]

Try running http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html but use option 2. Press the Grab All button and give it plenty of time, it takes it some time to generate all the files, which we need. I will look at the dump files, but we really need the othe files too.

Also if you don't mind, please provide more info on your hardware. We need manufacturer and model numbers sometimes. We sometimes need to look them up, and also need info on your cooling and PSU among other stuff this is what I usually post, it may help you a little.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

Also, if you would, please run this and tell me the results​

Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

 

[essenbe]

Here is what I get from your dump files. almost every one is one of these 2

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, d, 1, fffff800034941f4}
Probably caused by : [COLOR=red]hardware[/COLOR] ( nt!KiPageFault+260 )
Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=red]BugCheck 124[/COLOR], {0, fffffa800b5cb028, b66b4000, 135}
Probably caused by : AuthenticAMD
Followup: MachineOwner

An 0X124 is a general code for a hardware failure. It is not specific and gives us little info about which piece of hardware it is. The next one is the only one that have us any info.

nvlddmkm
start             end                 module name
fffff880`0ba3c000 fffff880`0c6ca000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 12:42:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is your graphics driver

Please reinstall your graphics driver to the latest WHQL version for your card. If you have the latest version, please reinstall it using this procedure
http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

Also, you will need a good Graphics temp monitoring program. Make sure you monitor temps. The tutorial mentions Speedfan. I don't find that useful, personally. Then run this stress test. It will cause your temps go increase very rapidly and very fast, so keep a close watch on temps and if they get too high, stop the test to keep from damaging your card. http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[Sithhlord715]

Hey essenbe,

First, thank you so much for your help! Always a pleasure doing business with a Jedi

Secondly, I ran the SF Diagnostic tool and have uploaded a new attachment to my original post. I hope it helps. Let me know if any files are missing. I have also updated my system specs to the best of my abilities .

Thirdly, I did reinstall my graphics drivers a while ago, because I thought it was the culprit, but nothing changed. However, I did not use your method. I plan on doing this the moment I get back home (gotta run to an appointment) and will report on my findings.

Finally, I will run the sfc scan and will let you know what I find.

Again, thank you so much! Let me know if you need anything else from me to help you out!

EDIT: Forgot to mention, I ran Memtest overnight with a total of 4 passes. No issues were found

 

[essenbe]

Ok, let me know. The method for installing drivers, is in order to make sure you have a clean install. Wait until you see what is in the display driver folder. Every driver you have ever installed. So we are going to delete every one to get them out of your system. Next, on install, use custom install and be sure the check box for clean install is checked. The only thing you need to install is the display driver and Phys X, everything else your motherboard drivers cover. So, you are just adding redundant drivers that may be having conflicts with what you already installed. You can install Nvidia Experience, if you want to. But, it has caused me more trouble than it has helped. Even though I showed it to be installed in the tutorial, it is not istalled in my system. if you need it, want it, like it, install it. I don't. But, few people use any of the 3D stuff, and you already have audio/HDMI drivers and are setting up the possibility for driver conflicts by installing them when they are not needed or used.

As for memory test here is what I recommend. 4 Passes is half a test. A minimum of 8 passes is needed, more is better. But, lets see if the graphics driver helps first. But, these are my instructions.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[Sithhlord715]

Alright, quick update:

System File Checker scan yielded no errors, so all good on that end.

I have done a complete uninstall and reinstall of the latest NVIDIA drivers. I'll play through some Wasteland 2 and let you know if any BSOD occur. If they do, I will update this thread with the new .dmp files.

Finally, I will run Memtest overnight again per your request. I will probably have to run it through half the day tomorrow, as it takes quiet a while (9 hours for just 4 passes).

 

[Sithhlord715]

Well, that didn't take long. Another BSOD. I have attached the new .dmp file. I will enable Verifier and go again until another BSOD, at which point I'll upload another .dmp file.

Really starting to lose hope here. Might just need to do a clean install of Windows....*sigh*

 

[Sithhlord715]

Well, here we go...another post, another BSOD. This time with Verifier on. Seems to point to amdppm.sys, but that's a system file...I honestly don't know, and I'm not that great at reading the stack trace.

Let me know what you find. I greatly appreciate your assistance with this

 

[essenbe]

Ok from the DV program. I'll look at the one before after I post this.

amdppm
start             end                 module name
fffff880`047db000 fffff880`047f0000   amdppm     (pdb symbols)          c:\symcache\amdppm.pdb\AB154B73C6884E70807CA6407175368D1\amdppm.pdb
    Loaded symbol image file: amdppm.sys
    Mapped memory image file: c:\symcache\amdppm.sys\4A5BC0FD15000\amdppm.sys
    Image path: \SystemRoot\system32\DRIVERS\amdppm.sys
    Image name: amdppm.sys
    Timestamp:        Mon Jul 13 18:19:25 2009 (4A5BC0FD)
    CheckSum:         0001EA42
    ImageSize:        00015000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     amdppm.sys
    OriginalFilename: amdppm.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  Processor Device Driver

Another driver from Windows update, this is your Processor Device Driver. That should also be among your Motherboard drivers. It is the device driver for your CPU, I am not that familiar with AMD, I would know what it is if it were Intel. But I would think it may be among your Chipset Drivers.

 

[essenbe]

The other one was really of no use. It blamed it on the NT Kernel of Windows which is not possible unless you have an altered copy of Windows. Where did you get the DVD disk or the ISO file for your installation? I only ask because everything seems to be pointing to system files as the cause of the crashes, which isn't possible.

Also, I wasn't suggesting you run memtest again right now, I only gave the instructions as I figure you may eventually have to run it again and you will have the instructions. When you ran it, did you download it from the link listed in the post?

Are you using any of the 'speed up windows' type Windows optimizer programs?

 

[Sithhlord715]

Yeah, most likely is. I downloaded a BIOS updated which came out in 2011 (haven't updated since 2009) and will update/flash in a little bit...I'll let you know what happens.

The main thing thats odd is that some games are fine, while others like Wasteland 2 cause the BSOD...just seems so odd and random

 

[Sithhlord715]

Sorry, didn't see your other post, but to answer your question, the Windows I'm running is installed from an official disk and has served me well for years. And nope, not running any optimization programs

 

[essenbe]

Truthfully, the games thing is not really that uncommon. Some games are coded bad. They will work on some people's machines, but not on others. I have had problems with a few games just like you. You have to be really perceptive to tell the difference. I had that problem with BF4 and nothing else, so I started watching exactly what was going on. I realized it was the game crashing even though the debugger would say graphics drivers or something else, when it wasn't. I could tell it was the game itself crashing. I found that a lot of people were having the same problem with BF4. They kept patching it to try to fix all the problems but each patch made it worse. It finally got to where the game wouldn't even load. EA was absolutely worthless. I ended up just uninstalling the game and had no more problems.

A lot of times they are in a hurry to get the game out as soon as possible and just take shortcuts in the coding, which is never a good idea. But they only care about getting your money. They don't care whether the game is playable or not. That is true. so, in some cases when it is just one or 2 games you have problems with, it can very well be the game.

 

[essenbe]

Sorry, didn't see your other post, but to answer your question, the Windows I'm running is installed from an official disk and has served me well for years. And nope, not running any optimization programs

No problems. I do that all the time.

 

[Sithhlord715]

Yeah, I honestly think it is the games themselves, which is a damn shame. I mean, even the most graphic intensive games, like Metro, run fine, yet these games don't. So what do you suggest man? Report this issue to the devs and try to find a temporary solution? Or should I just say screw it and reinstall Windows?

 

[essenbe]

Well, I wouldn't be so quick to reinstall windows if it is a game. We may be able to do something a little less drastic first. For right now, tell me how tha game is installed. Is it through steam or Orinin?

 

[Sithhlord715]

It's a Steam game. Just like with the other games, most games on Steam are fine (Divinity: Original Sin, Metro 2033 Redux, Skyrim, Fallout: New Vegas), but others cause the BSOD (Marvel Heroes 2015, Wasteland 2, Dawn of War 2 - though this one did it only once or twice I believe). So yeah, not sure. I thought it might be Steam that's the culprit, but then I noticed it occur in other games. Watch Dogs caused a BSOD quickly, and Sims 3 caused it 2-3 times over the course of 60 hours.

Honestly, I'm starting to think it's a hardware issue. My CPU and MOBO are about 5 years old now, and I think when things get too intensive for too long, it crashes. But I'm not sure, since Metro 2033 and 3D Mark are pretty intensive on the system, and WoW can get crazy sometimes in heavily populated combat scenarios. So yeah, it's tricky... I wish the logs and stacktrace would tell us more than of "Kernel problem, but not really Kernel problem"

 

[essenbe]

OK, do you have an external hard drive, or another hard drive you could use? Create a filder on the external and name it the name of the game, and open it. Now open another instance of explorer and open the Steam folder, find the Steam Apps folder and open it, find the Common folder and open it, then find the folder of the game that is causing you problems. Copy that folder to the external drive and Paste it there. Now Delete that game folder, then uninstall the game from control panel. See how it goes now. That way, you can just copy/paste the game back in later, if you want to and Steam will install it and you won't have to re download it.

 

[Sithhlord715]

That's a really good idea, though unfortunately, I don't have an external HD =(

However...I do have somewhat good news. I read on reddit that this game thats causing the issue now (Wasteland 2) has an issue where it puts GPU utilization at 99%. A bug no doubt. I made some changes which put the GPU utilization back where it should be, and have been able to play for over an hour without a hitch. I also had Firefox closed this time, if that makes any difference, though I doubt it.

So, could be 1 of 2 things: Games with bugs causing these issues, or too much stress on my "older" hardware causing the BSOD. Probably both: unoptimized code (for my configuration) which causes too much stress, yielding a BSOD.

What do you think? Have we got a case closed here?