AMD Overdrive Bluescreen

Anyone else gotten a bluescreen when running AMD Overdrive?

I just downloaded it a bit ago to play with and when I ran it the first time I immediately got a bluescreen. Then, when my computer booted again I got another bluescreen immediately after entering Windows, presumably when one of Overdrive's services started. I had to boot in safe mode and remove the installation folder to break the cycle.

 

Same encounter here,bro.i don't think AMD overdrive is meant for our chipset.

 

mmm could be becouse of Ulps...


install it back, don't do any modification at this point. Instead open your registry (regedit). Find "EnableUlps" as i wrote it without quotes and watch out becouse is UL and not Ui. There are several entryies for EnableUlps on the registry, you must set all of them to 0 (zero). Once you are done, reboot and check if OD give you any other trouble. i don't know if is needed with OD, but it is definetly worth a try

 

What is ulps?

 

If set to 1 it will crash the pc at every overclock attempt, it is related powerplay function and when doing oc with rivatuner for example it is required to set EnableUlps to 0. That's why i'm sugeting this solution.

 

Hmmm,at the moment i am using Trixx,but it randomly causes system freeze,that's why i am considering alternative OC program like AMD overdrive,although in Trixx ULPS is disabled,so we still had to go into registry & manually tweak ULPS?
First time start up AMD overdrive causes BSOD 3 times,nearly enough to stop my heart...

 

AMD Overdrive (as opposed to Catalyst Overdrive) is for AMD processors and chipsets, not Intel systems. See AMD OverDrive? System Requirements. It won't work in an R3.

 

Ah, that makes sense. Where is Catalyst/ATI Overdrive then? I have the full Catalyst 11.7 from AMD's site and I don't see Overdrive or any overclocking tools in the CCC.

 

Open Regedit and navigate to HKEY_CURRENT_USER\Software\ATI\ACE\Settings\Graphics\OverDrive2. Change the value of the key "Accessible" from "Nobody" to "All". Proceed to Overdrive3 and Overdrive 5 in the same section and apply the same change. After reboot, open CCC. There should be a new Tab called Performance, which contains Overdrive. You have to click on the lock icon and agree to various warnings to launch OD and click on Enable to make it active. This works in most cases with ATI/AMD reference drivers. If the OD settings are not included in the Registry, you may need to reflash your vbios and then reinstall Cat 11.7. You'll want to modify your vbios and reflash in any event to increase the o/c limits to more useful levels.

 

cool revelator just did it but why they only let me go 740/1000 max????
i didnt max it out yet just little by little. i set it to 700/900 lol

 

Congratulations, greatest335i. Those 740/1000 o/c limits are set in the stock 6990M vbios. Just use RBE to edit the vbios to increase the limits by navigating to the Additional Features tab or screen and using the sliders in the lower left quadrant to set the desired levels. I find 900/1200 works well for the 6990M.

​

 

o wow 49 temp????? im getting like 59-60 temp...

 

Hmmm,followed your regedit instructions,but CCC is still missing the Performance tab.Should reinstall CCC?

 

I'm not sure, Shinob!. Were the Registry entries present on your computer? With my 6970M I had to edit the vbios to make it OD capable and to cause the installation routine to make the OD entries, whereas the 6990M vbios came that way. If you would post a copy of your vbios, I'll take a look. (For this purpose, load GPU-Z, click on the small icon located adjacent to the "BIOS Version" box, select save to file, name it "testbios.rom" and save to the desktop. Change the extension to .txt and post here as an attachment. Also please include a screenshot of GPU-Z with the HD 6900 Series card selected in the box at the bottom to allow confirmation of the vbios used.)

 

The registry entries were indeed there,& all have been changed to "All".Currently I'm using Trixx to OC my card but it always have a 50/50 chance of causing system freeze,that is why i am looking for an alternative OCing program.i tried to load GPU-Z for the info you requested,but it also froze up my system like Trixx,then BSOD twice.Seems like I'm stuck a program that behaves like a russian roulette,really appreciate the help though,thanks.

 

Sorry. I had that same problem with Trixx for a time, but a different version restored stability. Attached is a Dell 6970M vbios using the stock settings (680/900/1.1v), but modified to enable OD and set o/c limits to 900/1200, if you want to use it. (Change the extension from .txt to .rom to flash.)

View attachment 69211

 

So I found some interesting behaviors after enabling Overdrive and flashing my vbios.

I've had PowerPlay off since my computer is in desktop mode right now. There were no ill effects of this previously. Anyways, after the BIOS flash I go to run a benchmark an overclock setting I've used before (but this time via Overdrive) and I notice a little bit in that the fan isn't running and the GPU is getting rather hot. I Alt+F4 out and reset Overdrive to stock settings and try again. Now, not only is the fan still not running, but the GPU clocks won't increase from their minimum of 100/150. The first 3DMark11 test is a slideshow so I alt+F4 out again.

I figured the flash did it so I flashed back to the stock vBIOS. However, the issue persisted even after I did that, which I thought was strange. After trying a number of things, I found that enabling PowerPlay immediately fixed the problem, enabling the GPU fan and allowing it to clock up.

I flashed back to the modded vBIOS and all is still well, but I still thought my experience was a bit odd.

Anyone else seen this?

 

Had not experimented with PowerPlay in the R3. I had the same experience as you; with PP disabled, the 6990M gets locked at 100/150. Interesting. Same thing happens with the 6970M in my M15x. With the older 5850M in the M15x, disabling PP resulted in the clocks being locked at 300/400.

 

Oh, and speaking of fans, we really need a fan control utility for the R3.

I tried hwinfo32/64 and while I could manually set the fans, they didn't consistently run within applications, and seemed to completely suppress the automatic default fan settings even when you tell it not to (to the point where I had to re-flash my system BIOS to get fan function). Also, I wasn't convinced that the application was controlling both fans as it claimed. There were times that the GPU fan was going full blast but then the CPU got hot and its fan was obviously not going.

 

Yes, we do. The fans on the R3 are somewhere between erratic and whacked and are responsible for the high idle and operating temps sometimes seen. I've been using HWiNFO64. It doesn't work nearly as well or seamlessly as it does with the M15x, but it beats the stock scheme and keeps things much cooler. I think Martin is still trying to discover the secrets of the R3's EC and sensor control, but isn't there yet.

 

Its ok,Rev,really appreciate you go through the trouble for the vbios.Sticking with Trixx for the time being & hoping they solve the stability issues in future updates.As for the temps,i knew something was wrong when idle temps constantly hover at high 50s to low 60s despite repasting numerous times using different paste & methods.But at least max temps do not go beyond 76 degrees,no complaints here.

 

Also try elevating the back of the R3 slightly (i.e., thin book). The improved air circulation will usually result in a noticeable reduction in temps (5-8C).

 

I use a Zalman NC2000 cooler which elevates the rear a bit and also circulates cool air around under the laptop. It seems to work well, as I notice a substantial increase in temps when I turn it off.

 

Guys, i hae the 6990M as well....and have enablled the overdrive options in REGEDIT to all....still no panel?

BIOS Version is 013.012.000.012.040739

 

All good advice you are getting from this experienced team. In case you (or any lurkers out there) are still curious... Ultra Low Power State (part of PowerPlay). Not sure you had an answer to that question.