Windows 7 guest aborted when switching to/from full-screen

[sgp]

I just set up a brand new Windows 7 32-bit guest OS using VirtualBox 4.2.6.r82870.
The VM was working great through all windows patching steps, installing guest add-ons, etc.

But, as soon as I felt like things were looking good and I decided to switch to full-screen, the VM stopped ("Oracle VM Virtual Box Manager has stopped working" <Close program>), then in the Oracle VM VirtualBox Manager host window the VM shows a status of "Aborted". (log file attached)
A couple other times I managed to get switched to full-screen, but then when switching out the same "aborted" result occurred.

The last line in the attached log file is:
16:48:28.606524 VMMDev::SetVideoModeHint: got a video mode hint (2048x1152x0) at 0

This aborted problem is consistently happening when I switch to/from full-screen mode.

More information:
Host: Windows 7 64-bit 24 GB RAM (Intel i7 930 processor, 4 cores/8 threads)
Guest: Windows 7 32-bit 4 GB RAM (2 processors) (video memory 90 Mb, 2 monitors, no acceleration enabled)

Possible workaround:
I did a quick test where I removed the 2nd monitor setting from the VM and so far, switching in and out of full-screen appears to be working... I also tried testing the VM with a single processor, but that did not seem to make a difference.

Any ideas? I really need both of my monitors to work in this VM.

Related Notes:
1) I have another similar guest VM that I set up initially with an earlier version of VirtualBox (not sure the version at the time, created June 2012) which was already set to run in full-screen mode when I installed this version of VirtualBox and it is working fine. (Also a Windows 7 32-bit VM)
2) I had this exact same problem with another brand new Windows 7 64-bit guest yesterday, but I thought 64-bit might have been causing the problem so I blew it all away and rebuilt the system as 32-bit... but, the same thing is happening. So, crossing my fingers and reporting this here.

Thank you!

[mpack]

If you have a repeatable bug then the best thing is to raise a BugTracker ticket for it.

[sgp]

Thanks for the Bug Tracker suggestion. I looked there and believe I found an existing bug that covers my situation. (Ticket #11247)

I also believe I've found a workaround which may relate to why my older VM is not experiencing this problem.
Workaround Steps:
1) Shutdown the VM.
2) Change the VM to only have one monitor.
3) Start the VM and login.
4) Switch the VM to fullscreen (Host+F).
5) Shutdown the VM.
6) Add a second monitor
7) Start the VM and (in the case of Windows) configure the second monitor using the Screen Resolution control panel.

RESULT:
From now on both of my monitors are running in full screen and I have not yet experienced a crash after restarting, etc. (although I admit, I have only dared to try switching out of full screen a couple times)