Windows7 x32 host system crashes after update to VirtualBox 4.1.10 with Extension Pack 4.1.10

[Jurii Lysenko]

Crash happens when starting Windows8beta x64 guest system. See attached its logs before and after update to VirtualBox 4.1.10.

[Frank Mehnert]

So your host crashes, what does that mean in detail, BSOD or host hang? Did you even try this guest with an older version of VirtualBox (e.g. 4.1.8)? Which host graphics card do you have and are you sure that your host graphics drivers are up-to-date?

[Jurii Lysenko]

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          3/22/2012 9:35:39 AM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      Comp
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

NVIDIA GeForce 210 driver version 8.17.12.9573 (just downloading last Version: 296.10 WHQL)

[Jurii Lysenko]

Observe both logs please (last one with crash)

[Frank Mehnert]

Ah, you tested it with 4.1.8 as well and it did apparently not crash.

[Jurii Lysenko]

Yes, it's regression!

[Jurii Lysenko]

After NVIDIA GeForce 210 driver update to last Version: 296.10 WHQL VirtualBox crash appears when starting the same guest, see attached Image.

[Jurii Lysenko]

Faulting application name: VirtualBox.exe, version: 4.1.10.0, time stamp: 0x4f60dc5a Faulting module name: VBoxVMM.dll, version: 0.0.0.0, time stamp: 0x4f60dc30 Exception code: 0x80000003 Fault offset: 0x000c6656 Faulting process id: 0x1fbc Faulting application start time: 0x01cd08166f209705 Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe Faulting module path: C:\Program Files\Oracle\VirtualBox\VBoxVMM.dll Report Id: b2378de2-7409-11e1-86aa-c860005eed30

[Jurii Lysenko]

Fault bucket 2883082987, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0

Problem signature: P1: VirtualBox.exe P2: 4.1.10.0 P3: 4f60dc5a P4: VBoxVMM.dll P5: 0.0.0.0 P6: 4f60dc30 P7: 80000003 P8: 000c6656 P9: P10:

Attached files: C:\Users\User\AppData\Local\Temp\WEREF6F.tmp.WERInternalMetadata.xml

These files may be available here: C:\Users\User\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_VirtualBox.exe_7fd1854b4767e54c7b399b4402da3e176af34_06bb2b08

Analysis symbol: Rechecking for solution: 0 Report Id: b2378de2-7409-11e1-86aa-c860005eed30 Report Status: 0

[Jurii Lysenko]

C:\Users\User\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_VirtualBox.exe_7fd1854b4767e54c7b399b4402da3e176af34_06bb2b08

[Jurii Lysenko]

How much time should I wait any updates? thanks

[Frank Mehnert]

Please reopen if still relevant with VBox 4.1.18. Also, the chipset ICH9 is marked as experimental and there is no real reason to use this setting for your configuration.