[UPDATE] AMD Catalyst and FurMark: the Return of BSoD!

FRAPS 3.2.4
A nice BSoD (blue screen of death) under Win7 64-bit + Catalyst 10.10e + FurMark/etqw

UPDATE: I removed Cat10.10e, installed Cat10.10c and the etqw profile worked like a charm. I also tested SeriousSam, another OpenGL profile, and it worked fine with Cat10.10c. Then to be sure, I re-installed Cat10.10e and… crash on both etqw and SeriousSam. Conclusion: Cat10.10e is not recommanded for FurMark CrossFire support!

I’m polishing the new FurMark and after having successfully tested a 2-way SLI of GTX 480, I tested a 2-way CrossFire of HD 5770. Since CrossFire is not enabled for FurMark.exe, I used the well known trick: renaming FurMark.exe in etqw.exe.

Bad idea man!

This trick worked fine for previous versions of FurMark and Catalyst but now, seems AMD has changed something in etqw profile (I used the latest Catalyst 10.10e hotfix) and now my OpenGL miserably crashes when etqw profile id used. Now the only solution: install two Radeon on my devstation and debug this pesky bug!


↑ Grab this Headline Animator