BSOD: Memory Management, even after reinstall

Mark67 · 29 Mar 2013

Hello everyone, I am having a very generic BSOD issue with a new computer I built about 2 months ago. I initially built the computer, and everything worked great for about 1 week, then started getting blue screens, constantly, they were complaining about MEMORY_MANAGEMENT, and the ntoskrnl.exe. It go so bad it would blue screen right after reboot with nothing running. I tried removing all the drivers I could think of, but they still happened. They wouldn't happen in Safe Mode, so I still believe it was software and not hardware. Even though, I performed a complete Memtest86+ test, but that returned no errors.

I gave up, and figured I would reinstall W7 Pro, and slowly reinstall the drivers. But after doing that I had no problems. I completed the reinstall, and everything was fine for 2 months no, but the other day I received another BSOD, with the same MEMORY_MANAGEMENT. I figured it was time to ask for help.

Here is the information from the WhoCrashed app:

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 3/27/2013 5:00:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032613-4102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x41284, 0x6C3A2001, 0x53, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 3/27/2013 5:00:20 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: 0x1A (0x41284, 0x6C3A2001, 0x53, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Also, I am attaching the SF files.

I really don't want to redo the system since I haven't been able to nail down the cause. I really hope you guys can help.

Arc · 30 Mar 2013

In the present situation, the BSOD is caused by avast! Virtualization Driver.

Code:

fffff880`088c01d8  fffff880`03f6141aUnable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
 aswSnx+0x7741a

Description here: Driver Reference Table - aswSnx.SYS

Uninstall Avast using Avast Uninstall Utility. 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.

Mark67 · 30 Mar 2013

That is great news, thanks so much for the help. I have swapped the AV applications and now have MSE. I will give it a few days to see, but I think this will solve my issue.

Arc · 16 Apr 2013

How is the system running now?

Mark67 · 17 Apr 2013

Everything is running smooth as butter!!!!

Closing...

Arc · 18 Apr 2013

Good news :)
For any further issue, let us know :)

Mark67 · 02 May 2013

Ok, so it has been a little more then 1 month, and another BSOD. Looks to be the same type, MEMORY MANAGEMENT.

I have included the current files.

Arc · 02 May 2013

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Mark67 · 02 May 2013

I have done both of those tasks in the past, but not for as long as you are asking, with negative results each time. I will do that over the next few nights.

Arc · 03 May 2013

If after running memtest over at least 8 passes with no errors, enable driver verifier.

It should be either a failing RAM or any driver passing bad memory information. So we should get some idea out of either of these tests.