Windows crashed due to memory_corruption

Question

I had this week a few bsod crashes.I looked up to the dump file and uploaded it to OSR online to see it.Here's what it showed.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`de40b000 PsLoadedModuleList = 0xfffff803`de7575c0
Debug session time: Sat Sep  2 12:19:46.046 2017 (UTC - 4:00)
System Uptime: 0 days 0:46:26.676
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff9d00d21db388, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803de4a765a, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffff9d00d21db388 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiUnlinkStandbyBatch+2ea
fffff803`de4a765a 49891c24        mov     qword ptr [r12],rbx

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  AV

PROCESS_NAME:  chrome.exe

BAD_PAGES_DETECTED: a58b

TRAP_FRAME:  ffffd980e88f4ff0 -- (.trap 0xffffd980e88f4ff0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0a00000000000000 rbx=0000000000000000 rcx=c000000000000001
rdx=ffffd78000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803de4a765a rsp=ffffd980e88f5180 rbp=0000000020000006
 r8=ffffd7ffffffffff  r9=00016a0db0000000 r10=7fffffffffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiUnlinkStandbyBatch+0x2ea:
fffff803`de4a765a 49891c24        mov     qword ptr [r12],rbx ds:00000000`00000000=000000000000a58b
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff803de5828a9 to fffff803de577560

STACK_TEXT:  
ffffd980`e88f4ea8 fffff803`de5828a9 : 00000000`0000000a ffff9d00`d21db388 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd980`e88f4eb0 fffff803`de580e7d : fffff803`de788100 ffffec80`034829a0 80000000`00000000 fffffe57`19b9f450 : nt!KiBugCheckDispatch+0x69
ffffd980`e88f4ff0 fffff803`de4a765a : ffffef80`00007508 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x23d
ffffd980`e88f5180 fffff803`de45082b : 00000000`0000000f ffffd980`e88f52e0 00000000`00000002 ffffec80`00000001 : nt!MiUnlinkStandbyBatch+0x2ea
ffffd980`e88f51e0 fffff803`de44f61e : 00000000`00001c40 00000000`00040000 ffffec80`044c89e0 ffffc785`df405de0 : nt!MmCheckCachedPageStates+0x92b
ffffd980`e88f5380 fffff803`de894419 : 00000000`01c40000 00000000`00000000 00000000`00000001 ffffd980`e88f5490 : nt!CcFetchDataForRead+0x8e
ffffd980`e88f53e0 fffff803`de44f3cb : ffffc785`ddbdd2a8 00000000`01c40000 00000000`00040000 fffff804`1f52ad01 : nt!CcMapAndCopyFromCache+0xd9
ffffd980`e88f5480 fffff804`1f5ed135 : ffffd980`e88f5590 ffffd980`00000000 ffffc785`00080000 ffff9d0d`ce77f710 : nt!CcCopyReadEx+0x12b
ffffd980`e88f5510 fffff804`1f385e3e : 00000000`00000190 ffffc785`e6320080 ffffc785`ddceb7a0 0000020a`c33ef080 : NTFS!NtfsCopyReadA+0x235
ffffd980`e88f57b0 fffff804`1f38331d : ffffd980`e88f58a0 ffffc785`ddceb700 ffffc785`e2577108 ffffc785`e2577010 : FLTMGR!FltpPerformFastIoCall+0x13e
ffffd980`e88f5810 fffff804`1f3b5da9 : ffffc785`e6320080 00000000`00000001 00000000`00000000 00000000`01c00000 : FLTMGR!FltpPassThroughFastIo+0xbd
ffffd980`e88f5870 fffff803`de8a01fd : ffffc785`ddceb7a0 ffffd7eb`f5e04100 ffffc785`e211cdf0 ffffc785`ddceb7a0 : FLTMGR!FltpFastIoRead+0x159
ffffd980`e88f5910 fffff803`de582413 : 00000000`0000157c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x43d
ffffd980`e88f5a10 00007ffa`7b315464 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000bd`c13feb28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffa`7b315464

STACK_COMMAND:  kb

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

 *** Memory manager detected 42379 instance(s) of page corruption, target is likely to have memory corruption.

Please respond if you can tell me a solution 

Thanks again 

***Post moved by the moderator to the appropriate forum category***

Answer 1

Hi,

The error that you're getting is possibly caused by a corrupted driver on your computer. Now, to resolve the blue screen that you're getting on your computer, you can follow some helpful steps from this article: Troubleshoot blue screen errors.

In addition to this, if the issue persist after performing the recommended steps from the provided article, you can use a debugging tool to track down the driver in question. You can refer to this article: Driver Verifier.

For more information about the error that you're getting, you can refer to this article: Bug Check 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.

Let us know the outcome. Feel free to post back.