burgerd

I agree with some of the others here. A problem that is this big should be looked at by ATI and perhaps a list of things that CAN cause it should be posted on their website. The problem is that this would be bad publicity for ATI (or any other manufacturer for that matter).

Judas

you have any idea how many system ATI would have to setup and configure?... i mean.. my gaud... they would have to put more money into test systems... then the entire company..... i agree... if should be taken care off.... But it's just plain out and out not cost effective to spend that much considering they have a huge lab with a couple hundred different machines with different specs... with various videocards.... they thoroughly test them... they have a beta community....they are trying.... Perhaps you could take/send your system off the ATI and tell them to figure it out.... But i doubt that would be viable..... Take a look at omega's site for the RADEON Bios settings and start browsing.... check your IRQ tables... and Resources to see if the video card is sharing with another device..... I mean... i've solved these problems before by digging right into the machine.... Settings that worked with 3DFX don't work with any other cards... and vice versa for them all.... you can't simply slap ATI with the "driver bug" issue... Even though it may be.... you got to give something to get back..... Have you even tried to Reset the Cmos on your motherboard?

__________________

max1pc

bro its def not a shit load of issues causing this one problem on ALOT of diff systems....all ati has 2 do is recreate the error....if they can recreate it, they can fix it....their just 2 lazy to do it

burgerd

Judas,
Perhaps you misunderstand me... I am not suggesting that ATI build a huge farm of PCs with every conceivable configuration in it. That would be way too expensive to maintain.

However, they do already have a massive sampling of machine with a myriad hardware/software configurations.... It is called their userbase. All of us that have or are dealing with this problem are submitting valuable information to ATI in the form of bug reports. This information can be used to build a few systems that seem to have the common denominators that appear in the userbase to try and recreate the issue. This way, a comprehensive list of what tends to cause the problem can be created whenever issues are discovered. This could even lead to a resolution of the issue if it is found to be a software related issue. Heck, they could probably build a few systems and put them on the developers desks so it wouldn't be just a testing system and they could get their money's worth.

It just seems to me that their is a tremendous amount of information to be found on this subject yet no conclusive information on ATI's website regarding it. Even a blog of the testing that is being performed would be a nice thing... At least that way people know that they are doing something more than just saying it is a known issue.

Judas

i agree with you there burgerd..... i really do agree... but you gotta consider that there are millions of submitions..... sorting through and connecting them all is another thing.. for all i know it could take up to a month or 2 before they get sorted through the mess of e-mails.... Also.... i know that ATI has gone out and just built machines that would crash.... but they sometimes don't find anything wrong.... as it can be as simple as a little tiny... jumper setting.. or bios switch... or something completely passed by innocently..... I guess what i'm trying to say is you gotta give them a bit of slack.. they are trying there best... they've come a long damn way ...they have made it a guarantee to bring out one driver package with as many fixes as they could put in... test thoroughly... and push through MS's Quality labs....... what would be of help is a Bios Settings dump program of sorts....

__________________

max1pc

bro ur def wrong on this is a simple thing.....this is a critical error! its not like this is cause some small crash but a huge one.....also it says that THEIR driver file goes into infinity loop during the error....i don;t care what u tell me, jumper settings have NOTHING to do with a crash like this....and since this error has been around for a few years now because even their old video cards seem to have it, then that means that ati is just lazy....ur telling me it takes them years to open emails and bug reports then after 5 years they might place out a good driver? cmon now im not even gona have an ati card in 5 years....
bro u make it seems like its some stupid windows crash when its not....this is the type of crash that ur whole system is unstable. and the fact that it says that its the ati file causing it well its just stupid to say its because of my jumper settings ...

Judas

I wasn't saying it was for sure a jumper setting... i was saying it could be all related to something as simple as a jumper setting.... and just because WINDOWS blames a crash on the infinite loop... doesn't actually mean it is the drivers..... Alot of people with Kyro 2's and even Kyro ones would get the same error... but it wasn't related to the driver at all..... it was a setting in the bios for a memory setting.... or simply switching from UC to WTUC (spelling... but something like that... i personally never had a problem with my Kyro 2.... i didn't have a setting like the in the bios)..... For all i know it could be the entire CARD itself having some kind of bad trace on the PCB .... getting a replacement might do the trick..... or who knows what it is.... obviously ATI themselve are having a bloody hard time finding it....

__________________

max1pc

i think ati isn't trying ......just do a search...this problem has been out there for while now....

Judas

I've done the search... i know of it.... i've done a search on the kyro 2 problem..... came up with the same thing... i've done a search on some of the Nvidia TNT problems I had.... i ended up with the same results of nothing but bad news everywere for a long time...... however.. I... fixed my TNT issue.... it appears that setting the AGP Apature lower fixes it up... a setting of 32.... 64 wouldn't work.... 128 was obviously out of the question... as i was running it at 256..... i got a Geforce 2 MX400 that i thought was an absalute pile of crap cause i was getting a loop error... no driver fixed it..... seems the have the AGP Write to PCI (or something similare to that name) enabled... caused it... it's been awhile... i know a geforce 5200 FX had the same problem in one of my firends rigs...... result? he was totally po'ed cause at the time.. he paid a good chunk for it......no driver release fix it.... what did i do? i took a good look at it.... i completely messed up the bios .... changing settings like a crazy...... with his rig... setting the AGP to 4X mode completely solved the problem (forcing it down from 8x)

__________________

Captn

DONT BUY DELL or GATEWAY !

Problem Solved ! !

__________________
Asus P4C800-E Deluxe
P4 2.8cGhz @ 3.4Ghz
1024mb Corsair XMS
Leadtek GeForce 6800 Ultra
Audigy 2 ZS
Enermax 550 Watt
WD 160Gig
WD 160Gig

max1pc

my dell was a gift so its not like i had a choice in the matter

if u got a free dell (with a nice flat 19'inch screen) would u take it or say hey its a dell i don't want it ? exactly

Crash Override

actually I would smack the person with a rubber mallett.

My business is in system building and repair

Most of our computers that come in for repair are either Dell or HPQ (HP Compaq) models.

Gateway doesnt sell too well over here otherwise I would imagine I would see them in the shop as well.

I can just about guarantee I could build a PC with everything the dell has for cheaper (well other than maybe the LCD since they seem to be just throwing those out for free)

Crash Override

ok since you seem so bent on calling him stupid I'll return the favor.

YOURE STUPID

Feels pretty crappy to have someone say that to you eh?

Most of the people who have the dates on their names going back a couple years here are hardware experts.

Not to sound superior but we are most likely smarter than you and know what can and cannot cause these types of failures.

What if I told you that I had a similar issue with my 8500 doing the INFINITE (not infinity mind you) LOOP ERROR.

Turned out that it was my Power Supply. Something had gone wrong in it at some point and it wasnt kicking out enough power to my components.

I saw it in another PC where it was a memory setting.

I saw it in another PC where it was a conflict with a Sound Blaster Live!!!


Trust me it doesnt always mean its the card or the drivers. And if thousands of people own this card without this problem it means its most likely not software related

So take it in to a computer repair shop and have an expert look at it.

But dont bite the members here for trying to provide help and dont call them stupid unless you want to have that label tossed back at you.


edit -

oh and just a hint.

Dell is notorious for putting in low quality, low power, power supplies which can cause all sorts of instability issues.

5 bucks says you have a 250W PSU in that thing when you should have at least a 350W

Sourcer_2002

Hopefully after 5 pages he has seen the light....

max1pc

ok first off i didn;t call anyone STUPID! ur the only scumbag here that thinks this way....i respect the guy and I tried some of his ways but in the end it all failed....then u point out stupid shit like its a power supply SORRY to tell u but the other 10 guys who posted with a problem like mine decide to buy a new power supply or new motherboard ect and nothing helped....so why would i go and spend $$ to buy a new power supply when it won't fix the problem? i sure as hell don't want to go out and buy parts i don't need just cause u THINK it might be the problem but for all u know it could be 10000 others.....

and another thing is that I EMAILED ATI about this and they told me that they have received emails about it but their answer to the problems was to just use the old drivers because their almost the same.

i never called anyone stupid and i never bashed anyone...how did i call him stupid? i simple explained to him that the problem was most likely a driver problem not my bios settings since i played with them allrdy.
Well since u like to be an online dick, go fuck ur self

Crash Override

excuse me?

I was one of the opening crew here on this site so be respectful bub.

also I do believe this is a direct quote from you

and the fact that it says that its the ati file causing it well ITS JUST STUPID TO SAY ITS BECAUSE OF MY JUMPTER SETTINGS...

Also keep the profanity down to a minimum please

DH is a family friendly site.

Also the reason why some of those people may be having issues still is that they went from one brand of cheap psu to another brand of cheap psu.

Ive been a technician for the last 16 years of my life so I do like to think that I know what I am talking about.

zerodamage

Thread closed due to being off topic and name calling and flaming.


Crash, your behavior is way out of line. I expect no more of this behavior from you.