Programs crashing, "Memory_Management" BSOD

Hi thatguy126.

There is only one crash dump in the uploaded zip, and that is not providing adequate information about the probable cause. But a MEMORY_MANAGEMENT (Stop 0x1A) BSOD occurs either for the failing physical RAM or for any driver passing bad information the the memory.

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 it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If there is no error, 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.
_____________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800428edd0, ffff, 0}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800428edd0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80003549d50 to fffff800034d8bc0

STACK_TEXT:  
fffff880`0ea7f5d8 fffff800`03549d50 : 00000000`0000001a 00000000`00041790 fffffa80`0428edd0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0ea7f5e0 fffff800`034a9e75 : ffffffff`00000000 00000000`337fffff fffffa80`00000000 fffffa80`12ad9b50 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`0ea7f7a0 fffff800`037ae05a : fffff8a0`0ba3b410 fffff880`0ea7fae0 00000000`00000000 fffffa80`12ad9b50 : nt!MmCleanProcessAddressSpace+0x679
fffff880`0ea7f7f0 fffff800`03792b7d : 00000000`00000001 fffff880`0ea7fa01 00000000`fffd5000 fffffa80`0d8feb50 : nt!PspExitThread+0x56a
fffff880`0ea7f8f0 fffff800`034cb6fa : 00000000`00000001 fffff880`0ea7fa68 00000000`00000001 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`0ea7f920 fffff800`034cba40 : 00000000`02dcf724 fffff880`0ea7f9a0 fffff800`03792af0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0ea7f9a0 fffff800`034d7ef7 : fffffa80`12ad9b50 00000000`fffd5000 00000000`000000c0 00000000`7421dd7c : nt!KiInitiateUserApc+0x70
fffff880`0ea7fae0 00000000`77ac2bba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`00d3e178 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ac2bba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`03549d50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+35084

FAILURE_ID_HASH:  {f6a6ed79-e275-9f8c-d5a4-3a37a32b0b4e}

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