BSOD when playing some games: Caused by both ntoskrnl.exe and ntkrnlmp

MidnightR · 03 Feb 2014

Hello,

I've been getting the BSOD for the past couple weeks when playing the game Hearthstone and only Hearthstone. I wiped my computer and did a fresh install hoping it would fix it but it didn't. I figured it must be something with the game since no other game was giving me the error and windows never crashed outside of it.

But I just bought Skyrim and got an error almost right away.

I did some searching and read it might be a memory problem. I ran Windows Memory Diagnostic tool and it came up with nothing. The errors have always been linked to ntoskrnl.exe but tonight's latest error also included ntkrnlmp.exe in on the fun.

I'm kinda running out of ideas on what to do. Maybe Windows Update has been corrupting those files?

I've attached the two dmp files from the crashes. Whocrashed also says there's a file called "Memory.dmp" but that's almost 700mb. So I'll just post what Whocrashed reported there:

On Mon 2/3/2014 8:03:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7A (0xFFFFF6FC400316A0, 0xFFFFFFFFC000000E, 0x1659DBBE0, 0xFFFFF880062D4000)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

koolkat77 · 03 Feb 2014

AVG is contributing to your BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from system
Registry and SPTD problems | DAEMON Pro Help

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

Rt64win7.sys Thu Feb 26 15:04:13 2009 (49A65B0D)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Driver Reference Table - Rt64win7.sys

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

Install all updates including Service Pack One: Learn how to install Windows 7 Service Pack 1 (SP1)

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Run Disk Check on your Hard Drive(s): Disk Check

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

Keep us posted.

MidnightR · 07 Feb 2014

Thanks for your advice. I did some checking on my hard drive and it was going bad. It was having trouble spinning up and staying at 7200rpm. So I put in a new hard drive, redid my computer, followed your advice on what not to install and everything seemed to be going well. But last night I got another BSOD. This time though, the computer was just idling. I really don't know where to go from here.

I've attached the DMP file from last night. Thanks again for any help.

koolkat77 · 07 Feb 2014

Same error.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc400357a8, ffffffffc000000e, 5b421be0, fffff88006af5000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36c1a )

Followup: MachineOwner
---------

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

MidnightR · 04 Mar 2014

Hello,

I found my computer had two reserved partitions for windows, one on each hard drive. So I wiped all the partitions and started fresh. For the next three weeks, my computer ran great and there were no more crashes. Until a few days ago when I started getting the same exact crashes. Thinking I must have installed something to cause it, I redid my computer again and kept only the basic things. No go, it just crashed again today.

I've tried everything suggested here and I don't know why I'm still getting crashes. It's driving me bonkers.

Thanks for any help.