SBIE2101 Crash When Playing Starcraft 2

[AquaMagic]

Describe the bug
When I run Starcraft 2 in a sandbox, it crashes after several minutes with the following error messages in the sandboxie notifications:
WerFault.exe (1816): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1.
WerFault.exe (1816): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1

This happens regardless of what actions I take within Starcraft 2; it always crashes after several minutes regardless of what settings I use or what I'm doing in-game. Sometimes the error messages don't appear and Starcraft 2 crashes and opens its own crash report window.

To Reproduce
Steps to reproduce the behavior:

1. Open Sandboxie and run the Battle.net launcher from a sandbox.
2. Launch Starcraft 2 from the Battle.net launcher.
3. Wait a few minutes.
4. The game will crash and the above error messages may appear in the Sandboxie notifications.

Expected behavior
The game does not crash.

System details and installed software

• Windows 10 home edition, Version 10.0.19041 Build 19041
• Sandboxie-plus 0.7.5 and Sandboxie-Classic 5.49.8 (tested on both)
• I have not used prior builds of Sandboxie, so I don't know in what version this bug started to appear.
• Only the default Windows security software is running.

Additional context
I haven't been able to find a workaround. So far I have tried:

• Installing all the driver updates in the Windows settings app.
• Changing the graphics settings in Starcraft 2 to minimum (I usually play on maximum).
• Uninstalling and reinstalling both Sandboxie-Plus and -Classic and clearing the sandbox contents.
• Allowing Sandboxie to copy the game's files into the Sandbox; it crashes regardless of which option I choose.
• Disabling the "block network files and folders" and "prevent change to network and firewall parameters" options in the sandbox configuration.

I have tried running Google Chrome and Borderlands 2. These and the Battle.net launcher do not crash.

Aside from the above-mentioned changes, I'm using a sandbox with the default settings. I don't know enough about Sandboxie to be comfortable with fiddling with the settings, as I have no idea what many of them do.

Sandboxie configuration
The applicable sandbox is "SCIIBox"
https://gist.github.com/AquaMagic/851600cf4a77888afedd99d03a6e3317

[isaak654]

1. Did you able to reproduce the same issue on the release v0.8.2?
2. Do you have Chrome as default browser?
3. If the answer to the previous question is yes, could you set Edge as default browser and tell if you notice any difference?

[AquaMagic]

I updated to v0.8.2 and tried again, the issue is persists in that version. I switched my default browser to Edge and restarted my PC and Starcraft 2 still crashes. I don't notice any particular difference. So, in short:

1. Yes.
2. Yes.
3. I don't notice any difference.

EDIT: In case my initial report was misleading, Chrome is working just fine.

[AquaMagic]

I found out today where one can find crash logs for Starcraft 2. I've attached one from yesterday for the described issue in case it's helpful.
BlizzardError.zip

[NewKidOnTheBlock]

Sandboxie keeps complaining about a file being too large to copy and keeps asking to raise the file migration limit.
So you might wanna consider giving that sandbox access to your Starcraft folder.

[AquaMagic]

I've just tried that, It still crashes in the same way. I've attached a screenshot in case I've configured it wrong.

I've also just been allowing Sandboxie to copy the larger files when it asks me, so this should no longer be an issue? The offending files in this case are the game's data files, which are 26 files roughly 1 GB in size each.

I've also just discovered that Starcraft 2 doesn't generate a crash report unless the Starcraft 2 error report window appears, which doesn't happen for ~80% of the crashes. However, if the crash log is useful, I can try to generate another one.

[worthy7]

Any news on this one? 😁

[DKalenscher]

Same exact issue, have tried same steps as original user and same results.

[DavidXanatos]

can you try getting an other dump this one unfortunately is not contianing usefull data

[isaak654]

Further instructions about the creation of a crash dump on the sandbox itself are in the v1.0.5 / 5.55.5 changelog:

added sandbox top level exception handler to create crash dumps -- it can be enabled per process or globally using "EnableMiniDump=process.exe,y" or "EnableMiniDump=y" respectively -- the dump flags can be set as hex with "MiniDumpFlags=0xAABBCCDD" -- a preselected flag set for a verbose dump can be set with "MiniDumpFlags=Extended" -- Note: created dump files are located at: C:\Sandbox\%USER%\%SANDBOX%