amd relive driver

[Skipping-Bear]

when i update my driver both by clock and memory clock is cut down doesnt go any higher than 300mhz for both of them i rolled back driver and i have to clockblocker to keep it at the the speeds i want them at i cant even oc the card when its stuck at 300mhz im not sure whats going on with this was wondering can anyone help me with this or if its a bug in re live driver

 

[renz496]

system spec please?

 

[Skipping-Bear]

system spec please?

can no one see my system specs in the lower right corner?


anyway here it is


Intel i7 6700k 4.6ghz / Corsair vengeance 16gb ddr4 3000mhz / Gigabyte G1 R9 390 8gb / Viewsonic 22 inch freesync / ASUS Z170 Pro Gaming / Corsair tx750w v2 / Deepcool Tesseract SW /

 

[renz496]

well some people did have different system than the one they put on their sig. so i'm just asking to be sure.

anyway does the problem only happen with relive? older drivers working for you?

 

[Skipping-Bear]

well some people did have different system than the one they put on their sig. so i'm just asking to be sure.

anyway does the problem only happen with relive? older drivers working for you?

if i dont use clockblocker on the older driver im using now (16.11.2) then my core clock with stay at 300mhz but my mem clock will oc but my core clock just stays there so i use clock blocker then my core clock goes to what i oc'd it to even when i use default settings on my gpu without clock blocker it still stuck at 300mhz i think this started after i tried to play the new tomb raider game

 

[renz496]

have you tried doing clean driver install using DDU? i think this clock issue starts with crimson drivers. try doing clean driver install using DDU first. if the problem still persist try using pre-crimson drivers for your 390.

 

[Skipping-Bear]

have you tried doing clean driver install using DDU? i think this clock issue starts with crimson drivers. try doing clean driver install using DDU first. if the problem still persist try using pre-crimson drivers for your 390.

yes i have done that with ddu also did the safe mode uninstall of the drivers

 

[renz496]

so there is still clock issue even using non-crimson driver?

 

[Skipping-Bear]

so there is still clock issue even using non-crimson driver?

the driver i use that i have to use clock blocker is 16.11.2 and that way clock blocker keeps the core clock and mem clock to whtai set it at on msi after burner but clock blocker doesnt work on the new relive driver the core clock sites at 300mhz and the mem clock sits at 150mhz ive tried reinstalling everything but once i install the relive driver it makes it so i cant go back to the previous driver i have to use systme restore in order to go back to 16.11.2 driver

 

[renz496]

why can't you install older driver manually?

 

[Skipping-Bear]

why can't you install older driver manually?

the problem isnt about the 16.11.2 driver its with the new relive driver 16.12.1 WHEN I install the new relive driver my clock speeds are stuck. core clock at 300mhz and the mem stuck at 150mhz some times the core clock will go to 400mhz but then it goes right back down to 300mhz i thought that it just might be reading it wrong and tried to start a game up and that it wasnt reading the sensors wrong the core and mem speeds are stuck. i really want the relive driver cause of the new relive feature that you can do streaming and local recording. and now if i install the relive driver it messes something up cause i will uninstall the relive driver with ddu in safe mode then go back to try and reinstall the 16.11.2 driver and it will just install amd catalyst and not the driver and at the end of the installation it says that it was not able to install that driver.

 

[renz496]

have you tried the latest driver that just release yesterday?

 

[Skipping-Bear]

have you tried the latest driver that just release yesterday?

yep does the same thing except the mem clock will do to what i set iut at but the core clock is still stuck at 300mhz

 

[renz496]

then you probably need to wait for another driver update.

 

[Skipping-Bear]

then you probably need to wait for another driver update.

Thanks for trying to help anyway much obliged. i even tried the amd clean uninstall utility and it still did work the core and mem clocks are stuck downlcocked tried both 16.12.1 and 16.12.2