VirtualBox

Ticket #16004 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Windows 7 guest crash blue screan

Reported by: duchamk Owned by:
Component: host support Version: VirtualBox 5.1.6
Keywords: Cc:
Guest type: Windows Host type: Linux

Description

After the upgrade to version 5.1.2, 5.1.4 and 5.1.6 from 5.0.26 guest OS win7 shortly after startup crash and shows blue screen.

After returning to version 5.0.26 guest OS windows 7 works properly.

Attachments

VBox.log Download (134.1 KB) - added by duchamk 6 years ago.
VBox.log
VBox_5.1.8.log Download (134.1 KB) - added by duchamk 6 years ago.
VBox_5.1.10.log Download (134.7 KB) - added by duchamk 6 years ago.
VBox 5.1.10 log

Change History

Changed 6 years ago by duchamk

VBox.log

comment:1 Changed 6 years ago by FelipeS11

Hi, I have the same issue. My problem was that I have Hyper-v installed. If you have the Hyper-v installed you need to unable the Hyper-v. You can use the following command: on CMD run: C:\windows\system32> bcdedit /set hypervisorlaunchtype off and reboot your machine.

This worked for me. I will report this in another ticket... (I'm sorry for my english)

comment:2 Changed 6 years ago by duchamk

Hi, thanks for your help. I tested solution, but unfortunately in my case it did not work.

Can you give the ticket number that you reported?

comment:3 Changed 6 years ago by frank

Any improvement with VBox 5.1.8?

Changed 6 years ago by duchamk

comment:4 Changed 6 years ago by duchamk

Version 5.0.28 is working properly.

Version 5.1.8 shortly after startup crash and shows blue screen. Log attached.

Changed 6 years ago by duchamk

VBox 5.1.10 log

comment:5 Changed 6 years ago by duchamk

Version 5.0.30 is working properly.

Version 5.1.10 shortly after startup crash and shows blue screen. Log attached.

Sometimes, you can login but it ends up after some time the blue screen. On the blue screen is the text : IRQ_NOT_LESS_OR_EQUAL.

comment:6 Changed 6 years ago by duchamk

After raising version 5.1.14 I tested all possible settings. It helped change the amount of CPU 2 to 1.

In 5.1.16 still work properly.

Please close.

comment:7 Changed 6 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Thank you for the information!

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use