Getting a BSOD with the error of MEMORY MANAGEMENT

Dump file:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10240.16412.amd64fre.th1.150729-1800
Machine Name:
Kernel base = 0xfffff801`0bc19000 PsLoadedModuleList = 0xfffff801`0bf3e030
Debug session time: Mon Aug 31 01:50:56.922 2015 (UTC - 5:00)
System Uptime: 0 days 0:04:48.853
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`7bc7d018).  Type ".hh dbgerr001" for details
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41793, fffff6bffce0cf38, 3, 2} Page 10b08b not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+219b8 ) Followup: MachineOwner
--------- 2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
******************************************************************************* MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: fffff6bffce0cf38
Arg3: 0000000000000003
Arg4: 0000000000000002 Debugging Details:
------------------ Page 10b08b not present in the dump file. Type ".hh dbgerr004" for details BUGCHECK_STR:  0x1a_41793 DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT PROCESS_NAME:  backgroundTask CURRENT_IRQL:  2 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre LAST_CONTROL_TRANSFER:  from fffff8010bd967b8 to fffff8010bd66220 STACK_TEXT: 
ffffd001`01e6c348 fffff801`0bd967b8 : 00000000`0000001a 00000000`00041793 fffff6bf`fce0cf38 00000000`00000003 : nt!KeBugCheckEx
ffffd001`01e6c350 fffff801`0bc45eb0 : ffffe001`67bb4500 ffffd001`01e6c619 ffffe001`62e43c78 ffffe001`667f68b0 : nt! ?? ::FNODOBFM::`string'+0x219b8
ffffd001`01e6c550 fffff801`0c0dacb7 : ffffe001`667f0b30 ffffe001`667f0b30 ffffe001`6831a380 ffffe001`62e43780 : nt!MiDeleteVad+0x4b0
ffffd001`01e6c680 fffff801`0c0daa13 : 00000000`00040000 ffffd001`01e6c918 00000000`00000000 ffffe001`62e43780 : nt!MmCleanProcessAddressSpace+0xef
ffffd001`01e6c6e0 fffff801`0c0d361b : ffffe001`62e43780 ffffc001`4b5c3950 ffffd001`01e6c918 00000000`00000000 : nt!PspRundownSingleProcess+0x12b
ffffd001`01e6c770 fffff801`0c137318 : ffffe001`c000007b ffffd001`01e6cb01 00007ff6`7bc7b000 ffffe001`62e43780 : nt!PspExitThread+0x5fb
ffffd001`01e6c870 fffff801`0c1372ff : 00000000`00000000 fffff801`0bcc3601 00000000`00000101 ffffe001`6830b4e0 : nt!PsExitCurrentUserThread+0x18
ffffd001`01e6c8a0 fffff801`0bc5a7d2 : 00000000`00000000 00007ff9`00000010 ffffe001`6830b558 ffffe001`6830b570 : nt!KiSchedulerApcTerminate+0x1f
ffffd001`01e6c8d0 fffff801`0bd69550 : 0000000a`42406c60 ffffd001`01e6c950 fffff801`0bcc4268 00000000`00000000 : nt!KiDeliverApc+0x2f2
ffffd001`01e6c950 fffff801`0bd7090a : fffff6fb`5ffe70d8 fffff6bf`fce1b850 ffff1f79`460ec01e 0000000a`42403e50 : nt!KiInitiateUserApc+0x70
ffffd001`01e6ca90 00007ff9`c376505a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
0000000a`4235f478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`c376505a
STACK_COMMAND:  kb FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+219b8
fffff801`0bd967b8 cc              int     3 SYMBOL_STACK_INDEX:  1 SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+219b8 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: nt IMAGE_NAME:  ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP:  55b99f32 BUCKET_ID_FUNC_OFFSET:  219b8 FAILURE_BUCKET_ID:  0x1a_41793_nt!_??_::FNODOBFM::_string_ BUCKET_ID:  0x1a_41793_nt!_??_::FNODOBFM::_string_ ANALYSIS_SOURCE:  KM FAILURE_ID_HASH_STRING:  km:0x1a_41793_nt!_??_::fnodobfm::_string_ FAILURE_ID_HASH:  {2bb49b32-09fa-a96d-8b93-292cf7a50b3f} Followup: MachineOwner
---------