It would help to know what was running in containment before you did a container reset, though I’m sure this is the same issue that has happened for a very long time, and was fixed in an previous un-released build. If you were running a web browser that is based on chrome then used reset the container which resulted in a BSoD, that is a known issue but was not included in the 8012 release.