Re: Windows 8?
Posted: 3. Jul 2012, 18:43
I think I know the source of the crash, looking onto the way to fix it now..
Looks like I have some problems with core dump, since nothing appears on cores folder when OSX crashes totally.. (naturally killing virtualbox manually will make coredump file). Looks like panic file OSX generates automatically is bit empty, or is it so?misha wrote: I bet this is Intel GPU - specific stuff..
Assuming you encounter VBox host process crash, could you create a core dump for your crash, and attach it here?
Also you've mentioned earlier you were getting guest BSOD when running with 3D disabled. Could you also try whether this issue is still valid for the latest test build you're using?
We've fixed the BSOD issue you observed while additions update.Perryg wrote:I have been able to restore from backup. I tried and tried to figure it out but it is just not happy with my build. I see there were a few more changesets later this day and am compiling against them now. but the whole driver error and something about the file being changed that is making Windows mad is beyond reprehensible and has almost always results in a re-install for me to make it happy. As scotty says the more MS tries to improve the darned thing the easier it is to muckup the plumbing. (well slight change in wording)
Btw, I've also noticed that windows explorer may crush while guest additions (wddm driver in particular) update/uninstall.Perryg wrote:I have been able to restore from backup. I tried and tried to figure it out but it is just not happy with my build. I see there were a few more changesets later this day and am compiling against them now. but the whole driver error and something about the file being changed that is making Windows mad is beyond reprehensible and has almost always results in a re-install for me to make it happy. As scotty says the more MS tries to improve the darned thing the easier it is to muckup the plumbing. (well slight change in wording)
No, what I'm seeing here is that after wddm driver uninstall the explorer.exe process terminates, i.e. no taskbar, desktop icons, <win>+hotkey support until explorer.exe is manually started.Perryg wrote:..I did notice a flicker during the video driver install but this has always been the case IIRC. Is that what you were talking about when you said explorer crash?
Ah! Haven't seen that one *yet. Maybe difference in host? Mine is Linux.misha wrote:No, what I'm seeing here is that after wddm driver uninstall the explorer.exe process terminates, i.e. no taskbar, desktop icons, <win>+hotkey support until explorer.exe is manually started.Perryg wrote:..I did notice a flicker during the video driver install but this has always been the case IIRC. Is that what you were talking about when you said explorer crash?
Is the flickering you saw while winsat run also gone for you btw? You could test it by manually running "winsat d3d" from an elevated console.Perryg wrote:You have nailed this one misha. Worked great..
I'm mostly on Windows host, but I'd guess the host type should not matter..Perryg wrote:Ah! Haven't seen that one *yet. Maybe difference in host? Mine is Linux.
Then I am truely blessed since I have not encountered this one.misha wrote:I'm mostly on Windows host, but I'd guess the host type should not matter..Perryg wrote:Ah! Haven't seen that one *yet. Maybe difference in host? Mine is Linux.
Yes no flickering when running "winsat d3d" lots of errors and performance test is poor, but it works.misha wrote:Is the flickering you saw while winsat run also gone for you btw? You could test it by manually running "winsat d3d" from an elevated console.Perryg wrote:You have nailed this one misha. Worked great..
Most of those warnings are ok, I'll have a look into the reason of the "invalid format" warning, as well as will make sure non-critical warnings do not get printed,Perryg wrote:Yes no flickering when running "winsat d3d" lots of errors and performance test is poor, but it works.
Test results attached: