blue screen memory management 0x1a

[transamraiser]

we are getting a memory management blue screen, attached is the dmp file

 

[Arc]

Hello transamraiser.

It is difficult to comment based on a single dump file .... it would have been better if you have posted it following the Blue Screen of Death (BSOD) Posting Instructions .

Anyway, the crash dump does not point to any failing driver. In this situation it would be better to test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error/red line, 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; obviously following the Blue Screen of Death (BSOD) Posting Instructions .
___________________________________________________________________________

BugCheck 1A, {41201, fffff68000380e80, b190ffffffffffff, fffffa80133767b0}

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

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