Windows 10: Struggling with BSOD for the last 2 months. Pls help

I've been really going crazy over my BSOD. I was able to go a good 3-4 days without BSOD.. thought everything was ok, but it happened again today.. Here is the last 5 crash dump files from May 5th, April 29th, April 26th, April 24th and also April 23rd. Much thanks in advanced. Code: MAY 5TH Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\050521-21343-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff800`3e006000 PsLoadedModuleList = 0xfffff800`3ec30490 Debug session time: Wed May 5 14:39:01.900 2021 (UTC - 7:00) System Uptime: 5 days 16:08:08.596 Loading Kernel Symbols ............................................................... ................................................................ ........................................................... Loading User Symbols Loading unloaded module list .................................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`3e3fbc50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc09`1c47f320=000000000000000a 6: 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: fffff8003f276da6, memory referenced Arg2: 00000000000000ff, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8003f276da6, address which referenced memory Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2874 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 16017 Key : Analysis.Init.CPU.mSec Value: 780 Key : Analysis.Init.Elapsed.mSec Value: 12889 Key : Analysis.Memory.CommitPeak.Mb Value: 83 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 BUGCHECK_CODE: d1 BUGCHECK_P1: fffff8003f276da6 BUGCHECK_P2: ff BUGCHECK_P3: 0 BUGCHECK_P4: fffff8003f276da6 READ_ADDRESS: fffff8003ed01390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse fffff8003f276da6 IP_IN_PAGED_CODE: PSHED!`string'+89e fffff800`3f276da6 0000 add byte ptr [rax],al ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target. CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: fffffc091c47f460 -- (.trap 0xfffffc091c47f460) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000db2 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8003f276da6 rsp=fffffc091c47f5f0 rbp=0000000000000000 r8=0000008000000000 r9=0000000000000200 r10=ffffc9876a3e8010 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl nz na po nc PSHED!`string'+0x89e: fffff800`3f276da6 0000 add byte ptr [rax],al ds:00000000`00000000=?? Resetting default scope FAILED_INSTRUCTION_ADDRESS: PSHED!`string'+89e fffff800`3f276da6 0000 add byte ptr [rax],al STACK_TEXT: fffffc09`1c47f318 fffff800`3e40db69 : 00000000`0000000a fffff800`3f276da6 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx fffffc09`1c47f320 fffff800`3e409e69 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffffc09`1c47f460 fffff800`3f276da6 : ffffc987`6a3e8328 00000000`00000000 00000475`13a80a49 00000000`00000000 : nt!KiPageFault+0x469 fffffc09`1c47f5f0 ffffc987`6a3e8328 : 00000000`00000000 00000475`13a80a49 00000000`00000000 ffffc987`6a3e8330 : PSHED!`string'+0x89e fffffc09`1c47f5f8 00000000`00000000 : 00000475`13a80a49 00000000`00000000 ffffc987`6a3e8330 00000475`13a80a49 : 0xffffc987`6a3e8328 SYMBOL_NAME: PSHED!`string'+89e MODULE_NAME: PSHED IMAGE_NAME: PSHED.dll IMAGE_VERSION: 10.0.19041.208 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 89e FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_VRF_CODE_AV_PAGED_IP_PSHED!_string_ OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {400aed94-12d0-6885-151e-2b9fcde7857f} Followup: MachineOwner April 29th Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\042921-20843-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff802`37c04000 PsLoadedModuleList = 0xfffff802`3882e490 Debug session time: Thu Apr 29 21:05:21.763 2021 (UTC - 7:00) System Uptime: 3 days 20:50:01.731 Loading Kernel Symbols ............................................................... ................................................................ ........................................................... Loading User Symbols Loading unloaded module list .................................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`37ff9c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8781`7bbfd8f0=0000000000000124 11: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffa60dfd498028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000001001152, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2952 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 19582 Key : Analysis.Init.CPU.mSec Value: 296 Key : Analysis.Init.Elapsed.mSec Value: 2431 Key : Analysis.Memory.CommitPeak.Mb Value: 77 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 BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffa60dfd498028 BUGCHECK_P3: be000000 BUGCHECK_P4: 1001152 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: iCUE.exe STACK_TEXT: ffff8781`7bbfd8e8 fffff802`380b7a6a : 00000000`00000124 00000000`00000000 ffffa60d`fd498028 00000000`be000000 : nt!KeBugCheckEx ffff8781`7bbfd8f0 fffff802`38e715ab : 00000000`00000000 ffffa60d`fd498028 ffffa60d`f68d0980 ffffa60d`fd498028 : nt!HalBugCheckSystem+0xca ffff8781`7bbfd930 fffff802`381b95f9 : 00000000`00000000 ffff8781`7bbfd9d9 ffffa60d`fd498028 ffffa60d`f68d0980 : PSHED!PshedBugCheckSystem+0xb ffff8781`7bbfd960 fffff802`380b9391 : ffffa60d`f9f7b910 ffffa60d`f9f7b910 ffffa60d`f68d09d0 ffffa60d`f68d0980 : nt!WheaReportHwError+0x469 ffff8781`7bbfda40 fffff802`380b9703 : 00000000`0000000b ffffa60d`f68d09d0 ffffa60d`f68d0980 00000000`0000000b : nt!HalpMcaReportError+0xb1 ffff8781`7bbfdbb0 fffff802`380b95e0 : ffffa60d`f5ee37c8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef ffff8781`7bbfdc00 fffff802`380b9831 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0 ffff8781`7bbfdc40 fffff802`380b8a9b : 00000000`00000000 00000000`00000000 ffff8781`7bbfded0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9 ffff8781`7bbfdc70 fffff802`380bb2e5 : ffffa60d`f5ee37c8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f ffff8781`7bbfdca0 fffff802`38110a29 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35 ffff8781`7bbfdcd0 fffff802`38008cfa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9 ffff8781`7bbfdd00 fffff802`380089b7 : ffff9780`00000000 fffff802`380088ec ffffffff`ffffffff 00000000`00000000 : nt!KxMcheckAbort+0x7a ffff8781`7bbfde40 fffff802`37e93586 : fffff802`37e92ae2 80000000`00000002 ffff9780`00000004 8a000008`00000000 : nt!KiMcheckAbort+0x277 ffff9b0b`f2726c98 fffff802`37e92ae2 : 80000000`00000002 ffff9780`00000004 8a000008`00000000 00000000`00000000 : nt!MiInsertPageInList+0xa86 ffff9b0b`f2726ca0 fffff802`37e2542c : 00002001`4080d860 ffff9780`03c18288 ffff9b0b`f2726dc8 00000000`00000006 : nt!MiPfnShareCountIsZero+0x652 ffff9b0b`f2726d00 fffff802`37e2443b : fffff802`38853100 fffff808`00000000 fffff808`00000000 00000001`622c4021 : nt!MiWsleFree+0x5fc ffff9b0b`f2726d90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFreeWsleList+0x1bb MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_VRF_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {0156c93e-774d-00d2-8700-b230dcbf3b6c} Followup: MachineOwner --------- April 26th Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\042621-20546-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff803`34a0b000 PsLoadedModuleList = 0xfffff803`35635490 Debug session time: Mon Apr 26 00:14:56.437 2021 (UTC - 7:00) System Uptime: 1 days 1:43:12.663 Loading Kernel Symbols ............................................................... ................................................................ .......................................................... Loading User Symbols Loading unloaded module list ................................ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`34e00c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffef01`41abf320=000000000000000a 10: 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: fffff8033ec7bda6, memory referenced Arg2: 00000000000000ff, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8033ec7bda6, address which referenced memory Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2968 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 10313 Key : Analysis.Init.CPU.mSec Value: 233 Key : Analysis.Init.Elapsed.mSec Value: 4773 Key : Analysis.Memory.CommitPeak.Mb Value: 82 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 BUGCHECK_CODE: d1 BUGCHECK_P1: fffff8033ec7bda6 BUGCHECK_P2: ff BUGCHECK_P3: 0 BUGCHECK_P4: fffff8033ec7bda6 READ_ADDRESS: fffff80335706390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse fffff8033ec7bda6 ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target. CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: ffffef0141abf460 -- (.trap 0xffffef0141abf460) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000db2 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8033ec7bda6 rsp=ffffef0141abf5f0 rbp=0000000000000000 r8=0000008000000000 r9=0000000000000200 r10=ffffdf0941a4d010 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl nz na po nc fffff803`3ec7bda6 ?? ??? Resetting default scope FAILED_INSTRUCTION_ADDRESS: +0 fffff803`3ec7bda6 ?? ??? STACK_TEXT: ffffef01`41abf318 fffff803`34e12b69 : 00000000`0000000a fffff803`3ec7bda6 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx ffffef01`41abf320 fffff803`34e0ee69 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 ffffef01`41abf460 fffff803`3ec7bda6 : ffffdf09`41a4d328 00000000`00000000 000000d7`959e2a32 00000000`00000000 : nt!KiPageFault+0x469 ffffef01`41abf5f0 ffffdf09`41a4d328 : 00000000`00000000 000000d7`959e2a32 00000000`00000000 ffffdf09`41a4d330 : 0xfffff803`3ec7bda6 ffffef01`41abf5f8 00000000`00000000 : 000000d7`959e2a32 00000000`00000000 ffffdf09`41a4d330 000000d7`959e2a32 : 0xffffdf09`41a4d328 SYMBOL_NAME: nt!KiPageFault+469 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.870 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 469 FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_VRF_CODE_AV_BAD_IP_nt!KiPageFault OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {9bc18f4e-055a-cf88-10ae-aeb756fbee38} Followup: MachineOwner --------- April 24th Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\042421-17687-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff801`29a11000 PsLoadedModuleList = 0xfffff801`2a63b490 Debug session time: Sat Apr 24 22:31:17.217 2021 (UTC - 7:00) System Uptime: 1 days 1:10:35.750 Loading Kernel Symbols ............................................................... ................................................................ ........................................................... Loading User Symbols Loading unloaded module list ........................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`29e06c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8700`603a78f0=000000000000001e 10: 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: fffff80129c85da6, The address that the exception occurred at Arg3: ffff870060359340, Parameter 0 of the exception Arg4: ffffb089332a1010, Parameter 1 of the exception Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3093 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 9333 Key : Analysis.Init.CPU.mSec Value: 249 Key : Analysis.Init.Elapsed.mSec Value: 5954 Key : Analysis.Memory.CommitPeak.Mb Value: 83 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 BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc000001d BUGCHECK_P2: fffff80129c85da6 BUGCHECK_P3: ffff870060359340 BUGCHECK_P4: ffffb089332a1010 EXCEPTION_PARAMETER1: ffff870060359340 EXCEPTION_PARAMETER2: ffffb089332a1010 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System FAILED_INSTRUCTION_ADDRESS: nt!MiFillSystemPtes+c6 fffff801`29c85da6 ff ??? STACK_TEXT: ffff8700`603a78e8 fffff801`29ea258f : 00000000`0000001e ffffffff`c000001d fffff801`29c85da6 ffff8700`60359340 : nt!KeBugCheckEx ffff8700`603a78f0 fffff801`29e07ae2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x166b2f ffff8700`603a7fb0 fffff801`29e07ab0 : fffff801`29e18ca5 ffffb089`2dec6be0 fffff801`29c4d550 ffffb089`2dec6c98 : nt!KxExceptionDispatchOnExceptionStack+0x12 ffffac05`47abf278 fffff801`29e18ca5 : ffffb089`2dec6be0 fffff801`29c4d550 ffffb089`2dec6c98 fffff801`29c4d20f : nt!KiExceptionDispatchOnExceptionStackContinue ffffac05`47abf280 fffff801`29e131e9 : 00000000`00000000 00000000`00000000 00000000`40dfdcb0 00000000`00000000 : nt!KiExceptionDispatch+0x125 ffffac05`47abf460 fffff801`29c85da6 : ffffb089`332a1328 00000000`00000000 000000d3`0734bfc5 00000000`00000000 : nt!KiInvalidOpcodeFault+0x329 ffffac05`47abf5f0 ffffb089`332a1100 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffb089`332a1010 : nt!MiFillSystemPtes+0xc6 ffffac05`47abf6b0 00000000`00000000 : 00000000`00000001 00000000`00000000 ffffb089`332a1010 00000000`00000000 : 0xffffb089`332a1100 SYMBOL_NAME: nt!MiFillSystemPtes+c6 MODULE_NAME: nt IMAGE_VERSION: 10.0.19041.870 STACK_COMMAND: .thread ; .cxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: c6 FAILURE_BUCKET_ID: 0x1E_c000001d_VRF_BAD_IP_nt!MiFillSystemPtes OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {398b323d-9d15-fc85-9c00-d5e79c43f696} Followup: MachineOwner --------- April 23rd Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\042321-19937-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff800`6f60b000 PsLoadedModuleList = 0xfffff800`70235490 Debug session time: Fri Apr 23 21:20:14.802 2021 (UTC - 7:00) System Uptime: 1 days 22:14:30.500 Loading Kernel Symbols ............................................................... ................................................................ ............................................................ Loading User Symbols Loading unloaded module list ................................ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`6fa00c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9a01`073a78f0=000000000000001e 10: 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: fffff8006f87fda6, The address that the exception occurred at Arg3: ffff9a0107359340, Parameter 0 of the exception Arg4: ffffc3893eb83010, Parameter 1 of the exception Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2921 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 10647 Key : Analysis.Init.CPU.mSec Value: 327 Key : Analysis.Init.Elapsed.mSec Value: 1422 Key : Analysis.Memory.CommitPeak.Mb Value: 81 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 BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc000001d BUGCHECK_P2: fffff8006f87fda6 BUGCHECK_P3: ffff9a0107359340 BUGCHECK_P4: ffffc3893eb83010 EXCEPTION_PARAMETER1: ffff9a0107359340 EXCEPTION_PARAMETER2: ffffc3893eb83010 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System FAILED_INSTRUCTION_ADDRESS: nt!MiFillSystemPtes+c6 fffff800`6f87fda6 ff ??? STACK_TEXT: ffff9a01`073a78e8 fffff800`6fa9c58f : 00000000`0000001e ffffffff`c000001d fffff800`6f87fda6 ffff9a01`07359340 : nt!KeBugCheckEx ffff9a01`073a78f0 fffff800`6fa01ae2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x166b2f ffff9a01`073a7fb0 fffff800`6fa01ab0 : fffff800`6fa12ca5 ffff851a`00000000 00001f80`00000200 fffff800`6f9fcd40 : nt!KxExceptionDispatchOnExceptionStack+0x12 ffff8087`e62bf278 fffff800`6fa12ca5 : ffff851a`00000000 00001f80`00000200 fffff800`6f9fcd40 fffff7bf`0000a000 : nt!KiExceptionDispatchOnExceptionStackContinue ffff8087`e62bf280 fffff800`6fa0d1e9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125 ffff8087`e62bf460 fffff800`6f87fda6 : ffffc389`3eb83328 00000000`00000000 00000183`983d4402 00000000`00000000 : nt!KiInvalidOpcodeFault+0x329 ffff8087`e62bf5f0 ffffc389`3eb83100 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffc389`3eb83010 : nt!MiFillSystemPtes+0xc6 ffff8087`e62bf6b0 00000000`00000000 : 00000000`00000001 00000000`00000000 ffffc389`3eb83010 00000000`00000000 : 0xffffc389`3eb83100 SYMBOL_NAME: nt!MiFillSystemPtes+c6 MODULE_NAME: nt IMAGE_VERSION: 10.0.19041.870 STACK_COMMAND: .thread ; .cxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: c6 FAILURE_BUCKET_ID: 0x1E_c000001d_VRF_BAD_IP_nt!MiFillSystemPtes OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {398b323d-9d15-fc85-9c00-d5e79c43f696} Followup: MachineOwner ---------

:)

 

help to remote connect

not sure how to use both programs u 2 suggested, i need more helpful steps thanks

 

i update bios then black screen ???? pls help me 980ti

@smoka Great you fixed it and would be interesting to know how you did it. Care to list the basic steps you took to do it so that it can help others stuck in the same situation?

 

BSOD at least twice a month - uncertain cause

I have run driver verifier with the below settings for >48 hours. There have been no BSOD. Please advise on next steps

• I/O verification
• Force pending I/O requests
• IRP logging