4.3.16 Multiple BSODs

[mskov]

Starting with 4.3.14 we are having multiple BSODs with different reasons: PAGE_FAULT_IN_NONPAGED_AREA, PFN_LIST_CORRUPT, SYSTEM_SERVICE_EXCEPTION, DRIVER_IRQL_NOT_LESS_OR_EQUAL.
This happens quite often (on average 1-4 times per 8 hours of virtualbox use).
Host OS: Win7 x64. Guest OSes: debian linux, Win7 x64.
It seems that (at least) some of the problems are caused by incompatibilities with some drivers (NCP Secure Entry Client, USB Smart Card Reader).
But we never had such problems with 4.3.12 or any other VirtualBox version prior to 4.3.12.
I attach here some reports from the typical minidumps that we get. Unfortunately, the log files get completely corrupted after BSODs, so I cannot provide them here.
Are we the only ones experiencing this problem?

[mpack]

Please pick one VirtualBox version and one VM, and provide: Minimum information needed for assistance.

[mskov]

The crashes always happen at startup. VBoxStartup.log gets completely corrupted, so posting it here doesn't make any sense. The guest log file at this point is not yet created.
So I am attaching here log from a successful startup that was performed immediately after the crash (don't think will help though). A successful VBoxStartup.log is too big for posting it here.
The VM was SELinux, 32bit, 32 mb ram, running headless, guest additions 4.2. Host: Win7-x64, 8gb RAM. Antivirus installed: Avira. VirtualBox version: 4.3.16 - self-built OSE.

We also had crashes for Win7-x64 VM (2gb RAM) and Debian Linux VM 32 bit (1gb RAM), running on the kind of host with both OSE version and the version from Oracle.
We had these crashed on three different machines. So it's surprising that we seem to be the only one having the issue... Could it be somehow caused by Avira? (it was installed on all three hosts, where we observed crashes).

[IdeCable]

Easy to fix.

Open VirtualBox, go in File -> Preferences, Extensions

And remove the old Extension.

Now go on the website, download the current version, and install the extension.

You should not have these issues anymore!

Let me know if this fixes your issue!

[mskov]

Extensions were not installed on any of the test PCs.

After the last BSOD today the logs were not completely corrupted. The last lines in the VboxStartup.log are:

71c.f4c: supR3HardenedMonitor_LdrLoadDll: 'avrt.dll' -> 'C:\Windows\system32\avrt.dll' [rcNt=0xc0150008]
71c.f4c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume2\Windows\System32\avrt.dll
71c.f4c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=000007fefbcc0000 'C:\Windows\system32\avrt.dll'

I attach here the logs and the dump file.

[mpack]

The log is for someone's (Sirrix) fork of VirtualBox, and hence is not supported here. We can only support one of the official downloads.

It's unusual to see a fork used on a Windows host. If you go "self build" you need to be able to debug it yourself too.

[mskov]

I'm sorry. As I've already said, this is an OSE version (just different naming). But no problem, here are the logs and the minidump with the official build from Oracle. Unfortunately, the VBoxStartup log is completely corrupted there (contains only NULL chars I think). It's SELinux, 32 bit, 32mb RAM, running headless on Win7-x64 host.

[mpack]

Since I suspect you have been fiddling with self compiled variants, I suggest that you discard the saved state currently associated with the VM and avoid using this feature thereafter. Also I would either revert to 4.3.12 or try the 4.3.17 test build.

[mskov]

Indeed, it seems that the problem is solved in 4.3.17 test build #3. Thank's for your work.