S
SZ1234_301
Guest
Just recently, I am constantly having bluescreens when rendering animations and playing video games and other high GPU demand activities. I upgraded my GPU driver to the most current version, and also upgraded the BIOS of ASUS motherboard. However, it is still having this issue. When the bluescreen happens, the GPU seems to operate at about 60% limit, GPU temperature about 70 °C, dedicated memory usage about 5GB/10GB, which seems pretty normal. The below scripts are from the crash report and the minidump file.
What would be a solution to this problem?
Thanks in advance.
Description
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffe40bc0c33010
Parameter 2: fffff8003eef71c0
Parameter 3: 0
Parameter 4: e14
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033
Extra information about the problem
Bucket ID: LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere_SCG3D
Server information: 67bfcff7-701c-4ef2-bb73-746cbb85897f
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022021-6828-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`5e800000 PsLoadedModuleList = 0xfffff804`5f42a390
Debug session time: Sat Feb 20 23:11:25.620 2021 (UTC - 7:00)
System Uptime: 0 days 0:14:44.287
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`5ebf5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc400`46baac10=000000000000001e
19: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8045ebfe549, The address that the exception occurred at
Arg3: ffffc40046b96540, Parameter 0 of the exception
Arg4: ffffc40046bab000, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2562
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-0A00HVT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 82758
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff8045ebfe549
BUGCHECK_P3: ffffc40046b96540
BUGCHECK_P4: ffffc40046bab000
EXCEPTION_PARAMETER1: ffffc40046b96540
EXCEPTION_PARAMETER2: ffffc40046bab000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
BAD_STACK_POINTER: ffffc40046baac08
FAILED_INSTRUCTION_ADDRESS:
nt!_chkstk+39
fffff804`5ebfe549 4d3bd3 cmp r10,r11
STACK_TEXT:
ffffc400`46baac08 fffff804`5ec7078c : 00000000`0000001e ffffffff`c000001d fffff804`5ebfe549 ffffc400`46b96540 : nt!KeBugCheckEx
ffffc400`46baac10 fffff804`5ebfe93f : fffff804`5eb1474c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionStackSwitchHandler+0x15c040
ffffc400`46baac50 fffff804`5eb2bf97 : ffffc400`46bab1c0 00000000`00000000 ffffc400`46babfb0 fffff804`5ebf6912 : nt!RtlpExecuteHandlerForException+0xf
ffffc400`46baac80 fffff804`5eb2ab86 : ffffc400`46babb98 ffffc400`46bab8d0 ffffc400`46babb98 00000302`ae9f1824 : nt!RtlDispatchException+0x297
ffffc400`46bab3a0 fffff804`5ec07bac : 00610074`0065006d 00790065`006b0020 004e0045`0022003d 00220052`00450054 : nt!KiDispatchException+0x186
ffffc400`46baba60 fffff804`5ec020e9 : 003e002f`00220065 00200020`000a000d 00200020`00200020 00740065`006d003c : nt!KiExceptionDispatch+0x12c
ffffc400`46babc40 fffff804`5ebfe549 : 00000000`00000001 00000000`00000002 fffff804`5eb2aaed ffffa301`3754f388 : nt!KiInvalidOpcodeFault+0x329
ffffc400`46babdd8 fffff804`5eb2aaed : ffffa301`3754f388 00000000`00000000 00000302`ae9f1824 00630061`000004d0 : nt!_chkstk+0x39
ffffc400`46babdf0 fffff804`5ebf6912 : 00720022`003d006e 0076006f`00630065 00220079`00720065 000a000d`003e002f : nt!KiDispatchException+0xed
ffffc400`46babfb0 fffff804`5ebf68e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffa301`3754f248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
SYMBOL_NAME: nt!KiExceptionStackSwitchHandler+15c040
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.804
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 15c040
FAILURE_BUCKET_ID: 0x1E_c000001d_STACKPTR_ERROR_BAD_IP_nt!KiExceptionStackSwitchHandler
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c5b53289-ef3c-893b-d3dd-06266ae260b3}
Followup: MachineOwner
---------
Continue reading...
What would be a solution to this problem?
Thanks in advance.
Description
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffe40bc0c33010
Parameter 2: fffff8003eef71c0
Parameter 3: 0
Parameter 4: e14
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033
Extra information about the problem
Bucket ID: LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere_SCG3D
Server information: 67bfcff7-701c-4ef2-bb73-746cbb85897f
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022021-6828-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`5e800000 PsLoadedModuleList = 0xfffff804`5f42a390
Debug session time: Sat Feb 20 23:11:25.620 2021 (UTC - 7:00)
System Uptime: 0 days 0:14:44.287
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`5ebf5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc400`46baac10=000000000000001e
19: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8045ebfe549, The address that the exception occurred at
Arg3: ffffc40046b96540, Parameter 0 of the exception
Arg4: ffffc40046bab000, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2562
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-0A00HVT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 82758
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff8045ebfe549
BUGCHECK_P3: ffffc40046b96540
BUGCHECK_P4: ffffc40046bab000
EXCEPTION_PARAMETER1: ffffc40046b96540
EXCEPTION_PARAMETER2: ffffc40046bab000
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
BAD_STACK_POINTER: ffffc40046baac08
FAILED_INSTRUCTION_ADDRESS:
nt!_chkstk+39
fffff804`5ebfe549 4d3bd3 cmp r10,r11
STACK_TEXT:
ffffc400`46baac08 fffff804`5ec7078c : 00000000`0000001e ffffffff`c000001d fffff804`5ebfe549 ffffc400`46b96540 : nt!KeBugCheckEx
ffffc400`46baac10 fffff804`5ebfe93f : fffff804`5eb1474c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionStackSwitchHandler+0x15c040
ffffc400`46baac50 fffff804`5eb2bf97 : ffffc400`46bab1c0 00000000`00000000 ffffc400`46babfb0 fffff804`5ebf6912 : nt!RtlpExecuteHandlerForException+0xf
ffffc400`46baac80 fffff804`5eb2ab86 : ffffc400`46babb98 ffffc400`46bab8d0 ffffc400`46babb98 00000302`ae9f1824 : nt!RtlDispatchException+0x297
ffffc400`46bab3a0 fffff804`5ec07bac : 00610074`0065006d 00790065`006b0020 004e0045`0022003d 00220052`00450054 : nt!KiDispatchException+0x186
ffffc400`46baba60 fffff804`5ec020e9 : 003e002f`00220065 00200020`000a000d 00200020`00200020 00740065`006d003c : nt!KiExceptionDispatch+0x12c
ffffc400`46babc40 fffff804`5ebfe549 : 00000000`00000001 00000000`00000002 fffff804`5eb2aaed ffffa301`3754f388 : nt!KiInvalidOpcodeFault+0x329
ffffc400`46babdd8 fffff804`5eb2aaed : ffffa301`3754f388 00000000`00000000 00000302`ae9f1824 00630061`000004d0 : nt!_chkstk+0x39
ffffc400`46babdf0 fffff804`5ebf6912 : 00720022`003d006e 0076006f`00630065 00220079`00720065 000a000d`003e002f : nt!KiDispatchException+0xed
ffffc400`46babfb0 fffff804`5ebf68e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffa301`3754f248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
SYMBOL_NAME: nt!KiExceptionStackSwitchHandler+15c040
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.804
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 15c040
FAILURE_BUCKET_ID: 0x1E_c000001d_STACKPTR_ERROR_BAD_IP_nt!KiExceptionStackSwitchHandler
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c5b53289-ef3c-893b-d3dd-06266ae260b3}
Followup: MachineOwner
---------
Continue reading...