https://bugs.winehq.org/show_bug.cgi?id=56912
--- Comment #21 from stormtrackertony@gmail.com --- Zeb, I would definitely have to agree with you at this point. Even though we've not had a bare-metal confirmation, you've gone above and beyond expectation to document that an unintended AVX instruction has somehow made it into the updated GR2Analyst code. I thank you (and Andrew) both for the time and effort to help reach this conclusion!
Further, I'm now starting to believe that even though the error is likely to occur on actual bare-metal Windows with similar hardware, it's going to be hard to find a system to actually reproduce it (and rare, if ever, to be an issue for real world users.) Another program user was trying to test this with a bunch of old laptops and in all cases, the system either had AVX support and worked or either the hardware lacked D3D11 support needed to even open the software to begin with. According to his research, there's very few systems that are old enough to lack AVX support yet new enough to support the D3D11 requirement. Most of those that would be affected were built between 2010 and 2011 (as mine was). Guess I'm just unlucky (or either this is my sign that I'm well overdue for a system upgrade. lol)
What still baffles me the most is why the instruction does not appear until trying to load a radar file. I can display weather warnings, move/zoom around on the map, access menus, etc. for as long as I want with no problem. Then I try to load a radar data file and boom! Granted, I'm no programmer, so I'm kind of learning little bits as I go. Yet if copy protection is the problem source and the whole exe is copy protected, then why does it wait until that point rather than crashing immediately when opening the software? That's what's most mysterious to my old brain!
In any event, I'll share those disassembly results with the developer and it's up to him to decide whether he wants to pursue a fix for it or ignore it hoping no one else runs into the issue. Will let you know if he ever finds a fix. I thank you again and feel free to reach out anytime I can ever return the favor! Who knows, maybe you'll need me to test a software on this apparently rare, 2010 clunker of a computer I have! lol