https://bugs.winehq.org/show_bug.cgi?id=39674
--- Comment #16 from Austin English austinenglish@gmail.com --- (In reply to Sergey Isakov from comment #14)
This workaround is also valid for wine-staging-1.8rc2.
Looks like Futuremark SystemInfo doesn't like fake Bluetooth.cpl
I see no evidence of that here. The previous information in the bug is about fltmgr.sys and bthprops.cpl, not bluetooth.cpl (and that info has changed a few times). There is no reference to bluetooth.cpl in the relay log either.
For me, with -nosysteminfo, 3dmark03 launches fine, as it did in 1.7.54. I suspect your regression test is wrong, as you've mentioned it may be timing/load related.
Additionally, bluetooth wasn't in Windows when 3DMark03 was released (it came in XP SP2, released in 2004), so I highly doubt 3DMark03 has any knowledge of bluetooth (additionally, why would a d3d benchmark need/use bluetooth).