Page MenuHomeFeedback Tracker

BSOD While multiplayer
Closed, ResolvedPublic

Description

Was playing with a friend, he was hosting the game, when suddenly I crashed into a BSOD.
We were flying a Ka-60 (black).
Since it crashed into a BSOD, I figured it's important enough to be reported.

Details

Legacy ID
2123296873
Severity
Crash
Resolution
Not Fixable
Reproducibility
Unable To Reproduce
Category
General
Additional Information

Event Timeline

Shryke2a edited Additional Information. (Show Details)
Shryke2a set Category to General.
Shryke2a set Reproducibility to Unable To Reproduce.
Shryke2a set Severity to Crash.
Shryke2a set Resolution to Not Fixable.
Shryke2a set Legacy ID to 2123296873.May 7 2016, 1:11 PM

I see three crashdumps, which is from situation described in report? The last one?

Probably, I made the package right after the BSOD.

Simon added a subscriber: Simon.May 7 2016, 1:11 PM
Simon added a comment.May 16 2013, 2:15 PM

Minidumps show 3 completely different callstacks, so we are unable to solve this. However, BSOD probably means there is a problem with your system (hardware, drivers...).

Mass close.