Question Random system freeze

[capofobviously]

Hi there!

My system has strange behavior, whole computer just freeze indefinitely without any error and sometimes even without BSOD. Screen shows picture but i cannot move the cursor or use keyboard. The only way is to restart.
It happens during various states - sometimes during light work, rarely during gaming, few times I was doing nothing and PC was idle. My PC is relatively new and only few months old, Here are the specs

Event Viewer only shows bunch of Critical events ID 41 "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." but with no details inside report itself

Spoiler: Screenshot

I found only one MiniDump but struggle to investigate the cause. Dump relates to the general driver win32kbase.sys and doesn`t give some directions to search what exactly could cause the freeze.
Also tried to run Windows Memory Diagnostic and memtest86+ and both tests are successfully passed.

What could possibly couse critical freeze like that and what to look for? I just stuck and don`t know what to investigate next. I apperciate any help or advice. Thanks everyone in advance!

Dump file

5: 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: fffff80523833dd6, Address of the instruction which caused the BugCheck
Arg3: ffff810fc2907060, 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: 843

    Key  : Analysis.Elapsed.mSec
    Value: 2523

    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: 202

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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

    Key  : Failure.Bucket
    Value: AV_win32kbase!DirectComposition::CApplicationChannel::GetBatchFragment

    Key  : Failure.Hash
    Value: {0f52f06a-4d9e-e2b7-758c-85f1596f71a0}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80523833dd6

BUGCHECK_P3: ffff810fc2907060

BUGCHECK_P4: 0

FILE_IN_CAB:  051424-6828-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

CONTEXT:  ffff810fc2907060 -- (.cxr 0xffff810fc2907060)
rax=ffff9785c1c89080 rbx=ffffda823f5a8010 rcx=0000080000000000
rdx=0000000000000001 rsi=ffffda823e832580 rdi=0000080000000000
rip=fffff80523833dd6 rsp=ffff810fc2907a80 rbp=0000000000000d88
 r8=0000000000000000  r9=0000000000000001 r10=ffff8209e86d9c30
r11=0000000000000000 r12=0000000000000128 r13=ffff810fc2907c01
r14=ffffda823f5a8a01 r15=0000000000000004
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!ExAcquireResourceExclusiveLite+0x6:
fffff805`23833dd6 440fb7411a      movzx   r8d,word ptr [rcx+1Ah] ds:002b:00000800`0000001a=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  StartMenuExper

STACK_TEXT: 
ffff810f`c2907a80 ffff8209`e8637896     : ffff810f`00000000 ffffda82`3f5a8010 ffff810f`c2907b98 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x6
ffff810f`c2907ac0 ffff8209`e8636d77     : 00000000`00000000 ffff810f`00000004 00000000`00000001 ffffda82`3f5a8010 : win32kbase!DirectComposition::CApplicationChannel::GetBatchFragment+0x296
ffff810f`c2907b30 ffff8209`e8636a9c     : 00000000`00000000 ffff810f`c2907c58 00000000`00000000 ffffda82`00000004 : win32kbase!DirectComposition::CApplicationChannel::BuildBatch+0x187
ffff810f`c2907bd0 ffff8209`e8cbfc20     : ffffda82`0000000f 00000014`623fcb84 00000014`623fcbe8 00000000`00000000 : win32kbase!NtDCompositionCommitChannel+0x2cc
ffff810f`c2907d50 fffff805`23a2d935     : 00000000`00000000 0000020e`3641f3a8 00000000`00000020 00000000`00000000 : win32k!NtDCompositionCommitChannel+0x58
ffff810f`c2907db0 00007ffb`c6553794     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000014`623fcad8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`c6553794


STACK_COMMAND:  .process /r /p 0x3f800000; .cxr 0xffff810fc2907060 ; kb

SYMBOL_NAME:  win32kbase!DirectComposition::CApplicationChannel::GetBatchFragment+296

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.22621.3447

BUCKET_ID_FUNC_OFFSET:  296

FAILURE_BUCKET_ID:  AV_win32kbase!DirectComposition::CApplicationChannel::GetBatchFragment

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0f52f06a-4d9e-e2b7-758c-85f1596f71a0}

Followup:     MachineOwner
---------

 

[Lutfij]

Welcome to the forums, newcomer!

Speccy's don't include the make and model of your PSU nor it's age. Please include them. What sort of temps do you see when at idle and under load? How are you cooling your processor?

 

[capofobviously]

Speccy's don't include the make and model of your PSU nor it's age. Please include them

Power supply is ASUS ROG STRIX 650W 80+ Gold and was built in 2021.

What sort of temps do you see when at idle and under load?

CPU and GPU temperatures aren't exceeding 60°C under maximum load and works fine under stress tests. During idle its 35°C for CPU and 30°C for GPU.

How are you cooling your processor?

CPU is air-cooled and JONSBO HX6250 cooler is installed which should be more than enough for i5-12400f

 

[capofobviously]

I guess i found out the reason of system instability.
My PC had 4 sticks of RAM of the same vendor and model.
But it was two memoty kits of G.Skill F4-3200C16D-16GIS and another G.Skill F4-3200C16D-16GIS.
Four sticks of ram were running under XMP profile 3200 MT/s and according to the manufacturer state - this is not reccomended scenario since 4 overclocked sticks are too much for the memory controller and mixing the same ram sticks from different kits (even if they are identical) can cause unexpected behaviour.

I removed one 16 GB kit and for the past few weeks system seems OK.

Here is G.Skill support reply for the issue:

Dear Customer,

We would not suggest to use 2 memory kits together as this is considered mixing memory kit. Please note that mixing memory kits, even if the same model number, may result in compatibility issue. G.SKILL will guarantee the compatibility for single memory kit only. Each of our memory kit is thoroughly tested to ensure compatibility within each memory kit. And because we have not tested our memory kit with your existing memory kit, we cannot guarantee compatibility when multiple kits are used. Please visit our FAQ for more information: http://www.gskill.com/en/faq/Memory

With four modules from two kits, we would suggest to try the following combination:

Combination 1: [CPU] (A) (B) (A) (B)
Combination 2 :[CPU] (A) (A) (B) (B)
(A): first memory kit containing two modules with consecutive serial numbers.
(B): second memory kit containing two modules with consecutive serial numbers.

Please update BIOS to the latest version, clear CMOS prior to booting, boot with XMP enabled Then, save and exit BIOS. This is to check if the memory is able to boot at rated or lower speed.

To try one kit at a time, when installing the memory kit, please make sure that the memory modules are installed in the correct memory slots, as recommended by the motherboard user guide. This is usually slots A2 and B2 for motherboards with 4 memory slots.

Thank you.