[SOLVED] BSOD problem with my new computer, attached DMP details

[Crocforce]

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

Spoiler: dump File

Loading Dump File [C:\Windows\MEMORY.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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80758200000 PsLoadedModuleList = 0xfffff80758e2a190
Debug session time: Thu Sep 2 23:20:26.135 2021 (UTC + 3:00)
System Uptime: 0 days 3:23:24.750
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000034d1abf018). Type ".hh dbgerr001" for details Loading unloaded module list ........ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff807585f71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffad8164effc90=0000000000000101 11: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 000000000000000c, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffad8164a40180, The PRCB address of the hung processor. Arg4: 0000000000000005, The index of the hung processor. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2467 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 6005 Key : Analysis.Init.CPU.mSec Value: 999 Key : Analysis.Init.Elapsed.mSec Value: 76475 Key : Analysis.Memory.CommitPeak.Mb Value: 83 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 BUGCHECK_CODE: 101 BUGCHECK_P1: c BUGCHECK_P2: 0 BUGCHECK_P3: ffffad8164a40180 BUGCHECK_P4: 5 FAULTING_PROCESSOR: 5 PROCESS_NAME: LeagueClientUxRender.exe BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 STACK_TEXT: ffffad8164effc88 fffff8075861f46e : 0000000000000101 000000000000000c 0000000000000000 ffffad8164a40180 : nt!KeBugCheckEx ffffad8164effc90 fffff8075841c53d : 0000000000000000 ffffad8164e6d180 0000000000000246 00000000000beb30 : nt!KeAccumulateTicks+0x20614e ffffad8164effcf0 fffff8075841cae1 : 00000000000be900 0000000000071aa6 ffffad8164e6d180 0000000000000001 : nt!KiUpdateRunTime+0x5d ffffad8164effd40 fffff80758416953 : ffffad8164e6d180 0000000000000000 fffff80758e314a8 0000000000000000 : nt!KiUpdateTime+0x4a1 ffffad8164effe80 fffff8075841f312 : fffff00f1439e7a0 fffff00f1439e820 fffff00f1439e800 000000000000000c : nt!KeClockInterruptNotify+0x2e3 ffffad8164efff30 fffff807584de045 : 0000001c6aaff18f ffffd78682f0a160 ffffd78682f0a210 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2 ffffad8164efff60 fffff807585f8c7a : fffff00f1439e820 ffffd78682f0a160 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffad8164efffb0 fffff807585f91e7 : 000000000ad5720c ffffad8164e6d180 0000000000000002 ffffad8164e70130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff00f1439e7a0 fffff8075843a7c0 : 0000000000000000 0000000000000000 0000000000000002 fffff807587b088f : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff00f1439e930 fffff8075843a5b8 : 0000000000000000 ffffd78600000000 ffffd786b0aeea00 fffff807584c1dca : nt!KeFlushMultipleRangeTb+0x160 fffff00f1439e9d0 fffff8075846339e : 800000021ecbe921 800000021ecbe921 0000000000000000 0000000000000004 : nt!MiFlushTbList+0x88 fffff00f1439ea00 fffff807584bf260 : 0000000000000000 0000000000000000 fffff00f1439ec60 0000000000000000 : nt!MmSetAddressRangeModifiedEx+0x2ae fffff00f1439eb60 fffff8075851e50f : ffffd786afd08568 0000000000000000 0000000000000000 0000000000000000 : nt!CcFlushCachePriv+0x5b0 fffff00f1439ecb0 fffff8075ae3f81d : 0000000000000005 0000000000000000 0000000000000000 ffff868e867aa170 : nt!CcCoherencyFlushAndPurgeCache+0x6f fffff00f1439ed00 fffff8075ae3f6db : ffff868e867aa170 0000000000000000 ffffd786b8bede00 ffffd786ab5994d8 : Ntfs!NtfsCoherencyFlushAndPurgeCache+0x55 fffff00f1439ed40 fffff8075ae3f58d : ffff868e867aa170 ffff868e867aa170 ffff868e867aa170 ffffd786b8bede50 : Ntfs!NtfsFlushUserStream+0xa3 fffff00f1439edd0 fffff8075ae403a9 : ffff868e867aa170 ffff868e867aa170 ffffd786aa703080 ffffd786b8886f68 : Ntfs!NtfsPerformOptimisticFlush+0xa1 fffff00f1439ee20 fffff8075ae3fd19 : ffffd786ab5994d8 ffffd786b8beda20 ffffd786ab599401 fffff00f1439f050 : Ntfs!NtfsCommonFlushBuffers+0x60d fffff00f1439ef40 fffff807584f8458 : fffff00f1439f050 ffffd786ab5994d8 ffffd78600000000 ffffd786b8beda20 : Ntfs!NtfsCommonFlushBuffersCallout+0x19 fffff00f1439ef70 fffff807584f83cd : fffff8075ae3fd00 fffff00f1439f050 0000000000000000 fffff80700000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78 fffff00f1439efe0 fffff8075ae17f6b : ffffd78682802000 fffff80758489569 fffff00f143a0000 0000000000000030 : nt!KeExpandKernelStackAndCalloutEx+0x1d fffff00f1439f020 fffff8075ae17e95 : 0000000000000000 ffffd78685b61010 fffff00f1439f0b8 0000000000000000 : Ntfs!NtfsCommonFlushBuffersOnNewStack+0x67 fffff00f1439f090 fffff8075848f855 : ffffd786b1205010 ffffd786b8beda20 ffffd786ab5994d8 fffff00f1439f0b8 : Ntfs!NtfsFsdFlushBuffers+0xe5 fffff00f1439f100 fffff80754ac6c5f : ffffd7868ac3ad60 ffffd786b1205110 fffff00f1439f210 0100000000100000 : nt!IofCallDriver+0x55 fffff00f1439f140 fffff80754ac4673 : fffff00f1439f1d0 0000000000000000 ffffad8100000000 ffffd78685c4d300 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f fffff00f1439f1b0 fffff8075848f855 : ffffd786b8beda20 fffff00f1439f440 ffffd786b8beda40 aaaaaaaaaaaaaaaa : FLTMGR!FltpDispatch+0xa3 fffff00f1439f210 fffff807588754b8 : ffffd786aa703080 ffffd786b8beda20 0000000000000001 0000000000000000 : nt!IofCallDriver+0x55 fffff00f1439f250 fffff807588e7b49 : ffffd78600000000 fffff00f1439f440 0000000000000000 fffff00f1439f440 : nt!IopSynchronousServiceTail+0x1a8 fffff00f1439f2f0 fffff807588e7936 : ffffd786aa703080 000044680c3e6240 ffffd7868ac3ad60 0000000000000000 : nt!NtFlushBuffersFileEx+0x1f9 fffff00f1439f380 fffff80758608bb5 : ffffd786aa703080 ffffd786b96ccf60 fffff00f1439f3d8 fffff00f1439f440 : nt!NtFlushBuffersFile+0x16 fffff00f1439f3c0 00007ffce5e8d784 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 00000034d33fdfa8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffce5e8d784


SYMBOL_NAME: nt!KeAccumulateTicks+20614e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 20614e

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}

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

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[Colif]

results - https://jsfiddle.net/mdsc6zLg/show
discord and chrome as victims.

i am already thinking its internet drivers.

do you use Ethernet or WIFI?
its a simple question but answer seems confusing

Jul 23 2020

e2kw10x64.sys

Realtek 8125/8136/8168/8169 NDIS Adapter driver

that is probably Ethernet (cable) but I don't see it listed on laptop drivers site?

Aug 12 2020

KfeCo10X64.sys

Killer Networking Suite driver

Dec 01 2020

Netwtw10.sys

Intel Wi-Fi driver

Now intel bought killer so those might be related to each other.

amazed Acer don't have an auto update feature on website
new killer driver under lan utility
lan driver is also made by Killer
Newer WIFI drivers also on link below:
https://www.acer.com/ac/en/US/content/support-product/8430?b=1

the realtek drivers don't seem to match?

 

[Crocforce]

I have an ethernet cable attached at the moment, and I just downloaded the latest drivers from Acers website so I will try to figure out next how to actually update them manually... To be honest it's quite a pain to go through all of this with a brand new computer, and that Acer doesn't have an auto-update software/feature. The last option is to go and get it fixed up with the guarantee but they told me that it will take about 2 weeks and I need to have a computer meanwhile... Any easy way to manually update the correct drivers after I extracted all of them?

 

[Colif]

https://community.acer.com/en/kb/articles/48-windows-10-download-and-install-a-driver

those instructions match what i can see

 

[Crocforce]

Thank you so much for your help in advance, but do you know if the "setup.cmd" will do the job of installing the driver, if there is no ".exe" format setup file in some of the driver folders?

 

[Colif]

its an exe file, windows hides commonly known extensions so it isn't a mess in there.

setup likely full name is setup_cmd.exe