Strange Random crashes that does not seem to be related to anything

[Tjalve]

Hello there.

Ive been building my own PCs for about 20 years now. Im that kind of guy who thinks that a PC is something you should build yourself. Anything else is just not good enough. But im having some strange issues with my current build and im in a bit of a loss to where I should go next with my trobleshooting. Since i dont play much games anymore its not been that much of a problem. Most of my daily computing is done on my phone or my laptop. But i recently started playing alittle again and now i feel like i should get the machine working proparly. And i hope that someone might have an idee on what to try next.

 

Machine:
CPU: AMD Ryzen 5 3600X

MB: Gigabyte X570 AORUS PRO (Bios v F37f)

GPU: Gigabyte RTX 2080 Ti (with custom fan)

Memory: Corsair Vengeance LPX 32 GB DDR4 3600MHz (CMK32GX4M2Z3600C18)

SSD: Samsung MZVLB256HAHQ, Intel Optane 900p 480GB, Samsung 960 Pro 2TB

OS: Windows 10 22H2 19045.4239 (this is the current version, but i have had the problem befor)

 

The problem:
I get random crashes. Sometimes in the form of a BSOD. But most of the time its just a random crash/error within the application that im currently running. For example a Tab can just randomly crash in firefox without any warning and i get the "Your tab just crashed" message. This can be a any website but usually youtube. But i also get random crashes in games. Im currently palying trough Halo: The masterchief collection, and i get random crashes with a small error window and the game freezes. I can close the game and restart it, and it can run fine for 5min or sometimes for 2-3 hours. Ive managed to get trough Halo 1 and 2 on about 20-25 crashes maybe. But i have had similar "soft" crashes in other games aswell.

 

Old machien and known Good Parts:

The problems started when i rebuild the machine using the current motheraboard, CPU and Memory. My old machine worked fine and it had the same GPU, PSU, SSD, Soundcard, case, mouse etc. That was an Intel 6800K. I got an upgrade package with the motherboard and the 3600x and 4x4GB of memory. I had the issues from the start, but i wanted more memory so replaced the old 4x4 sticks and got 2x16GB och DDR4. I can run the Memory att 2800Mhz or 3600Mhz withe the same result. Im currelty running it at the XMP profile.

 

What i have tried:

Im not sure that the problem is related to load. CPU Temps are fine at 35 C Idle. Dont remember what is was under load, but i think it was around 70. I have tried running Memtest86+ for about 12 hours, no issue. I have also run Prime95 on all cores for 10 hours without any issue. I have also tested running furmark for a few hours (to stress the GPU) and there ware no crashes.

Its strange. All stresstesting seems to be working fine, but i just get random crashes for no reason. Also when i tried to enable rebar in the UEFI, the system gets super ustable and would sometimes not even boot. So ive just let it be off. I have updates my BIOS several times, no change. Reset to default. No change. Reinstalled windows, no change. Anyone have any idee on what i can do?

[Parsivan]

Have you looked through the event viewer maybe there's a clue there we can follow

[Bjoolz]

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

[Tjalve]

4 hours ago, Parsivan said:

Have you looked through the event viewer maybe there's a clue there we can follow

haha FF tab crashes just is i tried to post this response.
I have a few erros in the event log. Most of them are the same as reported here:  "https://answers.microsoft.com/en-us/windows/forum/all/event-id-86-this-error-has-been-happening-for-two/a61ca458-d3f6-4e7c-9f5e-6a3941745bd6"
But some are the last app that crashed. For example when Halo crashed yesterday i get av event 1000.

One time it was halo2.dll
Faulting application name: MCC-Win64-Shipping.exe, version: 1.3385.0.0, time stamp: 0x00000000
Faulting module name: halo2.dll, version: 1.3385.0.0, time stamp: 0x65959e09
Exception code: 0xc0000005
Fault offset: 0x00000000000f47e3
Faulting process id: 0x2f70
Faulting application start time: 0x01da834c096e273a
Faulting application path: D:\SteamLibrary\steamapps\common\Halo The Master Chief Collection\MCC\Binaries\Win64\MCC-Win64-Shipping.exe
Faulting module path: D:\SteamLibrary\steamapps\common\Halo The Master Chief Collection\halo2\halo2.dll
Report Id: 7903cc92-2822-4534-b5a7-a8b436d6d9ad
Faulting package full name:
Faulting package-relative application ID:

 

And another time it was nvwgf2umx.dll witch i guess is part of the nvidia driver.
Faulting application name: MCC-Win64-Shipping.exe, version: 1.3385.0.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 31.0.15.3623, time stamp: 0x64826927
Exception code: 0xc0000005
Fault offset: 0x0000000000458a43
Faulting process id: 0x2b20
Faulting application start time: 0x01da834109ee94da
Faulting application path: D:\SteamLibrary\steamapps\common\Halo The Master Chief Collection\MCC\Binaries\Win64\MCC-Win64-Shipping.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_7e5fd280efaa5445\nvwgf2umx.dll
Report Id: 644c9ab7-9674-4960-b9b3-1dd1f30b282c
Faulting package full name:
Faulting package-relative application ID:

 

I also found one from firefox:

Faulting application name: firefox.exe, version: 124.0.1.8846, time stamp: 0x65fccdba
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x3770
Faulting application start time: 0x01da82dc6a7c7131
Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe
Faulting module path: unknown
Report Id: 5c84e4a1-ac23-4cc0-b3c4-bfdb3d121a8b
Faulting package full name:
Faulting package-relative application ID:

[Tjalve]

4 hours ago, Bjoolz said:

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

I did a quick WinDBG of the files in the minidump folder:
 

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE (162)
A lock tracked by AutoBoost was released by a thread that did not own the lock.
This is typically caused when some thread releases a lock on behalf of another
thread (which is not legal with AutoBoost tracking enabled) or when some thread
tries to release a lock it no longer owns.
Arguments:
Arg1: ffffe58a126dd080, The address of the thread
Arg2: ffffe58a0a37ded0, The lock address
Arg3: 00000000ffffffff, The session ID of the thread
Arg4: 0000000000000000, Reserved

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2405

    Key  : Analysis.Elapsed.mSec
    Value: 5829

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x162

    Key  : Bugcheck.Code.TargetModel
    Value: 0x162

    Key  : Failure.Bucket
    Value: 0x162_nt!ExReleaseCacheAwarePushLockSharedEx

    Key  : Failure.Hash
    Value: {0408c3fa-e7d6-0235-af08-41350148000b}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  162

BUGCHECK_P1: ffffe58a126dd080

BUGCHECK_P2: ffffe58a0a37ded0

BUGCHECK_P3: ffffffff

BUGCHECK_P4: 0

FILE_IN_CAB:  040324-9531-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MoUsoCoreWorker.exe

STACK_TEXT:  
ffff8c85`a44ca0d8 fffff800`42a2eb0d     : 00000000`00000162 ffffe58a`126dd080 ffffe58a`0a37ded0 00000000`ffffffff : nt!KeBugCheckEx
ffff8c85`a44ca0e0 fffff800`4203633d     : 00000000`00000000 00000000`00000000 ffffe58a`00000000 ffffe58a`0a378700 : nt!ExReleaseCacheAwarePushLockSharedEx+0x1f1f3d
ffff8c85`a44ca130 fffff800`42035f7a     : ffff8c85`a44ca200 fffff800`42037c00 00000000`00000000 ffffe58a`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x1dd
ffff8c85`a44ca250 fffff800`42069f40     : ffff8c85`a44cb000 ffff8c85`a44c5000 ffffe58a`0b30d8d0 00000000`00000000 : FLTMGR!FltpPassThroughInternal+0xca
ffff8c85`a44ca2a0 fffff800`4282d935     : ffffe58a`11e9d500 ffffe58a`0b330b10 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x310
ffff8c85`a44ca350 fffff800`42844704     : 00000000`00000000 ffffe58a`1124a850 ffffe58a`0b3a7950 ffffe58a`0b30d8d0 : nt!IofCallDriver+0x55
ffff8c85`a44ca390 fffff800`42c3ec6b     : ffff8c85`a44ca650 ffffe58a`0b330b10 ffffe58a`11e9d678 ffff8c85`00000001 : nt!IoCallDriverWithTracing+0x34
ffff8c85`a44ca3e0 fffff800`42c33527     : ffffe58a`0b330b10 ffffe58a`0b330a00 ffffe58a`10e8c010 ffff9488`6d052101 : nt!IopParseDevice+0x11bb
ffff8c85`a44ca550 fffff800`42c3baca     : ffffe58a`10e8c001 ffff8c85`a44ca7b8 00000000`00000040 ffffe58a`0410cae0 : nt!ObpLookupObjectName+0x1117
ffff8c85`a44ca720 fffff800`42cd66ee     : 00000000`00000000 00000089`e357f000 00000000`00000000 00000089`e357efd0 : nt!ObOpenObjectByNameEx+0x1fa
ffff8c85`a44ca850 fffff800`42a11378     : ffffe58a`126dd000 00000000`00000001 ffffe58a`126dd080 00000277`4bf70270 : nt!NtQueryFullAttributesFile+0x1ce
ffff8c85`a44cab00 00007ffd`0968f8b4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000089`e357ef78 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`0968f8b4

SYMBOL_NAME:  nt!ExReleaseCacheAwarePushLockSharedEx+1f1f3d

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.4239

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f1f3d

FAILURE_BUCKET_ID:  0x162_nt!ExReleaseCacheAwarePushLockSharedEx

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0408c3fa-e7d6-0235-af08-41350148000b}

Followup:     MachineOwner

[Parsivan]

10 hours ago, Bjoolz said:

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

that's good to know! i'm learning here