|
|||||||
 |
|
|
LinkBack (544) | Thread Tools |
Jun 15, 2007, 10:26 AM
|
 #61
|
|
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17  |
Quote:
Not your fault, everyone who needs their problem fixed seem to be relying on information passed on from others since ATI won't answer to it... Problem is, there are some out there that will purposely post their bogus "fix", that those with less experience and knowledge about the different settings and options within the OS, will try, and ultimately make things worse, not knowing any better... Hopefully a REAL answer will eventually be available...
__________________
 Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
Jun 26, 2007, 01:54 AM
|
#62 |
|
DriverHeaven Newbie
Join Date: Apr 2007
Posts: 15
Rep Power: 0 |
Well that does it. I've waited long enough. Catalyst 7.6 is out, and still no fix. Video still locks up forcing a hard reboot, or the video crashes and restarts, just 45 seconds into watching tv. I've had it. According to ATI, they've known about this problem since April. We've told them what the problem is, and they've acknowledged it. However, they still feel it's more important to get out 16% or more improvement when you play HL2:Episode 1 with HDR enabled and in Crossfire config with 2 of the most expensive cards on the market. To hell with the rest of the community. We want more FPS, better detail in water, and their systems to cost $5,000 grand. Nevermind the fact that MOST of their buyers are people who HAVEN'T bought new cards. And with poor ass drivers, nobody WANTS to buy a new card anyway. It's just burning money. I was going to wait for 2 more revisions (up to 7.7) but now, there's no way. In the 7.6 documentation, they list what features they're going to fix in 7.7 and 7.8, and our little atikmdag issue is not anywhere on the priority list. Sorry ATI, but I gotta give my money to somebody else.
Features to be worked on Vista 7.7: - Playing a DVD under the Windows Vista operating system using the Windows Media Player may result in the DVD failing to play when switching between display devices using the hot-key function. (who in the hell watches DVD's with Media Player? Don't most people use WinDVD or PowerDVD? And why the hell would anybody be switching display devices while watching a DVD in the first place?) - The desktop shortcut to the Catalyst Control Center may disappear after performing a Windows Anytime Upgrade on some hardware configurations running Vistal. (Ok, thats just sad. Isn't Windows Anytime Upgrade supposed to upgrade the OS from like Home Premium to Ultimate? Who cares if the icon disappears? Don't most people RIGHT-CLICK the desktop, or use the taskbar tray icon by the clock? Just remake the stupid icon if it's that important to you.) Features to be worked on Vista 7.8 - Hot-plugging a CRT to a system running Windows Vista and containing an ATI Radeon X1100/1150 series of product may result in extended desktop mode failing to be applied. (This may be a problem, but I wouldn't know. I always thought 'hotplugging' was unsafe between powered components. So, I've never tried 'hotplugging' anything except for USBs for fear of frying the connectors, the card, the cable, or the monitor itself.) - Enabling Crossfire followed by disconnecting and then reconnecting the CRT display device may result in duplicate video options being seen within the Catalyst Control Center. (whoopdeedoo.. I still feel 'hotplugging' is a bad idea, let alone doing it with a crossfire setup. You gotta be ignorant to think something like this is an important priority.) - Enabling Crossfire followed by setting AA to 14x and AF to 16x may result in the AA showing a setting of 0x level when disabling the Crossfire and unchecking the AA option in the 3D aspect. (ok, um, why would somebody enable crossfire then disable it? And why would having it show a setting of 0x after unchecking the AA option in the first place be an issue?) - Making changes to the color aspect found in the Catalyst Control Center without applying the changes may result in the Reactivate ATI color controls button remaining active after the Catalyst Control Center is closed then relaunched. (again, a STUPID finding by the ATI programmers. If the reactivate button is enabled, the user is supposed to make changes. If they don't, and close the program, nothing was changed. Therefore, the button SHOULD still remain active. Fucking clueless morons.) - Enabling Crossfire followed by setting the Overdrive clocks to their maximum settings may result in Catalyst Control Center failing to accurately report the requested Overdrive values. (ok, this ones deserves being fixed. I don't have crossfire or overdrive functions, but if I did, and wanted to overclock it, this would be something important to have.) As you can see, they really are on the ball with STUPID tweaks. Out of everything announced above, does anything really stand out as being system critical? Wouldn't you think something like our atikmdag issue causing massive system instability be more important? I mean, if it goes unchecked, we're looking at our cards getting fried, not to mention the slots and potentially the motherboard and/or system. I hate seeing ATI do this to their people. Sure, not many people have this problem, but those that do are in serious need of a fix. I'm tired of waiting. Gonna work on building my new PC over the next few weeks, and hopefully won't have any issues like this again. Goodluck all. |
|
|
|
|
Jun 26, 2007, 03:41 AM
|
#63 |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Sadly enough, it would appear that my long time standing with ATI is no more as well.
I've been using ATI cards since the "Mach64" was released, (obviously this was way before the HUGE boom of 3d apps/games etc..) I've owned just about every card ATI has ever offered simply because they were always ROCK SOLID! Was always happy with their support/drivers as well as they never ignored a single support question I may have had, and any problems submitted were answered. Now it just seems that ATI has in fact sold out. No answers to the problems many people are having, only focusing on the newer hardware, even though some of us own cards that were only bought 6 months ago BEFORE the new HD series hit the shelves...  Sad to see ATI go down this road, it will eventually lead to the loss of many loyal customers. Nvidia isn't any better though, they have their problems with drivers, as well as pissing people off by dropping entire lines of support for certain chipsets/cards in vista and only giving those poor people a 'So sorry, nothing we can do" (even though it wouldn't take even a day to get out some reference drivers for the things they decided weren't worth supporting in vista... stupid decisions by stupid people.... ) This is what happens when a generally good solid company, gets bought up by a known cheap, corner-cutting, only out to make a quick buck company. AMD sucks, has sucked, and always will suck. If it weren't for INTEL ALLOWING AMD to clone it's very first cpu's (8086's running at a whopping 4MHZ!..may be to far back for most to remember...  ) and funding them in the early years to do so, AMD would be NOTHING, and look at what they pulled with Intel.... (again, was long ago... most won't remember or even know...) Anyways...Speaks volumes for what will be the end result for ATI... Hansolo77: I don't blame you for not waiting anymore, I've waited since cat ver. 7.2 for a fix, with god only knows how many trouble tickets that will "supposedly" be resolved in the "next" driver release, right, ATI has yet to address the issue... I got rid of my Crossfire card since It was dead from the start, RMA'ed to ATI, came back fine, but unusable due to driver problems, so what was the point of keeping it... now my buddy is pulling his hair out with the problems he has with ATI and their HORRIBLE drivers... I got my money back, that's all I care about...I'm sure there would be more done if the competition was larger, but it only appears to be ATI and Nvidia at the moment for the mainstream, and as long as it stays like that, we are lucky to see anything being done. They are only interested in supporting their "top of the line" cards and the bullshit tweaks because there is nothing or no one forcing them to do otherwise... Interestingly enough, You would think Microsoft, the one who claims to certify the drivers would do something. One might start to think it's a problem with the new driver structure in Vista, but shhhh... don't say that, it will give AMD/ATI another excuse to use and someone else to blame... as usual... P.S. I'm not even going to waste my bandwidth DL'in the ati crap anymore unless the listed fixes include one for the ATIKMDAG problems. I'm currently looking at NV's latest offering of cards, may actually grab one to check out. Seems as though they have issues as well, but nothing like what I'm having with ATI... So I may not need to DL ATI's crap ever again... we'll see
__________________
Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
Jun 26, 2007, 05:34 AM
|
#64 |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Ok, so I had to see if the 7.6's were better or worse...
Waste of bandwidth, as i suspected. Same shit, different day.... ATIKMDAG error if I don't use ATI Tool....  I submitted another ticket with ATI, I also submitted a detailed explaination of how to re-create the problem I'm having... even though i know they won't even bother with it. I doubt I'll hear anything back, or see anything different... BTW, one new thing I noticed since 7.5's, is every now and then I'll get a BSOD for "Unrecoverable hardware error....blah blah blah..video" something like that. never had that before the 7.5's, but it happenes so rarely (that is why i can't remember what it says exactly) that it doesn't bother me. Although it did happen once right in the middle of a hairy battle in C&C 3...  Had to start all over...
__________________
Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
Jun 26, 2007, 07:15 AM
|
#65 |
|
Come on you Spurs!
Join Date: Mar 2003
Posts: 21
Rep Power: 0 |
Can you guys confirm that the Atikmdag error doesn't happen using Ati tool ?. I have not yet tried it myself. Thanks...
|
|
|
|
|
Jun 26, 2007, 09:06 AM
|
#66 |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Only way to know is to try it out for yourself, and let us know how it goes... EVEN though you have the Toxic card, which DOESN'T have the fan, the driver doesn't know it, it just sees it as a x1900xtx.
The ATIKMDAG error is non-exsistant as long as I use ATI Tool (or any other program) to set the fan to 100%. Without it, the error is like clockwork and pops up as soon as the gpu temp starts to increase. (that's when the driver tries to access the fan control and BAM! driver error or lockup) For me, (may not be the same for everyone else) it's definitely a thermal/power control problem with the drivers, I can even duplicate the error using ATI's own Automatic clock config in the overdrive section. If i run it without ATI tool running, as soon as the GPU starts to heat up, I get black screens, followed by the wonderful message saying the ATIKMDAG.SYS stopped responding and has recovered crap... If I run it WITH ATI Tool running, no problems at all, and the same goes for any game, video, etc.... Like I said, I have this problem with my X1900XTX (had it with the X-Fire card too, among much worse problems...) different cards seem to have a different reason for throwing the ATIKMDAG error, or it could be the same problem, I don't have all the cards to test  , but I'm sure it's all related to whatever ATI screwed up with the drivers...:EDIT: I need to correct myself I said as long as ATI Tool is running i don't have problems...that is incorrect, what I should have said is ONCE I run ATI tool and set the fan to 100%, I don't get the error. That means, I can exit out of ATI Tool, because once set, the fan stays at 100%... now why can't ati add this to the drivers?
__________________
Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
Jun 27, 2007, 01:08 AM
|
#67 |
|
DriverHeaven Newbie
Join Date: Apr 2007
Posts: 15
Rep Power: 0 |
My card is the X800Pro, 8x AGP /w 256mb ram. I get the ATIKMdAG error regardless of ATI tool running or not. I do, however, also believe my issues is thermal related. I can recreate the error time and time again by playing a 3D game, or watching a video in Full screen that requires the video card to decompress the signals (ie; Live Tv, DVD's, etc in the MPG2 format). Clearly it's a problem with the card overworking then overheating, and the inability for the drivers to drive the fan correctly to compensate. But like I said, it's the DRIVERS. The hardware works fine. ATI Tool doesn't help either. It might keep the card cool, but even at 100% fanspeed, eventually it gets hot enough to trip the driver and cause it to stop working. It just happens for me within the first 5 minutes of said activities.
I'm working on a new system that is Intel based. I gotta admit though, AMD and ATI combinations have always been rock solid setups for me in the past. I've always used them together and never had any issues until Vista. Something I read in another forum... apparently Microsoft had a set level for Vista logo drivers and hardware before they released Vista. However, like 2 weeks before the official launch, they CHANGED their requirements. Software and hardware companies have been playing catchup ever since. So, ATI had a list of products, designed to Vista specifications set from before. They went out on store shelves, bearing their Vista compatible and Vista ready logos. People bought them, just to have them not work when Vista was finally released due to the change in requirements. I also read that ATI was aware of this change, but decided it was better to release the hardware anyway and upgrade drivers rather than recall the incompatible products. The reason for this, obviously, was for money. However, reports also state that because ATI was aware of this, they are fully prepared to be sued by each and every owner of one of these new cards. Their answer/solution? They'll counter sue Microsoft for lost wages due to their increase in requirements prior to release after having provided a set level before hand. So, if you got one of these cards, and still have problems like this, just threaten ATI with a lawsuit, get your money back, and buy a turkey instead. Wait until ATI or nVidia comes out with a new Vista card that fully meets the latest requirements and buy that. |
|
|
|
|
Jun 27, 2007, 04:30 AM
|
#68 | |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
If your card is heating up even with the fan @100%, then I would look into the possibility the heatsink is not making good contact. I know when i first bought the X1900xtx, first thing I did was rip off the stock cooler and notice the crap job and crap thermal paste that was used.
I redid it with AS5 (carefully) and mounted it back up, I have always had low temps on my card. much lower than I see others getting with a stock cooler... and with the fan @ 100%, fugedaboudit... never heats up (as long as the fan is @ least 25%). Now the regulator section, thats a different story, but I was able to knock off a few C or more by redoing the BS job with that sink too... You state a good point though, about the drivers not driving the fan correctly. My gpu can get up to 85c+ BEFORE the fan even attempts to spin up, and when it does, that's when I get the error, which resets the driver, thus preventing the fan from spinning up at all, and allowing the gpu to reach ridiculous temps even @ idle!... Quote:
 at least the turkey will be good for something, and I'd get my money's worth from it! Sue ATI? never happen, regular Joe sixpack and his friends will NEVER have enough money to ever win such a suit, which is sad, as it's just another indicator that money rules our legal system... Just look at the shining example of Paris Hilton getting off so easy for DWI, or as I'd like to put it, DWBAIS (Driving While Being An Intoxicated Skank) if that were some average Joe, the book would be thrown at them, and they would STILL be locked up, with much more time...Anyways, as far as Microsoft is concerned, From what I know, ATI was the main company who were helping Microshaft develop the DX10 platform for vista, so I don't think ATI can use micro-crap's last minute changes as an excuse, seeing they were fully aware of everything since they were an active part of the development, which would obviously include the proper driver structures, no matter what they were changed to... This of course, was BEFORE AMD took over ATI, so what happened since then is anyone's guess...
__________________
Everything and everyone, eventually fade into Oblivion.
Last edited by Th3_VVr41th; Jun 27, 2007 at 04:45 AM. |
|
|
|
|
|
Jul 2, 2007, 07:22 PM
|
#69 |
|
DriverHeaven Newbie
Join Date: Jul 2007
Posts: 8
Rep Power: 0 |
Hey wraith I have been having the ATIKMDAG error(Black screen in the middle of WoW) since I've installed Vista. We actually have some of the same components including motherboard and PSU. I have one gig of Corsair memory and 2 Gigs of Gskill. I noticed that you and a few of the others who have posted in this thread also have Corsair memory.
If I take the Corsair memory out and run the system with just the Gskill I get no ATIKMDAG errors. I was wondering if you or someone else could test this to confirm? Links to memory in my system: Corsair: http://www.newegg.com/Product/Produc...82E16820145566 G.Skill: http://www.newegg.com/Product/Produc...82E16820231098 |
|
|
|
|
Jul 3, 2007, 01:56 PM
|
#70 |
|
DriverHeaven Newbie
Join Date: Apr 2007
Location: Land of Hamlet
Posts: 13
Rep Power: 0 |
On my machine it's usually because of the refresh rate.. I only have it at 60, cuz as soon as I go any higher I get BSOD!
|
|
|
|
|
Jul 3, 2007, 02:37 PM
|
#71 |
|
Come on you Spurs!
Join Date: Mar 2003
Posts: 21
Rep Power: 0 |
I don't have any memory to try, but I have tried running just 1 stick (1Gb) and get the same result. I came across this whilst serching - http://www.microsoft.com/whdc/device...m_timeout.mspx
I don't know if any of you have seen it. It doesn't seem to offer any help though..  Nvidia users are experiencing the same issue. |
|
|
|
|
Jul 4, 2007, 10:26 AM
|
#72 | |
|
DriverHeaven Junior Member
Join Date: Jun 2007
Posts: 47
Rep Power: 0 |
How did you come to the conclusion that this is a system memory issue. It is not, these problems don't happen in XP. It's Vista only which means its a software/driver issue.
I've also had the ATIKMDAG problem in Vista, it doesn't happen all the time but when it does its annoying. I either get away with it and the PC still operates or it has completely frozen. What makes it worse is there is no pattern to it. It happens at random times. Which I also have Corsair ram, 2GB TwinX DDR3500 though. As I said it does not happen in XP. It's like saying a car runs out of fuel, but you think to fix it change the spark plugs. You wont fix it until you fill it with fuel, or something silly like that. Quote:
|
|
|
|
|
|
Jul 4, 2007, 12:02 PM
|
#73 | |
|
DriverHeaven Newbie
Join Date: Jul 2007
Posts: 8
Rep Power: 0 |
Quote:
I did not come to any conclusions I am just raising a couple of questions. I am well aware that this does not happen in XP. Its flawed logic to just group everything into black and white. Its silly to assume that one OS interacts and treats RAM the exact same as another. I was not and am not saying that changing RAM is the solution, I am just trying to see if what I can do is repeatable elsewhere. You seem to be able to tell exactly what the error is and is not maybe you should write to the engineers at ATI and tell them of your findings.Be sure to include some of your hackneyed and stilted analogies. |
|
|
|
|
|
Jul 5, 2007, 08:37 AM
|
#74 |
|
DriverHeaven Newbie
Join Date: Jul 2007
Posts: 4
Rep Power: 0 |
Possibly hardware related???
I purchased two 'identical' Packard Bell iMedia 2579 PCs. They both have this ATI Radeon X1650 graphics card in them. One has the problem and the other doesn't.
1. I have tried every Catalyst driver version going (from the Vista RTM one to 7.2 and up to the recent 7.6) without fixing the problem 2. I have swapped the cards over between the machines, and the other machine then gets the problem. 3. If I downgrade the 'faulty' card to an ATI Radeon X600 everything works fine again. I suspect that there may be some 'dodgy' cards out there in which the problem is manifesting itself as a driver error, when in fact the drivers are fine, as long as the card is a good one. So the next question is, will ATI recognise this as a genuine error and replace all the 'dodgy' cards for us? Dave. |
|
|
|
|
Jul 5, 2007, 08:53 AM
|
#75 |
|
DriverHeaven Newbie
Join Date: Jul 2007
Posts: 4
Rep Power: 0 |
Possibly hardware related???
I bought two 'identical' Packard Bell iMedia 2579 PCs in the same store at the same time back in March. The PC's have a date stamp on the back of 27-Dec-2007 stating made in China. One PC works absolutely fine and the other has this 'display driver error'.
I have tried the RTM Vista driver, the Catalyst 7.2, 7.3, 7.4 and 7.6 version drivers all without any luck. The RTM driver gives an R300 driver error message, whilst the Catalyst drivers give the atikmdag driver error message. So in order to see if I could work out what was going on I swapped over the ATI Radeon X1650 graphics cards between the two machines. The other machine then started having problems and the previously failing one worked fine. This conclusively ruled out anything to do with software configuration, since the software is the same on both machines, and each machine works with the same working card, and doesn't work with the non-working card. Although the error message suggests a fault with the driver, we're all using a driver which essentially works if the card itself is a good one. I deduced from this that there is a batch of cards that have this problem whilst there is another batch which don't. The serial numbers on my two cards are A064600111697 (working) and A064600113152 (not-working). So I guess I'm looking for either PC World, or Packard Bell or ATI to replace the 'faulty' card with one that works properly. Hope this info helps other people. Dave. |
|
|
|
|
Jul 5, 2007, 09:02 AM
|
#76 | |
|
DriverHeaven Junior Member
Join Date: Jun 2007
Posts: 47
Rep Power: 0 |
Quote:
This same problems lies with 2 X1950's, and also tested a long time ago in single configurations. It has also happened on a 9800XT as well as a X850XT. You going to tell me these are all faulty cards?  Considering these problems do not happen under XP with heavy gaming, and Vista has a long way to go in the driver department. |
|
|
|
|
|
Jul 5, 2007, 09:40 AM
|
#77 |
|
DriverHeaven Newbie
Join Date: Jul 2007
Posts: 4
Rep Power: 0 |
Seek a new card!
I agree, it is not necessarily all down to hardware, however it is a combination of hardware and software that has to work correctly together that is required. At present, some cards work with the drivers that are available and some cards don't. I had two cards, one worked fine, the other didn't. The software was identical, same drivers, and same OS (Windows Vista Home Premium) so it must have been down to hardware differences between the two cards.
If you can't get a driver to make the hardware work, get the hardware replaced instead. We've already deduced that it could be related to the fan, and the temperature, but we're going to be waiting forever to get a driver fix, when you can simply get a replacement card instead. I've spoken to my supplier and asked for a replacement card which they've agreed to send. I suggest everyone else asks for one too. Dave. |
|
|
|
|
Jul 12, 2007, 09:06 AM
|
#78 |
|
DriverHeaven Newbie
Join Date: Jul 2007
Posts: 4
Rep Power: 0 |
All fixed now!
After getting a replacement card shipped from my supplier I can confirm that all of my problems have disappeared. I haven't changed the drivers, just swapped the dodgy card for the new one. Both are ATI Radeon X1650s and my days of not being able to play Guild Wars and Vanguard are over. I've now had a week of problem-free gaming since swapping the card over.
Just to reiterate what I posted before, if you're having this error (either ATIKMDAG or R300) after switching to Windows Vista it's because there are differences in the performance of the ATI cards' hardware from one card to the other when operating under the Windows Vista version of the drivers. The drivers are fine, and most of the cards that ATI have produced are fine too, but there are some out there that just don't work, and therefore you should seek a replacement if you have this error. Dave. |
|
|
|
|
Jul 13, 2007, 02:53 AM
|
#79 | |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Quote:
Secondly, I Have in fact replaced the cards already, with exactly the same results. How do I know it's not hardware related? Because under Windows XP, the cards run flawless, so if the hardware works under one OS, it should work under another, unless of course, the drivers are exactly what they are...crap for Vista... If the hardware does what it is supposed to under one OS, and it doesn't do what it is supposed to under another, it is, without a doubt, Software related. Plain and simple truth here is... When you Spend close to $500 for an OS, and close to $500 for a piece of hardware, you already are in the hole almost a grand, and for that amount of money, which doesn't even include all the other system components, it should all work together fine! Especially if BOTH companies certify it to be supported. WTF are we paying for if these morons writing the software get away with ignoring the people who made it possible for them to see a paycheck last week, month year...you get the picture.... The retards over at ATI need to get their heads out of their collective asses and address the issues people are having, NOT just with the new DX10 cards... and in saying that, perfect example of being ignored is not even a ONE, of the so called, supposed ATI employees who are on this site, has had anything to say about it. Where is their input on this matter? where are they since this is a real problem, but with slightly older hardware (which ATI seems to not give a shit about anymore) Why haven't they even come in just to ACKNOWLEDGE this and the other threads about this error many are having??? They haven't come in because they are either full of shit and DON'T have anything to do with ATI, OR.... as i said, could care less. That is what you can expect in the future as well, and it will only get worse... ugghhh...before AMD was in the picture, this issue would have been resolved with 2 driver releases... if that many... shaquatch: I have tried with 1 GB, 2GB, 4 GB, 512Mb of different memory other than the corsair I have, still the same problem. The amount or manufacturer of the memory I've tried doesn't matter, I can replicate the error at will every time. The only thing I HAVE noticed in the 7.6's is that if i forget to start ATI tool, and I load up a game and it inevitably starts the BS ATIKMDAG crap, if i try to start up ATI tool after I get the error, the system hard locks with massive screen corruption or restarts itself, something that WASN'T happening with the 7.5's and below. So ati broke something else in the drivers yet again. At the rate they are going, soon I won't even be able to load up ATI tool... then again, by that time, I'll probably have new NV cards in the systems I have as my faith in ATI is pretty much gone...
__________________
Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
|
Jul 13, 2007, 10:16 PM
|
#80 | |
|
DriverHeaven Junior Member
Join Date: Jun 2007
Posts: 47
Rep Power: 0 |
Quote:
It's far from it, I left NVIDIA just before Vista came out because of their crummy drivers, and only having a NVIDIA card again from September 06. Both have their fair share of problems. Don't get me wrong it's frustrating the problems ATI have with Vista, but because of that I have stopped using Vista and just sticking to XP for now. Until then and they get the drivers sorted, it'll all hopefully blow over. To claim NVIDIA is the bees knees. Sorry, let me rephrase that. To think moving to NVIDIA will sort all the problems wont make much of a difference. You're delusional my friend.
Last edited by vf-; Jul 13, 2007 at 10:24 PM. |
|
|
|
|
|
Jul 13, 2007, 10:54 PM
|
#81 | |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Quote:
Delusional? where if at all did I claim NV was best? Not anywhere, in any thread I can rememeber... NV DOES have their fair share of problems as well, one difference though, at least THEY are actively trying to sort theirs out, ATI is just blatantly ignoring the problems, while trying to "tweak" for all the users of their newest boards..... I'd rather be with a company who actually listens to what the customers are saying, and even if they fail, one who at least tries to fix the problems, rather than to be stuck with a company who only cares about their top line products (which ironically don't work very well either) and profits.... Delusional? no, I think not. Tired of being ignored and tired of dealing with a problem that should have been dealt with already, but doesn't even get a mention in the "Known problems" section of the driver releases... YES... That to me is ATI completely and blatantly ignoring the problem. Not a company I want to give my money to anymore. The only ones delusional would be ATI/AMD, their employees, and any of their fan-boys to think something like this won't eventually cost the company a small fortune, and possibly their stake/reputation in the high end graphics market. Who else is there besides NV and ATI? There are only 2 major players right now, and ATI is doing the one thing no company in their position should, and that is ignore the customers and the problems they have... Capiche? Like I said, it is to be expected though, after all ATI is now an AMD company... and this would have never happened before...
__________________
Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
|
Jul 14, 2007, 10:04 AM
|
#82 | |||
|
DriverHeaven Junior Member
Join Date: Jun 2007
Posts: 47
Rep Power: 0 |
Quote:
Quote:
I had no choice to reinstall the system because of it. Quote:
You also hardly ever see any of the ATI people hang about here now. Only time you did is if things are going well. And if I remember correctly this is why the Catalyst maker left Rage3D, because of the same problems and came here instead. Users were giving him a lot of flack because of bugs not getting fixed. Yet here we are again. |
|||
|
|
|
|
Jul 14, 2007, 10:16 AM
|
#83 |
|
DriverHeaven Newbie
Join Date: Feb 2007
Posts: 5
Rep Power: 0 |
Hi!
I'm getting the atikmdag error when I try to play a dvd with PowerDVD Ultra 7.2 (It's meant to be compatible). I have a Sapphire 2900xt, 4 gigs RAM under Vista Ultimate x64.I'm using Catalyst 7.6. No help from me, just adding another disgruntled customer to the list! |
|
|
|
|
Jul 14, 2007, 08:14 PM
|
#84 | ||
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Quote:
XP performance is as it always was, flawless for me, but I didn't spend upward s of $1000 for Vista X32 and x64 (I have multiple systems, some of which can't run x64...yet) to not be able to run it because some hardware manufacturer continues to screw up their drivers on a daily basis. ATI spewed their crap about being 100% ready for Vista, got a ton of people to buy the hardware, and now they have fallen on their face trying to fix an obviously horrible driver base. Nv isn't that much better, but at least the problems on that side are getting worked out... Time to start from scratch ATI, just like you had to before which led to the birth of the "catalyst" drivers. Fire all the morons who can't get it right and get some fresh talent in there to fix things, or start refunding all the $$$ you made claiming your products were 100% vista ready... Apparently the older "catalyst" team are getting too fat, lazy and comfortable, take out the trash ATI.... Quote:
I'm curious to know if the 2900xt will throw the error if you go into the overdrive section and use the automatic clock utility to find the highest clocks the card will go. keep an eye on the temp as well and try to note if your fan is adjusting to the core temps, or not... then again, I'm not sure if these otions are available for the newer cards, since i WON'T buy any more ATI cards past the x1900xtx's I presently have.... (actually, down to my last 2, one in this, my gaming/online rig, and the other in my backup rig to this one)
__________________
Everything and everyone, eventually fade into Oblivion.
|
||
|
|
|
|
Jul 15, 2007, 05:34 AM
|
#85 | |
|
DriverHeaven Newbie
Join Date: Feb 2007
Posts: 5
Rep Power: 0 |
Quote:
Sorry I can't help more...I like Vista but it sure is a pain in the derriere!  (I'm also a bit of an ATI fan...or rather used to be...!)Debs Last edited by debs67; Jul 15, 2007 at 05:26 PM. Reason: wanted to add something |
|
|
|
|
|
Jul 19, 2007, 05:07 AM
|
#86 |
|
Administrator
Join Date: Nov 2002
Location: Cloaked
Posts: 2,999
Rep Power: 72  |
HI All,
Just wanted to let you know that I have been speaking to ATI's driver guys directly about the ATIKMDAG issue over the past week or so. (Happens on my 2900XT) I'll point them to this thread and make sure they know its a priority. (FYI, they have recreated one of my crashes so hopefully thats going to lead to a solution). I also get the R300 error on my Alienware laptop (X1400) so will start progressing that one further as well. (Thought it was just me until now). |
|
|
|
|
Jul 20, 2007, 04:20 AM
|
#87 | |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Quote:
Hopefully a light at the end of this dark tunnel? What task is being done when your 2900XT throws the error? I'm curious. Can you get the error every time if you repeat it? what about what I had asked the previous poster? Notice anything unusual as the temp goes up on the core and the fan kicks up (or tries to) in speed? I'm just trying to find out what each model/version of the cards do, as it appears the driver crashes for different reasons with different cards, which makes absolutely no sense. The driver CAN'T be written THAT bad...  (OK, it can, but I'm trying to remain optimistic...)
__________________
Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
|
Jul 20, 2007, 08:12 AM
|
#88 |
|
Administrator
Join Date: Nov 2002
Location: Cloaked
Posts: 2,999
Rep Power: 72 |
For me, the KMDAG error can be repeated by opening PowerDVD 7.3 and trying to play Casino Royale (Blu-Ray) with Avivo acceleration enabled.
The disabling of cores does not make any difference. As for the R300 error, that happens 3 or 4 times a week at least on my laptop. Dont have a repeatable scenario atm however i am monitoring. |
|
|
|
|
Jul 21, 2007, 10:52 AM
|
#89 |
|
DriverHeaven Newbie
Join Date: Apr 2007
Location: Land of Hamlet
Posts: 13
Rep Power: 0 |
I used to get the ATIKMDAG a lot, whenever I opened a program using 3D.
This would happen even if I used the ATI Tool. I then reduced refresh rate from 75 to 60 and haven't had any errors since. This is several months ago. I'm still only using Catalyst 7.4 |
|
|
|
|
Jul 24, 2007, 08:52 AM
|
#90 | |
|
DriverHeaven Junior Member
Join Date: Apr 2007
Location: NYC, N.Y.
Posts: 55
Rep Power: 17 |
Quote:
As far as the laptop, is there a way to monitor temps on the GPU? I would keep an eye on them, see if maybe a certain temp correlates to an error, etc...
__________________
Everything and everyone, eventually fade into Oblivion.
|
|
|
|
|
|
| Bookmarks |
| Thread Tools | |
|
|
Network:
