cancel
Showing results for 
Search instead for 
Did you mean: 

PC Drivers & Software

GuavaDaPengu
Journeyman III

Random BSODS at least once a day, dumps point towards gpu drivers

I've been having this problem for a few days and I just can't figure out what could be causing it. It started after I updated my bios. I used to get driver timeouts on occasion that would cause my screens to flicker to black then come back. After updating my bios it's turned into random blue screens. I've updated my chipset drivers, updated BIOS, run DISM scans, checked my RAM and CPU (both look good used memtest86), disabled FTMP in bios, and uninstalled my gpu drivers with DDU and then reinstalled them. The only thing that's sort of helped is the DISM scan and that just prolongs the time between BSODS. Windows event viewer and the .dmp files seem like they're pointing in the direction of my GPU drivers. I'm completely out of ideas with what else could be causing them. Thank you so much for looking at this, any help is greatly appreciated.

Specs:

Cpu: Ryzen 5 2600x

GPU: Radeon RX 6600 Drivers: 24.10.1

Ram: G Skill 16gb DDR4-3200

MOBO: Gigabyte B450M DS3H, Bios Version 66

PSU: 550W corsair TX550M

OS: Windows 10

 

Event viewer:

Event 1001, windows reporting

Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 84
P3: 2
P4: 0
P5: fffff8014a8f91a0
P6: 10_0_19045
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\Minidump\111324-9031-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43EE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER443D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER445C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44CA.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_6eb4836534b89830bd08feb74d0673f274e4df_00000000_cab_1491fb7c-c929-4b05-861a-a111040625f5

Analysis symbol:
Rechecking for solution: 0
Report Id: 8f792afe-4d9b-4374-8b6a-1514b4b7c651
Report Status: 4
Hashed bucket:
Cab Guid: 0

 

Dump file:

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

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, 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: fffff8014a8f91a0, address which referenced memory

 

Debugging Details:

------------------



KEY_VALUES_STRING: 1

 

    Key  : Analysis.CPU.mSec

    Value: 1562

 

    Key  : Analysis.Elapsed.mSec

    Value: 1569

 

    Key  : Analysis.IO.Other.Mb

    Value: 0

 

    Key  : Analysis.IO.Read.Mb

    Value: 1

 

    Key  : Analysis.IO.Write.Mb

    Value: 0

 

    Key  : Analysis.Init.CPU.mSec

    Value: 468

 

    Key  : Analysis.Init.Elapsed.mSec

    Value: 4079

 

    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 91

 

    Key  : Analysis.Version.DbgEng

    Value: 10.0.27725.1000

 

    Key  : Analysis.Version.Description

    Value: 10.2408.27.01 amd64fre

 

    Key  : Analysis.Version.Ext

    Value: 1.2408.27.1

 

    Key  : Bugcheck.Code.LegacyAPI

    Value: 0xa

 

    Key  : Bugcheck.Code.TargetModel

    Value: 0xa

 

    Key  : Dump.Attributes.AsUlong

    Value: 8

 

    Key  : Dump.Attributes.KernelGeneratedTriageDump

    Value: 1

 

    Key  : Failure.Bucket

    Value: AV_amdkmdag!unknown_function

 

    Key  : Failure.Hash

    Value: {c753a2f9-94a6-448f-1d0e-e079b3442215}



BUGCHECK_CODE:  a

 

BUGCHECK_P1: 84

 

BUGCHECK_P2: 2

 

BUGCHECK_P3: 0

 

BUGCHECK_P4: fffff8014a8f91a0

 

FILE_IN_CAB:  111324-9031-01.dmp

 

DUMP_FILE_ATTRIBUTES: 0x8

  Kernel Generated Triage Dump

 

FAULTING_THREAD:  fffff8014b327a00

 

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

 0000000000000084 

 

BLACKBOXBSD: 1 (!blackboxbsd)



BLACKBOXNTFS: 1 (!blackboxntfs)



BLACKBOXPNP: 1 (!blackboxpnp)



BLACKBOXWINLOGON: 1

 

CUSTOMER_CRASH_COUNT:  1

 

PROCESS_NAME:  System

 

TRAP_FRAME:  fffff8014da74320 -- (.trap 0xfffff8014da74320)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000044 rbx=0000000000000000 rcx=0000000000000080

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8014a8f91a0 rsp=fffff8014da744b8 rbp=0000000000000044

 r8=0000000000000000  r9=00000000000070e5 r10=ffff920c3e9c6020

r11=fffff8014da74590 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!FsRtlNumberOfRunsInBaseMcb:

fffff801`4a8f91a0 8b4104          mov     eax,dword ptr [rcx+4] ds:00000000`00000084=????????

Resetting default scope

 

STACK_TEXT:  

fffff801`4da741d8 fffff801`4aa12da9     : 00000000`0000000a 00000000`00000084 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff801`4da741e0 fffff801`4aa0e778     : fffff801`4da74580 fffff801`4a9d1581 00000000`0000001f fffff801`4da744f0 : nt!KiBugCheckDispatch+0x69

fffff801`4da74320 fffff801`4a8f91a0     : fffff801`64af6fa0 00000000`000070e5 fffff801`4da74580 ffff920c`42c28aa0 : nt!KiPageFault+0x478

fffff801`4da744b8 fffff801`64af6fa0     : 00000000`000070e5 fffff801`4da74580 ffff920c`42c28aa0 00000000`00989680 : nt!FsRtlNumberOfRunsInBaseMcb

fffff801`4da744c0 00000000`000070e5     : fffff801`4da74580 ffff920c`42c28aa0 00000000`00989680 fffff801`4da745d0 : amdkmdag+0x66fa0

fffff801`4da744c8 fffff801`4da74580     : ffff920c`42c28aa0 00000000`00989680 fffff801`4da745d0 fffff801`4da74780 : 0x70e5

fffff801`4da744d0 ffff920c`42c28aa0     : 00000000`00989680 fffff801`4da745d0 fffff801`4da74780 00000000`00000000 : 0xfffff801`4da74580

fffff801`4da744d8 00000000`00989680     : fffff801`4da745d0 fffff801`4da74780 00000000`00000000 fffff801`4b327a00 : 0xffff920c`42c28aa0

fffff801`4da744e0 fffff801`4da745d0     : fffff801`4da74780 00000000`00000000 fffff801`4b327a00 ffff920c`42c28aa0 : 0x989680

fffff801`4da744e8 fffff801`4da74780     : 00000000`00000000 fffff801`4b327a00 ffff920c`42c28aa0 fffff801`4da74580 : 0xfffff801`4da745d0

fffff801`4da744f0 00000000`00000000     : fffff801`4b327a00 ffff920c`42c28aa0 fffff801`4da74580 ffff920c`40202000 : 0xfffff801`4da74780



SYMBOL_NAME:  amdkmdag+66fa0

 

MODULE_NAME: amdkmdag

 

IMAGE_NAME:  amdkmdag.sys

 

STACK_COMMAND:  .process /r /p 0xfffff8014b324a00; .thread 0xfffff8014b327a00 ; kb

 

BUCKET_ID_FUNC_OFFSET:  66fa0

 

FAILURE_BUCKET_ID:  AV_amdkmdag!unknown_function

 

OSPLATFORM_TYPE:  x64

 

OSNAME:  Windows 10

 

FAILURE_ID_HASH:  {c753a2f9-94a6-448f-1d0e-e079b3442215}

 

Followup:     MachineOwner

0 Likes
0 Replies