Windows 10: Persistent BSODs memory corruption

Hello,


I'm posting here after lots of fruitless googling around to find the answer. I hope I'm in the right place. Is anyone able to lend a hand in figuring out why I keep getting BSODs every couple weeks? Latest minidump is pasted in below. I've memchecked, chkdsk'd and everything checks out ok. I googled what commsapps.exe and only found "commsapp.exe". At a bit of a loss here as I've updated all the drivers I can think to update and Win updates are ongoing and up-to-date. Could it be as simple as buying new sticks of memory? My online research seems to point more to driver failure, but no idea which driver. Thanks in advance for any help, everyone!


Danny

Microsoft R Windows Debugger Version 6.12.0002.633 AMD64
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080320-23046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 18362 MP 8 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`5400b000 PsLoadedModuleList = 0xfffff801`54453190
Debug session time: Mon Aug 3 14:25:33.766 2020 UTC - 4:00
System Uptime: 9 days 3:36:01.002
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, ffff8e683cbbd4af, ffff878f9ff2b990, 0}

Probably caused by : memory_corruption

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

*** Memory manager detected 390913 instances of page corruption, target is likely to have memory corruption.

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

SYSTEM_SERVICE_EXCEPTION 3b
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: ffff8e683cbbd4af, Address of the instruction which caused the bugcheck
Arg3: ffff878f9ff2b990, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
win32kbase!DirectComposition::CApplicationChannel::CompleteDisconnection+14f
ffff8e68`3cbbd4af 498b5e08 mov rbx,qword ptr [r14+8]

CONTEXT: ffff878f9ff2b990 -- .cxr 0xffff878f9ff2b990
rax=ffff8e100fab1130 rbx=f7ff8e1003ae3db0 rcx=0000000000000473
rdx=0000000000000280 rsi=ffff8e100a604cb0 rdi=0000000000000000
rip=ffff8e683cbbd4af rsp=ffff878f9ff2c380 rbp=ffff878f9ff2c501
r8=ffff8e100faa117a r9=0000000000000022 r10=00000000ffffffff
r11=0000000000000248 r12=0000000000000000 r13=ffffd18f48e3a080
r14=f7ff8e1003ae3db0 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
win32kbase!DirectComposition::CApplicationChannel::CompleteDisconnection+0x14f:
ffff8e68`3cbbd4af 498b5e08 mov rbx,qword ptr [r14+8] ds:002b:f7ff8e10`03ae3db8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x3B

PROCESS_NAME: commsapps.exe

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 5f701

LAST_CONTROL_TRANSFER: from 0000000000000000 to ffff8e683cbbd4af

STACK_TEXT:
ffff878f`9ff2c380 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!DirectComposition::CApplicationChannel::CompleteDisconnection+0x14f


CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
ffff8e683cbbd0a8-ffff8e683cbbd0a9 2 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+78
[ 48 ff:4c 8b ]
ffff8e683cbbd0af-ffff8e683cbbd0b2 4 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+7f +0x07
[ 0f 1f 44 00:e8 6c 93 29 ]
ffff8e683cbbd0b9-ffff8e683cbbd0ba 2 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+89 +0x0a
[ 48 ff:4c 8b ]
ffff8e683cbbd0c0-ffff8e683cbbd0c3 4 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+90 +0x07
[ 0f 1f 44 00:e8 5b 93 29 ]
ffff8e683cbbd0e4-ffff8e683cbbd0e5 2 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+b4 +0x24
[ 48 ff:4c 8b ]
ffff8e683cbbd0eb-ffff8e683cbbd0ee 4 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+bb +0x07
[ 0f 1f 44 00:e8 30 93 29 ]
ffff8e683cbbd0f0-ffff8e683cbbd0f1 2 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+c0 +0x05
[ 48 ff:4c 8b ]
ffff8e683cbbd0f7-ffff8e683cbbd0fa 4 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteReconnection+c7 +0x07
[ 0f 1f 44 00:e8 24 93 29 ]
ffff8e683cbbd2b4-ffff8e683cbbd2b5 2 bytes - win32kbase!DirectComposition::CDwmChannel::Create+98 +0x1bd
[ 48 ff:4c 8b ]
ffff8e683cbbd2bb-ffff8e683cbbd2be 4 bytes - win32kbase!DirectComposition::CDwmChannel::Create+9f +0x07
[ 0f 1f 44 00:e8 60 91 29 ]
ffff8e683cbbd2c5-ffff8e683cbbd2c6 2 bytes - win32kbase!DirectComposition::CDwmChannel::Create+a9 +0x0a
[ 48 ff:4c 8b ]
ffff8e683cbbd2cc-ffff8e683cbbd2cf 4 bytes - win32kbase!DirectComposition::CDwmChannel::Create+b0 +0x07
[ 0f 1f 44 00:e8 4f 91 29 ]
ffff8e683cbbd2e5-ffff8e683cbbd2e6 2 bytes - win32kbase!DirectComposition::CDwmChannel::Create+c9 +0x19
[ 48 ff:4c 8b ]
ffff8e683cbbd2ec-ffff8e683cbbd2ef 4 bytes - win32kbase!DirectComposition::CDwmChannel::Create+d0 +0x07
[ 0f 1f 44 00:e8 2f 91 29 ]
ffff8e683cbbd2f1-ffff8e683cbbd2f2 2 bytes - win32kbase!DirectComposition::CDwmChannel::Create+d5 +0x05
[ 48 ff:4c 8b ]
ffff8e683cbbd2f8-ffff8e683cbbd2fb 4 bytes - win32kbase!DirectComposition::CDwmChannel::Create+dc +0x07
[ 0f 1f 44 00:e8 23 91 29 ]
ffff8e683cbbd34f-ffff8e683cbbd354 6 bytes - win32kbase!DirectComposition::CConnection:iscardAllCompositionFrames+17 +0x57
[ ff 15 5b 94 22 00:e8 4c 8f 29 00 90 ]
ffff8e683cbbd3dc-ffff8e683cbbd3e1 6 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteDisconnection+7c +0x8d
[ ff 15 ce 93 22 00:e8 bf 8e 29 00 90 ]
ffff8e683cbbd4cd-ffff8e683cbbd4d2 6 bytes - win32kbase!DirectComposition::CApplicationChannel::CompleteDisconnection+16d +0xf1
[ ff 15 dd 92 22 00:e8 ce 8d 29 00 90 ]
ffff8e683cbbd56f-ffff8e683cbbd574 6 bytes - win32kbase!DirectComposition::CApplicationChannel::ReleaseShellResourceReference+13 +0xa2
[ ff 15 3b 92 22 00:e8 2c 8d 29 00 90 ]
ffff8e683cbbd5f0-ffff8e683cbbd5f5 6 bytes - win32kbase!NtDCompositionSetChannelCommitCompletionEvent+50 +0x81
[ ff 15 ba 91 22 00:e8 ab 8c 29 00 90 ]
ffff8e683cbbd69d-ffff8e683cbbd69e 2 bytes - win32kbase!DirectComposition::CApplicationChannel::SetCommitCompletionEvent+85 +0xad
[ 48 ff:4c 8b ]
ffff8e683cbbd6a4-ffff8e683cbbd6a7 4 bytes - win32kbase!DirectComposition::CApplicationChannel::SetCommitCompletionEvent+8c +0x07
[ 0f 1f 44 00:e8 77 8d 29 ]
ffff8e683cbbd95e-ffff8e683cbbd95f 2 bytes - win32kbase!NtDCompositionBeginFrame+ce +0x2ba
[ 48 ff:4c 8b ]
ffff8e683cbbd965-ffff8e683cbbd968 4 bytes - win32kbase!NtDCompositionBeginFrame+d5 +0x07
[ 0f 1f 44 00:e8 b6 8a 29 ]
ffff8e683cbbd977-ffff8e683cbbd978 2 bytes - win32kbase!NtDCompositionBeginFrame+e7 +0x12
[ 48 ff:4c 8b ]
ffff8e683cbbd97e-ffff8e683cbbd981 4 bytes - win32kbase!NtDCompositionBeginFrame+ee +0x07
[ 0f 1f 44 00:e8 9d 8a 29 ]
ffff8e683cbbd99c-ffff8e683cbbd99d 2 bytes - win32kbase!NtDCompositionBeginFrame+10c +0x1e
[ 48 ff:4c 8b ]
ffff8e683cbbd9a3-ffff8e683cbbd9a6 4 bytes - win32kbase!NtDCompositionBeginFrame+113 +0x07
[ 0f 1f 44 00:e8 78 8a 29 ]
ffff8e683cbbd9ad-ffff8e683cbbd9ae 2 bytes - win32kbase!NtDCompositionBeginFrame+11d +0x0a
[ 48 ff:4c 8b ]
ffff8e683cbbd9b4-ffff8e683cbbd9b7 4 bytes - win32kbase!NtDCompositionBeginFrame+124 +0x07
[ 0f 1f 44 00:e8 67 8a 29 ]
ffff8e683cbbd9e2-ffff8e683cbbd9e3 2 bytes - win32kbase!NtDCompositionBeginFrame+152 +0x2e
[ 48 ff:4c 8b ]
ffff8e683cbbd9e9-ffff8e683cbbd9ec 4 bytes - win32kbase!NtDCompositionBeginFrame+159 +0x07
[ 0f 1f 44 00:e8 32 8a 29 ]
ffff8e683cbbd9ee-ffff8e683cbbd9ef 2 bytes - win32kbase!NtDCompositionBeginFrame+15e +0x05
[ 48 ff:4c 8b ]
ffff8e683cbbd9f5-ffff8e683cbbd9f8 4 bytes - win32kbase!NtDCompositionBeginFrame+165 +0x07
[ 0f 1f 44 00:e8 26 8a 29 ]
ffff8e683cbbda90-ffff8e683cbbda91 2 bytes - win32kbase!NtDCompositionBeginFrame+200 +0x9b
[ 48 ff:4c 8b ]
ffff8e683cbbda97-ffff8e683cbbda9a 4 bytes - win32kbase!NtDCompositionBeginFrame+207 +0x07
[ 0f 1f 44 00:e8 84 89 29 ]
ffff8e683cbbdaf6-ffff8e683cbbdaf7 2 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+26 +0x5f
[ 48 ff:4c 8b ]
ffff8e683cbbdafd-ffff8e683cbbdb00 4 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+2d +0x07
[ 0f 1f 44 00:e8 1e 89 29 ]
ffff8e683cbbdb25-ffff8e683cbbdb26 2 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+55 +0x28
[ 48 ff:4c 8b ]
ffff8e683cbbdb2c-ffff8e683cbbdb2f 4 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+5c +0x07
[ 0f 1f 44 00:e8 ef 88 29 ]
ffff8e683cbbdb36-ffff8e683cbbdb37 2 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+66 +0x0a
[ 48 ff:4c 8b ]
ffff8e683cbbdb3d-ffff8e683cbbdb40 4 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+6d +0x07
[ 0f 1f 44 00:e8 de 88 29 ]
ffff8e683cbbdb8a-ffff8e683cbbdb8f 6 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+ba +0x4d
[ ff 15 20 8c 22 00:e8 11 87 29 00 90 ]
ffff8e683cbbdba8-ffff8e683cbbdbad 6 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+d8 +0x1e
[ ff 15 02 8c 22 00:e8 f3 86 29 00 90 ]
ffff8e683cbbdbc4-ffff8e683cbbdbc9 6 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+f4 +0x1c
[ ff 15 e6 8b 22 00:e8 d7 86 29 00 90 ]
ffff8e683cbbdbe7-ffff8e683cbbdbe8 2 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+117 +0x23
[ 48 ff:4c 8b ]
ffff8e683cbbdbee-ffff8e683cbbdbf1 4 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+11e +0x07
[ 0f 1f 44 00:e8 2d 88 29 ]
ffff8e683cbbdc68-ffff8e683cbbdc6d 6 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+198 +0x7a
[ ff 15 42 8b 22 00:e8 33 86 29 00 90 ]
ffff8e683cbbdc80-ffff8e683cbbdc85 6 bytes - win32kbase!DirectComposition::CConnection::BeginFrame+1b0 +0x18
[ ff 15 2a 8b 22 00:e8 1b 86 29 00 90 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.
240 errors : !win32kbase ffff8e683cbbd0a8-ffff8e683cbbdf87

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

STACK_COMMAND: .cxr 0xffff878f9ff2b990 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

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

*** Memory manager detected 390913 instances of page corruption, target is likely to have memory corruption.

2: kd> lmvm memory_corruption
start end module name
2: kd> lmvm memory_corruption
start end module name
2: kd> lmvm memory_corruption
start end module name

:)

 

Persistent BSOD ntoskrnl.exe

Ok understood CW. Could it be possible that even though the memory used is in the QVL list for the motherboard that it would still cause BSODs? I don't really feel like futzing with Memtest so would next steps be updating to latest BIOS, installing all RAM and then retesting?

 

BSODs with corrupt pagefile - Is That Possible?

Past couple of days I have been having random BSODS. A few examples of the messages was - Memory management / IRQL less than or equal to/ Thread could not be activated/ Page Pool something or other.

First BSODS I have had on this relatively new system so decided to take everything back to stock and test each part. I'm on Windows 7 Ultimate 64bit BTW.

HDtune error check - fine
Memtest86 - 10 passes fine
Prime 95 - 7hrs overnight fine
Graphics card - furmark/3DMark fine

Go to play a bit of WOW last night and it locks up straight away with memory management issue. So I looked into it a bit and read that it could possibly be a virtual memory/pagefile issue and that if it is corrupted it may cause these issues.

I then set the pagefile to zero and enabled clear pagefile on shutdown in the registry. When it rebooted I let the amount be set by Windows and disabled the registry entry for clearing it on shutdown and will see how it goes.

I had never heard of this issue before causing BSODS, is it common and what should be the next step if I get another one today with the new pagefile in place?

 

Multiple IRQ_NOT_LESS_OR_EQUAL bsod with memory corruption bsod's

Diagnostics Test [/i] Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.