That's always possible, but it's not the way to bet, given the large number of other applications -- including DVD burning applications -- that run on it just fine
As to more information, what's the best thing to provide? I looked at the log files, but I didn't see anything other than some initialization/startup stuff. I presume there's a way to crank up the logging level?
Just for fun I did run the Visual Studio 2008 debugger against DVDFab when it crashed the second time. That wasn't the blue screen, obviously, but later when I tried to pick up the backup task by pointing DVDFab at the files it had created and had it try to burn them to a DVD. For that crash, VS2008 reported an error reading memory at location 0...which sounds like freeing a null pointer.
One other piece of information I can pass along is that the files created by DVDFab burned just fine with ImgBurn, which is also installed on the machine. I didn't configure DVDFab to use ImgBurn, BTW; I just ran ImgBurn and pointed it at the directory created by DVDFab in the Document tree.
Just to be clear, I find DVDFab invaluable for transferring work to my iPod. And obviously the reading end of things works fine, too (or I wouldn't have had success using ImgBurn). There just seems to be something screwy in the DVD writing subsystem.