HP Running the ATi QA Show?

ATi's RubyFrom the day I built my PC a few years ago until just last week, it’s been impossible for me to play a game (pretty much *any* full-screen DirectX/OpenGL game) without the ATi drivers crashing. (For reference, stock ATi HD3870 on an ASUS RoG Maximus Formula II motherboard). I’ve tracked down each and every possible lead, and solved a number of crash-inducing issues in the process, but haven’t been able to completely prevent the display driver crashes from the days Vista or now on Windows 7.

There were issues pertaining to dual-displays in a mixed VGA/DVI environment (one display DVI, the second VGA) which were never resolved by ATi (to the best of my knowledge) and were worked around by initially downgrading the DVI to a VGA connection and later replacing the older monitor with a new DVI-based display. There were issues related to the refresh rate. There were issues related to the resolution. There were issues related to the games. There were issues related to the OS. Basically, wherever you look, there were problems caused by poor development practices and crappy QA all around.

There were issues that Microsoft/Windows’ new WDM model caught, triggering a restart of the graphics subsystem without causing a BSoD. And there were (unfortunately the majority) of the ATi display driver crashes that caused BSoDs left, right, and center.

Today, my Windows 7 PC surprised me with an interesting question:

Send info to HP?

Continue reading

Vista’s Purple Screen of Death

We’ve all heard of (and, quite unfortunately, experienced) the infamous Blue Screen of Death. Some of us who tested the earlier Windows Vista beta builds had the unique experience of trying out the Red of Screen Death, which occurred when the bootloader experienced an un-handled exception (we experienced more than our fair share of these during the early days of EasyBCD development!). And then there’s Vista’s Purple Screen of Death, which few have seen.

Vista Purple Screen of Death 

Continue reading

SetPoint 4.00 and Vista USBPort.sys BSODs

These driver problems with Windows Vista and various manufacturers just keep going from bad to worse. Whether it’s a graphics card, printer, or mouse; Vista seems to BSOD right, left, and center at the slightest provocation.

If you’re using Windows Vista and you’ve been getting a ton of blank blue screens (more on that later), and you just happen to have a Logitech USB mouse or keyboard with Logitech’s “Vista Compatible” SetPoint 4.00 installed, then that’s most likely to blame.

Not having written drivers ourselves, we can’t honestly and fairly point the finger of blame at any party in particular. It’s very possible that either Microsoft or Logitech is to blame for this, but you never know.

If you know how to analyze BSOD dumps (btw, blank BSODs won’t create kernel memory dumps, make sure you have “small memory dump” selected); you’ll find that the WinDBG (or whatever debugging tool you choose) points its stubby little fingers at USBPort.sys and Win32k.sys – both stock Vista components.

Continue reading