virtualbox.org

I've been trying the various tips that I've found to fix this problem that seems fairly common.

Virtual box doesn't get past the boot screen - "Windows failed to start. a recent hardware or software change might be the cause"

Windows 7 (64 bit) - VirtualBox 4.2.1 - Bootcamp on Snow Leopard 10.8.2

I have no problem booting from the windows partition normally.

I've now tried:

chmod a+rw
setting the 'SSD' box on the SATA controller - some advice recommends using IDE, but it is grayed out.


I'm just wondering if it might be a problem with the new macbook pro (mid-2012) which has the SSD and no CD or DVD drive.

Has anybody got VirtualBox working with this?

If so, please, what is the secret that I'm missing?

Sorry, I just realised that I should have said 'Mountain Lion' 10.8.2 - I'm not sure what made me say 'snow leopard'.

This might be why nobody has said anything...

I've still had no joy getting this to work. I'd love any suggestion as to how to get Windows 7 to complete it's bootup successfully..

Some information on the failure.

All you have stated is that something is broke.

wait state (Black Screen Of Death) code? potentially 0000007B?

going into loop?

Configuration?

VirtualBox does not run bootcamp directly. You need to do preparation work first.

Thank you for the response!

I'm afraid that there is no number given on the black screen of death - the only number is a count-down to it trying again.

fustbariclation wrote:I'm afraid that there is no number given on the black screen of death - the only number is a count-down to it trying again.

And if you do nothing? Does it keep repeating?

Most people/persons call that looping.


You need to press F8 (fn-F8 depending on . . . ) while the countdown is happening.
Select Disable automatic restart on system failure
then, depending on your version of windows, allow the machine try one more time.

You should have selected that option inside of Windows 7 (steps vary depending on windows version)

• Select Start
  Select Computer
  Select System Properties (in the menu bar)
  Select Advanced system settings (om the left)
  in the third block labeled Startup and Recovery, punch button Settings
  under System failure, unCheck Automatically restart
  Punch OK
  Punch OK on the returning panel/pane/window

If you have not already done so, you might want to review "How to Use a MacOS Bootcamp Partition as a VirtualBox Guest" Under Board Index->General->Other. This describes the steps to enable setting up a VBox Guest on a Bootcamp partition containing Windows 7.

Hello,

I think I've a similar problem with Windows 7 on my Mac Pro (10.8.2) with VirtualBox 4.2.6

I downloaded Windows 7 set of files from Microsoft in order to make test with IE8 from Windows 7.

All downloaded files are in rar format and generate Win7_IE8.vhd file when uncompressed.

Then, I created a new virtual machine (Windows 7 or Windows 7 (64 bits) with same result) and I get failure message

Windows failed to start. a recent hardware or software change might be the cause

The system suggests a repair process but it failed too with following diagnostic

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200538
Problem Signature 05: AutoFailover
Problem Signature 06: 7
Problem Signature 07: CorruptAcl
OS Version : 6.1.7600.2.0.0.256.1

Dan

Hello,

I solved my problem by moving the VHD file from SATA to IDE in Storage settings.

Before the message displayed in previous post, I had this one at the beginning (blue screen) :

A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check for viruses on your computer. Remove and newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated.

Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Technical information:

*** STOP: 0x0000007B (0x80786B58 0xC0000034 0x00000000 0X00000000)

Dan