Diagnosing ERROR 134 in Windows

Go through each of these.

LoadSectorTable
If the error log is always at the same file, reboot your computer, then run the Repair utility in your wow folder and see if it fixes the error.

If your error log is on different files each time and they're LoadSectorTable type errors, those are generally file read problems where either the hard drive isn't giving that data up or your antivirus/security program is blocking it. For this type of issue, you'll want to follow the directions on Repeated ERROR 131/132/134.

DecompressData
If your error log is on different files each time and they're DecompressData failed, you're having a random corruption that's usually from an overheating or memory issue. Try running a memory scan program, such as http://oca.microsoft.com/en/windiag.asp or http://www.memtest86.com. A prolonged run (or the Microsoft one on extended mode) may reveal things.

Keep in mind that memory test programs will not show issues if the system is right on the edge of being stable. Testers are low-resource so it won't do anything like put a heavy load on the system's power, its power supply or send data all over the place like a live computer running a game can. In these cases, you definitely want to make sure that all of your BIOS settings matches your RAM manufacturer's specifications and that the diagnostic tools show the voltage being stable.