PCS PC Crash - Hardware Error Report - Help to Understand

jklondon · Nov 15, 2021

Have my PCS PC for just under a year had a few PC resets - no blue screen.

In Windows Reliability Monitor Got this report. Any help to what it means pls?

Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffc804c336c010
Parameter 2: fffff80290a0a9c4
Parameter 3: 0
Parameter 4: 1300
OS version: 10_0_19042
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19042.2.0.0.256.4
Locale ID: 2057

Rakk · Nov 15, 2021

If you could post your system specs please - instructions are in here: https://www.pcspecialist.co.uk/forums/threads/when-posting-for-technical-support.77839/

Also some details about when it happens, and exactly what happens at the time.

jklondon · Nov 15, 2021

Sure, specs

Case
CORSAIR CRYSTAL SERIES 680X RGB GAMING CASE
Processor (CPU)
AMD Ryzen 9 5950X 16 Core CPU (3.4GHz-4.9GHz/72MB CACHE/AM4)
Motherboard
ASUS® CROSSHAIR VIII HERO (DDR4, PCIe 4.0, CrossFireX/SLI) - RGB Ready!
Memory (RAM)
32GB Corsair VENGEANCE DDR4 3600MHz (4 x 8GB)
Graphics Card
3090 ZOTAC
1st M.2 SSD Drive
500GB SAMSUNG 980 PRO M.2, PCIe NVMe (up to 6900MB/R, 5000MB/W)
1st M.2 SSD Drive
2TB INTEL® 660p M.2 NVMe PCIe SSD (up to 1800MB/sR | 1800MB/sW)
Power Supply
CORSAIR 850W AX SERIES™ MODULAR 80 PLUS® TITANIUM
Power Cable
1 x 1 Metre UK Power Cable (Kettle Lead)
Processor Cooling
Corsair H115i RGB PLATINUM Hydro Series High Performance CPU Cooler
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Sound Card
ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card
10/100/1000 GIGABIT LAN PORT
Wireless Network Card
WIRELESS INTEL® Wi-Fi 6 AX200 2,400Mbps/5GHz, 300Mbps/2.4GHz PCI-E CARD + BT 5.0
USB/Thunderbolt Options
MIN. 2 x USB 3.0 & 2 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating System
Windows 10 Home 64 Bit - inc. Single Licence [KUK-00001]
Operating System Language
United Kingdom - English Language
Windows Recovery Media
Windows 10/11 Multi-Language Recovery Image - Unlimited Downloads from Online Account
Office Software
FREE 30 Day Trial of Microsoft 365® (Operating System Required)
Anti-Virus
NO ANTI-VIRUS SOFTWARE
Browser
Microsoft® Edge (Windows 10 Only)
Warranty
3 Year Gold Warranty (2 Year Collect & Return, 2 Year Parts, 3 Year Labour)
Delivery
STANDARD INSURED DELIVERY TO UK MAINLAND (MON-FRI)
Build Time
Standard Build - Approximately 14 to 16 working days
Promotional Item
Get CoD:Cold War & 1YR GeForce Now w/ select RTX Graphics Cards
Welcome Book
PCSpecialist Welcome Book - United Kingdom & Republic of Ireland
Logo Branding
PCSpecialist Logo

Happened twice when playing Far Cry 6.

Just updated the NVIDIA drivers (taking a bet that its GPU related).

ubuysa · Nov 15, 2021

That's an indication that a crash occurred but was recovered and a minidump was written to C:\Windows\LiveKernelReports (which is where all 'on-the-fly' minidumps are written). The bug check code of 0x141 is a VIDEO_ENGINE_TIMEOUT_DETECTED, which indicates a graphics issue - most likely with the graphics driver but possibly with the card.

BUT

Just as one swallow doesn't make a summer, neither does one 0x141 error indicate a serious driver or card issue. How serious this is depends on what other symptoms you have.

To proceed further we need to see the FULL spec from the original PCS order though, so that we can see the whole picture. What you just linked to doesn't help I'm afraid.

jklondon · Nov 15, 2021

ubuysa said:
That's an indication that a crash occurred but was recovered and a minidump was written to C:\Windows\LiveKernelReports (which is where all 'on-the-fly' minidumps are written). The bug check code of 0x141 is a VIDEO_ENGINE_TIMEOUT_DETECTED, which indicates a graphics issue - most likely with the graphics driver but possibly with the card.

BUT

Just as one swallow doesn't make a summer, neither does one 0x141 error indicate a serious driver or card issue. How serious this is depends on what other symptoms you have.

To proceed further we need to see the FULL spec from the original PCS order though, so that we can see the whole picture. What you just linked to doesn't help I'm afraid.

sorry yes - updated with Full Spec

jklondon · Nov 15, 2021

I was thinking I should stress test the GPU over a period of time? Any suggestions as to what to use to achieve this (3DMark) or something else?

moosEh · Nov 15, 2021

jklondon said:
I was thinking I should stress test the GPU over a period of time? Any suggestions as to what to use to achieve this (3DMark) or something else?

I'd recommend you clean reinstall your graphics card drivers with the latest drivers and then stress your system. Some suggested stress tests are below.

3DMark - https://www.3dmark.com/
Superposition - https://benchmark.unigine.com/superposition
FF Benchmark - https://eu.finalfantasyxiv.com/benchmark/

jklondon · Nov 15, 2021

Did a clean reinstall and stress test with 3D Mark. It restarted and I analyzed the minidump here is the output below. Any suggestions on next steps?

**

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

Loading Dump File [C:\Windows\Minidump\dump\111521-9140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`58a00000 PsLoadedModuleList = 0xfffff803`5962a2d0
Debug session time: Mon Nov 15 20:39:36.011 2021 (UTC + 0:00)
System Uptime: 0 days 6:16:05.338
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`58df72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9602`c10b79e0=0000000000000116
27: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffcb82e3354050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8036f4c1a4c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_44dc4eefedc0d082\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3953

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 23548

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

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

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

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

FILE_IN_CAB: 111521-9140-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffcb82e3354050

BUGCHECK_P2: fffff8036f4c1a4c

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffcb82e3354050
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9602`c10b79d8 fffff803`68af665e : 00000000`00000116 ffffcb82`e3354050 fffff803`6f4c1a4c ffffffff`c000009a : nt!KeBugCheckEx
ffff9602`c10b79e0 fffff803`68aa6e44 : fffff803`6f4c1a4c ffffcb82`d757b050 00000000`00002000 ffffcb82`d757b110 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff9602`c10b7a20 fffff803`68a9f97c : ffffcb82`d75ac000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff9602`c10b7a50 fffff803`68af5d85 : 00000000`00000100 ffffcb82`d75aca70 00000000`b589fc20 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff9602`c10b7ad0 fffff803`68af5ef7 : fffff803`59725440 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9602`c10b7b00 fffff803`58cb8515 : ffffcb82`da670040 fffff803`68af5ed0 ffffcb82`b589fc20 ffffcb82`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff9602`c10b7b30 fffff803`58d55855 : ffffcb82`da670040 00000000`00000080 ffffcb82`b5886040 00000000`00000001 : nt!ExpWorkerThread+0x105
ffff9602`c10b7bd0 fffff803`58dfe8f8 : ffffde01`c1115180 ffffcb82`da670040 fffff803`58d55800 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff9602`c10b7c20 00000000`00000000 : ffff9602`c10b8000 ffff9602`c10b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nvlddmkm+da1a4c

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

SpyderTracks · Nov 15, 2021

jklondon said:
Did a clean reinstall and stress test with 3D Mark. It restarted and I analyzed the minidump here is the output below. Any suggestions on next steps?

**

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

Loading Dump File [C:\Windows\Minidump\dump\111521-9140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`58a00000 PsLoadedModuleList = 0xfffff803`5962a2d0
Debug session time: Mon Nov 15 20:39:36.011 2021 (UTC + 0:00)
System Uptime: 0 days 6:16:05.338
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`58df72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9602`c10b79e0=0000000000000116
27: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffcb82e3354050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8036f4c1a4c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_44dc4eefedc0d082\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3953

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 23548

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

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

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

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

FILE_IN_CAB: 111521-9140-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffcb82e3354050

BUGCHECK_P2: fffff8036f4c1a4c

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffcb82e3354050
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9602`c10b79d8 fffff803`68af665e : 00000000`00000116 ffffcb82`e3354050 fffff803`6f4c1a4c ffffffff`c000009a : nt!KeBugCheckEx
ffff9602`c10b79e0 fffff803`68aa6e44 : fffff803`6f4c1a4c ffffcb82`d757b050 00000000`00002000 ffffcb82`d757b110 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff9602`c10b7a20 fffff803`68a9f97c : ffffcb82`d75ac000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff9602`c10b7a50 fffff803`68af5d85 : 00000000`00000100 ffffcb82`d75aca70 00000000`b589fc20 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff9602`c10b7ad0 fffff803`68af5ef7 : fffff803`59725440 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9602`c10b7b00 fffff803`58cb8515 : ffffcb82`da670040 fffff803`68af5ed0 ffffcb82`b589fc20 ffffcb82`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff9602`c10b7b30 fffff803`58d55855 : ffffcb82`da670040 00000000`00000080 ffffcb82`b5886040 00000000`00000001 : nt!ExpWorkerThread+0x105
ffff9602`c10b7bd0 fffff803`58dfe8f8 : ffffde01`c1115180 ffffcb82`da670040 fffff803`58d55800 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff9602`c10b7c20 00000000`00000000 : ffff9602`c10b8000 ffff9602`c10b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nvlddmkm+da1a4c

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

Your windows version is very out of date, it's on 2004 which is only eligible for updates until December 14th.

First thing I would suggest is getting windows fully updated.

This is almost certainly a driver issue from the crash log.

Could you upload a screenshot of your windows update page?

You'll need to apply all updates, plus optional updates as those are driver related and won't automatically install.

jklondon · Nov 15, 2021

jklondon · Nov 15, 2021

Taken a video as well to help explain.

- One of the fans on 3090 is not running the other two are which is odd
- Motherboard beeps a lot before restarting
- There is now a BIOS error 'video card not supported by UEFI' ...

Hard reboot and it got back into windows thankfully but doesnt look too healthy at all

jklondon · Nov 15, 2021

jklondon · Nov 15, 2021

updated but it happened after the reboot as well. Performing a full system reset now. Really hope that sorts it as I use the machine to work from home

SpyderTracks · Nov 15, 2021

jklondon said:
Taken a video as well to help explain.

- One of the fans on 3090 is not running the other two are which is odd
- Motherboard beeps a lot before restarting
- There is now a BIOS error 'video card not supported by UEFI' ...

Hard reboot and it got back into windows thankfully but doesnt look too healthy at all

Out of interest, what USB devices do you have plugged in? Have you had any issues with USB devices disconnecting randomly?

This is a common error on that board on older BIOSes, from what I can see from your video you're on 3202 which was before AMD released their AGESA updates in January this year. I think it's worth giving PCS a call and getting the BIOS updated to the latest version they deem appropriate. Current version is 3801 which is almost a year newer, so there's a lot of improvements to be made in that time.

"The VGA card is not supported by UEFI driver" on POST - Dark Hero

I set up my new Dark Hero build a few days ago, and I occasionally get this error on POST. "The VGA card is not supported by UEFI driver. CSM (Compability Support Module) settings have been changed For further adjustments, press [F1] to enter BIOS setup The message only comes when the monitor...

rog.asus.com

It's possible there are other things at play here, but this is significant enough to make a substantial improvement to general stability.

I would also suggest uninstalling GPU drivers with DDU (that's the only method to properly uninstall them) and then install the latest direct from nvidia (don't use Geforce Experience).

jklondon · Nov 15, 2021

SpyderTracks said:
Out of interest, what USB devices do you have plugged in? Have you had any issues with USB devices disconnecting randomly?

This is a common error on that board on older BIOSes, from what I can see from your video you're on 3202 which was before AMD released their AGESA updates in January this year. I think it's worth giving PCS a call and getting the BIOS updated to the latest version they deem appropriate. Current version is 3801 which is almost a year newer, so there's a lot of improvements to be made in that time.

"The VGA card is not supported by UEFI driver" on POST - Dark Hero

I set up my new Dark Hero build a few days ago, and I occasionally get this error on POST. "The VGA card is not supported by UEFI driver. CSM (Compability Support Module) settings have been changed For further adjustments, press [F1] to enter BIOS setup The message only comes when the monitor...

rog.asus.com

It's possible there are other things at play here, but this is significant enough to make a substantial improvement to general stability.

I would also suggest uninstalling GPU drivers with DDU (that's the only method to properly uninstall them) and then install the latest direct from nvidia (don't use Geforce Experience).

No USB devices but will update bios thanks.

Other thing i am experiencing as I do the windows reset is 3 short consecutive beeps from the motherboard upon reboot.

Any idea what that's telling me?

Thanks again for your help.

SpyderTracks · Nov 15, 2021

jklondon said:
No USB devices but will update bios thanks.

Do do this with PCS approval though otherwise you void your warranty.

jklondon said:
Other thing i am experiencing as I do the windows reset is 3 short consecutive beeps from the motherboard upon reboot.

That's because there's an incompatibility between the graphics drivers you have installed and UEFI, that's what that BIOS error is showing on boot, that it's enabled CSM which is essentially like a "safe mode" for UEFI to allow the incompatible drivers to load. This is normally because the driver file is unsigned, but in this case, it could also be due to an issue with that early BIOS.

CSM stands for Compatibility Support Module, it basically allows the UEFI BIOS to load in legacy mode.

But if you disabled UEFI and secure boot, that error would likely disappear and it would load fine. That's not the answer though, that's reducing security.

ubuysa · Nov 16, 2021

jklondon said:
Did a clean reinstall and stress test with 3D Mark. It restarted and I analyzed the minidump here is the output below. Any suggestions on next steps?

No, you didn't 'analyse the minidump'. All you've done there is run the !analyse -v command to do the top level analysis, there is so much more information to be obtained from the dump, that's why we ask for them to be uploaded so we can analyse them properly and fully.

The failing driver that the !analyse -v command identified is nvlddmkm.sys, the Nvidia graphics driver (unsurprisingly given the 0x141 error you reported at first) - but this triage analysis isn't always right, which is why we always need the full dump uploaded.

jklondon · Nov 16, 2021

Hi,

Ok spoke with PCS today and got OK to update BIOS to latest version.

Ran 3DMark Stress test and it crashed again.

Attaching the dmp file to help.

SpyderTracks · Nov 16, 2021

jklondon said:
Hi,

Ok spoke with PCS today and got OK to update BIOS to latest version.

Ran 3DMark Stress test and it crashed again.

Attaching the dmp file to help.

Have you done the GPU driver uninstall with DDU?

jklondon · Nov 16, 2021

SpyderTracks said:
Have you done the GPU driver uninstall with DDU?

Yes did that also

PCS PC Crash - Hardware Error Report - Help to Understand

Bronze Level Poster

The Awesome

Bronze Level Poster

The BSOD Doctor

Bronze Level Poster

Bronze Level Poster

Administrator

Bronze Level Poster

We love you Ukraine

Bronze Level Poster

Bronze Level Poster

Attachments

Bronze Level Poster

Bronze Level Poster

We love you Ukraine

Bronze Level Poster

We love you Ukraine

The BSOD Doctor

Bronze Level Poster

Attachments

We love you Ukraine

Bronze Level Poster