blue screen ntkrnlmp.exe RRS feed

  • Question

  • hello i have windows 8.1 and i have been getting this annoying kernal data inpage error and i have found that this is the cause please help me on what to do 

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. ( Online Crash Dump Analysis Service See for more information Windows 8 Kernel Version 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 9600.18696.amd64fre.winblue_ltsb.170511-1554 Machine Name: Kernel base = 0xfffff800`f1e14000 PsLoadedModuleList = 0xfffff800`f20e6630 Debug session time: Mon Jul 3 06:55:36.207 2017 (UTC - 4:00) System Uptime: 0 days 0:13:17.942 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address) Arg2: 0000000000000000, error status (normally i/o status code) Arg3: ffffe000c50a2010, current process (virtual address for lock type 3, or PTE) Arg4: ffffc000aab29040, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x7a_0 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: ffffd000a5fa1870 -- (.trap 0xffffd000a5fa1870) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000022 rbx=0000000000000000 rcx=ffffd000a5fa1a20 rdx=ffffc000aab29000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800f22d36c3 rsp=ffffd000a5fa1a00 rbp=0000000000000001 r8=00000000ffffffff r9=fffff800f1e14000 r10=fffff800f2112560 r11=ffffc000aaaa9850 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!MiFreeRelocations+0x37: fffff800`f22d36c3 488b4f40 mov rcx,qword ptr [rdi+40h] ds:00000000`00000040=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800f1f96795 to fffff800f1f61da0 STACK_TEXT: ffffd000`a5fa14f8 fffff800`f1f96795 : 00000000`0000007a 00000000`00000004 00000000`00000000 ffffe000`c50a2010 : nt!KeBugCheckEx ffffd000`a5fa1500 fffff800`f1e9e764 : 00000000`00000002 ffffd000`a5fa1668 fffff800`f2167dc0 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x244c5 ffffd000`a5fa15f0 fffff800`f1e59d3a : fffff800`f2167dc0 ffffe000`c3e39040 00000000`00000000 00001f80`000c0018 : nt!MiIssueHardFault+0x184 ffffd000`a5fa16b0 fffff800`f1f6c02f : 00000000`00000000 ffffe000`c90cdff0 ffffe000`c4382c00 fffff800`f20b0704 : nt!MmAccessFault+0x5ba ffffd000`a5fa1870 fffff800`f22d36c3 : 00000000`00000000 ffffe000`c90cdff0 00000000`00000001 ffffe000`c90cdd80 : nt!KiPageFault+0x12f ffffd000`a5fa1a00 fffff800`f1eb616d : ffffe000`c90cdff0 00000000`00000000 ffffc000`aaaa9850 fffff800`f1e5973f : nt!MiFreeRelocations+0x37 ffffd000`a5fa1a40 fffff800`f1eb60f8 : 00000000`000802a1 00000000`00000000 ffffe000`c90cdd80 00000000`00000001 : nt!MiDeleteControlArea+0x6d ffffd000`a5fa1a70 fffff800`f21eed75 : 00000000`00000000 ffffe000`c90cdd80 ffffe000`000802a1 00000000`0000000a : nt!MiDereferenceControlAreaProbe+0x10 ffffd000`a5fa1aa0 fffff800`f1f2bbe8 : fffff800`f2167000 ffffd000`a5fa1b50 ffffe000`c90cdd88 00000000`80000000 : nt!MiSegmentDelete+0xbd ffffd000`a5fa1ae0 fffff800`f1f48f95 : 00000000`00000000 fffff800`f20e6ba0 ffffe000`c3dab8c0 00000000`00000012 : nt!MiProcessDereferenceList+0x100 ffffd000`a5fa1b70 fffff800`f1e7b074 : ffffe000`c3e39040 00000000`00000080 ffffe000`c3e39040 00000000`00000000 : nt!MiDereferenceSegmentThread+0xd9 ffffd000`a5fa1c00 fffff800`f1f683c6 : fffff800`f2110180 ffffe000`c3e39040 fffff800`f2168a00 00000000`00000000 : nt!PspSystemThreadStartup+0x58 ffffd000`a5fa1c60 00000000`00000000 : ffffd000`a5fa2000 ffffd000`a5f9c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+244c5 fffff800`f1f96795 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+244c5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 59151392 FAILURE_BUCKET_ID: X64_0x7a_0_nt!_??_::FNODOBFM::_string_+244c5 BUCKET_ID: X64_0x7a_0_nt!_??_::FNODOBFM::_string_+244c5

    Monday, August 7, 2017 9:02 AM