Using the most recent VB and Windows 7 keeps crashing

[Ike12345]

I just tried to post a log of the error and it said the file is too big. I dunno what to do cuz I'm new to Virtual Box. It works for a little bit then it always crashes. Here's some of the Error since it won't let me post it all.

05:06:47.994004 ********************* End of statistics **********************
05:06:48.009901 VUSB: detached 'HidMouse' from port 1
05:06:48.371145 NAT: zone(nm:mbuf_cluster, used:0)
05:06:48.371782 NAT: zone(nm:mbuf_packet, used:0)
05:06:48.371806 NAT: zone(nm:mbuf, used:1)
05:06:48.371960 NAT: zone(nm:mbuf_jumbo_pagesize, used:0)
05:06:48.372628 NAT: zone(nm:mbuf_jumbo_9k, used:0)
05:06:48.372990 NAT: zone(nm:mbuf_jumbo_16k, used:0)
05:06:48.373185 NAT: zone(nm:mbuf_ext_refcnt, used:0)
05:06:49.571852 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
05:06:50.553459 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 0 as 800x600
05:06:50.943976 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false
05:06:51.148460 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false



If you need more of the logs I guess I can try to post it all on here via more posts. I just need help it keeps crashing. All I'm running on it is two programs to play a 2D game.

[loukingjr]

You can compress the log file then attach it to your post.

[Ike12345]

Ok, I did it and I've been running my VB and so far no crash. Do you think it was crashing cuz it was set to go into sleep mode after 20 mins of inactivity? I turned it to Never so it will stay on all the time and so far no crashes.

[mpack]

You're getting the VERR_TRPM_DONT_PANIC crash. Every time I've seen this it has involved a VM in which VT-x is enabling in the settings, but not available on the host. I'd guess that some part of VirtualBox has a bug whereby it tries to do something with VT-x (because it's enabled), but hasn't checked that it isn't actually available. Your B960 CPU is one of those rare Intel beasts that supports 64bit, but doesn't have VT-x.

To fix this I think the simplest solution would be to fully shut down the VM, open up the .vbox file in "Notepad++", and disable the VT-x option there. I.e. in the CPU section find the HardwareVirtEx and HardwareVirtExNestedPaging options and set the enabled attribute of both to "false".

As to the "something" for which it tries to use VT-x, putting the drives into power down mode is certainly a possibility.

[Ike12345]

I fixed that but for some reason it's still crashing and now it's saying something else. This is getting annoying. Ok here's the logs for the new issue...

[mpack]

I'm afraid you haven't fixed anything, at least according to the new log. The error is exactly the same, and you still have VT-x enabled in the VM settings.

[Ike12345]

I thought I disabled it with the notebook++. I dunno how to access the Vbox Manage or how to edit it and make it permanent apparently.

[mpack]

I didn't mention VBoxManage. If you don't know how to use a text editor either then perhaps you should get someone else to do it. I would recommend Notepad++ for the purpose of editing the .vbox file. You absolutely must not use a word processor, e.g. Wordpad or Word, as those are not designed for plain text.

Making a backup of the file before editing might also be a good idea.

[frank]

Problem covered by ticket 13521. Bug will be fixed in the next 4.3.x maintenance release.

[Ike12345]

I meant to say I had Notepad++* and does that mean that I just should wait for the next version and that problem will be fixed?

[mpack]

It would appear so.

[Ike12345]

Yeah cause I just did it with notepad++ turns out I was doing it to the prev. file but I did it to the real thing and I exit and close out and it says "false" But it still crashes.

[mpack]

You still haven't posted a log which shows that.

[Ike12345]

I think I have one but I'm not sure. Imma just run it now and wait for it to crash again and when it does I'll post.

[Ike12345]

Yeah it crashed after running for almost 24 hours. Ok here is the log.