Page 1 of 2
Windows 7 Ultimate x64 Guest Crashing
Posted: 23. Apr 2012, 05:39
by saberman
Host: Windows 7 Ultimate x64 with all important patches
VirtrualBox 4.1.12
Guest: Windows 7 Ultimate x64 with all important patches
I have posted:
https://www.virtualbox.org/ticket/10474
I stayed on VirtualBox 3.0.10 for a long time because all of my VMs were stable under it. (I tried 3.0.12 but the VMs kept crashing.)
I upgraded to 4.1.12 and my VMs crash when left running. I have attached the log files that cover the period of the latest crash and an analysis of the MEMORY.DMP file that windows produces.
The crash point varies. Some say: Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45a35 )
but others point to the ntfs module.
Again -- the VM was rock solid under 3.0.10.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 23. Apr 2012, 11:42
by mpack
You should attach a VM log to that ticket. The logs you have attached are VBoxSVC logs. Look in the "Logs" subfolder of the VM. Generally only the most recent log (showing the event) will be needed. The logs with names such as ".1" are from previous sessions.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 24. Apr 2012, 04:26
by saberman
I uploaded the correct log file that went with the memory dump analysis.
I also uploaded another pair of log file and memory dump analysis. The log file contented this at the point the guest rebooted:
00:03:10.547 RTC: period=0x20 (32) 1024 Hz
00:03:10.562 RTC: period=0x200 (512) 64 Hz
00:48:50.588 Changing the VM state from 'RUNNING' to 'RESETTING'.
00:48:50.652 CPUMSetGuestCpuIdFeature: Enabled APIC
00:48:50.652 CPUMSetGuestCpuIdFeature: Disabled x2APIC
00:48:50.652 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:48:50.670 PIIX3 ATA: Ctl#1: finished processing RESET
00:48:50.670 PIIX3 ATA: Ctl#0: finished processing RESET
00:48:50.670 Audio: set_record_source ars=0 als=0 (not implemented)
00:48:50.673 PDMR3Reset: after 20 ms, 1 loops: 1 async tasks - piix3ide/0
00:48:50.673 Changing the VM state from 'RESETTING' to 'RUNNING'.
00:48:50.676 Guest Log: BIOS: VirtualBox 4.1.12
00:48:50.676 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:48:50.679 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xe0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:48:50.679 PIIX3 ATA: Ctl#0: finished processing RESET
00:48:50.679 Guest Log: BIOS: ata0-0: PCHS=16383/16/63 LCHS=1024/255/63
00:48:50.679 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:48:50.679 PIIX3 ATA: Ctl#1: finished processing RESET
Does this: 00:48:50.588 Changing the VM state from 'RUNNING' to 'RESETTING'.
mean that VirutalBox initiated the reset or that VirutalBox detected the guest resetting?
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 24. Apr 2012, 11:50
by mpack
saberman wrote:I uploaded the correct log file that went with the memory dump analysis.
Take my word for it: if the VM process crashes then it's the VM log we are interested in seeing, not the host service log.
saberman wrote:Does this: 00:48:50.588 Changing the VM state from 'RUNNING' to 'RESETTING'.
mean that VirutalBox initiated the reset or that VirutalBox detected the guest resetting?
The latter: it means that it was the guest app which crashed (not the VM and not the host service process). To be precise there was a BSOD inside the Windows guest, which did an auto-reset to recover. If you turn off auto-reset inside the guest then you should see the cause of the BSOD.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 25. Apr 2012, 03:45
by saberman
>If you turn off auto-reset inside the guest then you should see the cause of the BSOD.
The memory dump analysis includes the bugcheck information which is all the BSOD gives you.
The point is this system was rock solid under VirtualBox 3.0.10. I installed VirtualBox 4.1.12, booted the OS, installed the extensions and the guest crashes after being idle for a while.
Can I uninstall the 4.1.12 extensions in my guests after I go back to 3.0.10 or do I have to do it under 4.1.12? The reason I ask is that I have installed the extensions on a number of VMs that I don't use very often and would just as soon wait until I need to use them before going through the uninstall process.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 27. Apr 2012, 20:58
by squall leonhart
saberman wrote:>If you turn off auto-reset inside the guest then you should see the cause of the BSOD.
The memory dump analysis includes the bugcheck information which is all the BSOD gives you.
The point is this system was rock solid under VirtualBox 3.0.10. I installed VirtualBox 4.1.12, booted the OS, installed the extensions and the guest crashes after being idle for a while.
Can I uninstall the 4.1.12 extensions in my guests after I go back to 3.0.10 or do I have to do it under 4.1.12? The reason I ask is that I have installed the extensions on a number of VMs that I don't use very often and would just as soon wait until I need to use them before going through the uninstall process.
they aren't interested in the bsod info, its the logging information of the actual virtual machine that matters to reproduce and find the issue then fix it.
btw, are you using the 1st release of 4.1.12 or the refresh release?
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 27. Apr 2012, 22:35
by saberman
r77245
>its the logging information of the actual virtual machine that matters to reproduce and find the issue then fix it
The logs -- which I have uploaded -- only show that the guest reset itself:
00:03:10.562 RTC: period=0x200 (512) 64 Hz
00:48:50.588 Changing the VM state from 'RUNNING' to 'RESETTING'
I have uploaded an analysis of the minidumps from BlueScreenView. The bugchecks occur in:
atapi.sys (five times)
ntoskrnl.exe (five times)
ndis.sys (two times)
Ntfs.sys (one time)
The bug check string is MEMORY_MANAGEMENT for all of the bug checks except the on in Ntfs.sys where it is NTFS_FILE_SYSTEM. The crashes have all occurred when the machine was unattended with just Outlook 2007 running.
Code: Select all
==================================================
Dump File : 042712-15406-01.dmp
Crash Time : 4/27/2012 12:35:11 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+1604
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042712-15406-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 042612-9093-01.dmp
Crash Time : 4/26/2012 8:04:24 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+16e4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042612-9093-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 042512-26375-01.dmp
Crash Time : 4/25/2012 1:17:48 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042512-26375-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 042412-9046-01.dmp
Crash Time : 4/24/2012 8:41:22 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+16e4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042412-9046-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 042412-35781-01.dmp
Crash Time : 4/24/2012 12:17:29 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00003452
Parameter 2 : 00000001`3ff00000
Parameter 3 : fffff700`0109fb30
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042412-35781-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 042312-8937-01.dmp
Crash Time : 4/23/2012 8:48:58 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042312-8937-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 042212-14687-01.dmp
Crash Time : 4/22/2012 12:55:40 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+1604
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042212-14687-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 042212-22500-01.dmp
Crash Time : 4/22/2012 12:25:56 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ndis.sys
Caused By Address : ndis.sys+88d1e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\042212-22500-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 041912-9359-01.dmp
Crash Time : 4/19/2012 12:34:27 AM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`03024c98
Parameter 3 : fffff880`030244f0
Parameter 4 : fffff880`01238c52
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+12c52
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\041912-9359-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 041912-22718-01.dmp
Crash Time : 4/19/2012 12:32:55 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ndis.sys
Caused By Address : ndis.sys+88d1e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\041912-22718-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 041812-9031-01.dmp
Crash Time : 4/18/2012 7:52:53 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+2a10
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\041812-9031-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 041712-11578-01.dmp
Crash Time : 4/17/2012 8:14:39 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\041712-11578-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
==================================================
Dump File : 041612-9203-01.dmp
Crash Time : 4/16/2012 7:32:37 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\041612-9203-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 268,472
==================================================
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 27. Apr 2012, 22:40
by saberman
The references in my prior posts to 3.0.x should have been to 3.2.x.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 27. Apr 2012, 22:51
by Perryg
What is your "V:" drive?
Also do you know whether the power management feature in the Windows guest has been disabled?
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 27. Apr 2012, 23:46
by saberman
The V: drive is a 465GB partition on the same physical disk as the C: drive. It contains everything assocated with VirtualBox including the .VirtualBox folder that is pointed to via a hard link.
>Also do you know whether the power management feature in the Windows guest has been disabled?
I am not sure. The balanced plan is selected in power options but it includes turning off the display after 10 minutes and that never happens.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 27. Apr 2012, 23:55
by Perryg
Well power management is a know problem in a virtual guest. Say it tries to spin down the virtual HDD or suspend. That can be a major reason for intermittent problems. I let the host take care of these things but even at that spinning down a drive on the host can effect the guest.
Now should it work with power management? Probably but in all reality it doesn't (not for me anyway). I don't have these issues on any of my set ups and I have hundreds. All of them only use blank screen and user lock if unattended. Add to that where you say it always happens when unattended, this is where I would focus.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 28. Apr 2012, 00:52
by saberman
This guest has had the same settings since it was originally built a couple of years ago.
However, I will try turning them off.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 1. May 2012, 22:52
by saberman
I turned off all power monitoring. Set display to never turn off and disk to never spin down.
The system is still crashing. However, the VMs fail in two different modes:
1. If the VM is minimized it hits a memory bugcheck.
2. If the VM is open and the display is set to full screen it locks up. That is it freezes completely requiring a reset. No dump occurs.
I tried pausing the VM and then unpausing it. All that happened was the display became speckuled. I then reset the VM.
As you can see from the log there isn't anything up until I paused the VM which was already hung:
00:22:12.193 RTC: period=0x100 (256) 128 Hz
00:22:12.202 RTC: period=0x20 (32) 1024 Hz
00:22:12.217 RTC: period=0x200 (512) 64 Hz
04:13:25.668 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
04:13:25.862 PDMR3Suspend: 193 939 374 ns run time
04:13:25.862 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
04:13:29.896 Changing the VM state from 'SUSPENDED' to 'RESUMING'.
04:13:29.897 Changing the VM state from 'RESUMING' to 'RUNNING'.
04:13:29.920 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000bdf0000 w=1024 h=768 bpp=0 cbLine=0x400, flags=0x1
04:13:37.942 Changing the VM state from 'RUNNING' to 'RESETTING'.
04:13:37.975 CPUMSetGuestCpuIdFeature: Enabled APIC
04:13:37.975 CPUMSetGuestCpuIdFeature: Disabled x2APIC
04:13:37.975 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
04:13:37.994 AHCI ATA: Ctl: finished processing RESET
04:13:37.994 AHCI ATA: Ctl: finished processing RESET
04:13:37.994 PIIX3 ATA: Ctl#1: finished processing RESET
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 5. May 2012, 03:53
by saberman
Tried 4.1.14 with the same results.
I am a little surprised that no one else is reporting this problem. I have had it with two Windows 7 Ultimate x64 VMs with different software installed and a Windows 7 Professional x64 VM that had Visual Studio 6 installed but not used and was being used to connect via a VPN to a machine at an office. The problem was consistent. If a VM was left idle for an extended period it hit a memory bugcheck.
Anyway, I have reverted to 3.2.10 and my VMs are happy again. I can leave them running minimized all night without a problem.
Re: Windows 7 Ultimate x64 Guest Crashing
Posted: 28. May 2012, 21:04
by saberman
Tried 4.16 -- Same problem -- same crash in atapi.sys
Additional idtem: The VMs are running on the same Windows Ultimate x64 host and the VB GUI is in use. The machines are idle and minimized when the crash occurs.