VB resizes video then locks up
Posted: 9. Mar 2018, 00:57
Greetings:
I've got an issue that only affects my WIndows 10 VB, never my Windows 7 or Linux VB's. The issue is that, out of the blue, the video display is resized down to 640x480 and the session seems completely locked up. I've found no method for recovery, just 'Power off the machine' and start over.
My host is a Windows 10 Home x64 OS on an MSI 350 Tomahawk motherboard running an AMD Ryzen 1700x Eight-Core processor with 16GB RAM. VB is version 5.2.8. The VB is configured as Windows 10 Pro x64, 4GB RAM, two threads, single monitor (the VB runs on a second host monitor) w/128MB Video Memory.
This VB will always do the same little video resizing trick at start-up, but restoring the maximized window and maximizing it again returns it to normal maximized status. This does not help at all when the actual issue occurs.
I'm attaching the latest log to this post. In the log, at 02:39:27.639407 is where I think the issue starts (obviously the VB has been running a bit). I 'restore/maximize' again, then 'Power off the machine' to get back to work.
As usual, it's likely something very stupid in my config, but I see nothing.
Thanks for any and all assistance!!
I've got an issue that only affects my WIndows 10 VB, never my Windows 7 or Linux VB's. The issue is that, out of the blue, the video display is resized down to 640x480 and the session seems completely locked up. I've found no method for recovery, just 'Power off the machine' and start over.
My host is a Windows 10 Home x64 OS on an MSI 350 Tomahawk motherboard running an AMD Ryzen 1700x Eight-Core processor with 16GB RAM. VB is version 5.2.8. The VB is configured as Windows 10 Pro x64, 4GB RAM, two threads, single monitor (the VB runs on a second host monitor) w/128MB Video Memory.
This VB will always do the same little video resizing trick at start-up, but restoring the maximized window and maximizing it again returns it to normal maximized status. This does not help at all when the actual issue occurs.
I'm attaching the latest log to this post. In the log, at 02:39:27.639407 is where I think the issue starts (obviously the VB has been running a bit). I 'restore/maximize' again, then 'Power off the machine' to get back to work.
As usual, it's likely something very stupid in my config, but I see nothing.
Thanks for any and all assistance!!