virtualbox.org

---

[ModEdit; related ticket: #17590: Freezing every time a BSOD appears on Windows 10 guest]

---

I am running the latest VirtualBox and every time a bsod appears in a Windows 10 guest.it will also freeze and every time I reset the machine It also freezes on the windows boot screen until I reopen the VM. The ticket number is 17590.

Windows 10 is the guest

Host: MacOS 10.13.4, build 17E199
Guest: Windows 10, 1709, build 16299.371
VirtualBox: 5.2.10, r122088

Neptune BSC wrote:every time a bsod appears

Where? Host? Guest? Both?

Neptune BSC wrote:Windows 10 it will also freeze

Is Win10 your host? Guest? Both?

Neptune BSC wrote:every time I reset the machine I also freeze until I reopen the VM.

I can't even understand what that means.

Neptune BSC wrote:The ticket number is 17590.

Thank you for including that! I will update your first post to reflect that.

Now, you need to be a lot more descriptive as to what's going on. Start with complete and detailed versions about your host, guest, and VirtualBox. Example:

• Host: OSX 10.11.6, build 15G1611
• Guest: Windows 10, 1703, build 15063.726
• VirtualBox: 5.2.11, r122202

Then describe a step-by-step process of what you're doing, what happens, the conditions under which it happens, if it's always reproducible or only sometimes, any peripherals you have connected (USB, HDs, monitors, other), if you're using any peripherals when this happens, and everything/anything else that might help us.

We're also going to need to see a VM log from a complete VM run:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

This is not Twitter, you can use more than 128 characters to describe the problem. The more details we have, the better we could help you.

Windows 10 is my guest.

Host: MacOS 10.13.4, build 17E199
Guest: Windows 10, 1709, build 16299.371
VirtualBox: 5.2.10, r122088

I asked you a gazillion questions, and you come back with a log? Look, we're not going to go far if you keep on doing that. I told you I need details, I can't be reading the tea-leaves.

So, read my post again. I expect to see an answer to each and every question in there, if you want this thread to have a future. I'm not going to be reading other people's minds, I'm not good at it.

The VM freezes in the blue screen and in the windows boot screen

In Windows 10 version 1803 and 1709 it displays random BSODs with 0x00000109. the module is ntoskrnl.exe. in 5.2.8 it would also freeze the VM until you reopen the VM. 5.2.10 fixed the freezing when the BSOD appears bug. the ticket number is 17736

Windows 10 is the guest

Host: MacOS 10.13.4, build 17E199
Guest: Windows 10, 1803, build 17134.1
VirtualBox: 5.2.10, r122088

I merged your new thread with the thread that you already had open. You do NOT open a new thread for the same issue, you continue on the same thread. And you DEFINITELY NOT open a new ticket. Unless you've resolved this in the forums, by answering the questions asked.

Opening new threads and new tickets without providing any information when asked, is not going to have a happy ending. In the best case scenario, you will be completely ignored, because there's nothing else that can be done about your issue...

Neptune BSC wrote:Host: MacOS 10.13.4, build 17E199
Guest: Windows 10, 1803, build 17134.1
VirtualBox: 5.2.10, r122088

That is about the same configuration as I have on my 2017 iMac but haven't seen the issues you are reporting. My Windows VM gets a good workout when it is spun up as it is used for compilation in Visual Studio.

VBox.log wrote:

00:00:02.492286 Host RAM: 8192MB (8.0GB) total, 981MB available
00:00:02.596456 RamSize <integer> = 0x00000000e9700000 (3 916 431 360, 3 735 MB, 3.6 GB)
00:00:02.596736 VRamSize <integer> = 0x0000000010000000 (268 435 456, 256 MB)

Ordinarily, we would go "woooo, you have over committed RAM to the guest that you don't have available on your host". With Apple's aggressive in memory caching in recent OS X versions that may or may not be the case here.

Neptune BSC wrote:random BSODs with 0x00000109

Microsoft very usefully publish the documentation for bugcheck codes as they are part of one of the header files for the driver development kit. Bugcheck code 0x00000109 is about as serious as it comes. Something has either modified kernel code in memory or has hosed the internal kernel data structures within Windows.

Until you answer the other questions from socratis in sufficient detail then that is about as much help as we can be!

-Andy.

This could be a bug in Virtualbox Guest additions

Could be/might be/I think...
These are not good reasons to believe something, you got to prove it. And you know what can prove it?

The information that I asked for, and you have yet to provide!!!

it displays random BSODs with 0x00000109. the module is ntoskrnl.exe. Every time I reset the machine It also freezes until I close and reopen the VM.

For the third time (and last time) that is not the information I asked for! Read the thread from the beginning. See what I'm asking for.

which questions do I have to answer

Whatever you haven't replied in my very first answer to your post: viewtopic.php?f=2&t=87676#p418821

I already replied to the first answer in the post