Win 11 BSOD PC Crash, All Bugcheck and PC Details in post TIA

Open | BSOD

Hey All, today my Sim Racing PC crashed for the first time ever. It did it two times back to back. Its about a year old now on the build and has been flawless. I was in the middle of racing in Assetto Corsa when it froze up and then shut down and restarted.

Thinking it was a fluke, I reloaded as normal, all worked as normal, then mid race again it did it again.

PC SPECS:

  • Windows 11
  • i7-13700kf
  • 3090ti FE
  • 64gb DDR5 5200mhz
  • 3TB Samsung NVME - 2 drives 1tb & 2tb
  • 1000w Gold 80+ PSU
  • Corsair water cooler - 7 fans total minus the GPU fans

I have tracked down details to understand why or what caused the crashes. It led me to the Bugcheck information. "The bugcheck was: 0x000000d1 (0x0000000000000a64, 0x0000000000000008, 0x0000000000000000, 0xfffff8073ebd8b82)"

I installed and ran Windbg to get the detail below. I do have two minidump crash reports that I can share but this post hasn't worked with the links I think? I have them loaded into my google drive for easy sharing.

As I type this Chrome continues to "Not Respond" which it has NEVER done before either.

Based on searching and rabbit hole digging, I thought that this could be related to the GPU Driver so I did update my Nvidia 3090ti driver. I have yet to run the sim again until after I made a post assuming its going to crash again.

THANK YOU ALL FOR THE HELP IN ADVANCE

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: 0000000000000a64, memory referenced

Arg2: 0000000000000008, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff80676018b82, address which referenced memory

Debugging Details:

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 500

Key : Analysis.Elapsed.mSec

Value: 1781

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

Key : Analysis.Init.Elapsed.mSec

Value: 36246

Key : Analysis.Memory.CommitPeak.Mb

Value: 96

Key : Bugcheck.Code.LegacyAPI

Value: 0xd1

Key : Dump.Attributes.AsUlong

Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key : Dump.Attributes.ErrorCode

Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage

Value: 0

Key : Failure.Bucket

Value: AV_nvlddmkm!unknown_function

Key : Failure.Hash

Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

BUGCHECK_CODE: d1

BUGCHECK_P1: a64

BUGCHECK_P2: 8

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80676018b82

FILE_IN_CAB: 110123-5000-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

READ_ADDRESS: fffff8064e71d468: 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

0000000000000a64

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff80652a7e9e0 -- (.trap 0xfffff80652a7e9e0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80676018b82 rsp=fffff80652a7eb70 rbp=fffff80652a7ec99

r8=fffff80652a7ed90 r9=fffff80652a7ed90 r10=fffff80652a7f100

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nvlddmkm+0xb8b82:

fffff806`76018b82 8bb9640a0000 mov edi,dword ptr [rcx+0A64h] ds:00000000`00000a64=????????

Resetting default scope

STACK_TEXT:

fffff806`52a7e898 fffff806`4de27da9 : 00000000`0000000a 00000000`00000a64 00000000`00000008 00000000`00000000 : nt!KeBugCheckEx

fffff806`52a7e8a0 fffff806`4de23434 : 00000000`00000000 ffffe50a`54af8a30 00000000`00000000 ffffe50a`60dcb000 : nt!KiBugCheckDispatch+0x69

fffff806`52a7e9e0 fffff806`76018b82 : fffff806`76c72ee0 fffff806`760fc225 00000000`00000038 00000000`00000001 : nt!KiPageFault+0x474

fffff806`52a7eb70 fffff806`76c72ee0 : fffff806`760fc225 00000000`00000038 00000000`00000001 fffff806`76c72ee0 : nvlddmkm+0xb8b82

fffff806`52a7eb78 fffff806`760fc225 : 00000000`00000038 00000000`00000001 fffff806`76c72ee0 fffff806`52a7ec00 : nvlddmkm+0xd12ee0

fffff806`52a7eb80 00000000`00000038 : 00000000`00000001 fffff806`76c72ee0 fffff806`52a7ec00 ffffe50a`67965af8 : nvlddmkm+0x19c225

fffff806`52a7eb88 00000000`00000001 : fffff806`76c72ee0 fffff806`52a7ec00 ffffe50a`67965af8 fffff806`76022e85 : 0x38

fffff806`52a7eb90 fffff806`76c72ee0 : fffff806`52a7ec00 ffffe50a`67965af8 fffff806`76022e85 00000000`00000000 : 0x1

fffff806`52a7eb98 fffff806`52a7ec00 : ffffe50a`67965af8 fffff806`76022e85 00000000`00000000 00000000`00000000 : nvlddmkm+0xd12ee0

fffff806`52a7eba0 ffffe50a`67965af8 : fffff806`76022e85 00000000`00000000 00000000`00000000 fffff806`52a7ec99 : 0xfffff806`52a7ec00

fffff806`52a7eba8 fffff806`76022e85 : 00000000`00000000 00000000`00000000 fffff806`52a7ec99 fffff806`76c72ee0 : 0xffffe50a`67965af8

fffff806`52a7ebb0 00000000`00000000 : 00000000`00000000 fffff806`52a7ec99 fffff806`76c72ee0 fffff806`52a7ec50 : nvlddmkm+0xc2e85

SYMBOL_NAME: nvlddmkm+b8b82

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: b8b82

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner

Posted Nov 2, 2023, 1:29 AM UTC

17
Loading comments…