[vbox-dev] Host BSOD after r49150 and r49151

llyzs llyzs.vic at gmail.com
Mon Oct 21 09:00:17 UTC 2013


Hi Ram,

Thanks for you response. I attached logs to you off the list to avoid
traffic. I am using Win2008R2SP1 as host. The host went into BSOD always at
a definite point. For an installed win7 guest, the host BSOD when the guest
win7 boot screen just appeared at 1024x768 but the windows logo not yet
appear. For an empty VM booting into Win7 installation CD, the host BSOD
exactly when the setup finished the first copy phase in text mode (a text
progress bar at the bottom of the screen) and before it went into graphics
mode.

The last guest log entry seems to be always

00:00:05.122349 Display::handleDisplayResize(): uScreenId = 0,
pvVRAM=00000000081a0000 w=1024 h=768 bpp=24 cbLine=0xC00, flags=0x1

Best regards,

Vic


On Mon, Oct 21, 2013 at 4:42 PM, Ramshankar <
ramshankar.venkataraman at oracle.com> wrote:

> On 10/21/2013 09:51 AM, Ramshankar wrote:
>
>> Which host are you using exactly? Could you attach a VBox.log for a VM
>> you start that causes the BSOD?
>>
>> Also how quickly does it BSOD?
>>
>
> Nevermind I re-read and see that you already answered the 2nd question.
> Just attaching the VBox.log would be helpful.
>
> Regards,
> Ram.
>
>
>  Regards,
>> Ram.
>>
>> On 10/20/2013 07:34 AM, Vic Lee wrote:
>>
>>> Hi there,
>>>
>>> Recently when I updated to latest SVN tree I found out that my host
>>> (yes, the host, not guest) always BSOD whenever I try to start any VM
>>> with more than 1 vCPU. This kind of BSOD is so weird, that there's no
>>> bug check code or minidump whatsoever, only a bluescreen with some texts
>>> saying things like "Hardware Malfunction" (google "BSOD hardware
>>> malfunction" for images and you will see what I mean). So I can't tell
>>> which source line exactly is causing it. I managed to confirm the
>>> following:
>>>
>>> 1. It happens only after r49150 and r49151 (which should be the same
>>> changeset). If I stay at revision r49149 it's ok.
>>> 2. It happens only if I use more than 1 vCPU in the guest. Everything
>>> seems to be fine if I change the VM to use 1 vCPU.
>>> 3. I tried to boot a windows 7 installation CD in a newly created VM,
>>> but the host still BSOD (as long as condition 1 and 2 are met), just
>>> before the setup ran into graphic mode. So it should have nothing to do
>>> with guest OS.
>>>
>>> Anyone is aware of this or trying to fix it?
>>>
>>> Thanks,
>>>
>>> Vic
>>> Anyone is aware of this or trying to fix it?
>>> ______________________________**_________________
>>> vbox-dev mailing list
>>> vbox-dev at virtualbox.org
>>> https://www.virtualbox.org/**mailman/listinfo/vbox-dev<https://www.virtualbox.org/mailman/listinfo/vbox-dev>
>>>
>>
>> ______________________________**_________________
>> vbox-dev mailing list
>> vbox-dev at virtualbox.org
>> https://www.virtualbox.org/**mailman/listinfo/vbox-dev<https://www.virtualbox.org/mailman/listinfo/vbox-dev>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.virtualbox.org/pipermail/vbox-dev/attachments/20131021/a0eade53/attachment.html 


More information about the vbox-dev mailing list