Computer Type: Desktop
GPU: rx 7700xt pure
CPU: RYZEN 7 5800x 8 cores 16 threads
Motherboard: MSI b550 tomahawk
BIOS Version: 7C91vAG
RAM: 32 gb ram kingston ddr4 cl16 3200mhz
PSU: corsair rm 850i
Case: antec
Operating System & Version: WINDOWS 10 PRO
GPU Drivers: adrenalin 24.6.1
Chipset Drivers: AMD B550 CHIPSET DRIVERS VERSION 2.10.13.408
Background Applications: windowsm, firefox
Description of Original Problem: I was trying to perform gpu stability tests with furmark v1 and v2 in full screen but the screen goes black and with furmark v2 it gave me a DRIVER_IRQL_NOT_LESS_OR_EQUAL bsod. caused by dxgmms2dxgmms2.sys
Troubleshooting: The problem occurs with all the 2024 drivers (24.1.1 -24.7.1) when I have returned to the 23.12.1 driver the problem does not occur and I can perform the full screen tests.
Open a AMD SUPPORT ticket and see what they believe might be the problem with those AMD drivers and your GPU card from here: https://www.amd.com/en/forms/contact-us/support.html
Seems like several Users at AMD Forums are complaining about version 24.7.1 driver causing crashing and errors.
ok I'm going to do it because after going back to version 24.6.1 and playing I got a bsod now I'm going back to version 23.12.1 and testing, thanks
Ok, I was playing and when I activated the overlay and a bsod occurred. Can anyone help me?
************ Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToV8JsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 41 Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidumps\080724-5562-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 (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff804`59e00000 PsLoadedModuleList = 0xfffff804`5aa2a8c0 Debug session time: Wed Aug 7 20:31:07.354 2024 (UTC - 5:00) System Uptime: 0 days 8:05:30.946 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................. Loading User Symbols Loading unloaded module list ................... For analysis of this file, run !analyze -vnt!KeBugCheckEx: fffff804`5a1fde50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff804`5d084530=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: 0000000000000000, memory referenced Arg2: 000000000000000a, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000000000000, address which referenced memory Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for amdkmdag.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1905 Key : Analysis.Elapsed.mSec Value: 4515 Key : Analysis.IO.Other.Mb Value: 4 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 18 Key : Analysis.Init.CPU.mSec Value: 531 Key : Analysis.Init.Elapsed.mSec Value: 9346 Key : Analysis.Memory.CommitPeak.Mb Value: 135 Key : Bugcheck.Code.LegacyAPI Value: 0xd1 Key : Bugcheck.Code.TargetModel Value: 0xd1 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: AV_CODE_AV_NULL_IP_amdkmdag!unknown_function Key : Failure.Hash Value: {8b5ee15c-d5fc-f4cc-ad98-af34e2376aa6} BUGCHECK_CODE: d1 BUGCHECK_P1: 0 BUGCHECK_P2: a BUGCHECK_P3: 8 BUGCHECK_P4: 0 FILE_IN_CAB: 080724-5562-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump READ_ADDRESS: fffff8045aafb390: 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 0000000000000000 PROCESS_NAME: System BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 TRAP_FRAME: fffff8045d084670 -- (.trap 0xfffff8045d084670)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffce01faeb3000 rdx=fffff8045d084830 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000000 rsp=fffff8045d084808 rbp=0000000000000013 r8=0000000000000000 r9=0000000000000010 r10=ffffce01fae58000 r11=ffff75fe08a00000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc 00000000`00000000 ?? ??? Resetting default scope IP_IN_FREE_BLOCK: 0 FAILED_INSTRUCTION_ADDRESS: +0 STACK_TEXT: fffff804`5d084808 fffff804`7f88a981 : 00000000`00000000 fffff804`7dcb3fd8 00000000`00000000 00000000`00000000 : 0x0 fffff804`5d084810 00000000`00000000 : fffff804`7dcb3fd8 00000000`00000000 00000000`00000000 00000001`00000008 : amdkmdag+0x1bda981 STACK_COMMAND: .trap 0xfffff8045d084670 ; kb SYMBOL_NAME: amdkmdag+1bda981 MODULE_NAME: amdkmdag IMAGE_NAME: amdkmdag.sys BUCKET_ID_FUNC_OFFSET: 1bda981 FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_amdkmdag!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {8b5ee15c-d5fc-f4cc-ad98-af34e2376aa6} Followup: MachineOwner --------- 0: kd> !blackboxbsd Version: 0xb0 Product type: 1 Auto advanced boot: FALSE Advanced boot menu timeout: 30 Last boot succeeded: TRUE Last boot shutdown: FALSE Sleep in progress: FALSE Power button timestamp: 0x0 System running: TRUE Connected standby in progress: FALSE User shutdown in progress: FALSE System shutdown in progress: FALSE Sleep in progress: 0 Connected standby scenario instance id: 0 Connected standby entry reason: 0 Connected standby exit reason: 0 System sleep transitions to on: 0 Last reference time: 0x1dae929d2df97e5 2024-08-08T00:28:00.165Z Last reference time checksum: 0xe3f92885 Last update boot id: 215 Boot attempt count: 1 Last boot checkpoint: TRUE Checksum: 0xec Last boot id: 215 Last successful shutdown boot id: 214 Last reported abnormal shutdown boot id: 214 Error info boot id: 0 Error info repeat count: 0 Error info other error count: 0 Error info code: 0 Error info status: 0x0 Power button last press time: 0x0 Power button cumulative press count: 0 Power button last press boot id: 0 Power button last power watchdog stage: 0 Power button watchdog armed: FALSE Power button shutdown in progress: FALSE Power button last release time: 0x0 Power button cumulative release count: 0 Power button last release boot id: 0 Power button error count: 0 Power button current connected standby phase: 0 Power button transition latest checkpoint id: 0 Power button transition latest checkpoint type: 0 Power button transition latest checkpoint sequence number: 0 Power transition Shutdown Device Type: 0 Power transition Setup In Progress: FALSE Power transition OOBE In Progress: FALSE Power transition Sleep Checkpoint Source: 0 Power transition Sleep Checkpoint: 0 Power transition Connected Standby Entry Reason Category: 0 Power transition Connected Standby Exit Reason Category: 0 Power transition Connected Standby Entry Scenario Instance Id: 0x0 Feature Configuration State : Uninitialized
You have a AMD Driver issue.
I know I have seen several threads at AMD Forums about the Overlay causing problems.
Unfortunately I am not familiar with that new feature and someone else will need to assist you.
@goodplay or @FunkZ are knowledgeable Users and they might have a suggestion otherwise I would open a AMD SUPPORT TIcket.
Just did each 4 runs back to back, no crash here.
Using 24.5.1 and no problem running Furmark full screen or using the Adrenalin Metric Overlay, and haven't heard of anyone else having that particular issue before.
@erikovick you're using the latest BIOS for your board but your chipset driver is 4 years old, recommend you update that.
Also since your BSOD referenced dxgmms2.sys you may want to run a dxdiag.
Hello, thanks for your response, how can I see the version of my chipset?
If I have returned to version 24.5.1 and I don't have that problem, what I have noticed is that in versions 24.6.1 and 24.7.1 they have the memory temperature option in programs like afterburner, adrenalin and gpuz... the 24.5.1 doesn't have it so I wouldn't know if that would be an error.
I have done a dxdiag, it has not given me any errors...
In your first post you listed
Chipset Drivers: AMD B550 CHIPSET DRIVERS VERSION 2.10.13.408
That is from 2020
https://www.amd.com/en/support/downloads/previous-drivers.html/chipsets/am4/b550.html
Oh, yes I made a mistake when pasting the info, I have the latest chipset driver and as I said, with version 24.5.1 I have no problems with either Furmark or the overlay. Yesterday I tried playing eleven human for 3 hours, active and options from the overlay and no. it gave me errors
So no problems with 24.5.1 then?
Yes, there were some additional overlay metrics added in the latest Adrenalin version, 24.5.1 does not monitor GPU memory temperature.
Yes, I have not had problems with that driver so far, but if I get scared with the BSOD :(, would it be advisable to apply RMA better?
No if it's running fine on 24.5.1 then just keep using that until a newer version comes out.
Here are some Users with issues with AMD Overlay from the past, granted some are fairly old but some are fairly new also.
I wasn't talking about his specific issue but in general about Users having issues with AMD Overlay.
Thanks for answering though:
https://community.amd.com/t5/graphics-cards/fps-counter-disappears-from-amd-overlay/m-p/207066
https://community.amd.com/t5/drivers-software/amd-adrenaline-is-not-working-properly/m-p/698147
https://community.amd.com/t5/general-discussions/problem-with-overlay/m-p/596312
https://community.amd.com/t5/drivers-software/overlay-problem-in-latest-drivers/m-p/231854