virtualbox.org

Hello,

Host 10x64 build 18363.720
Guest: Similar as above.

Once on about 3 starts dialog windows about error occured.
Attachning log: mediafire[dot]com/file/kggtiyl48p6o96t/10x64_Latest-2020-03-20-20-35-15.log/file

Host OS passed extended stability tests (prime95, memtest), no overclocking is used.

Please help

Start the guest from cold boot, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please zip and post the guest's vbox.log, using the forum's Upload Attachment tab.

scottgus1 wrote:Start the guest from cold boot, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please zip and post the guest's vbox.log, using the forum's Upload Attachment tab.

Attached log from failed start (while OS load)

I see a VM started from a saved state, not a cold boot. So the opposite of what was requested. Right click, discard the saved state, and try again.

What is a "cold boot" there is no such term in VirtualBox, I see Headless and Deatchatable start.
It was from state but after system reboot, so what's the difference?
Shouldn't it work well with saved state? State was saved perfectly well. Also it happened to two differnet Windows 10 (32 bit other instance the same)

Even if you don't understand what cold boot means, I would have thought that "not saved state" should be clear enough?

"Cold boot" is a common industry term, like boot itself for that matter. When in doubt, use Google.

mpack wrote:Even if you don't understand what cold boot means, I would have thought that "not saved state" should be clear enough?

"Cold boot" is a common industry term, like boot itself for that matter. When in doubt, use Google.

Sounds funny. Industry term does not matter there, I'm long enough in IT to know how details are important.
So when someone telling "cold boot" it's not precise enough for me, especially if we consider this cold boot is done via virtualization application with few options common with VM run.

So, snapshot feature is useless and shall I forget about using it then when you analyze only cold boot logs?
Worth to mention that from the same snapshot is sometimes start somtimes not after such procedure: Restore snapshot - > Reboot OS (I know this is not the same as cold start, but nothing relevant exist in logs? )

Now experienced BSOD (2nd time in 2 days) which seems to point to your drvier.
https://mediafire.com/file/h8awnyjcnc9y ... 1.dmp/file

vitualboxer wrote:I'm long enough in IT to know how details are important.

Long enough to know to google something?

googling "cold boot meaning", 1st response reveals:

techterms.com wrote:To perform a cold boot (also called a "hard boot") means to start up a computer that is turned off. It is often used in contrast to a warm boot, which refers to restarting a computer once it has been turned on. A cold boot is typically performed by pressing the power button on the computer.

Of course, for a virtual machine, "cold boot" would refer to starting the virtual machine, not the physical PC.

vitualboxer wrote:it happened to two differnet Windows 10 (32 bit other instance the same)

Not mentioned in the first post, so we may have been led down a rabbit hole... Also what is 'it'? what are the "two differnet Windows 10 (32 bit other instance the same)": physical computers? virtual machines?

vitualboxer wrote:Shouldn't it work well with saved state?

Again, what is 'it'? If the log, then no, not unless the specific problem has been pinned down to a difficulty with 'saved state', which has happened before. In which case we would ask for logs starting from saved state. We asked for what we needed: a log showing a start from the guest turned off (which is what 'cold boot' means, see and infer above). A log from cold boot contains important data that is not always in a saved-state log.

vitualboxer wrote:snapshot feature is useless and shall I forget about using it

Though saved-state and snapshots may use similar base functionality, saved state != snapshots. (Just in case, !=) Each has its uses and drawbacks. Saved state is quite like Windows Hibernate. Snapshots are quite like Windows System Restore points.

So if we ask for a log from cold boot, it means to get your VM into a state where it is completely shut down normally or by having the "power turned off" on the guest (see the Virtualbox guest window Close box for the "power off" terminology). If we ask for a log from saved state, it means to turn off a running guest with Saved State.

As for analyzing BSODs, the original post only mentioned:

vitualboxer wrote:Once on about 3 starts dialog windows about error occured.

What error, what window, what source of the window, not included. I do not have the BSOD analyzing software installed on my computer, nor do I wish to, at least until a suitably detailed post is provided containing exactly what error originally happened and where from, host or Virtualbox or guest.

As you can see, vitualboxer, this topic has gone to heck in a handbasket so far. It is up to you to provide more detailed explanatory post of the original problem, with a log from cold boot of the guest, zipped and posted via the forum's Upload Attachment tab, not on a third-party site, after the original problem has occurred again.

@scottgus1
Haha very "funny" with googling, really.
By different option I meant headless start and so on, who expect you told about host machine?

Don't try to fool me, what is the " BSOD analyzing software" ?? Who are you talking with you think ?
Developer need only memory dump eventually larger like kernel memory dump + WinDbg, I guess as developers you have pdb,map and sources right?
So you can locate if that points to specific part of code of your driver.

Fact is fact - My computer NEVER EVER crashed single time for over 24 months just started crashing after Virtual Box install.
Aleardy it has 4 BSODs in 5 days.

So there are two problems, sometimes does not start after reboot from saved state, second it crashed, both problems happens on two different installations of Guests one 10x32 other 10x64, disk scanned no logical errors, as I said computer is rock solid when comes to hardware, mem test ran over 20 hours without single error, no other BSOD for over 24 months.

What kind of support is this ?
I want to help myself but for your software as well !

OK, we will try to look into this more, gotta get some stuff done for now. But, just so you know...

vitualboxer wrote:I guess as developers you have pdb,map and sources right?...What kind of support is this ?

We aren't the developers. We, like you, are fellow freeloaders using the free Virtualbox and we volunteer some time as we wish to help on the forum. If you think the devs should know, see the Bugtracker. But they will probably want this fleshed out better on the forum first.

vitualboxer wrote:@scottgus1
Haha very "funny" with googling, really.
By different option I meant headless start and so on, who expect you told about host machine?

Don't try to fool me, what is the " BSOD analyzing software" ?? Who are you talking with you think ?
Developer need only memory dump eventually larger like kernel memory dump + WinDbg, I guess as developers you have pdb,map and sources right?
So you can locate if that points to specific part of code of your driver.

Fact is fact - My computer NEVER EVER crashed single time for over 24 months just started crashing after Virtual Box install.
Aleardy it has 4 BSODs in 5 days.

So there are two problems, sometimes does not start after reboot from saved state, second it crashed, both problems happens on two different installations of Guests one 10x32 other 10x64, disk scanned no logical errors, as I said computer is rock solid when comes to hardware, mem test ran over 20 hours without single error, no other BSOD for over 24 months.

What kind of support is this ?
I want to help myself but for your software as well !

I've been using VBox close to 10 years. My two host PCs which I've had it installed on it never crashed, never BSODed, never had a single trouble.

Maybe just maybe your Windows PC is so stuffed with different applications there's a sort of conflict and you're seeing these issues. In this case it might help to reinstall Windows from scratch while installing *only* drivers for missing hardware (yellow flags in Device Manager) and nothing else.

Also this forum is driven by volunteers. If you need commercial support, you may want to purchase VBox.

Also, just also, Windows 10 Home/Pro/Enterprise editions are ill-advised for using VBox because they are basically beta-quality OSes.

You may want to use Linux (CentOS 8 or Ubuntu LTS to be precise) or Windows 10 Enterprise LTSC if you really want to have a stable virtualization environment. And again make sure you do not install anything but the absolute necessary software under W10.

I'll add onto Birdie's thoughs, I have also run Virtualbox solidly on several PCs for years. Had one that had a couple BSODs too. I may have reinstalled Windows or reinstalled/upgraded/downgraded Virtualbox, can't remember, it was many years ago. It's Windows, whatcha gonna say?

Thank you guys for all your inputs, I guess driver developers should take a look on this.

I do not say that's it's VirualBox for 100%, but minidump I attached link to - points for vbox driver.
Of course it could be Windows kernel bug as well - anyway never happened before.
It happens on version 6.x, previously used 5.x, I think this dump could be useful for devs, if not I'm ready to help to provide more info.

Anybody can send this crash dump to devs?