Need help with finding cause of BSOD errors

GabeVainkill 1 Reputation point
2022-10-23T11:30:43.01+00:00

Hello and good day! My laptop has been having hardware errors (LiveKernel Event 141 and 144) almost every other day and BSODs almost once a week especially while playing Warframe.

I've tried some solutions online such as:
Running memtest
Windows Memory Diagnostic
Chkdisk/DISM
Hardware and devices diagnostic
rolling back graphics card drivers/updating to the latest version, doing a clean installation every time
checking if Windows has the most current updates

I'm honestly not sure what I'm doing since none of the diagnostic tools I've used found any errors; it seems to be a problem with the graphics card driver but rolling back, updating and reinstalling it doesn't seem to have solved the problem entirely, so I would really appreciate your assistance on this matter. I checked the memory dump file and I thought it might help though, let me know if there's anything more I can provide to help diagnose the problem.

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.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80633800000 PsLoadedModuleList = 0xfffff8063442a270
Debug session time: Sun Oct 23 17:37:37.525 2022 (UTC + 8:00)
System Uptime: 0 days 3:24:03.223
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80633bf90f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff80636870cc0=000000000000000a
0: kd> !analyze -v


  •                                                                         *    
    
  •                    Bugcheck Analysis                                    *    
    
  •                                                                         *    
    

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffff9b0e5f21fcfc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80658ab2f92, address which referenced memory

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec    
Value: 2124    

Key  : Analysis.DebugAnalysisManager    
Value: Create    

Key  : Analysis.Elapsed.mSec    
Value: 2853    

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

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

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

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

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

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

Key  : Bugcheck.Code.DumpHeader    
Value: 0xd1    

Key  : Bugcheck.Code.KiBugCheckData    
Value: 0xd1    

Key  : Bugcheck.Code.Register    
Value: 0xa    

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: d1

BUGCHECK_P1: ffff9b0e5f21fcfc

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80658ab2f92

READ_ADDRESS: ffff9b0e5f21fcfc Nonpaged pool

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: fffff80636870e00 -- (.trap 0xfffff80636870e00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9b03f2578e80 rbx=0000000000000000 rcx=ffff9b03f2578e80
rdx=0000000a6cca6e7c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80658ab2f92 rsp=fffff80636870f98 rbp=fffff80636871010
r8=00000000000000c0 r9=ffff9b03da36e0a8 r10=ffff9b03da36ec40
r11=ffff9b0e5f21fdbc r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
kbdclass!memcpy+0x92:
fffff80658ab2f92 0f100411 movups xmm0,xmmword ptr [rcx+rdx] ds:ffff9b0e5f21fcfc=????????????????????????????????
Resetting default scope

STACK_TEXT:
fffff80636870cb8 fffff80633c0b069 : 000000000000000a ffff9b0e5f21fcfc 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff80636870cc0 fffff80633c07369 : fffff80659b45c02 0000000000000000 ffff9b03e26626c8 ffff9b03ed4ccab0 : nt!KiBugCheckDispatch+0x69
fffff80636870e00 fffff80658ab2f92 : fffff80658ab56dd 000000007b823f64 fffff80636871010 ffff9b03f4204a20 : nt!KiPageFault+0x469
fffff80636870f98 fffff80658ab56dd : 000000007b823f64 fffff80636871010 ffff9b03f4204a20 fffff806352b129b : kbdclass!memcpy+0x92
fffff80636870fa0 fffff80668de1511 : ffff9b03da12f190 fffff80636871168 ffff9b03da35f310 fffff80636871168 : kbdclass!KeyboardClassServiceCallback+0x16d
fffff80636871040 fffff80658a860db : ffff9b03da12f190 fffff806368710f9 fffff80636871401 fffff80658a8f000 : HKKbdFltr+0x1511
fffff80636871090 fffff80633a3489e : fffff8062e35c240 0000000000000010 0000000000000000 fffff80636871420 : i8042prt!I8042KeyboardIsrDpc+0x1bb
fffff80636871160 fffff80633a33b84 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
fffff806368712d0 fffff80633bfcc8e : 0000000000000000 fffff8062e359180 fffff80634527a00 ffff9b03f2b3d080 : nt!KiRetireDpcList+0x1f4
fffff80636871560 0000000000000000 : fffff80636872000 fffff8063686b000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: kbdclass!memcpy+92

MODULE_NAME: kbdclass

IMAGE_NAME: kbdclass.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 92

FAILURE_BUCKET_ID: AV_kbdclass!memcpy

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {dfec7698-3775-c204-13ee-4d0f5bb2791c}

Followup: MachineOwner

Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes

2 answers

Sort by: Most helpful
  1. Docs 15,761 Reputation points
    2022-10-27T05:12:38.047+00:00

    1) Uninstall the Nvidia GPU drivers nvlddmkm.sys using Display Driver Uninstaller (DDU).

    2) Reinstall the Nvidia drivers using the Nvidia website.

    3) Make sure that the clean install is performed and if available install the physx driver.

    https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

    https://www.wagnardsoft.com/

    https://www.nvidia.com/download/index.aspx

    https://www.wagnardsoft.com/content/ddu-guide-tutorial

    4) The BIOS: BIOS Version/Date INSYDE Corp. FB04, 01/07/2021

    Upgrade the BIOS to the most up to date non-beta BIOS.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  2. Docs 15,761 Reputation points
    2022-10-30T14:55:09.037+00:00

    Just checking if there's any progress or updates?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.