Writing drivers seems to be difficult

Posted on:June 07 2010

When I worked full time as game developer some years ago I learned quite quickly that the most problematic issues with computer games are graphic drivers: Some of them are buggy, and a small percentage of your customers will come back to you and blame your game for creating blue screens, randomly restarting their PC and other nasty behaviors. The game developer is completely innocent in this case, the reason for this is usually an error in the 3d graphics driver. But explain this to the customer: Quite difficult.

Today, the situation is a bit better, because apparently the quality of the graphic drivers and the operating system using it has improved (for example Windows 7 will no longer crash when its graphics driver does), but these issues still are there. But I also now have learned that this problem is not only limited to graphic drivers: Since I developed the audio library irrKlang and a lot of games are now using it, from time to time gamers report that when starting up the game using irrklang weired stuff happens: For example the screen becomes dark or mouse input stops, things which a sound library has no influence over, honestly.

Again, the reason for this is not irrKlang but a buggy hardware driver. Fortunately, these effects only happen in very, very, very rare cases, and since irrKlang supports multiple audio drivers it is possible to circumvent these, but it really makes me think that it must be quite difficult to write working hardware drivers. Or maybe these companies are simply hiring weird programmers.


A printer driver once caused a video playback to crash over and over again. Guess how long it took to find this one out...
2010-06-07 20:43:00

yes drivers are a major issue.. i think the companies that try to minimize cost by removing a feature of two that are the standard are to blame.. like we have intel doing that with built in video cards..

btw the spelling of weird in the last sentence is wrong..
2010-06-07 21:13:00

thanks, corrected
2010-06-07 21:19:00

Ah, those good old times, spending three days debugging a blue screen caused by some graphics driver that is incapable of handling AGP textures correctly, crashing the machine after some 2 to 5 minutes playing the game... When you think that debugging without symbols is awesome, debugging without a debugger is even more so...

Btw.: Do the AMD drivers still crash when you call CreateStateBlock immediately after initializing Direct3D?
2010-06-08 11:05:00

"... Or maybe these companies are simply hiring weird programmers."

Weird programmers combined with weak/missing quality assurance is a good recipe for software desaster. Know it from experience.
2010-06-08 12:33:00

I know this problem. One part of the project I'm working on (responsible for the whole network traffic) always shifts it's bugs back to anyone else instead of even searching for the real cause. That's when software development stops being fun.
2010-06-09 07:37:00

Add comment:

Posted by:

Enter the missing letter in: "Internationa?"




Possible Codes

Feature Code
Link [url] www.example.com [/url]
Bold [b]bold text[/b]
Quote [quote]quoted text[/quote]
Code [code]source code[/code]