[SOLVED] What's causing my new build to crash constantly ?

[OperaterDJKoze]

Hi there,

I build my first gaming computer late January this years. System specs are:

OS Windows 10 Pro
CPU Ryzen 5600x
GPU MSI RX 6800 XT Gaming Trio
MOBO MSI X570 Tomahawk WIFI
NZXT Kraken X63
G.Skill Trident Z NEO 32GB
SSD WD SN850 1TB
PSU Corsair RMx 850

The putting it together was the easy part, compared to what I am dealing with now. It booted up fine, installed windows, all of the drivers etc. no problem. I can play the games I want to and the parts seem to be worth their money. For some reason it just keeps crashing every couple of days. Most of the times it is whilst playing, but it happened whilst surfing a couple of times too. The reliability monitor shows "windows shut down unexpectedly". Some times the technical details show the good old "BSOD 10xE video memory management internal" error and other times it does not give me any other information. I did everything I could to fix it. Uninstalled drivers, reinstalled drivers, updated drivers, updated BIOS, updating windows regularly etc. I did run every test I could possible find (memtest86, AIDA64, cmdscannow, Heaven Benchmark), nothing is showing up. I constantly monitor the temperatures, GPU and CPU not even reaching 60C whilst gaming. I swapped the RAM Sticks. I changed the power management settings and disabled the fast startup option. I even paid for Restoro and use it daily, but it did not fix it. Sometimes I can play for 2-4 days with no problem, but then it just freezes, shuts down and restarts again.

I changed the advanced settings to create full dmp. files when a system crash like this occurs. I encrypted todays file with WinDbg, just unable to understand it, but I am going to put it underneath.

Sorry for the long thread, but I dont know what to do. I really hope it is not a hardware related issue, but could very well be one. Appreciate any help I can get.

Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\LiveKernelReports\PoW32kWatchdog-20210318-1233.dmp] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19042 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff80445000000 PsLoadedModuleList = 0xfffff80445c2a490 Debug session time: Thu Mar 18 12:33:07.812 2021 (UTC + 0:00) System Uptime: 0 days 0:01:05.414 Loading Kernel Symbols ............................................................... ..............Page 80fe5b not present in the dump file. Type ".hh dbgerr004" for details .................................................. ................................................... Loading User Symbols PEB is paged out (Peb.Ldr = 000000b84ac22018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!IopLiveDumpEndMirroringCallback+0xb4:
fffff804459a82c4 498d8e00010000 lea rcx,[r14+100h] 0: kd> !analyze -v Page 3448 not present in the dump file. Type ".hh dbgerr004" for details

*
Bugcheck Analysis *
*
WIN32K_CALLOUT_WATCHDOG_LIVEDUMP (1a1) A callout to Win32k did not return promptly. Arguments: Arg1: ffffa48ff80ca140, Thread blocking prompt return from a Win32k callout. Arg2: 0000000000000000, Reserved. Arg3: 0000000000000000, Reserved. Arg4: 0000000000000000, Reserved.

Debugging Details:
Page 3448 not present in the dump file. Type ".hh dbgerr004" for details Page 7d7484 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2140

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7014

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1
DUMP_FILE_ATTRIBUTES: 0x10 Live Generated Dump

BUGCHECK_CODE: 1a1

BUGCHECK_P1: ffffa48ff80ca140

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: csrss.exe

FAULTING_THREAD: ffffa48ff80ca140

STACK_TEXT:
ffff81806e4e5ea0 fffff80445265850 : ffffb780ffffffff 0000000000000000 ffff718000000000 0000000000000000 : nt!KiSwapContext+0x76 ffff81806e4e5fe0 fffff80445264d7f : 0000f8ff00000008 0000000000000004 ffff81806e4e61a0 0000000000000000 : nt!KiSwapThread+0x500 ffff81806e4e6090 fffff80445264623 : ffffa48f0000001e 0000000000000000 0000000000000000 ffffa48ff80ca280 : nt!KiCommitThreadWait+0x14f ffff81806e4e6130 fffff804452674fd : ffff81806e4e6318 ffffa48f0000001b ffff81806e4e6200 0000000011127200 : nt!KeWaitForSingleObject+0x233 ffff81806e4e6220 fffff80445262d40 : ffffa4800ba19f90 ffff81806e4e6300 0000000000010224 fffff804453225f0 : nt!ExpWaitForResource+0x6d ffff81806e4e62a0 fffff80445261f4c : ffffa4800b9b9010 0000000000000000 ffff81806e4e63d0 fffff804478103f0 : nt!ExpAcquireResourceExclusiveLite+0x320 ffff81806e4e6370 ffff8e9f3085e18f : ffff818000000002 fffff80447513b17 0000000000001000 ffff81806e4e63d0 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x3c ffff81806e4e63b0 ffff8e9f3085da27 : 0000000000000005 00000000c000001c ffff81806e4e79d0 0000000000000000 : win32kbase!UserPowerInfoCallout+0x13b ffff81806e4e7590 ffff8e9f30b710d0 : 00000000c000001c fffff80445c4ee00 0000000000000000 ffff81806e4e79d0 : win32kbase!W32CalloutDispatch+0x667 ffff81806e4e77a0 fffff80445710dcb : 0000000000000000 ffffa4800b8f2080 ffffa48ffea52080 ffff818094a81d6a : win32k!W32CalloutDispatchThunk+0x30 ffff81806e4e77e0 fffff80445637b54 : 0000000000000010 0000000000040086 ffff81806e4e78c8 0000000000000000 : nt!ExCallSessionCallBack+0xa3 ffff81806e4e78a0 fffff80445710c39 : ffffa4800b759ad0 ffff81806e4e7949 0000000000000000 ffffffffffffff01 : nt!PsInvokeWin32Callout+0xd4 ffff81806e4e78d0 fffff8044535d78f : 0000000000000005 ffff81806e4e79d0 0000000000000000 0000000000000000 : nt!PopInvokeWin32Callout+0x14d ffff81806e4e79b0 fffff8044570e380 : 0000000000000000 fffff80400000000 0000000000000001 0000000000000000 : nt!PopGetConsoleDisplayRequestCount+0x87 ffff81806e4e7a10 fffff804453159c4 : 0000000000000003 0000000000000000 ffffffffffffffff fffff80445c23d00 : nt!PopPolicySystemIdle+0x50 ffff81806e4e7af0 fffff80445225975 : ffffa48f00000003 ffffa48ff80ca140 fffff80445315930 ffffa48f00000000 : nt!PopPolicyWorkerThread+0x94 ffff81806e4e7b30 fffff80445317e85 : ffffa48ff80ca140 0000000000000080 ffffa48ff80ab040 0000000000000000 : nt!ExpWorkerThread+0x105 ffff81806e4e7bd0 fffff804453fd2a8 : fffff8044034a180 ffffa48ff80ca140 fffff80445317e30 0000000000000000 : nt!PspSystemThreadStartup+0x55 ffff81806e4e7c20 0000000000000000 : ffff81806e4e8000 ffff81806e4e1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

STACK_COMMAND: .thread 0xffffa48ff80ca140 ; kb

SYMBOL_NAME: win32kbase!UserPowerInfoCallout+13b

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

BUCKET_ID_FUNC_OFFSET: 13b

FAILURE_BUCKET_ID: LKD_0x1A1_WIN32K_CALLOUT_WATCHDOG_win32kbase!UserPowerInfoCallout

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {6c0c3561-4d71-6bb2-feb6-63d51ef17a17}

Followup: MachineOwner

 

[tennis2]

Sounds like a faulty stick of RAM

Is it a 2x16GB kit of RAM?

What does "i swapped the RAM sticks" mean? "swapped" as in moved various existing sticks to different slots in the mobo, or "replaced" the whole kit with a new one.

How long did you run MemTest for?

 

[OperaterDJKoze]

Yes it is. I moved the existing sticks to different slots. I did run the memtest for over 4hrs, till it was completed. Passed 100% no errors. Used the inbuild windows test for the RAM too, no errors.

 

[tennis2]

I've had a 2x8GB kit run without errors for 19 hours, but crashed repeatedly after 10 minutes on F@H. Sussed out the 1 faulty stick....error at 21 hours.

You could try other tests like OCCT, etc.

Test a single stick at a time. The larger the stick capacity, the longer it will take to fully test the stick.

 

[Beanruz]

Hello, as a fellow 5000series AMD user (5800x) and a x570 tomahawk I can say I'm having issues too.

although I'm now going down the path of issues with my 3080 ( think) - see my post Here,

when I first built my rig I was running the BIOS on the latest version 1.5 I believe, I downgraded/ backdated back to 1.4 version (as thats what my brother was running on without issue)

Since then had no issues with the crashes I had before (just the new one in the link above)- sudden kernel power 41, PC just restarted itself like it got a power cut and recovered.

might be worth giving it a try.

good luck!