17 R4, update to Dell BASE Device Driver

My system: Alienware 17 R4 (2016), Windows 10: 21H2 19044.2130

I am looking for a fix to a recurring BSOD problem. The problem file is: dcdbas64.sys. Is there a newer version for my system?

File Properties (C:\Windows\System32\drivers):
File description: Dell BASE Device Driver
Type: System file
File version: 8.2.0.454
Copyright: Copyright (C) Dell Inc. 1995-2015
Size: 47.3 KB
Date modified: 3/23/2022 4:28 AM
Language: English (United States)
Original file name: dcdbas64.sys

Device (Device Manager):
Device name: System Management Device
Device type: System devices

I cannot find a newer version. Microsoft Driver Verifier is active. I have opened the MEMORY.DMP file, from the latest BSOD, in WinDbg Preview, the results:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Page 200857b80 too large to be in the dump file.
Page 200003534 too large to be in the dump file.
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`6ae15000 PsLoadedModuleList = 0xfffff802`6ba3f290
Debug session time: Thu Oct 20 14:46:30.521 2022 (UTC - 5:00)
System Uptime: 0 days 0:02:45.393
Loading Kernel Symbols
...............................................................
..........................Page 7cf08f not present in the dump file. Type ".hh dbgerr004" for details
......................................
..........................Page 8630f0 not present in the dump file. Type ".hh dbgerr004" for details
.....................................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`6b20dfa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff970d`617328e0=00000000000000c4
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff80345512551, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000044424153, Pool Tag (if provided).

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2750

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5547

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xc4

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xc4

    Key  : Bugcheck.Code.Register
    Value: 0xc4

    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:  MEMORY.DMP

BUGCHECK_CODE:  c4

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff80345512551

BUGCHECK_P3: 0

BUGCHECK_P4: 44424153

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME:  System

STACK_TEXT:  
ffff970d`617328d8 fffff802`6b7e3e24     : 00000000`000000c4 00000000`00002000 fffff803`45512551 00000000`00000000 : nt!KeBugCheckEx
ffff970d`617328e0 fffff802`6b3b2045     : fffff802`6ba27c9c 00000000`00002000 fffff803`45512551 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xe0
ffff970d`61732920 fffff802`6b7dade4     : 00000000`44424153 fffff802`6ba27c9c fffff803`45512551 fffff802`6b026e83 : nt!VfReportIssueWithOptions+0x101
ffff970d`61732970 fffff802`6b7e8032     : 00000000`00000000 ffff858e`4cd08c20 00000000`00000010 00000000`00000000 : nt!VfCheckPoolType+0x90
ffff970d`617329b0 fffff803`45512551     : 00000000`00000004 ffff858e`60466030 ffff858e`60220000 00000000`00000000 : nt!VerifierExAllocatePoolWithTag+0x62
ffff970d`61732a00 fffff803`4551249b     : ffff858e`4cd08c20 ffff858e`4bf149c0 ffff858e`60466030 fffff802`6ba31ad0 : dcdbas64+0x2551
ffff970d`61732a50 fffff802`6b7e8c01     : ffff858e`60466000 fffff802`6ba31ad0 ffff858e`4bf149c0 ffff858e`60466030 : dcdbas64+0x249b
ffff970d`61732a80 fffff802`6b7e8ebc     : fffff802`6ba31a00 fffff802`6ba31ad0 00000000`00000080 fffff802`6b7e8e90 : nt!ViPendingCompleteAfterWait+0xed
ffff970d`61732ad0 fffff802`6b086d25     : ffff858e`31945040 fffff802`6b7e8e90 fffff802`6ba31ad0 00000000`00000000 : nt!ViPendingWorkerThread+0x2c
ffff970d`61732b10 fffff802`6b215628     : ffffb200`7e640180 ffff858e`31945040 fffff802`6b086cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff970d`61732b60 00000000`00000000     : ffff970d`61733000 ffff970d`6172c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dcdbas64+2551

MODULE_NAME: dcdbas64

IMAGE_NAME:  dcdbas64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2551

FAILURE_BUCKET_ID:  0xc4_2000_VRF_dcdbas64!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0e80b3ad-9626-66ba-8a08-914f8db8b417}

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