Frequent BSOD w/ Various Errors

Question

Issue:

Frequent BSOD and oddly high memory usage. For example, with only Google Chrome and Windows DBG open, I'm utilizing 78% of my memory and 30-40% of my CPU. System specs are below. The issue started after I installed a new video card ~ about two years ago. I switched from an RTX 2080 to GTX 1080. The BSOD errors weren't as frequent, and I assumed it was due to the video card, which I was only keeping temporarily, so I didn't think much about it.

A few months ago, I installed an RTX 3080, and the BSOD persists, except it has been much more frequent as of late. My Nvidia drivers are up to date, and I've downloaded 2 - 3 updates to them since.

All other hardware has remained the same.

Any advice is appreciated.

System:

Windows 10

intel i9. It is overclocked but was stable for years and I haven't changed it.

16GB ram at 3200MHz

RTX 3090

Errors:

UNEXPECTED_KERNEL_MODE_TRAP

IRQL_NOT_LESS_OR_EQUAL

HYPERVISOR_ERROR

SYSTEM_SERVICE_EXCEPTION

And, probably, some others I'm forgetting.

I've Tried:

Windows Defender

Sfc /ScanNow

Dism /Online /Cleanup-image /RestoreHealth

Checked drive health

Checked memory health

No issues found on anything

Dumps: https://drive.google.com/drive/folders/1fI6EtpULYJHhH-94bO_ChVwnmnKSNEnG

Sample Dump FIle:

`7: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff818e534a9570, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000fc, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8054fe8523c, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2687

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3501

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa

    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:  110222-7500-01.dmp

BUGCHECK_CODE:  a

BUGCHECK_P1: ffff818e534a9570

BUGCHECK_P2: ff

BUGCHECK_P3: fc

BUGCHECK_P4: fffff8054fe8523c

READ_ADDRESS: fffff805508fb390: 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
 ffff818e534a9570 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff818e4968f430 -- (.trap 0xffff818e4968f430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff78000000340 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8054fe8523c rsp=ffff818e4968f5c0 rbp=ffff818e4968f6f0
 r8=0000000000000008  r9=0000000000000000 r10=ffff8a818a4dc010
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na po nc
nt!KeQueryPerformanceCounter+0xac:
fffff805`4fe8523c 83bfdc00000040  cmp     dword ptr [rdi+0DCh],40h ds:00000000`000000dc=????????
Resetting default scope

STACK_TEXT:  
ffff818e`4968f2e8 fffff805`5000b069     : 00000000`0000000a ffff818e`534a9570 00000000`000000ff 00000000`000000fc : nt!KeBugCheckEx
ffff818e`4968f2f0 fffff805`50007369     : ffff8a81`8ab73390 fffff805`68a2b0b1 00000000`00000000 00000000`000100ee : nt!KiBugCheckDispatch+0x69
ffff818e`4968f430 fffff805`4fe8523c     : 00000018`20d18962 ffff8a81`8a4dc100 ffffd001`f3480180 00000000`00000000 : nt!KiPageFault+0x469
ffff818e`4968f5c0 fffff805`4ff93baa     : ffff8a81`8a4dc010 00000000`00000000 00000000`00000000 00000000`013c33f6 : nt!KeQueryPerformanceCounter+0xac
ffff818e`4968f5f0 fffff805`4fed31b5     : 00000000`00000000 00001f80`00000008 00000000`00000003 00000000`00000002 : nt!PpmIdleSelectStates+0x12a
ffff818e`4968f9f0 fffff805`4fffcc44     : ffffffff`00000000 ffffd001`f348b440 ffff8a81`82350600 00000000`00000816 : nt!PoIdle+0x405
ffff818e`4968fb60 00000000`00000000     : ffff818e`49690000 ffff818e`49689000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME:  nt!KeQueryPerformanceCounter+ac

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2130

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  ac

FAILURE_BUCKET_ID:  AV_nt!KeQueryPerformanceCounter

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0746266c-a4e0-cb68-6ac0-b683ecf61bab}

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

Answer 1

Hi JayA86,

Thanks for sharing the minidump files.

The minidump files indicate a hardware issue.

To troubleshoot this issue, kindly try the steps below (Skip a step that you have already tried):

1-Check for updates:

Go to Settings > Update and Security > Check for update > install all the pending updates

2-Uninstall the graphics card driver completely using the DDU free tool:

https://www.guru3d.com/files-details/display-dr...

Then, install the latest driver provided on the manufacturer's website.

3-Uninstall any third-party security software and scan for viruses & malware with the free Malwarebytes:

https://www.malwarebytes.com/mwb-download

4-Run Command Prompt as administrator. Type this command and hit enter:

dism.exe /online /cleanup-image /restorehealth

Then, type this command and hit enter:

sfc /scannow

5-If you are overclocking your PC, try running everything (CPU, GPU, system memory) at their stock speeds. See if the issue is still reproducible. Or, turn off XMP profile or set it to Auto.

6-Download then install the latest version of BIOS & Chipset drivers from the manufacturer's website.

7-Test the RAM with the free utility MemTest86, then run a full 8 pass scan to test your RAM for physical errors:

https://www.tenforums.com/tutorials/14201-memte...

8-Run the Windows Memory Diagnostic:

https://www.howtogeek.com/260813/how-to-test-yo...

Run Hard Drive Diagnostic:

https://www.lifewire.com/free-hard-drive-testin...

9-If you are comfortable of doing so, take all the system memory sticks out, examine them for any obvious defects, and then reseat them into the sockets. Make sure that they are seated properly in their slots. If you have multiple sticks of system memory installed and you suspect one is faulty, one thing to try is to reproduce the issue with only one stick of memory module at a time. This will help you to isolate the faulty module.

10-If the issue still persists after the steps above, enable the driver verifier and let the computer crash 3 times then disable it and share the newly created minidump file:

https://www.tenforums.com/tutorials/5470-enable...

Please do not hesitate to ask if you need further assistance.

Stay safe

____________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Answer 2

Hi,

Here's a link to the rest of the dump files: https://drive.google.com/drive/folders/1fI6EtpULYJHhH-94bO_ChVwnmnKSNEnG Thanks!

Answer 3

Hi JayA86,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

Regards,