Application Error and a crash. The memory could not be read.

[Mik]

During vm operation message box appears and VirtualBox.exe crashes.

[Mik]

The issue repeats once, twice a day, but unfortunatelly I don't have reproduction steps - the same actions done second time when the vm starts work fine.

[aeichner]

Please try a testbuild from Testbuilds. There was a crash fix related to audio after the release.

[Mik]

Audio is switched off on these machines.

[aeichner]

Then we need a VBox.log and a Windows minidump for furhter investigation, see here for further instructions on how to provide a minidump.

[Mik]

Ok, I prepared the setup, next time it breaks down I should have dumps.

[Mik]

However, no crash dumps have been found. Looks like an exception caught and handled causing application exit.

[Mik]

Minidumps of the processes tree

[Mik]

When the message box appeared (created by csrss.exe process) I suspended the process tree with procexp. Then I created minidumps, then I have clicked OK button on the message box and finally I resumed processes from the top-most from the tree (VBoxSVC). After resuming the bottom one VirtualBox (the one with most occupied memory) all the VirtualBox processes terminated without creating another dumps (despite configured WER like in the instruction). So it looks like an exception handled with sth like exit(1) function. Dumps are created during the wait for user reaction (the process would not terminate until user presses OK on the message box), so it should be possible to get the information where the execution point was and what was the exception.

[Mik]

And minidumps are numbered like in order of occurence in the process tree - 1 is the parent for 2, 3 is the child of 2. 3 is the one that terminated first after pressing OK button.