Question Driver BSOD after Windows reinstall on laptop ?

[AdeQ]

Hi All!

Around the beggining of January I've updated graphics driver on my girlfriend's Acer F5-573G laptop using an installer downloaded from NVIDIA website (It was from June 2021). At the same time I've updated a couple drivers using Driver Booster. A couple days after she started getting BSODs, specifically "video_dxgkrnl_fatal_error" and very very rarely a "driver_power_state_failure" error. DUMP file analysis pointed to NVIDIA driver being faulty here. After doing some stuff suggested in similar topics I've found on the Internet (Clean reinstall using DDU, DISM, Driver Verifier) nothing's changed. Desperate I've formatted the C drive which had Windows on it and installed fresh system from USB stick. After installing all the drivers everything seemed fine until two days later the BSOD came back. I've got absolutely no clue as to how to proceed now. I will appreciate any help regarding solving this problem. Below I'm attaching the DUMP file from "video_dxgkrnl_fatal_error" BSOD which happened after formatting.

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


Loading Dump File [C:\Windows\Minidump\020123-20640-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8020d200000 PsLoadedModuleList = 0xfffff8020de2a2d0
Debug session time: Wed Feb 1 20:43:51.596 2023 (UTC + 1:00)
System Uptime: 0 days 0:02:40.307
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8020d5fa1d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc18120e1f700=0000000000000113
1: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the BugCheck:
Arg2: 0000000000000002
Arg3: 00000000000010de
Arg4: 000000000000179c

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7233

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 63081

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

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

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

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x113

Key : Bugcheck.Code.Register
Value: 0x113

Key : DirectX.FatalError.Code
Value: 19

Key : DirectX.FatalError.Desc
Value: UNEXPECTED_DEFERRED_DESTRUCTION

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: 020123-20640-01.dmp

BUGCHECK_CODE: 113

BUGCHECK_P1: 19

BUGCHECK_P2: 2

BUGCHECK_P3: 10de

BUGCHECK_P4: 179c

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffc18120e1f6f8 fffff80223dd3ad0 : 0000000000000113 0000000000000019 0000000000000002 00000000000010de : nt!KeBugCheckEx
ffffc18120e1f700 fffff80223c111cc : ffffc30af8bc9180 ffffc30af2deb010 ffffc30af8bc9180 ffffc30af8bc9180 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc18120e1f740 fffff80223b90ee1 : ffffc30af2f5f400 0000000000989600 0000000000000000 ffffc30af2deb200 : dxgkrnl!DpiFdoHandleDevicePower+0x7fa2c
ffffc18120e1f7e0 fffff80223b92431 : ffffc30af2deb010 ffffc30af8bc9180 ffffc30af8bc9030 ffffc18120e1f900 : dxgkrnl!DpiFdoDispatchPower+0x21
ffffc18120e1f810 fffff8024323806f : ffffc30af8ba3000 ffffc30af88ef000 ffffc30af8ba3000 ffffc30af2deb200 : dxgkrnl!DpiDispatchPower+0xe1
ffffc18120e1f930 ffffc30af8ba3000 : ffffc30af88ef000 ffffc30af8ba3000 ffffc30af2deb200 ffffc30a00000004 : nvlddmkm+0xff806f
ffffc18120e1f938 ffffc30af88ef000 : ffffc30af8ba3000 ffffc30af2deb200 ffffc30a00000004 0000000000000000 : 0xffffc30af8ba3000
ffffc18120e1f940 ffffc30af8ba3000 : ffffc30af2deb200 ffffc30a00000004 0000000000000000 0000000000000001 : 0xffffc30af88ef000
ffffc18120e1f948 ffffc30af2deb200 : ffffc30a00000004 0000000000000000 0000000000000001 00000000000000ff : 0xffffc30af8ba3000
ffffc18120e1f950 ffffc30a00000004 : 0000000000000000 0000000000000001 00000000000000ff ffffc30af8ba3000 : 0xffffc30af2deb200
ffffc18120e1f958 0000000000000000 : 0000000000000001 00000000000000ff ffffc30af8ba3000 0000000000000000 : 0xffffc30a`00000004


SYMBOL_NAME: nvlddmkm+ff806f

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: ff806f

FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f}

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

 

[Fix_that_Glitch]

Does she have a restore point from before all this happened?

 

[johnbl]

the problem is in power management. first fix attempt would be to update the bios and the motherboard drivers from the acer website.
looking at the acer website I see the last bios update is from 2017.
this might mean you will have to disable sleep functions to work around the problem since you are unlikely to get a actual fix to the problem.
(last chipset update from acer was in 2016)
try the bios update and see if it helps, otherwise disable the sleep functions for the graphics card.
these old laptops might use a custom compiled version of the graphics driver.