Originally Posted by GBT-MatthewH
Perhaps, but they need to know what the bug is (be able to repro it) before they can deduce what may have fixed it.
I understand that to an extend but there are also other issues here
I doubt anyone is really willing to send you their motherboard and spend time taking apart their computer, not to mention not having a computer, for many weeks or even months. Especially if their issue is fixed by not using creative software or using the PAX driver, they are not really going to be willing to give up a motherboard whose issue has been 'fixed' and risk getting a different motherboard back that possibly has some other issues.
I think if you really want the motherboards of people who have this problem, you will have to ship them a new one first and then get their old one back. I know that for me, that is the only way I would consider it.
However, in the meantime, your engineers could take a look at the changes the PAX driver introduced versus the RC2 driver on the website. By logical deduction, it would be relatively easy to see and infer from the changes what the driver could've done that could've fixed the issue. Maybe it increased default buffer size, or disabled dithering by default or some other change. If they agree that the changes don't create any new issues, then they could release a beta driver with these changes incorporated and release it for testing. If people who had the issue report it as being fixed with this beta driver, you now have a proper release to publish.