Get your Catalyst 10.7 (non-WHQL) here

no more problems with flicker or other issues???? - god i cant quite believe this....its maybe the best news ive had all year......just hope its true....im praying it is so....

 

i still can't manage to fix the sleep issue, can someone elaborate on the methods used, and how do i remove all the registry stuff related to ati, full format is not an option for me

 

Great drivers! I never let my system go to sleep anyway and I set the turn display off to never and enabled the blank screen screen saver instead and it wakes the screen saver fine.

 

Well, Joker is responsible for letting Dell know of the problems or should I say letting AW know of the problems. He also made a great thread with the steps to take to install such driver when it was complicated.

Yeah he did much more than just post a driver... If it was not for him the 10.7 release might not actually work on the M17X R2 5870CF.....

 

Disabing power play was suggested by bat boy. Cc cleaner or driver sweeper can be used to remove anything thats left over. Just make sure it's only ati stuff being removed. The Programs should be run after uninstalling the radeon 5800 series devices in device manager * and * deleting the drivers. Restart after that, at which,point windows should load the standard VGA adapter drivers (it will actually be called that) run driver sweeper or cc clean, install new drivers, reboot again.

I find that incredibly hard To believe seeing as Dell has little influence over amd driver releases. As well as considering there are still problems beyond the ones I've described, such as no cf support in at least 3 games I can think of off the top of my head. All of which are huge title releases, and two of which worked just fine in 4870 or 280 crossfire/sli. Saying he had a direct hand in the functionality of 10.7 and the m17x is redicilous. He can submit the issues to his contact in dell and they can submit the problems to amd, without anything to say that they were looked over at specifically and fixed. We might as well say he's helping dell make a r3 too while we're at it. He's got connections, and has certinally helped the community his fair share but that's giving him way too much credit.

 

I presume were talking about Joker here, give the man a break...he has probably helped out alot already at no cost to himself ....people in glass houses shouldnt throw stones in my opinion....

 

I'm sorry, it's how I calm down and relax. rofl.
Reinstalling windows *again* going to try a few different things, hopefully they work...

 

Ha ha ha, well im calming down right now with a beer....works for me....i hope you get yours working properly, i havent even tried....im just waiting on what othher people report being a noob.

Goddammmit....every time i post on hhere, see its happened again.....eveytime i type h.....it does two h's, well not every time...but often.....grrrrrrrr

 

Tried both official and beta 10.7. Completely removed the drivers (first uninstall then safe mode, drive sweeper, CCleaner) the same think. Sleep or turning the screen off makes the system halt.

 

You're just installing it wrong

 

Then show me the correct way (screenshots are welcome)

 

I want to know how then.
Edit: Nevermind, got it.

 

I was playing on everyone else telling me that I was installing them wrong after following the exact same procedure. Just did another windows install and the issue still exists, system just stops responding after wakeup.the battery issue is still there as well, and now I need to uninstall the drivers again and just stick with 10.5s since again, the computer won't even boot after trying the battery now.

 

Works fine, no sleep problems here

 

I didn't see much if any improvement for benchmarking with these drivers. I think when you get in to the higher clocks, it's more about cooling and the GPU itself. On that note, it's nice to not have to use the rivatuner/furmark trick to get things in full screen, and they bench higher then the dell drivers, so to me they are a win win. I installed the betas and downloaded the officials, but those will be installed tommorrow.

As far as the sleep issue, i can niether confirm nor deny, I didn't mess with it that much. But every other driver had those issues so theres no sense in rolling back. I'm not so sure it's a driver issue either.

 

fine, but I demand a sacrafice or you shall not escape this thread unscathed!

I demand, a shurbbery!
Something nice, but not too expensive
Or else:

 

There. Though, now you are longer a knight who says ni


What does non-WHQL mean?

 

Lozz if we are installing it wrong PLEASE elaborate with precise detail because i tried what you suggested and my computer still has the sleep problem, if Lozz or anyone can help please give me the exact steps taken to get perfectly working 10.7s, id really appreciate it. I tried uninstalling my drivers from device manager, from the at install manager, ran driver sweeper, ran cc cleaner and then installed 10.7 and the problem is still here so to anyone who can help please post DETAILED steps in the exact order you have used, thanks.

 

The system does lock up in standby/sleep mode for me as well (had that with Dell 10.5 too so I always disabled it). I'm not having any problems on battery though. Gflyer is not having any issues with his install so what we need to do is try to find what exactly is causing this problem. The first step I'd suggest is to look at the event viewer logs (start menu-->right click on computer-->manage-->event viewer) and see what may be causing problems. A brief look at mine showed the OSD program was creating problems.

 

OK guys I fixed it
On the power plan under the PCI Express/Link State Power Management, change it into moderate power savings

 

Do I download the software suite or the control center?

 

of course you figure this out after I have 10.5's back in lol

 

Oh well, nust more time to uninstall, reinstall and hhey bpresto, bob should be your uncle???

Sory for the lame typing, i am celebrating 10.7 with some beers........

 

negative on this helping me.

;>_> stop typing, you'll be upset when you barf all over your 2500 pound laptop..

 

no chance of that, i have a bin placed in a handy position....mind you, barfing all over it at some times has seemed a good option...accidental damage and all that......

 

Mine was all ready set to Moderate and did not fix.

 

all 3 power profiles should have different settings. High performance is off by default, balanced is moderate, and battery/low power is maximum.

 

Ok for the problem Lozz reported of the system locking up on battery, I was getting the same issue. I reinstalled the 10.5 driver, uninstalled it and then installed 10.7. The reason I did that is because after I pulled the AC plug with the 10.7 WHQL, the system kept BSOD'ing on windows start.

To solve it..<post edited>.

Edit: See the first page for a workaround.

 

yes I changed my High Performance to Moderate but so far no difference.

Thanks.

 

Well, 10.7 went on well for me (after the workaround=true part...that is). No issues as far as I can tell so far. 3DMark scores didn't improve, but didn't go down either so I'll take that as a good sign. Still have the issue with the black screen and only the cursor showing when mine goes to sleep, but I've become very adept at putting the lid back down, bringing it up, and then pressing the power button to bring it out of sleep so it's all good

Now the real test comes tonight with Starcraft II

 

I know I set USB devices to wake the computer up from sleep mode in the BIOS trying to fix the sleep issue, but afaik I haven't changed anything else besides setting the HDD's to ACHI mode. I'll go look see again, however I will note that with crossfire disabled on 10.7's I didn't have the battery problem.

 

im taking it this is all better news than previous releases tho....it may have some other adverse effects but on the whole, is a better release....curing many problems? - gonna let you guys do the deciphering and just watch as well, i just about know how to type and thats not very well at times....LOL

 

that's a negative fix for me. typing in safe mode now

 

May or may not be related:

When I tried to use the 10.6 drivers I reported some problems that no one responded to - ill post them again here because they sound the same.

Of note:
When changing the resolution or plugging in an external monitor via displayport or hdmi, the system gets a black screen and HARD LOCKS.

When setting rivatuner to automatically set clock speed on startup, it causes a BSOD reboot loop.

Now, for the people having sleep troubles - it sounds to me that the internal display switches off JUST BEFORE sleep, and then causes a hard lock.
Same thing happens on the 10.6 if you try switch off the screen or do anything with an external screen.

I would like people having issues to plug in a second display and see if it locks up too.

I am almost certain its got something to do with the display output stuff in the video bios.

My theory is that when dell got these cards, they changed stuff around with the video bios concerning display control. When running the official drivers, accessing this stuff is going to the wrong address or somesuch and causing a hard lock.

We can determine if I am right if someone tries to plug in a displayport or hdmi display and see if there is a lockup.

Perhaps a possible fix is to install a generic video bios for the hd5870m that we know works with the cat 10.6/7 with all features?

-Ash

 

So right now we have two major bugs with this driver:

Major issues:

1. System halts when the AC plug is pulled and run on battery and then sends the system into either a BSOD loop or lockup during Windows 7 load. The only way to get around that after this happens is to either run in safe mode and uninstall the driver or press F8 during boot and choose the last known working configuration.

2. The system locks up after going into sleep mode.

Other minor issues:

1. Napoleon Total War/Empire Total War loading time takes too long in Crossfire mode.


What 10.7's fix:

1. Wavy/flickering horizontal lines that were present in all prior drivers.
2. Benchmarking performance is better than Dell 10.5 drivers.
3. Rivatuner + furmark are no longer needed to use a reference driver.


If we can solve the battery lockup bug, then I'd say the drivers are good for the time being. I'll still stick with them despite the two major bugs because the flickering is something I dislike very much.



Error log for the sleep mode:

Code:

 System

  - Provider

   [ Name]  Microsoft-Windows-Kernel-Power
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

   EventID 41

   Version 2

   Level 1

   Task 63

   Opcode 0

   Keywords 0x8000000000000002

  - TimeCreated

   [ SystemTime]  2010-07-26T23:48:17.211208300Z

   EventRecordID 50116

   Correlation

  - Execution

   [ ProcessID]  4
   [ ThreadID]  8

   Channel System

   Computer Brian-PC

  - Security

   [ UserID]  S-1-5-18


- EventData

  BugcheckCode 0
  BugcheckParameter1 0x0
  BugcheckParameter2 0x0
  BugcheckParameter3 0x0
  BugcheckParameter4 0x0
  SleepInProgress true
  PowerButtonTimestamp 129246616473864560

Each time the system BSOD's and creates a memory dump file (located in C:\Windows\Memory.DMP) it contains the information needed to identify what caused it. Microsoft has some debugging tools that analyze the DMP file: Driver Developer Resources: Debugging Tools for Windows I'm installing it right now, if we can compare error reports it may help figure out what's causing it. Even if we can't, submitting the error logs to Dell and AMD would be useful in fixing this issue in the next release.


What the memory dump file shows when the system is run on battery (AC adapter unplugged):

 

The game is napoleon Total War, and as well as Empire Total war. They're both the same game engine, so it's not surprising both experience the issue.
FFXIV Benchmark also does not work in Crossfire Mode, but it's still 2 months from release, so no biggie.

 

I run off hdmi sometimes. I just plunged it and unplugged it with no issue

 

claxdog what system bios you on?

 

Are you running a hD5870 crossfire setup with 10.7? Thats who I am directing the question to.

-Ash

 

sorry, no. there is no specs in your sig so I didnt know. my bad.I am on A06

 

Thanks for the info

 

Well, I guess we need to report these errors asap as to have them fixed with 10.8...

It seems these things take forever to work.

Against thanks Joker for all your help and the reporting you do to AW.

Speaking of this we have not seen many AW people on these forums lately.

 

Lol they are too busy trying to defy the laws of physic to get dual 480m's in the M17xR2 chassis.

-Ash

 

LOL

10 Char

 

they're all off hording their preciousssssessssss

 

NM I redownloaded the drivers and they worked this time.

/shrug

 

Well guess what: I turned on Rivatuner + furmark, set the clocks to 700/1000 and then pulled the AC plug. It's been 15 minutes so far and no lock up. SOO I guess for now that's a temporary solution to the system locking up when the AC adapter is plugged in. If anyone plans to do this, make sure you turn off Rivatuner OC'ing after plugging it back in if you plan to restart the system else you might get stuck in a nasty BSOD loop. Maybe some vbios tweaking could help...


Edit: Can someone test something for me. Disable Crossfire while plugged in, then once it's disabled, unplug the AC adapter and see if the system locks up on battery. If not then that could be another temporary band aid. Confirmed it works.

I've also modified the clocks + voltage on some of the powerplay clocks + set the power manager settings for ATi powerplay for max performance on battery and it doesn't lock up (no rivatuner needed). However, the problem is when the system is restarted it shuts off right away because of the higher clocks. Going to keep testing with clock + voltage settings.

 

Lozz lol again with the installing wrong, PLEASE explain the right way, for everyone with bfc2 and other game performance issues here is the fix:
Drivers & Support | GAME.AMD.COM
now someone please help me with the sleep issue and these will become perfect drivers.

 

This reminds me of the powerplay issues with the HD4870x2 cards.

We ended up changing the powerplay profiles + voltages to fix it. Maybe its worth looking into how the HD4870x2 fix was done and adapt it?

-Ash

EDIT:

Im gonna try my hand at some vido bios editing again (its like riding a bike, right?).

Can someone do a backup of their bios and attach it here, and also if anyone knows where I can get a generic HD5870m bios to look at it would be helpful.

-Ash

EDIT2:

Hmm... OK, I think I know whats going on. (if the bios on the m17x wiki is from an m17x hd5870m)

Dell has modified the Powerplay tables inside the VBIOS, in particular the values for certain references... and well, its all shuffled up.
To prevent issues, dell has changed the vendor ID themselves to an unknown value to prevent you from using standard drivers.

This is because when the OFFICIAL drivers try and do powerplay... yeah, they will be loading powerplay values from the wrong tables. Wrong clockspeeds and wrong voltages. This is most probably causing the lockups.

I just need a vbios from an OEM or stock HD5870m - then I can match the dell vendor ID and powerplay tables with the official ones, and probably fix (most) of the issues.

-Ash