Windows 7 SP1 x32 reboots after some time when x64 guest is runs

[McSim]

Hi, Environment:

Version of VirtualBox installed - 4.2.6 r82870 Type and version of the Host Operating System - Windows 7 Ent SP1 x32 Type and version of the Guest OS - Windows 2k8 R2, RHEL6 x64

Problem: I installed the guest OS (Win 2k8 r2). I have run the guest OS. My host is rebooted after a while. This problem is found in the previous version VB (4.2.4). This problem was not only in Win x64, in RHEL x64 too.

Attempted Resolutions: I try to reinstall guest OS. I try to change settings guest machine (more memory, en\dis IO APIC). When host restarted minidump-file not created. I try to change settings to create full-dump, but it does not work. dump-file not created.

[McSim]

log file Win 2k8 r2

[McSim]

Additionally, I checked my host HDD and memory. No error. x32 guest OS worked many time without error or reboot host.

[MikeInMaine]

I think I'm seeing the same thing.

Host: Windows 7 sp1 32bit. VM: Windows 7 sp1 64bit. Host reboots without any update to Windows logs shortly after starting VM.. but not always. Has happened twice in last day. VB 4.2.6

[Mihai Hanor]

Mc.Sim: Disable Trusted Execution in the host's BIOS and try again.
MikeInMaine: Attach a VM log.

Both of you should try to disable the OS "automatic reboot on system failure" option. It may still be a BSOD. ​http://www.evga.com/support/faq/afmviewfaq.aspx?faqid=59175

[McSim]

NO in BIOS

[McSim]

Disable auto restart

[McSim]

Replying to mhanor:

Mc.Sim: Disable Trusted Execution in the host's BIOS and try again.

I don't have that parameter in BIOS: Att DSC_0792.jpg May be this option is "Data Execution Prevention"?

Both of you should try to disable the OS "automatic reboot on system failure" option. It may still be a BSOD. ​http://www.evga.com/support/faq/afmviewfaq.aspx?faqid=59175

Automatic restart were disabled before. But BSOD is not show and minidump-file not created. Only restart host at this time. Att auto_restart.PNG

[McSim]

Today my host-system reboots again.

[McSim]

today log after reboot

[McSim]

After last reboot ( VBox.2.log ), I noticed that the corrupted filesystem inside the VM. And VM was terminated.

[McSim]

After that. I try to run the vm, but host-system reboots again.

[Mihai Hanor]

What laptop model are you using?

[McSim]

HP Elitebook 8400p (p\n VQ667EA#ACB)

[McSim]

P.S. ​http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02030597&prodSeriesId=4095872

[Mihai Hanor]

Have you read this, on how to enable/disable Trusted Execution? ​http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02620201/c02620201.pdf

[McSim]

This doc do not accept for my nout. And TXT on this laptop is turned off by BSU (BIOS Config Util). Support service helped me to understand how work Disable TXT ))) This technology was disabled before.

[Mihai Hanor]

If TXT is disabled, I would expect MSR_IA32_FEATURE_CONTROL to be 5, no 7, as seen in your logs.

[McSim]

Hmm .. Very strange ... I have not changed the configuration (only did exports). When I saw export config - TXT parameter was Disable. (maybe I accidentally changed something in the settings ...)

Now I am sure that TXT off. Next I will observe the work and if anything, I will write about the problem and will put the log here ....

[Mihai Hanor]

When changing the VT-x/TXT options, the CPU must power down in order to reinitialize the IA32 Feature control MSR. If the BIOS config tool doesn't do it, you must do it, by shutting down the laptop.

[McSim]

today my laptop again crashed. Log attached

[McSim]

Forgot to clarify - Power Off was done. To be sure the battery and the power cord has been removed.

[mickmm]

I'm having the same problem:

Host: Windows 7 x32

Guest: Fedora 14 x64, Windows server 2008 R2, Fedora 16

In all cases, the host reboot without blue screen of death. I haven't found any solution yet.

[McSim]

Today I updated VirtualBox to last version 4.2.10 r84104. I tried to install Debian x64 after that. But after some time my host crashed again. :(((

[McSim]

Debian x64 on Windows 7 x32.

[McSim]

Please, help me for resolve the problem.

[Mihai Hanor]

Do you have other virtualization software installed, such as Windows XP Mode or Virtual PC?

[McSim]

No, I have not installed any other virtualization. From Virtualized vendors I have installed VMware Converter and vSphere Client 5.1. But this bug was before install Vmware's utils.

[Mihai Hanor]

I find it strange that the IA32_FEATURE_CONTROL MSR is 7, in most of your logs. Maybe there is a BIOS bug. Do you use suspend-to-RAM, to put your laptop to sleep, or do you use the regular shutdown option?

If you have a firewire port, you could use it to set up a remote kernel debugging session, to see if that gives you any clues.

Also, could you post a listing of loaded drivers? You can use livekd or Autoruns, from Sysinternals.

[McSim]

I find it strange that the IA32_FEATURE_CONTROL MSR is 7, in most of your logs. Maybe there is a BIOS bug.

Maybe... But how can I fix this fact?

Do you use suspend-to-RAM, to put your laptop to sleep, or do you use the regular shutdown option?

Yes, I use sleep function very often. But I use shutdown option from time to time (maybe once in the two or three days).

If you have a firewire port, you could use it to set up a remote kernel debugging session, to see if that gives you any clues.

Now I don't have other PC to connect over firewire port. ( Maybe I will have other PC - 1 April, but I didn't work with debugging never . Can you give me howto-link? I'll be very grateful.

Also, could you post a listing of loaded drivers? You can use livekd or Autoruns, from Sysinternals.

List drivers attached.

[McSim]

Drivers in AutoRuns-file format (File-Save...) and in zip

[Mihai Hanor]

Replying to Mc.Sim:

I find it strange that the IA32_FEATURE_CONTROL MSR is 7, in most of your logs. Maybe there is a BIOS bug.

Maybe... But how can I fix this fact?

Do you use suspend-to-RAM, to put your laptop to sleep, or do you use the regular shutdown option?

Yes, I use sleep function very often. But I use shutdown option from time to time (maybe once in the two or three days).

You can't fix it, but you can report it to the manufacturer and get them to fix it. But first, you have to do some investigations. Download the RW utility from rweverything.com, use it to monitor the IA32_FEATURE_CONTROL MSR. You'll have to add it to the MSR User list (add the 0x3A value). Make sure TXT is off, in BIOS. First, shutdown the laptop, then start it again and never reboot it, until I mention so. After the OS has loaded, check the MSR value using that tool. All CPU cores must have the same value, 0x5. Now, put the laptop to sleep. Wake it up, check the MSR value, it should be unchanged. You can try another sleep/wake cycle and check the MSR value. Next is the first laptop reboot, followed by a sleep/wake cycle. Check the MSR value.

If you have a firewire port, you could use it to set up a remote kernel debugging session, to see if that gives you any clues.

Now I don't have other PC to connect over firewire port. ( Maybe I will have other PC - 1 April, but I didn't work with debugging never . Can you give me howto-link? I'll be very grateful.

​http://msdn.microsoft.com/en-us/library/windows/hardware/ff556866%28v=vs.85%29.aspx
On the host, you'll have to install the Windows Debugging Tools, which are a part of the Windows Software Development Kit (SDK) or the Windows Driver Kit (WDK). It's important that the host (the PC that is remotely debugging the laptop) is using the corect symbols. I use the MS Symbol Server:
​http://support.microsoft.com/kb/311503

[McSim]

Replying to mhanor:

You can't fix it, but you can report it to the manufacturer and get them to fix it. But first, you have to do some investigations. Download the RW utility from rweverything.com, use it to monitor the IA32_FEATURE_CONTROL MSR. You'll have to add it to the MSR User list (add the 0x3A value). Make sure TXT is off, in BIOS. First, shutdown the laptop, then start it again and never reboot it, until I mention so. After the OS has loaded, check the MSR value using that tool. All CPU cores must have the same value, 0x5. Now, put the laptop to sleep. Wake it up, check the MSR value, it should be unchanged. You can try another sleep/wake cycle and check the MSR value. Next is the first laptop reboot, followed by a sleep/wake cycle. Check the MSR value.

Sorry for the long silence. Today I created new support ticket 4644731726 in HP for that problem. I sent them screenshot RW utility. When I reboot laptop (Next is the first laptop reboot) , 0x3A value changed to all zero. Next I will keep informed of further developments.

​http://msdn.microsoft.com/en-us/library/windows/hardware/ff556866%28v=vs.85%29.aspx
On the host, you'll have to install the Windows Debugging Tools, which are a part of the Windows Software Development Kit (SDK) or the Windows Driver Kit (WDK). It's important that the host (the PC that is remotely debugging the laptop) is using the corect symbols. I use the MS Symbol Server:
​http://support.microsoft.com/kb/311503

The debug I did not do. I don't have many components for debug (time,other firewire host, firewire cable, knowledge and other ))) )

[McSim]

HP's technical support say that this problem is Microsoft products. (((

[Mihai Hanor]

What MS product? Windows? Ask them to explain how is it Windows at fault.

[McSim]

What MS product?

MS Win7 Ent

Ask them to explain how is it Windows at fault.

Unfortunately, I closed ticket. And I get new license for Vmware Workstation, and soon I reinstall Win from x32 to x64.

Thank you very much for your help.

[Frank Mehnert]

I'm quite sure this is a duplicate of #11979. Please try the test build which I provided in #11979 and report success or failure there. Thank you!