Newest virtualbox 4.3.8 v92456 bsod on x64 windows vm

[Milardo]

Hi, I have win 7 x64 as a host and win 7 x64 as a vm as well. Been using virtualbox with no problems the last version worked fine but when i updated to 4.3.8 v92456 and i have the extensions latest as well, my win 7 x64 vm will not start in safe mode or normal mode with a blue screen error that never happened before. i have a win 7 x86 vm that works fine on the same computer.

[Perryg]

Post the guests log file ( as an attachment )

[RVTimO]

I'll have to grab my logs as well, but I have the exact same issue. Just upgraded today and now BSOD. Scrambling to find out how to revert since I upgraded using Yum and this is my production desktop VM that I need desperately during the day.

[RVTimO]

Ok, attached is my logfile.

[Perryg]

Ok, attached is my logfile.

Looking at the log file VBox is not upset with anything. So this must be something that the guest is/was expecting to see.

To revert to a previous version go here http://download.virtualbox.org/virtualbox/ and download the version that you had along with the ext pack.
You will need to remove the one you have now before you install the previous version.

[RVTimO]

Yeah, nothing stood out to me either. I was able to do a yum remove, and a yum install, and by specifying the exact package name, it worked out well. I'm back running 4.3.6 and all is well. I'll be happy to help upgrade and screw it up again if it benefits the greater good, but otherwise, I'll sit back and wait to see what happens next. If it happened to 2 of us today already, I'm sure we'll hear a lot more.

[mpack]

You might try uninstalling the GAs in the guest and trying again. The error is a "Driver Verifier" bugcheck. If it boots after the VBox update then try installing the latest GAs.

[RVTimO]

What do you mean by GA's? I guess I'm a little slow today.

[Perryg]

GA's = Guest Additions.

[Milardo]

Here is my log.

[RVTimO]

Doesn't look like that fixed it for me. I uninstalled Guest Additions, did a yum update to 4.3.8 from 4.3.6, and tried booting up. Got the same error. So, I did a yum remove on the 4.3.8 version, yum install on the 4.3.6, and now I'm back in business.

Hopefully it's something that will get figured out and maybe the next release can fix it.

[Perryg]

Given the type of work that was done to this release I think it would be advisable to post a ticket at bugtracker for this.

[mpack]

If you still get the driver verifier bugcheck with no GAs installed then it implies a change in the VM hardware. If you didn't make any change yourself then you should highlight this aspect in the bug report.

[RVTimO]

The only change that I did have that I know of is I upgraded the RAM on the host. I don't think I was able to change anything on the guest side. I had at one point tried to do 3D acceleration and boost video ram to 256Mb, but it wouldn't boot so I backed it down to 128Mb and then was back to normal. So it shouldn't be anything that changed at least that I can think of.

[Milardo]

Anybody that looked at my log have a reply?