Low FPS in all games until I restart

[Beardactal]

Hi I've been having problems with my games in the past few weeks. Every time I come back from school or work and wake my computer up from sleep mode, the games that I launch will always have really low FPS until I cold boot my computer. This has been tested on World of Tanks and The Witcher 3 (15 - 20 FPS on lowest settings even). However, they work really well after I restart my computer (60-120 on World of Tanks and 60+ on the Witcher 3 both on max settings). Here are my specs:

GPU: Double Dissipation R9 290 4GB
CPU: i7 4770k @ 3.5Ghz
OS: Windows 10 64-bit
RAM: 16GB of DDR3
Monitor: 144Hz ASUS 1080p
Motherboard: Gigabyte GA-Z97X-SLI LGA 1150 Z97 2-Way SLI UEFI DualBIOS ATX Motherboard

Latest relive driver installed for GPU

EDIT: I believe the problem has to do with my motherboard which is the Gigabyte GA-Z97. I've read that it has had a history of BIOS problems associated with booting with the wrong settings or something. Can anyone give me more insight on this? By the way, I've tried switching the PCI-E setting from auto to GEN-2 but it does not work.

Thanks

EDIT 2: I fixed it. Solution in the comments.

 

[N3rdR4ge]

this sounds like a software issue. have you tried a clean boot or windows reinstall?

clean boot:
https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

 

[Beardactal]

I actually figured out why I was having this issue. For some reason the Dec - Jan iterations of AMD's relive drivers weren't working right and so every time my computer went to sleep and then turned on again, it would soft lock my R9 290's core clock to 150 MHz. In response, I completely removed whatever driver I had (some January version) and replaced it with an old November 2016 driver and now it works flawlessly. This was a raging topic on some forums regarding the newer AMD relive drivers. I am not sure if they have been hot fixed yet, but for now I'm sticking with my trusty November driver

All in all, if anyone else has trouble with this 150 MHz core clock lock problem, try to roll back your driver to an earlier version. Thanks for the help everyone.