virtualbox.org

I am using the final version of Windows 7 Prof. 64 Bit. I tried to run Vbox 3.0.6 and then 3.0.8 both clean installs. When I launch it, the screen goes blue directly with: DRIVER IRQL LESS NOT EQUAL

(Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000000, 0xfffff80002e880b6). Ein volles Abbild wurde gespeichert in: C:\Windows\MEMORY.DMP. Berichts-ID: 102309-24460-01)

The file memory.dmp is unfortunately not existing.

What shall i do?

ferrari987

Where did you get that disc from? I have W7 Pro RTM (MSDN release) running without problems. It installed on 3.0.6 without a sweat and boots just fine on 3.0.8. Something is wrong on your end, not VB's. Also check the settings, you might not have the needed settings or hardware for 64 bit guests (see the manual and VirtualBox FAQ).

I agree. Both 3.0.6 and 3.0.8 run fine on the RTM version of Windows 7 Pro x64.

I have the final version, not RTM, downloaded from MSDN. My cpu is Q6600 and I did not touch the BIOS settings. It used to run fine under Vista 64Bit. Any suggestions, I've read FAQ but nothing appeared to solve my issue.

ferrari987

Then read the Forum Posting Guide and give us some more information. And fyi, RTM means Release to Manufacturer, aka final.

Sorry for this confusion, which additional information should I provide?

Thanks for your help,

ferrari987

Did you read the guide or not? It's described there what we need.

Sorry, I searched the forum for my issue, but there was no success.

There are no Guest OS present, because I cannot even get the program to start. The .log file is also empty, the only error code is given in the Windows Event Log: IRQL_NOT_LESS_EQUAL
As stated above I use the latest version of Windows 7 x64 and VirtualBox 3.0.8., starting with administrive rights did not solve the problem, all network drivers were installed successfully.

While reading some other opening post, I feel that my information provided is superior to a fair amount of other posts, so please tell which if there are any more details missing.

You could give the VM settings for example. The Host CPU capabilities. If it's 32 bit or 64 bit. That kind of information.
The installer could crash if you don't have the right hardware for 64 bit Guests. It's in the manual and VirtualBox FAQ.

Windows Bugchecks are usually due to driver issues, or trying to map protected memory.
Just to be clear you can not install VirtualBox, or you can not install a guest?

It is like the following. Installation process goes through smoothly, no problems. The Blue Screen appears 1.Sek after trying to start VirtualBox. My CPU is the Q6600 (has VT).

As you should have read, there are no VM settings, since the program does not even start.

Thanks for your help.

ferrari987

Now do you have XPmode in this copy of Windows 7?
If so I don't think you can run them at the same time. You would need to turn off XPmode before you run VBox.

Nope, no XP-Mode running, not even installed yet.

Thanks for your support.

ferrari987

Something is making Windows really unhappy. That is the reason for the bugcheck.
Tell you what, let's try uninstalling VirtualBox, then reboot Windows.
Then do the install again and this time right click on the install and left click on run as admin.
Watch the screens very closely and note any errors. Always answer to the affirmative on any question that is asked.
Then before you try to use VirtualBox reboot the PC again (Windows loves to be rebooted).
Then see if it will work.

Please create a ticket on our bug tracker and attach the VBox.log of the session and the minidump. After a blue screen you usually get a popup after logging in the next time. That dialog should tell you where the minidump file was saved. Thanks.