VB all the time resize screen on double click
Posted: 28. Mar 2011, 13:41
Hardware: Dell Precision M4500 | Core i5 | nVidia Quadro FX 880 | 4Gb RAM
Operating System: Windows 7 x64
Guest: Winndows Server 2008 R2 x64
Guest settings: 2004MB, VT-x/AMD-V: ON | 2CPU's | Video: 96MB, 2D: ON 3D: ON
Until friday worked VB excellently. I save virtual machine state and suspend my computer. Today morning i woke up my computer and start up my virtual machine. No changes i made. But i have big troubles with VB window. If in guest machine i use double click or if i change some dialog/window size or change dialog/window position, VB change screen size. From fullscreen mode jump into no fullscreen maximized mode. Window is completly black. Another double click or resize change VB visible again, but maximized and with toolbar. Another double click change VB window mode lightly smudgy and without toolbar. Another double click again sharp and with toolbar. This blinking is terrible. I tried uninstall VB, delete virtual machine and create new one (with my old disks), update my graphic drivers, reboot operating system. Now i don't know what i can do more. Any idea where could be a problem? Thanks
Thats my log:
Operating System: Windows 7 x64
Guest: Winndows Server 2008 R2 x64
Guest settings: 2004MB, VT-x/AMD-V: ON | 2CPU's | Video: 96MB, 2D: ON 3D: ON
Until friday worked VB excellently. I save virtual machine state and suspend my computer. Today morning i woke up my computer and start up my virtual machine. No changes i made. But i have big troubles with VB window. If in guest machine i use double click or if i change some dialog/window size or change dialog/window position, VB change screen size. From fullscreen mode jump into no fullscreen maximized mode. Window is completly black. Another double click or resize change VB visible again, but maximized and with toolbar. Another double click change VB window mode lightly smudgy and without toolbar. Another double click again sharp and with toolbar. This blinking is terrible. I tried uninstall VB, delete virtual machine and create new one (with my old disks), update my graphic drivers, reboot operating system. Now i don't know what i can do more. Any idea where could be a problem? Thanks
Thats my log:
00:13:15.946 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:13:18.280 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000cec0000 w=1920 h=1135 bpp=32 cbLine=0x1E00, flags=0x1
00:13:18.280 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:13:18.479 2D is supported!
00:13:18.495 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:57:44.000 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000cec0000 w=1920 h=1135 bpp=32 cbLine=0x1E00, flags=0x1
00:57:44.181 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:57:44.832 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:57:47.998 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000cec0000 w=1920 h=1135 bpp=32 cbLine=0x1E00, flags=0x1
00:57:47.998 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:57:48.099 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:57:48.130 VMMDev::SetVideoModeHint: got a video mode hint (1920x1200x0) at 0
00:57:48.243 Guest Log: VBoxDisp[0]: VBVA enabled
00:57:48.243 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000cec0000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
00:57:48.245 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
00:57:48.245 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000cec0000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
00:57:48.330 2D is supported!
00:57:48.345 OpenGL Warning: !!!FAILED!!! Render SPU: SetWindowPos (e064c, 0, 0, 0, 0)
But only one week. After that the problem is back. 
This problem isn't depend on type of VM. I try create new blank VM and problem with double click is evident already during bios loading. This time the problem occured after installation new windows update on physical machine and rebooting system. But i can't exactly say if really exist any connection. That's the last thing what i did before problem in VM occured.