Crashing VirtualBox - host=W7/64bit, guest=WinXP SP3

[DerellLicht]

Well, after my previously posted problems trying to upgrade my WinXP guest to SP3, which ultimately ended up completely destroying the guest installation, I went out and got an SP3 version of WinXP and installed it from scratch. It installed with no problems and is running fine, AFAIK.

However, every afternoon (for two afternoons now), VirtualBox crashes, taking the guest with it. I am attaching the VB log file from this afternoon's crash. There are no minidump files present on the XP machine when I restart it, and the Event Logs are all clear.

I looked at the host Event Log, and I found a fault which occurred at the same time as the VB log event, I have attached that as well.

I looked at the VM log file, but I don't see anything in there that looks like an error message. Is there anything else I can look at?

My VB version: 4.3.4r92017 (I have just downloaded 4.3.6, I'll upgrade to that and see if that helps...)
I do have XP Guest Additions installed
host: Windows 7 Build 7601 Service Pack 1
guest: Windows XP Build 2600 Service Pack 3
Antivirus is MSE, on my previous crashed guest it was Avast

[mpack]

I suggest you try upgrading to 4.3.6, and if necessary post a log file from that.

[DerellLicht]

Okay, I've now survived a full day without another crash (with VB 4.3.6 installed). That's good!

There are several issues that I wonder if might be involved; I've bypassed as many as possible, and will re-introduce one at a time over the next couple of weeks.

1. I noticed that when I close Firefox (V26) on the guest, it sometimes leaves something running in the background, which pins the CPU at 100% utilization; I've never seen that on any other of my host nor guest OS installations. For now, I've installed Pale Moon V24, which is a build of Firefox optimized for Windows. We'll see if that avoids problems.

2. I turned off "shared clipboard" and "drag and drop" in VirtualBox, since that was once difference between my current installation and previous ones.

3. The third possibility is LogMeIn; I use that to log into my home computer from work, and the crash times were relatively consistent with times when I had logged into the home machine from work; maybe there's some conflict between LogMeIn and the guest installation, though it had not been a problem in the past. I'll check that out once I return to work next year...

If I learn anything interesting, I'll post information here, just in case someone else experiences this issue.