The AMD Driver Thread

[sanyimano]

Where do I find the serial number?

The Made in China sticker at the bottom of the fan shroud. You'd need to remove the card from the mobo to look at it. It's also present on the box next to 'Maid in China'. It starts with A followed by 12 numbers

 

[GoogalyMoogaly]

The Made in China sticker at the bottom of the fan shroud. You'd need to remove the card from the mobo to look at it. It's also present on the box next to 'Maid in China'. It starts with A followed by 12 numbers

Took the card out to check, no it's not that SN.
Was that your card and did you have the same or similar issue?
Did you find any other way to trigger it? Something that would be easy to re-create if they tested it if I returned it (again)?

 

[sanyimano]

Took the card out to check, no it's not that SN.
Was that your card and did you have the same or similar issue?
Did you find any other way to trigger it? Something that would be easy to re-create if they tested it if I returned it (again)?

Yes, I wondered if you received my RMA return from a few weeks ago.
My issue with the Pulse 7900XT was temperature dependant. At cold temperatures (room below 22 C) the card couldn't properly load its VBIOS. Linux refused to cold boot. Windows did boot, but it couldn't load the Adrenalin driver. I was also able to crash Windows by lowering the room temperature below 20C while the PC was running. When the card was warm, it was working as expected. You might have a similar issue. The card works fine when it's hot, but the driver crashes when it cools down.

 

[GoogalyMoogaly]

Yes, I wondered if you received my RMA return from a few weeks ago.
My issue with the Pulse 7900XT was temperature dependant. At cold temperatures (room below 22 C) the card couldn't properly load its VBIOS. Linux refused to cold boot. Windows did boot, but it couldn't load the Adrenalin driver. I was also able to crash Windows by lowering the room temperature below 20C while the PC was running. When the card was warm, it was working as expected. You might have a similar issue. The card works fine when it's hot, but the driver crashes when it cools down.

If anything mine seems like the opposite, it's fine in the menus but crashes when the games starts.
I have so little luck with AMD cards...

 

[sanyimano]

If anything mine seems like the opposite, it's fine in the menus but crashes when the games starts.
I have so little luck with AMD cards...

I only had those kind of crashes when I tried undervolting. Undervolting success can vary from game to game. Some work really well, others might crash as soon as they load. However, at stock settings the card should be 100% stable in all games. If it keeps crashing with default non-OC settings, that GPU might be defective.

 

[tommybhoy]

@GoogalyMoogaly

Type cache into Adrenaline search bar>Reset the shader cache in Adrenaline

Worth a try

 

[Game]

This AMD Driver Manager thing... every few days it pops up with a new Chip-Set driver system restart request, i click on restart and its fine until it pops up again a few days later with the same thing, and repeat.... repeat..... inflate loop of it making the same request every few days.

This is the sort of thing why people keep brining up "AMD bad Drivers" This stuff clearly needs more Q&A before its released.

never had it once it might be an automatic updates thing I never have this turned on

https://www.reddit.com/r/AMDHelp/comments/1k7m2mx/amd_install_manager_asking_for_a_restart/

 

[Firegod]

This AMD Driver Manager thing... every few days it pops up with a new Chip-Set driver system restart request, i click on restart and its fine until it pops up again a few days later with the same thing, and repeat.... repeat..... inflate loop of it making the same request every few days.

This is the sort of thing why people keep brining up "AMD bad Drivers" This stuff clearly needs more Q&A before its released.

Not seeing that here either, sorry. Latest optional GPU driver and latest chipset as well.

 

[GoogalyMoogaly]

I only had those kind of crashes when I tried undervolting. Undervolting success can vary from game to game. Some work really well, others might crash as soon as they load. However, at stock settings the card should be 100% stable in all games. If it keeps crashing with default non-OC settings, that GPU might be defective.

@GoogalyMoogaly

Type cache into Adrenaline search bar>Reset the shader cache in Adrenaline

Worth a try

Removed and re-insert graphics card and all connectors.
Removed my UV, memory changes, etc.
Cleared the Shader cache.
Downloaded the Black Ops 6 update.

Run game, crashes as soon as the first match loads. Anything else I can check? I don't want to assume it's the B-Grade RMA replacement, but I am starting to wonder if it's the B-Grade RMA replacement.
So far that's the only way I've been able to trigger it though. Tried the Adrenaline stress test, fine. Tried OCCT, fine. Ran Heaven, fine. Did the GPU render in Cinebench 2024, fine. Black Ops 6, instant driver/game crash once the match starts.

 

[theforce]

Removed and re-insert graphics card and all connectors.
Removed my UV, memory changes, etc.
Cleared the Shader cache.
Downloaded the Black Ops 6 update.

Run game, crashes as soon as the first match loads. Anything else I can check? I don't want to assume it's the B-Grade RMA replacement, but I am starting to wonder if it's the B-Grade RMA replacement.
So far that's the only way I've been able to trigger it though. Tried the Adrenaline stress test, fine. Tried OCCT, fine. Ran Heaven, fine. Did the GPU render in Cinebench 2024, fine. Black Ops 6, instant driver/game crash once the match starts.

Since the issue only arises during a particular game, in this case Black Ops 6, it might be because of a graphical setting in the game or the AMD drivers. After a quick search, it seems Black Ops supports DX12 and Vulkan. Does the crash occur with both DX12 and Vulcan? If that doesn't work, try lowering the graphical settings to see if the issue is fixed.

 

[GoogalyMoogaly]

Since the issue only arises during a particular game, in this case Black Ops 6, it might be because of a graphical setting in the game or the AMD drivers. After a quick search, it seems Black Ops support DX12 and Vulkan. If that doesn't work, try lowering the graphical settings to see if the issue is fixed.

It's only a 7900XT I think the setting are pretty low anyway (so I can hit 4K @ 120hz).
I don't recall seeing the option to switch between DX12 and Vulkan, but should a 7900XT be able to run both?
The only other game I think I've tried is Balatro, so I'm not sure that's a fair test. Oh, maybe Crusader Kings 3 too.

 

[henson0115]

Run game, crashes as soon as the first match loads. Anything else I can check? I don't want to assume it's the B-Grade RMA replacement, but I am starting to wonder if it's the B-Grade RMA replacement.
So far that's the only way I've been able to trigger it though. Tried the Adrenaline stress test, fine. Tried OCCT, fine. Ran Heaven, fine. Did the GPU render in Cinebench 2024, fine. Black Ops 6, instant driver/game crash once the match starts.

just trying lowering the max clock by 100/200mhz, if that fixes it send it back.

 

[GoogalyMoogaly]

Since the issue only arises during a particular game, in this case Black Ops 6, it might be because of a graphical setting in the game or the AMD drivers. After a quick search, it seems Black Ops supports DX12 and Vulkan. Does the crash occur with both DX12 and Vulcan? If that doesn't work, try lowering the graphical settings to see if the issue is fixed.

just trying lowering the max clock by 100/200mhz, if that fixes it send it back.

Lowered the max clock by 150-ish Mhz and the match started but then crashed part way through.
I lowered the setting to minimum, which set the render resolution to 1080p (instead of 4K) and I played a whole round. Then set the render resolution back to 4K and it once again crashed part way through a round. At this point the clock speeds had reset following the crash.

 

[henson0115]

Lowered the max clock by 150-ish Mhz and the match started but then crashed part way through.
I lowered the setting to minimum, which set the render resolution to 1080p (instead of 4K) and I played a whole round. Then set the render resolution back to 4K and it once again crashed part way through a round. At this point the clock speeds had reset following the crash.

obviously 4k is putting way more load on it than 1080, sounds like either the chip is pushing itself to hard and the clocks are boosting too high for the voltage or the voltage just isn't enough for the load. had a similar issue with a 6800 in the past where it would boost higher than it should have and just crash as a result, lowering the clocks a couple hundred mhz fixed it in my case, but if i were you id rma/return it and get a new one, you shouldn't have to deal with this kind of issue on a new card b grade or not.

 

[Game]

I'm having an issue at the minute where every time I try to play Call of Duty Black Ops 6 on my 7900 XT I get a driver crash as soon as a match begins.
First the game crashed, then then drivers crashes (or maybe this happens at the same time) and then more often than not a minute or two later I get a blue screen crash with DRIVER_POWER_STATE_FAILURE.

I don't see anything obvious in event viewer other than a few messages about windows not being shut down cleanly (due to the crash).

I've updated to the latest drivers, the game is up to date and I've tried repairing the game files.

It doesn't seem to crash in the menus or while running the benchmark but as soon as the map load it crashes.

Anyone know how to fix this or what I can try to make down the cause?

That's a warzone thing let me login to computer and send you the config fix

 

[Game]

just trying lowering the max clock by 100/200mhz, if that fixes it send it back.

rubbish that has been flying around forums constantly but mostly tosh from gamerz kids who know no better

this issue was caused by the update messing with the shader files its not an "AMD" issue its a game issue

Remove the old files from documents folder remove following files

s.1.0.cod24.m s.1.0.cod24.txt0 s.1.0.cod24.txt1

https://www.reddit.com/r/CODWarzone/comments/1kcewtw/directx_crash_since_update/

I had to do this yesterday morning after the update it was a touch frustrating till I changed the files

 

[henson0115]

rubbish that has been flying around forums constantly but mostly tosh from gamerz kids who know no better

this issue was caused by the update messing with the shader files its not an "AMD" issue its a game issue

Remove the old files from documents folder remove following files

s.1.0.cod24.m s.1.0.cod24.txt0 s.1.0.cod24.txt1

https://www.reddit.com/r/CODWarzone/comments/1kcewtw/directx_crash_since_update/

I had to do this yesterday morning after the update it was a touch frustrating till I changed the files

what are you talking about, its not rubbish. it can and does happen. as I've mentioned I've got a card that does this exact thing and i don't own that cod game. maybe his issue is cod but that doesn't mean everything else goes out the window when trying to diagnose the issue. from memory he's also already tried clearing the shader cache and still having the same issue.

 

[Game]

If anything mine seems like the opposite, it's fine in the menus but crashes when the games starts.
I have so little luck with AMD cards...

what are you talking about, its not rubbish. it can and does happen. as I've mentioned I've got a card that does this exact thing and i don't own that cod game. maybe his issue is cod but that doesn't mean everything else goes out the window when trying to diagnose the issue. from memory he's also already tried clearing the shader cache and still having the same issue.

Fair dues

I was speaking specifically Cod

 

[GoogalyMoogaly]

rubbish that has been flying around forums constantly but mostly tosh from gamerz kids who know no better

this issue was caused by the update messing with the shader files its not an "AMD" issue its a game issue

Remove the old files from documents folder remove following files

s.1.0.cod24.m s.1.0.cod24.txt0 s.1.0.cod24.txt1

https://www.reddit.com/r/CODWarzone/comments/1kcewtw/directx_crash_since_update/

I had to do this yesterday morning after the update it was a touch frustrating till I changed the files

Thanks for the suggestion, I tried this but it didn't help.

I also tried lowering my clock speeds further, normally sits at around 2700 so lowered it to 2400 for CoD, still did it.

I even swapped over my PSU. Played one match it was fine, played another and it crashed.

I'm not really sure what to try, I could stick my 4060Ti in the machine instead I guess, see if it still does it.

 

[henson0115]

Thanks for the suggestion, I tried this but it didn't help.

I also tried lowering my clock speeds further, normally sits at around 2700 so lowered it to 2400 for CoD, still did it.

I even swapped over my PSU. Played one match it was fine, played another and it crashed.

I'm not really sure what to try, I could stick my 4060Ti in the machine instead I guess, see if it still does it.

what 2 psus have you tried model etc? could it be that the psu are fine with the 4060ti as it has a lower wattage requirement and the 7900xt its just too much for them? could also try looking at the psu rails in hwifo specifically in the mobo section 3v/3.3v/5v and 12v, don't run cod, but check at idle are they close to the ratings (i.e is the 12v rail within 10% of 12v etc)? try the running another lower demanding game, check them again are they still close to the ratings? after having a psu that could not provide the correct voltages close to the rails, its one of the things i usually check now when it comes to gpu crashing although in my experience that issues causes a full system reset and not a crash but you never know and wouldn't loose anything but time.

edit: worth checking swapping the gpu as it will potentially eliminate things like cpu etc, when you swapped from the 4060 to 7900 did you a run DDU and fully nuke the nvidia drivers? most peopl,e say you dont need to bother now, but it is worth doing as it gives you more of a clean start than just an uninstall.