Memory clock stuck at 150MHz

[DrMacintosh]

Status: UNRESOLVED

Computer Type: Desktop self built

GPU: MSI R9 380 4GB

CPU: i5 4690k at stock

Motherboard: Gigabyte Z97N-Wifi

RAM: 8GB Crucial Ballistix Sport

PSU: Corsair CX600M

Operating System & Version: Windows 10, latest

GPU Drivers: Radeon ReLive 16.12.1

Chipset Drivers: N/A

Background Applications: Steam, Skype, iTunes, Chrome, Core Temp, MSI Afterburner

Description of Problem: It was working fine earlier today but now when I try to load up a game only the GPU frequency goes up or down, the memory clock is reported to be stuck at 150MHz by HWMonitor and Wattman

Troubleshooting: Restarted, nothing. Disabled overclock in MSI afterburner and reset, nothing. tried adjusting Memory clock in Wattman, cant.

[APasz]

I would suggest running memtest86 to check if it's bad ram.

[Drak3]

Revert drivers. Check if issue is fixed.

If yes:

1. Create system image.
2. Try a fresh install of ReLive drivers.
   1. If problem returns, revert and do not use new drivers.
   2. If problem doesn't return, then it was just a bad install.

If no, try the following (in any order):

• Reseat the card.
• Test card in another build (probably a friend's)
• Swapping the BIOS if the card has a dualBIOS switch
• Panic

 

[DrMacintosh]

1 minute ago, Drak3 said:

Revert drivers. Check if issue is fixed.

If yes:

1. Create system image.
2. Try a fresh install of ReLive drivers.
   1. If problem returns, revert and do not use new drivers.
   2. If problem doesn't return, then it was just a bad install.

If no, try the following (in any order):

• Reseat the card.
• Test card in another build (probably a friend's)
• Swapping the BIOS if the card has a dualBIOS switch
• Panic

 

I am reverting to the latest old WHQL drivers now. 

[Godlygamer23]

5 minutes ago, APasz said:

I would suggest running memtest86 to check if it's bad ram.

This is occurring on the GPU which memtest86 cannot check.

[DrMacintosh]

4 minutes ago, Drak3 said:

Revert drivers. Check if issue is fixed.

If yes:

1. Create system image.
2. Try a fresh install of ReLive drivers.
   1. If problem returns, revert and do not use new drivers.
   2. If problem doesn't return, then it was just a bad install.

If no, try the following (in any order):

• Reseat the card.
• Test card in another build (probably a friend's)
• Swapping the BIOS if the card has a dualBIOS switch
• Panic

 

This seems to have fixed it. Ran a DDU session and installed 16.10.something. FPS and core clocks are back to normal and my 380 is not dead! Although I kinda wish it was.......the RX 480 is one sexy card at one sexy price......

 

I'll have to wait for the bugs to be worked out of the GCN 2.0 cards and not install updates on day 1 ?

[APasz]

1 minute ago, Godlygamer23 said:

This is occurring on the GPU which memtest86 cannot check.

My bad, misread.

[Godlygamer23]

1 minute ago, DrMacintosh said:

This seems to have fixed it. Ran a DDU session and installed 16.10.something. FPS and core clocks are back to normal and my 380 is not dead! Although I kinda wish it was.......the RX 480 is one sexy card at one sexy price......

 

I'll have to wait for the bugs to be worked out of the GCN 2.0 cards and not install updates on day 1 ?

I'm curious if a fresh installation of the ReLive drivers would've fixed it. Would you be willing to test it?

[Drak3]

Just now, DrMacintosh said:

This seems to have fixed it. Ran a DDU session and installed 16.10.something. FPS and core clocks are back to normal and my 380 is not dead! Although I kinda wish it was.......the RX 480 is one sexy card at one sexy price......

 

I'll have to wait for the bugs to be worked out of the GCN 2.0 cards and not install updates on day 1 ?

Damn, not once has anyone tried panicking, and no one wants to be a part of my heaps of dead monkeys! I can't do science without heaps!

 

[DrMacintosh]

Just now, Godlygamer23 said:

I'm curious if a fresh installation of the ReLive drivers would've fixed it. Would you be willing to test it?

Yes, I really did like the ReLive Update. I think I can point to exactly where the issue with the memory clock occurred and it was during a long YouTube session with ReLive wanting to do something when entering full screen. 

 

Maybe I should email that to AMD? ?

[Godlygamer23]

4 minutes ago, DrMacintosh said:

Yes, I really did like the ReLive Update. I think I can point to exactly where the issue with the memory clock occurred and it was during a long YouTube session with ReLive wanting to do something when entering full screen. 

 

Maybe I should email that to AMD? ?

The more data they have, the better.

[Carclis]

I think this is an issue with multi-monitor setups on the ReLive driver.

[DrMacintosh]

1 minute ago, Godlygamer23 said:

The more data they have, the better.

Yeah. I'll stick with 16.10.1 for now. I just think the ReLive update isn't that stable for older cards right now. I bet you it's a mix between Wattman being introduced to older GCN cards as well as ReLive being handled differently on GCN cards as well. 

 

The first time I updated I had to reinstall Windows because Acronis True Image apparently has the authority to just take control over you PC and prevent and ruin driver installs. 

 

My computer stresses me out, and it makes me wish I bought a Mac sometimes, but I still love it ? 

[DrMacintosh]

2 minutes ago, Carclis said:

I think this is an issue with multi-monitor setups on the ReLive driver.

I have 3 displays so this could very well apply to me. 

[xAcid9]

This is a pretty wirespread issue alongside high ping when playing online games with ReLive driver, wait for hotfix and report the problem to them.

[miagisan]

It's a bug with multimonitor setups at the moment. I was overclocking with my r9 290x and the memory speed dropped to 150mhz and couldn't fix it. Used DDU and reinstalled relive driver. Worked fine after.