Do you have a way to trigger that one?To be honest I can't say. My brother's machine(s) has random crashes from time to time. We suspect that this erratum is to blame. He must have kept some information at least from one of those crashes but there was no time to analyze them till now. Finding those logs on our disks needs a big effort but it will be done! We are willing to discover the trouble maker no matter what it takes. To do that the machine must be stripped off from all cards and then put on quarantine. Then we can connect it with a another machine with an RS-232 cable to see what is wrong. After that we must test it on a different motherboard we have. I think we have one with a BIOS from a different BIOS vendor. We will surely inform you on this one as we can't do such a patch. So we will focus on triggering this bug. One thing is sure, its BIOS has no workaround for that erratum.