Windows 7: BSOD file WER-39171-0.sysdata.xml

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

   Warning

Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

dtsoftbus01  DAEMON Tools Virtual B DAEMON Tools Virtual B Kernel        System     Running    OK         TRUE        FALSE        32.768     208.896    0      13/01/2012 14:45:46    C:\Windows\system32\DRIVERS\dtsoftbus01.sys      8.192

More Daemon Tools 3rd party drivers
Driver Reference Table - dtsoftbus01.sys
Driver Reference Table - sp--.sys
Driver Reference Table - spaf.sys
Driver Reference Table - spba.sys
Driver Reference Table - spbg.sys