New Catalyst drivers cause BSODs

[Wreckage]

http://www.techreport.com/discussions.x/15981

Come on guys, it took you less than an hour to ruin this thread? I know Wreckage isn't everyone's favorite, but he didn't do anything wrong in posting a link to a valid story, so cool it. This thread is locked, a new thread can be created if desired.

-ViRGE

 

[Elfear]

You know Wreckage, with the way your posts generally flow, I'd almost think you didn't much like the red team. But of course I must be wrong, there is no way you'd show a lack of impartiality like that. :roll:

Hopefully AMD will resolve the BSOD issue in the next driver release.

 

[Keysplayr]

Originally posted by: Wreckage
http://www.techreport.com/discussions.x/15981

Feel Better?

 

[OCGuy]

Good thing they release new ones every month! :laugh:

 

[cmdrdredd]

Originally posted by: Ocguy31
Good thing they release new ones every month! :laugh:

:roll:


How come I don't remember this type of stuff happening when the GTX280 cards were arriving broken, you know...when N7 among others were pulling their hair out because of some cards that just plain overheated. Or the microstutter issue from the 8800 series (driver bug where framebuffer memory leaked).

I dunno maybe I missed all that.

Anyone who can't boot into safe mode, uninstall drivers and then download and install the ones that worked before to see if it's the new driver instead of posting 10000 threads on forums, doesn't deserve to have a crossfire config.

It's funny really, you only hear about it when there's a problem. Are we sure it's 100% for sure that everyone will have this issue? Not entirely. Nobody posts saying "new drivers work fine, no crash" lol

 

[OCGuy]

Originally posted by: cmdrdredd

Originally posted by: Ocguy31
Good thing they release new ones every month! :laugh:

:roll:


How come I don't remember this type of stuff happening when the GTX280 cards were arriving broken, you know...when N7 among others were pulling their hair out because of some cards that just plain overheated. Or the microstutter issue from the 8800 series (driver bug where framebuffer memory leaked).

I dunno maybe I missed all that.

Why cant we discuss yet another bad driver release by ATi without deflecting to nV? If you want to start a GTX280 launch overheating thread, go for it.

 

[cmdrdredd]

Originally posted by: Ocguy31

Originally posted by: cmdrdredd

Originally posted by: Ocguy31
Good thing they release new ones every month! :laugh:

:roll:


How come I don't remember this type of stuff happening when the GTX280 cards were arriving broken, you know...when N7 among others were pulling their hair out because of some cards that just plain overheated. Or the microstutter issue from the 8800 series (driver bug where framebuffer memory leaked).

I dunno maybe I missed all that.

Why cant we discuss yet another bad driver release by ATi without deflecting to nV? If you want to start a GTX280 launch overheating thread, go for it.

Because there was nothing other than a link, and obviously from someone who is 100% totally against everything ATI tries to do no matter what. Then your wisecrack, his thread and your post was nothing more than baiting and borderline trolling if you ask me.