Memory Management BSOD x2

DrSNAFU · 17 Nov 2013

My computer's been running well for at least a couple years now but ever since I played a particular game a week or so ago (probably not the issue but it's State of Decay, known to overheat some peoples computers) all my games have been crashing and now I've had BSODs in two separate games.

State of Decay began crashing, sometimes requiring me to restart my computer to get the game running again due to an engine memory writing error of some sort. I found things in the background were crashing while I played, like Firefox and OpenOffice that I had running while playing. Then the game BSOD'd me, MEMORY MANAGEMENT, Parameter 0x3452. I played other games. They too started crashing. Warframe and now Planetside 2, which crashed once the day before yesterday then 2 times today. That game crashes often but then this morning it BSODs me as well, Memory management, 0x41790. Since that last BSOD my antivirus software won't start due to an error in one of its files, probably due to the crash since it was functioning properly up until then. It seems to run well with no errors when I'm not doing strenuous things like playing games.

I've run 10 passes of windows memory checker on standard, no issues. Trying memtest 86 next. Zip file attached, please advise.

Arc · 17 Nov 2013

Hi DrSNAFU.

There is a hint that Kaspersky is failing.

Code:

fffff880`033fcf18  fffff880`04481d33Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
 klif+0x75d33

Description here: Driver Reference Table - klif.sys

Uninstall Kaspersky using Kaspersky Removal Tool. At least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.
_____________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 12f4a000, fffff700011f9530, 53100000910d0424}

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

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

DrSNAFU · 18 Nov 2013

I went in the hardware direction first. Found one of my ram DIMMs was throwing errors at a rate of about 10 per hour so I pulled the chip. Running on 4gb now.

Ran MBAM and MSE, both came up clean. Checking to see if I can RMA 2 year old ram to Patriot.