April 2019
Unfortunately, I don't know when. We'll do it ASAP, but things take time to get through our build pipeline and distribution channels.
April 2019
@Sakanaji-Sam, you crashed in your nVidia driver, so I recommend upgrading your driver.
April 2019
@Tekat0chiku, you have a unique crash. Thanks for reporting it. I've posted a bug for the appropriate engineer to investigate.
April 2019
@XDemon_NukeX, you got a unique crash. Thanks for posting it! I've reported a bug for the appropriate engineer to investigate.
April 2019
@RugerRell23, thanks for posting your crash. This report is for a crash that was already fixed in a patch that has gone live.
April 2019
@purplebiotc, thanks for the report. This is for a crash whose fix is already patched and live.
April 2019
@Windowz95, your crash is in Microsoft's speech API after the game has exited. I've seen this a couple times, but unfortunately I don't think we can do anything since it isn't our code that is crashing.
April 2019
After looking at another round of logs, the following people are getting the same Intel CPU crash that was described in post 1984, so I won't repeat that all here. In short, this appears to be an Intel hardware bug that is only fixed by lowering clock speeds, but we're trying to change the code to avoid this bug in a future patch.
@Rent-A-Bot-V2 @SavageReborn @Bonzay0 @PrOMnIsToRaS @SilverBulletPT @wilchen92 @Chagotta @DirtyScrubz @Karrororo @HegemonShuriken @Airwav3 @Stoney_Wild @Nels0nism @Riveliia @bigdaytv
User starcr also got this bug, but the forum won't let me ping him because it would rather ping a bunch of other people with "starcraft" in their name.