Crimson Driver - Overlock boot issues

A

a3venom

Gawd
Joined
Mar 3, 2015
Messages
695
As title states, I do a bad OC in any software (Trixx , AB, anything else) with the option "apply OC on boot" checked off and it still never boots up unless i delete driver in DDU.
It has lead me to believe that Crimson is restoring my bad OCs at boot and i never want it to.

Is there a fix to this?

This never happens on older driver verions, i checked a couple of pre-crimson versions today and they didn't do this.

It is really annoying to overclock because of this as i have to reinstall drivers every time....
 
Check off, as in not checked? Do you have Overdrive enabled? You must have if you think it is the app applying the overclock, so the first thing I would do is check that and disable it by using the reset option.

Hmm, in AB set a 2D profile, stock and leave the 3D blank. Then when you OC for a bench or whatever I assume you're benching. If you crash and reboot, AB will/should auto load the 2D profile which should allow you to logon.
 
Your post is slightly confusing but if i had to guess windows is screwed up some how.I have never heard of having to run DDU after every boot up. What card is this for, and what driver are you using? I would suggest doing the over clock in crimson instead of 3rd party if possible. If this is about memory and or voltages you might consider modding the bios?
 
I up volt / mem as high as I can. I need to have my card always at stock clocks when it boots up, the problem is that even before the user welcome screen, it goes black.
The older drivers don't do this but all versions of crimson based ones do, i have tested this.

even if MSI AB is uninstalled it will do the same shit, this screen goes black even before any program has a chance to start. I never see the logon screen.
r9 290
 
It's AMD's shit software crimson. Numerous issues like this on the AMD forums - solution seems to be install older drivers with catalyst control center and use "have disk" to install just the new drivers without their bloat.

Crimson will re-apply your memory and freq OC everytime you boot, but not the voltage which will guarantee a black screen if you go too high on your mem clocks.

I can't believe they haven't fixed this yet. Definitely my last AMD card, fuck this is infuriating.
 
a3venom said:
It's AMD's shit software crimson. Numerous issues like this on the AMD forums - solution seems to be install older drivers with catalyst control center and use "have disk" to install just the new drivers without their bloat.

Crimson will re-apply your memory and freq OC everytime you boot, but not the voltage which will guarantee a black screen if you go too high on your mem clocks.

I can't believe they haven't fixed this yet. Definitely my last AMD card, fuck this is infuriating.
Click to expand...

I assume it does this w/o you ever enabling Overdrive? If so, that is whacked. It shouldn't be doing that, not it's job since it's not enabled. This would be a logistics error on the driver.
 
thesmokingman said:
I assume it does this w/o you ever enabling Overdrive? If so, that is whacked. It shouldn't be doing that, not it's job since it's not enabled. This would be a logistics error on the driver.
Click to expand...

After a lot of installs where i never even opened the crimson control panel. Even my stable OCs will crash because it will never add the voltage on boot but make my mem 1500
 
why dont you just mod the bios voltage and reflash it so it always used the correct voltage? then you wouldnt even need a third party gpu app. Or is that not possible on 290's?
 
primetime said:
why dont you just mod the bios voltage and reflash it so it always used the correct voltage? then you wouldnt even need a third party gpu app. Or is that not possible on 290's?
Click to expand...

^+1 totally agree with this.. anyone wanting for an "OC apply on reboot" just need to flash BIOS it's a set and forget procedure..
 
I had this same problem over the weekend. I was just trying to avoid reprojection kicking in with my Vive and instead fell down a 4 hour rabbit hole of uninstalling and reinstalling my drivers 3 times in a row because AMD wrote software that allows the user to overclock but has no idea what to do if that OC is unstable. After reading the forums I can't understand why this bug has existed across multiple Crimson versions when it exists due only to lack of actual testing.
 
If I'm understanding you correctly, your memory OC is stuck at 1500? I've had that happen before--the solution was to set it to the minimum in Crimson, apply, and then set it to defaults.
Edit: Or is it stable at 1500, it's just that Crimson doesn't apply the voltage you set?
 
a3venom said:
As title states, I do a bad OC in any software (Trixx , AB, anything else) with the option "apply OC on boot" checked off and it still never boots up unless i delete driver in DDU.
It has lead me to believe that Crimson is restoring my bad OCs at boot and i never want it to.

Is there a fix to this?

This never happens on older driver verions, i checked a couple of pre-crimson versions today and they didn't do this.

It is really annoying to overclock because of this as i have to reinstall drivers every time....
Click to expand...

Psst, looks like this was fixed in the latest catalyst release.
 
Radeon Software Crimson Edition 16.7.3 Release Notes

Fixed Issues

  • Overwatch™ may experience an application crash on some Radeon™ RX 480 configurations when using AMD Crossfire mode.
  • Vulkan™ information in the Radeon Settings software information tab may display an incorrect version.
  • Radeon WattMan may retain settings of an overclock after it has failed. If you have failed an overclock with a system hang or reboot.
  • Hitman™ may experience graphical corruption when the game is set to use DirectX®12 API and using zoom with weapons.
  • Total War™: Warhammer may experience minor graphical corruption in some map textures on AMD Radeon R9 380.
  • Flickering may be observed in Rise of the Tomb Raider™ on some AMD Crossfire configurations using the DirectX®11 API.
  • Changing settings in Dragon Age Inquisition™ with the Mantle API may result in an application crash or driver recovery.
  • DiRT™ Rally may experience flickering terrain in some races when the advanced blending option is enabled in the games settings page.
  • Display may exhibit a minor flicker on Radeon RX 480 when Freesync is enabled on a games launch or exit.
  • Shadows may experience rendering issues in DOTA2™ when using the Vulkan™ API.
  • Textures may experience holes or gaps in DOOM™ when using the OpenGL API and three display AMD Eyefinity configurations.
  • Need for Speed™ may experience flickering on some light sources in AMD Crossfire mode.
  • Performing a task switch with two cloned displays during full screen gaming may cause flickering on the extended display.
Click to expand...
 
You must log in or register to reply here.
Back
Top