Windows 10 BSOD Memory Management / KNode Exception Not Handled

[KJBryan]

Hi,

I've been experiencing increasingly frequent BSODs on my system in the past month. The usual culprit is Memory Management but I occasionally get KNode_Exception... errors too.

I have read multiple threads on multiple sites and WF was the closest I came to finding useful answers.

It started when playing Tom Clancy's The Division in late March leading me to reformat my HDs and install a clean version of Windows 10. With the latest Nvidia drivers this improved stability a lot and the crashes almost stopped entirely in that game.

But the problem reared its ugly head again this week - the Overwatch Beta crashed every 5 minutes which led me to explore the BSOD issue further. I followed the advice you'd given another user (BSOD: Windows 10 Memory Management) and it definitely helped.

I ran a 6 hour+ MemTest but found no errors. I ran an SFC and Chkdsk but found no errors. I even bought Driver Fusion Premium to find the latest drivers for my hardware and updated them all. Finally, I removed Avast security and then cleaned the Nvidia drivers using the tool recommended and installed the latest versions (including the 3D drivers, and HD audio) and this improved things hugely. I maybe had one more crash in three days of play.

But then today, playing XCom 2 for a couple of hours on a warm day in London, the system has crashed 3 times on me and I decided to post my DMP files to you incredibly helpful people here.

I run my system slightly over-clocked using the Asus Suite 4-way-optimisation meaning the CPU scales from 0.8hz-4.5ghz depending on load.

I have a matched pair of Kingston ram so I don't think it's a timings clash.

My MSI 970 GTX card is only 6 months old so I'm hoping that's not the issue either though it should still be covered by warranty.

According to Window's Reliability Monitor I'm about a 2 at the moment. I was running this same system on Windows 7 and didn't have anything like this level of instability.

If you can help me narrow down whether this is a software, power or hardware issue I would be hugely grateful.

The .zip file of recent activity is attached.

Thanks,
K

 

[KJBryan]

Hi Kemical,

I ran FurMark and it was fine, no errors. Attached are the temperature readings from HWiNFO.

The PSU is a Cooler Master RS-750 - I'm pretty sure it's this one: Link Removed

There have been no crashes since I reset the BIOS to defaults but haven't been able to play anything for an extended period of time. Might be I was pushing it too far for Win 10 though.

K

 

[kemical]

Hi K,
your temps looked fine from what I could see. As does the PSU, thanks for the information.

I guess the real test is going to be the game it usually crashes under Xcom 2 is it?

 

[KJBryan]

Yeah XCom has caused every crash in the last week. I'l try and play it for a few hours straight soon and get back to you. Kind of hoping it is just an overclocking thing because then I'll just need to find better tweaked settings rather than forking out for new hardware,

 

[kemical]

It would be the best outcome..

 

[KJBryan]

Hey K,

So I downclocked the CPU and then ran the 'auto-tune' option from the BIOS which gave a very modest over clock from 3.5ghz - 4.1/2ghz on the CPU and everything has been much more stable. Played another couple of hours of XCom2 with no issues, and have played 5-6 hours of Fallout 4 since and it has been fine.

But just had my first BSOD since the downclock and auto-tune. Another Memory Management issue - suspecting something hardware based is wrong and guess it could be memoy, CPU or mobo. I have attached the dmp file in case it reveals anything else, otherwise I'm probably in the market for some new hardware.

In the meantime I can probably handle one crash every 6 hours of gaming.

 

[kemical]

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {61941, 1f24d270fc0, d, ffffd00040f56b00}

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

Followup: MachineOwner

Hi,
as you can see same old bugcheck. You wrote in post #21:

There have been no crashes since I reset the BIOS to defaults but haven't been able to play anything for an extended period of time. Might be I was pushing it too far for Win 10 though.

So it was decided you'd test playing Xcom:

Yeah XCom has caused every crash in the last week. I'l try and play it for a few hours straight soon and get back to you. Kind of hoping it is just an overclocking thing because then I'll just need to find better tweaked settings rather than forking out for new hardware,

Then your final post:

So I downclocked the CPU and then ran the 'auto-tune' option from the BIOS which gave a very modest over clock from 3.5ghz - 4.1/2ghz on the CPU and everything has been much more stable. Played another couple of hours of XCom2 with no issues, and have played 5-6 hours of Fallout 4 since and it has been fine.

But just had my first BSOD since the downclock and auto-tune.

First I assume when you wrote downclock of the CPU you actually meant GPU? Also it seems from the above that the system ran fine when settings were set back to defaults and your issue only appeared after the change.

So try playing Xcom on default settings or Fallout 4 and see if the crash still occurs. If it doesn't then you may need to tweak your overclocking even further.

Try the test and then post back.