Question PC Crash post RAM Upgrade - Minidumps created during game-play - Help me understand the Minidump

Hyperr3121

Honorable
Jan 1, 2016
3
0
10,510
0
Hi guys,

Hope you are all doing well!
As per the title of this post, I have been crashing from time to time with what looks like my graphics dying (screen goes black, several pixels remain, PC crashes and restarts) ever since adding 2 extra sticks of RAM.

Any help, suggestions or anything else is much appreciated!

Thanks.

Situation:
Here is a top level overview of happened:
  • PC ran absolutely fine, decided to upgrade RAM due to a Black Friday deal.
  • I have recently bought 2 extra sticks of RAM (same speed and vendor as my current).
  • Added the RAM but PC wouldn't POST; kept on restarting with a black screen after BIOS boot; occasionally it wouldn't even boot to BIOS.
  • Tried and tested the old and new pair of RAM separately in DIMM slots A2 B2 and they both worked fine, PC booted on 2 sticks both of the times.
  • After some research, it turned out to be my mobo problem; updated BIOS and I was able to boot with 4 sticks just fine.
  • BIOS set RAM speed to 2133 hz so I set a profile to boost it to RAM marketed speeds of 3600hz.
  • PC was fine booting with both speeds; idling (leaving PC on desktop) has been very stable.
  • Problems come when gaming.
Here is where the fun begins:
  • Idling my PC has not crashed me (as of yet); crashes often during gameplay, most recently World of Warcraft (just flying around the world).
  • Creates minidumps every time it happens.
  • I have not yet turned the speeds down from 3600hz as I would like to get an outside opinion on what might be causing this/how it can be troubleshooted.
PC Specs:
I will post my PC specs here and the mini-dumps below:
(bought the PC pre-build from Cyberpower as it was a good deal at the time)

----(I checked the Timing numbers on the back of the RAM sticks, both pairs are the same)----
OLD RAM: Corsair Vengeance 16GB (2x8GB) DDR4/3600mhz Dual Channel Memory (LPX w/Heat Spreader) - in slots 2A and 2B
New RAM : CORSAIR VENGEANCE RGB PRO 16GB (2x8GB) DDR4 3600 (PC4-28800) - in slots 1A and 1B
CPU: AMD Ryzen 7 5800x
GPU: GeForce(R) RTX 3070 Ti 8GB
Mobo: Asus Prime X570-P (on latest BIOS as of now; version 4408).
PSU: Corsair RM750(W)
Storage:
- ST2000DM 008-2FR102 SATA Disk Device - 2TB -- HDD (new) (holds most of my installations)
- WDC WDS100T2B0C - 1TB -- HDD (old, from previous PC, only use this as file storage)
- WDC WDS500G2B0C-00PXH0 -- M.2 SSD ; Windows 11 installed on this


Mini-Dumps:
Read using WinDBG.
(I am on Win11 although it says my Kernel version is Win10, slightly confused on this?)


Mini Dump 1:
***
  • *
  • 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: fffff80613c3bd5a, Address of the instruction which caused the BugCheck
Arg3: ffff82826304e3d0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1453

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2311

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 171

Key : Analysis.Init.Elapsed.mSec
Value: 4801

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 120322-9609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80613c3bd5a

BUGCHECK_P3: ffff82826304e3d0

BUGCHECK_P4: 0

CONTEXT: ffff82826304e3d0 -- (.cxr 0xffff82826304e3d0)
rax=0000000000000000 rbx=ffffd5892bb883d0 rcx=ffffd5892b3b74a6
rdx=ffffc5034c0fe228 rsi=ffff9f8018777ba0 rdi=ffffd5892b3b74a0
rip=fffff80613c3bd5a rsp=ffff82826304edf0 rbp=ffff82826304eef0
r8=ffff82826304f0e0 r9=ffffd5892bb883d0 r10=00000000ffffffff
r11=ffff9f8000000000 r12=000000001dc45000 r13=ffffc5034c0fe230
r14=000055892bb88450 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050216
nt!MiMakeSystemCacheRangeValid+0x73a:
fffff80613c3bd5a 498b1e mov rbx,qword ptr [r14] ds:002b:000055892bb88450=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Wow.exe

STACK_TEXT:
ffff82826304edf0 fffff80613c3a9d9 : 0000000000000002 ffffac4500000000 ffffac45863b9278 0000000000000000 : nt!MiMakeSystemCacheRangeValid+0x73a
ffff82826304eff0 fffff80613c374a5 : 0000000000000000 000000001dc40000 0000000000000000 0000000000000000 : nt!MmCheckCachedPageStates+0xaa9
ffff82826304f180 fffff80614095723 : 000000001dc40000 0000000000000000 ffffd5892dc4ed60 0000000000010000 : nt!CcFetchDataForRead+0x95
ffff82826304f1e0 fffff80613c37028 : ffffd5892dc4ed60 000000001dc40000 0000000000000000 fffff80613ce6f00 : nt!CcMapAndCopyFromCache+0xf3
ffff82826304f2a0 fffff80616973bbb : ffffc50300000000 ffffd58920bf4d40 ffffd58900010000 0000000000000000 : nt!CcCopyReadEx+0x1c8
ffff82826304f380 fffff806169763fe : 0000000000010000 ffffd5892dc4ed60 ffff82826304f5f0 0000000000000001 : Ntfs!NtfsCachedRead+0x197
ffff82826304f3f0 fffff80616976d07 : ffffd5892e2ee7e8 ffffd589202f3aa0 ffffd58912000000 ffffd5891b173d00 : Ntfs!NtfsCommonRead+0x1f5e
ffff82826304f5c0 fffff80613ccb875 : ffffd589307e0a00 ffffd589202f3aa0 ffffd5891b173da0 ffffd589202f3ed0 : Ntfs!NtfsFsdRead+0x227
ffff82826304f6b0 fffff80615d29f5b : ffffd589341dbea0 ffffd589307e0a00 0000000000000000 fffff806140cc813 : nt!IofCallDriver+0x55
ffff82826304f6f0 fffff80615d27ba3 : ffff82826304f780 0000000000000000 001f000313a00000 ffffd58900000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15b
ffff82826304f760 fffff80613ccb875 : ffffd589202f3aa0 0000000000000000 ffffd5891b173da0 0000000000000000 : FLTMGR!FltpDispatch+0xa3
ffff82826304f7c0 fffff806140c2c70 : ffffd589202f3aa0 0000000000000000 ffff82826304f861 ffffd589202f3f00 : nt!IofCallDriver+0x55
ffff82826304f800 fffff806141a18e7 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopSynchronousServiceTail+0x1d0
ffff82826304f8b0 fffff806141a0eb3 : ffffd5892dc4ed60 0000000000000000 0000000000000000 000002a5d24c2870 : nt!IopReadFile+0x9f7
ffff82826304f9a0 fffff80613e3d1e8 : ffffd58930205280 ffff82826304fb20 000000fe77bfed28 0000000000000000 : nt!NtReadFile+0xd3
ffff82826304fa30 00007ffbc2caeec4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000fe77bfed08 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffbc2caeec4


SYMBOL_NAME: nt!MiMakeSystemCacheRangeValid+73a

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22621.819

STACK_COMMAND: .cxr 0xffff82826304e3d0 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 73a

FAILURE_BUCKET_ID: AV_nt!MiMakeSystemCacheRangeValid

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a2ae3f2c-7a5e-4749-cbf3-9f95d9658ac2}

Followup: MachineOwner

[B]Event Viewer Log for Mini Dump 1:
Event ID: 1001
Level: Error
User: System
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8028325a050, 0xffffae806af58900, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\120322-9531-01.dmp. Report Id: 757396a4-bcdb-482a-95ad-2982e9c26b11.




Mini Dump 2:[/B]

*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1483

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12129

Key : Analysis.IO.Other.Mb
Value: 7

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 9

Key : Analysis.Init.CPU.mSec
Value: 187

Key : Analysis.Init.Elapsed.mSec
Value: 10304

Key : Analysis.Memory.CommitPeak.Mb
Value: 108

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 120322-9531-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8028325a050

BUGCHECK_P3: ffffae806af58900

BUGCHECK_P4: 0

CONTEXT: ffffae806af58900 -- (.cxr 0xffffae806af58900)
rax=ffffd00f450fcf70 rbx=ffffd00f450fcf70 rcx=7fffd00f4511d020
rdx=0000000000000000 rsi=ffffd00f43e22000 rdi=7fffd00f4511d010
rip=fffff8028325a050 rsp=ffffbe88c56be550 rbp=ffffbe88c56be619
r8=0000000000000558 r9=ffffd00f450fcf70 r10=0000000000000001
r11=0000000000000001 r12=000000000000003b r13=ffffd00f43e5d000
r14=ffffd00f450e9000 r15=ffffd00f4726d010
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+0x2c:
fffff802
8325a050 8b4708 mov eax,dword ptr [rdi+8] ds:002b:7fffd00f4511d018=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffbe88
c56be550 fffff80283282bf0 : ffffd00f450fcf70 ffffd00f3f0ef2f8 ffffd00f3f0ef300 ffffd00f3f0ef308 : dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+0x2c
ffffbe88
c56be580 fffff8028325f4bd : ffffbe88c56be760 ffffd00f43efdc00 ffffd00f00000001 ffffd00f00000000 : dxgmms2!VidSchiSubmitHwQueueMmIoFlipCommand+0x3c4
ffffbe88
c56be680 fffff8028325e6ef : 0000000000000000 ffffd00f43efdd90 ffffd00f43efdcf0 ffffbe88c56be760 : dxgmms2!VidSchiReleasePacketToGpu+0xe3
ffffbe88
c56be6b0 fffff8028325d258 : ffffbe88c56be760 0000000000000000 ffffd00f43efdd90 ffffd00f47282030 : dxgmms2!HwQueueStagingList::ProcessHwQueue+0x8b
ffffbe88
c56be700 fffff8028325f099 : ffffd00f47282001 ffffd00f4726d010 ffffd00f3f2ff228 ffffd00f3f2ff230 : dxgmms2!HwQueueStagingList::~HwQueueStagingList+0x125b8
ffffbe88
c56be730 fffff8028325fd85 : ffffd00f47282010 ffffd00f43e90000 ffffd00f4726d010 fffff80283246ece : dxgmms2!VidSchiInsertCommandToHwQueue+0x18d
ffffbe88
c56be790 fffff80283283f88 : ffffd00f47282010 ffffd00f4726d010 ffffd00f43e22000 ffffd00f4c7cd200 : dxgmms2!VidSchiSubmitCommandPacketToHwQueue+0xfb
ffffbe88
c56be810 fffff8028387f6c6 : 0000000000000000 0000000000000000 0000000000000000 00000000c0837825 : dxgmms2!VidSchSubmitCommandToHwQueue+0x3f8
ffffbe88
c56be890 fffff8028387d69f : ffffd00f4c7cd200 ffff9b83f688d5e0 0000000000000fa0 ffffd00f439128d0 : dxgkrnl!DXGCONTEXT::SubmitPresentMultiPlaneOverlays3+0xd76
ffffbe88
c56bed90 fffff8028387aa57 : ffffd00f46d53650 ffffd00f43e20088 ffffbe88c56bfb20 ffff9b83f66e0d70 : dxgkrnl!DXGCONTEXT::PresentMultiPlaneOverlay3+0x10bf
ffffbe88
c56bf7c0 fffff80263c3d1e8 : 000001f3082c8ba0 ffffd00f46edb0c0 000001f30087b2f0 0000000000000000 : dxgkrnl!DxgkPresentMultiPlaneOverlay3+0x6b7
ffffbe88
c56bfaa0 00007ffe77105954 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
0000002a
7071a828 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe77105954


SYMBOL_NAME: dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+2c

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.815

STACK_COMMAND: .cxr 0xffffae806af58900 ; kb

BUCKET_ID_FUNC_OFFSET: 2c

FAILURE_BUCKET_ID: AV_dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ac24e096-b26d-9279-36cd-e9bec68b629f}

Followup: MachineOwner


Event Viewer Log for Mini Dump 2:
Event ID: 1001
Level: Error:
User: System
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80613c3bd5a, 0xffff82826304e3d0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\120322-9609-01.dmp. Report Id: 87dfbe67-9a49-4ef3-88fa-865bb08af364.
 
Hi guys,

Hope you are all doing well!
As per the title of this post, I have been crashing from time to time with what looks like my graphics dying (screen goes black, several pixels remain, PC crashes and restarts) ever since adding 2 extra sticks of RAM.

Any help, suggestions or anything else is much appreciated!

Thanks.

Situation:
Here is a top level overview of happened:
  • PC ran absolutely fine, decided to upgrade RAM due to a Black Friday deal.
  • I have recently bought 2 extra sticks of RAM (same speed and vendor as my current).
  • Added the RAM but PC wouldn't POST; kept on restarting with a black screen after BIOS boot; occasionally it wouldn't even boot to BIOS.
  • Tried and tested the old and new pair of RAM separately in DIMM slots A2 B2 and they both worked fine, PC booted on 2 sticks both of the times.
  • After some research, it turned out to be my mobo problem; updated BIOS and I was able to boot with 4 sticks just fine.
  • BIOS set RAM speed to 2133 hz so I set a profile to boost it to RAM marketed speeds of 3600hz.
  • PC was fine booting with both speeds; idling (leaving PC on desktop) has been very stable.
  • Problems come when gaming.
Here is where the fun begins:
  • Idling my PC has not crashed me (as of yet); crashes often during gameplay, most recently World of Warcraft (just flying around the world).
  • Creates minidumps every time it happens.
  • I have not yet turned the speeds down from 3600hz as I would like to get an outside opinion on what might be causing this/how it can be troubleshooted.
PC Specs:
I will post my PC specs here and the mini-dumps below:
(bought the PC pre-build from Cyberpower as it was a good deal at the time)

----(I checked the Timing numbers on the back of the RAM sticks, both pairs are the same)----
OLD RAM: Corsair Vengeance 16GB (2x8GB) DDR4/3600mhz Dual Channel Memory (LPX w/Heat Spreader) - in slots 2A and 2B
New RAM : CORSAIR VENGEANCE RGB PRO 16GB (2x8GB) DDR4 3600 (PC4-28800) - in slots 1A and 1B
CPU: AMD Ryzen 7 5800x
GPU: GeForce(R) RTX 3070 Ti 8GB
Mobo: Asus Prime X570-P (on latest BIOS as of now; version 4408).
PSU: Corsair RM750(W)
Storage:
- ST2000DM 008-2FR102 SATA Disk Device - 2TB -- HDD (new) (holds most of my installations)
- WDC WDS100T2B0C - 1TB -- HDD (old, from previous PC, only use this as file storage)
- WDC WDS500G2B0C-00PXH0 -- M.2 SSD ; Windows 11 installed on this


Mini-Dumps:
Read using WinDBG.
(I am on Win11 although it says my Kernel version is Win10, slightly confused on this?)


Mini Dump 1:
***

  • *
  • 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: fffff80613c3bd5a, Address of the instruction which caused the BugCheck
Arg3: ffff82826304e3d0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1453

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2311

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 171

Key : Analysis.Init.Elapsed.mSec
Value: 4801

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 120322-9609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80613c3bd5a

BUGCHECK_P3: ffff82826304e3d0

BUGCHECK_P4: 0

CONTEXT: ffff82826304e3d0 -- (.cxr 0xffff82826304e3d0)
rax=0000000000000000 rbx=ffffd5892bb883d0 rcx=ffffd5892b3b74a6
rdx=ffffc5034c0fe228 rsi=ffff9f8018777ba0 rdi=ffffd5892b3b74a0
rip=fffff80613c3bd5a rsp=ffff82826304edf0 rbp=ffff82826304eef0
r8=ffff82826304f0e0 r9=ffffd5892bb883d0 r10=00000000ffffffff
r11=ffff9f8000000000 r12=000000001dc45000 r13=ffffc5034c0fe230
r14=000055892bb88450 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050216
nt!MiMakeSystemCacheRangeValid+0x73a:
fffff80613c3bd5a 498b1e mov rbx,qword ptr [r14] ds:002b:000055892bb88450=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Wow.exe

STACK_TEXT:
ffff82826304edf0 fffff80613c3a9d9 : 0000000000000002 ffffac4500000000 ffffac45863b9278 0000000000000000 : nt!MiMakeSystemCacheRangeValid+0x73a
ffff82826304eff0 fffff80613c374a5 : 0000000000000000 000000001dc40000 0000000000000000 0000000000000000 : nt!MmCheckCachedPageStates+0xaa9
ffff82826304f180 fffff80614095723 : 000000001dc40000 0000000000000000 ffffd5892dc4ed60 0000000000010000 : nt!CcFetchDataForRead+0x95
ffff82826304f1e0 fffff80613c37028 : ffffd5892dc4ed60 000000001dc40000 0000000000000000 fffff80613ce6f00 : nt!CcMapAndCopyFromCache+0xf3
ffff82826304f2a0 fffff80616973bbb : ffffc50300000000 ffffd58920bf4d40 ffffd58900010000 0000000000000000 : nt!CcCopyReadEx+0x1c8
ffff82826304f380 fffff806169763fe : 0000000000010000 ffffd5892dc4ed60 ffff82826304f5f0 0000000000000001 : Ntfs!NtfsCachedRead+0x197
ffff82826304f3f0 fffff80616976d07 : ffffd5892e2ee7e8 ffffd589202f3aa0 ffffd58912000000 ffffd5891b173d00 : Ntfs!NtfsCommonRead+0x1f5e
ffff82826304f5c0 fffff80613ccb875 : ffffd589307e0a00 ffffd589202f3aa0 ffffd5891b173da0 ffffd589202f3ed0 : Ntfs!NtfsFsdRead+0x227
ffff82826304f6b0 fffff80615d29f5b : ffffd589341dbea0 ffffd589307e0a00 0000000000000000 fffff806140cc813 : nt!IofCallDriver+0x55
ffff82826304f6f0 fffff80615d27ba3 : ffff82826304f780 0000000000000000 001f000313a00000 ffffd58900000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15b
ffff82826304f760 fffff80613ccb875 : ffffd589202f3aa0 0000000000000000 ffffd5891b173da0 0000000000000000 : FLTMGR!FltpDispatch+0xa3
ffff82826304f7c0 fffff806140c2c70 : ffffd589202f3aa0 0000000000000000 ffff82826304f861 ffffd589202f3f00 : nt!IofCallDriver+0x55
ffff82826304f800 fffff806141a18e7 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopSynchronousServiceTail+0x1d0
ffff82826304f8b0 fffff806141a0eb3 : ffffd5892dc4ed60 0000000000000000 0000000000000000 000002a5d24c2870 : nt!IopReadFile+0x9f7
ffff82826304f9a0 fffff80613e3d1e8 : ffffd58930205280 ffff82826304fb20 000000fe77bfed28 0000000000000000 : nt!NtReadFile+0xd3
ffff82826304fa30 00007ffbc2caeec4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000fe77bfed08 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffbc2caeec4


SYMBOL_NAME: nt!MiMakeSystemCacheRangeValid+73a

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22621.819

STACK_COMMAND: .cxr 0xffff82826304e3d0 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 73a

FAILURE_BUCKET_ID: AV_nt!MiMakeSystemCacheRangeValid

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a2ae3f2c-7a5e-4749-cbf3-9f95d9658ac2}

Followup: MachineOwner

[B]Event Viewer Log for Mini Dump 1:
Event ID: 1001
Level: Error
User: System
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8028325a050, 0xffffae806af58900, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\120322-9531-01.dmp. Report Id: 757396a4-bcdb-482a-95ad-2982e9c26b11.




Mini Dump 2:[/B]

*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1483

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12129

Key : Analysis.IO.Other.Mb
Value: 7

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 9

Key : Analysis.Init.CPU.mSec
Value: 187

Key : Analysis.Init.Elapsed.mSec
Value: 10304

Key : Analysis.Memory.CommitPeak.Mb
Value: 108

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 120322-9531-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8028325a050

BUGCHECK_P3: ffffae806af58900

BUGCHECK_P4: 0

CONTEXT: ffffae806af58900 -- (.cxr 0xffffae806af58900)
rax=ffffd00f450fcf70 rbx=ffffd00f450fcf70 rcx=7fffd00f4511d020
rdx=0000000000000000 rsi=ffffd00f43e22000 rdi=7fffd00f4511d010
rip=fffff8028325a050 rsp=ffffbe88c56be550 rbp=ffffbe88c56be619
r8=0000000000000558 r9=ffffd00f450fcf70 r10=0000000000000001
r11=0000000000000001 r12=000000000000003b r13=ffffd00f43e5d000
r14=ffffd00f450e9000 r15=ffffd00f4726d010
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+0x2c:
fffff802
8325a050 8b4708 mov eax,dword ptr [rdi+8] ds:002b:7fffd00f4511d018=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffbe88
c56be550 fffff80283282bf0 : ffffd00f450fcf70 ffffd00f3f0ef2f8 ffffd00f3f0ef300 ffffd00f3f0ef308 : dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+0x2c
ffffbe88
c56be580 fffff8028325f4bd : ffffbe88c56be760 ffffd00f43efdc00 ffffd00f00000001 ffffd00f00000000 : dxgmms2!VidSchiSubmitHwQueueMmIoFlipCommand+0x3c4
ffffbe88
c56be680 fffff8028325e6ef : 0000000000000000 ffffd00f43efdd90 ffffd00f43efdcf0 ffffbe88c56be760 : dxgmms2!VidSchiReleasePacketToGpu+0xe3
ffffbe88
c56be6b0 fffff8028325d258 : ffffbe88c56be760 0000000000000000 ffffd00f43efdd90 ffffd00f47282030 : dxgmms2!HwQueueStagingList::ProcessHwQueue+0x8b
ffffbe88
c56be700 fffff8028325f099 : ffffd00f47282001 ffffd00f4726d010 ffffd00f3f2ff228 ffffd00f3f2ff230 : dxgmms2!HwQueueStagingList::~HwQueueStagingList+0x125b8
ffffbe88
c56be730 fffff8028325fd85 : ffffd00f47282010 ffffd00f43e90000 ffffd00f4726d010 fffff80283246ece : dxgmms2!VidSchiInsertCommandToHwQueue+0x18d
ffffbe88
c56be790 fffff80283283f88 : ffffd00f47282010 ffffd00f4726d010 ffffd00f43e22000 ffffd00f4c7cd200 : dxgmms2!VidSchiSubmitCommandPacketToHwQueue+0xfb
ffffbe88
c56be810 fffff8028387f6c6 : 0000000000000000 0000000000000000 0000000000000000 00000000c0837825 : dxgmms2!VidSchSubmitCommandToHwQueue+0x3f8
ffffbe88
c56be890 fffff8028387d69f : ffffd00f4c7cd200 ffff9b83f688d5e0 0000000000000fa0 ffffd00f439128d0 : dxgkrnl!DXGCONTEXT::SubmitPresentMultiPlaneOverlays3+0xd76
ffffbe88
c56bed90 fffff8028387aa57 : ffffd00f46d53650 ffffd00f43e20088 ffffbe88c56bfb20 ffff9b83f66e0d70 : dxgkrnl!DXGCONTEXT::PresentMultiPlaneOverlay3+0x10bf
ffffbe88
c56bf7c0 fffff80263c3d1e8 : 000001f3082c8ba0 ffffd00f46edb0c0 000001f30087b2f0 0000000000000000 : dxgkrnl!DxgkPresentMultiPlaneOverlay3+0x6b7
ffffbe88
c56bfaa0 00007ffe77105954 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
0000002a
7071a828 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe77105954


SYMBOL_NAME: dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+2c

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.815

STACK_COMMAND: .cxr 0xffffae806af58900 ; kb

BUCKET_ID_FUNC_OFFSET: 2c

FAILURE_BUCKET_ID: AV_dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ac24e096-b26d-9279-36cd-e9bec68b629f}

Followup: MachineOwner


Event Viewer Log for Mini Dump 2:
Event ID: 1001
Level: Error:
User: System
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80613c3bd5a, 0xffff82826304e3d0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\120322-9609-01.dmp. Report Id: 87dfbe67-9a49-4ef3-88fa-865bb08af364.
Ram sticks not bought as a kit are a coin flip if they will work well.

You can fuss with timings, voltage, speed and see if you can get it to work.

Consider returning the ram and getting a 2x16GB kit.
 
Dec 4, 2022
1
0
10
0
Hi guys,

Hope you are all doing well!
As per the title of this post, I have been crashing from time to time with what looks like my graphics dying (screen goes black, several pixels remain, PC crashes and restarts) ever since adding 2 extra sticks of RAM.

Any help, suggestions or anything else is much appreciated!

Thanks.

Situation:
Here is a top level overview of happened:
  • PC ran absolutely fine, decided to upgrade RAM due to a Black Friday deal.
  • I have recently bought 2 extra sticks of RAM (same speed and vendor as my current).
  • Added the RAM but PC wouldn't POST; kept on restarting with a black screen after BIOS boot; occasionally it wouldn't even boot to BIOS.
  • Tried and tested the old and new pair of RAM separately in DIMM slots A2 B2 and they both worked fine, PC booted on 2 sticks both of the times.
  • After some research, it turned out to be my mobo problem; updated BIOS and I was able to boot with 4 sticks just fine.
  • BIOS set RAM speed to 2133 hz so I set a profile to boost it to RAM marketed speeds of 3600hz.
  • PC was fine booting with both speeds; idling (leaving PC on desktop) has been very stable.
  • Problems come when gaming.
Here is where the fun begins:
  • Idling my PC has not crashed me (as of yet); crashes often during gameplay, most recently World of Warcraft (just flying around the world).
  • Creates minidumps every time it happens.
  • I have not yet turned the speeds down from 3600hz as I would like to get an outside opinion on what might be causing this/how it can be troubleshooted.
PC Specs:
I will post my PC specs here and the mini-dumps below:
(bought the PC pre-build from Cyberpower as it was a good deal at the time)

----(I checked the Timing numbers on the back of the RAM sticks, both pairs are the same)----
OLD RAM: Corsair Vengeance 16GB (2x8GB) DDR4/3600mhz Dual Channel Memory (LPX w/Heat Spreader) - in slots 2A and 2B
New RAM : CORSAIR VENGEANCE RGB PRO 16GB (2x8GB) DDR4 3600 (PC4-28800) - in slots 1A and 1B
CPU: AMD Ryzen 7 5800x
GPU: GeForce(R) RTX 3070 Ti 8GB
Mobo: Asus Prime X570-P (on latest BIOS as of now; version 4408).
PSU: Corsair RM750(W)
Storage:
- ST2000DM 008-2FR102 SATA Disk Device - 2TB -- HDD (new) (holds most of my installations)
- WDC WDS100T2B0C - 1TB -- HDD (old, from previous PC, only use this as file storage)
- WDC WDS500G2B0C-00PXH0 -- M.2 SSD ; Windows 11 installed on this


Mini-Dumps:
Read using WinDBG.
(I am on Win11 although it says my Kernel version is Win10, slightly confused on this?)


Mini Dump 1:
***

  • *
  • 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: fffff80613c3bd5a, Address of the instruction which caused the BugCheck
Arg3: ffff82826304e3d0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1453

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2311

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 171

Key : Analysis.Init.Elapsed.mSec
Value: 4801

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 120322-9609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80613c3bd5a

BUGCHECK_P3: ffff82826304e3d0

BUGCHECK_P4: 0

CONTEXT: ffff82826304e3d0 -- (.cxr 0xffff82826304e3d0)
rax=0000000000000000 rbx=ffffd5892bb883d0 rcx=ffffd5892b3b74a6
rdx=ffffc5034c0fe228 rsi=ffff9f8018777ba0 rdi=ffffd5892b3b74a0
rip=fffff80613c3bd5a rsp=ffff82826304edf0 rbp=ffff82826304eef0
r8=ffff82826304f0e0 r9=ffffd5892bb883d0 r10=00000000ffffffff
r11=ffff9f8000000000 r12=000000001dc45000 r13=ffffc5034c0fe230
r14=000055892bb88450 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050216
nt!MiMakeSystemCacheRangeValid+0x73a:
fffff80613c3bd5a 498b1e mov rbx,qword ptr [r14] ds:002b:000055892bb88450=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Wow.exe

STACK_TEXT:
ffff82826304edf0 fffff80613c3a9d9 : 0000000000000002 ffffac4500000000 ffffac45863b9278 0000000000000000 : nt!MiMakeSystemCacheRangeValid+0x73a
ffff82826304eff0 fffff80613c374a5 : 0000000000000000 000000001dc40000 0000000000000000 0000000000000000 : nt!MmCheckCachedPageStates+0xaa9
ffff82826304f180 fffff80614095723 : 000000001dc40000 0000000000000000 ffffd5892dc4ed60 0000000000010000 : nt!CcFetchDataForRead+0x95
ffff82826304f1e0 fffff80613c37028 : ffffd5892dc4ed60 000000001dc40000 0000000000000000 fffff80613ce6f00 : nt!CcMapAndCopyFromCache+0xf3
ffff82826304f2a0 fffff80616973bbb : ffffc50300000000 ffffd58920bf4d40 ffffd58900010000 0000000000000000 : nt!CcCopyReadEx+0x1c8
ffff82826304f380 fffff806169763fe : 0000000000010000 ffffd5892dc4ed60 ffff82826304f5f0 0000000000000001 : Ntfs!NtfsCachedRead+0x197
ffff82826304f3f0 fffff80616976d07 : ffffd5892e2ee7e8 ffffd589202f3aa0 ffffd58912000000 ffffd5891b173d00 : Ntfs!NtfsCommonRead+0x1f5e
ffff82826304f5c0 fffff80613ccb875 : ffffd589307e0a00 ffffd589202f3aa0 ffffd5891b173da0 ffffd589202f3ed0 : Ntfs!NtfsFsdRead+0x227
ffff82826304f6b0 fffff80615d29f5b : ffffd589341dbea0 ffffd589307e0a00 0000000000000000 fffff806140cc813 : nt!IofCallDriver+0x55
ffff82826304f6f0 fffff80615d27ba3 : ffff82826304f780 0000000000000000 001f000313a00000 ffffd58900000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15b
ffff82826304f760 fffff80613ccb875 : ffffd589202f3aa0 0000000000000000 ffffd5891b173da0 0000000000000000 : FLTMGR!FltpDispatch+0xa3
ffff82826304f7c0 fffff806140c2c70 : ffffd589202f3aa0 0000000000000000 ffff82826304f861 ffffd589202f3f00 : nt!IofCallDriver+0x55
ffff82826304f800 fffff806141a18e7 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopSynchronousServiceTail+0x1d0
ffff82826304f8b0 fffff806141a0eb3 : ffffd5892dc4ed60 0000000000000000 0000000000000000 000002a5d24c2870 : nt!IopReadFile+0x9f7
ffff82826304f9a0 fffff80613e3d1e8 : ffffd58930205280 ffff82826304fb20 000000fe77bfed28 0000000000000000 : nt!NtReadFile+0xd3
ffff82826304fa30 00007ffbc2caeec4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000fe77bfed08 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffbc2caeec4


SYMBOL_NAME: nt!MiMakeSystemCacheRangeValid+73a

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22621.819

STACK_COMMAND: .cxr 0xffff82826304e3d0 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 73a

FAILURE_BUCKET_ID: AV_nt!MiMakeSystemCacheRangeValid

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a2ae3f2c-7a5e-4749-cbf3-9f95d9658ac2}

Followup: MachineOwner

[B]Event Viewer Log for Mini Dump 1:
Event ID: 1001
Level: Error
User: System
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8028325a050, 0xffffae806af58900, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\120322-9531-01.dmp. Report Id: 757396a4-bcdb-482a-95ad-2982e9c26b11.




Mini Dump 2:[/B]

*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1483

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12129

Key : Analysis.IO.Other.Mb
Value: 7

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 9

Key : Analysis.Init.CPU.mSec
Value: 187

Key : Analysis.Init.Elapsed.mSec
Value: 10304

Key : Analysis.Memory.CommitPeak.Mb
Value: 108

Key : Bugcheck.Code.DumpHeader
Value: 0x3b

Key : Bugcheck.Code.Register
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 120322-9531-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8028325a050

BUGCHECK_P3: ffffae806af58900

BUGCHECK_P4: 0

CONTEXT: ffffae806af58900 -- (.cxr 0xffffae806af58900)
rax=ffffd00f450fcf70 rbx=ffffd00f450fcf70 rcx=7fffd00f4511d020
rdx=0000000000000000 rsi=ffffd00f43e22000 rdi=7fffd00f4511d010
rip=fffff8028325a050 rsp=ffffbe88c56be550 rbp=ffffbe88c56be619
r8=0000000000000558 r9=ffffd00f450fcf70 r10=0000000000000001
r11=0000000000000001 r12=000000000000003b r13=ffffd00f43e5d000
r14=ffffd00f450e9000 r15=ffffd00f4726d010
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+0x2c:
fffff802
8325a050 8b4708 mov eax,dword ptr [rdi+8] ds:002b:7fffd00f4511d018=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffbe88
c56be550 fffff80283282bf0 : ffffd00f450fcf70 ffffd00f3f0ef2f8 ffffd00f3f0ef300 ffffd00f3f0ef308 : dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+0x2c
ffffbe88
c56be580 fffff8028325f4bd : ffffbe88c56be760 ffffd00f43efdc00 ffffd00f00000001 ffffd00f00000000 : dxgmms2!VidSchiSubmitHwQueueMmIoFlipCommand+0x3c4
ffffbe88
c56be680 fffff8028325e6ef : 0000000000000000 ffffd00f43efdd90 ffffd00f43efdcf0 ffffbe88c56be760 : dxgmms2!VidSchiReleasePacketToGpu+0xe3
ffffbe88
c56be6b0 fffff8028325d258 : ffffbe88c56be760 0000000000000000 ffffd00f43efdd90 ffffd00f47282030 : dxgmms2!HwQueueStagingList::ProcessHwQueue+0x8b
ffffbe88
c56be700 fffff8028325f099 : ffffd00f47282001 ffffd00f4726d010 ffffd00f3f2ff228 ffffd00f3f2ff230 : dxgmms2!HwQueueStagingList::~HwQueueStagingList+0x125b8
ffffbe88
c56be730 fffff8028325fd85 : ffffd00f47282010 ffffd00f43e90000 ffffd00f4726d010 fffff80283246ece : dxgmms2!VidSchiInsertCommandToHwQueue+0x18d
ffffbe88
c56be790 fffff80283283f88 : ffffd00f47282010 ffffd00f4726d010 ffffd00f43e22000 ffffd00f4c7cd200 : dxgmms2!VidSchiSubmitCommandPacketToHwQueue+0xfb
ffffbe88
c56be810 fffff8028387f6c6 : 0000000000000000 0000000000000000 0000000000000000 00000000c0837825 : dxgmms2!VidSchSubmitCommandToHwQueue+0x3f8
ffffbe88
c56be890 fffff8028387d69f : ffffd00f4c7cd200 ffff9b83f688d5e0 0000000000000fa0 ffffd00f439128d0 : dxgkrnl!DXGCONTEXT::SubmitPresentMultiPlaneOverlays3+0xd76
ffffbe88
c56bed90 fffff8028387aa57 : ffffd00f46d53650 ffffd00f43e20088 ffffbe88c56bfb20 ffff9b83f66e0d70 : dxgkrnl!DXGCONTEXT::PresentMultiPlaneOverlay3+0x10bf
ffffbe88
c56bf7c0 fffff80263c3d1e8 : 000001f3082c8ba0 ffffd00f46edb0c0 000001f30087b2f0 0000000000000000 : dxgkrnl!DxgkPresentMultiPlaneOverlay3+0x6b7
ffffbe88
c56bfaa0 00007ffe77105954 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
0000002a
7071a828 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe77105954


SYMBOL_NAME: dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry+2c

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.815

STACK_COMMAND: .cxr 0xffffae806af58900 ; kb

BUCKET_ID_FUNC_OFFSET: 2c

FAILURE_BUCKET_ID: AV_dxgmms2!_VIDSCH_FLIP_QUEUE_ENTRY::ZeroFlipQueueEntry

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ac24e096-b26d-9279-36cd-e9bec68b629f}

Followup: MachineOwner


Event Viewer Log for Mini Dump 2:
Event ID: 1001
Level: Error:
User: System
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80613c3bd5a, 0xffff82826304e3d0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\120322-9609-01.dmp. Report Id: 87dfbe67-9a49-4ef3-88fa-865bb08af364.
Hello , im not an expert but i have the impression that u can reliably go as fast as 3200mhz using 4 sticks especially when u haven t gotten a proper 4 sticks kit that "guarantees higher speeds and compatibility". The memory controller is much more stressed with 4 sticks and can t go as high in speeds...On the bright side u can probably run very tight timings cl14 and below and u ll get even better performance than 2 sticks of 3600 cl16-18 speed. Use the USMUS tool to find a good setting for 3200mhz and do ur testing.If that works fine then u can expirement a lil more bumping the speeds up slowly and see where s the sweet spot. Although if 3200mhz works great for you i don t think it ll be worth to try further for higher speeds,,,the returns will be diminishing especially for gaming
 

ASK THE COMMUNITY