Win 2008 image crashing after startup

[Cabbageman]

Hi

I am using 4.0.8 and have a Win 2008 64bit machine that has been running for a few months with no issues, including being rebooted.
Unfortunately after restarting it today it now crashes within a couple of minutes of being started.
I can start it in safe mode but can't then see anything that might be causing this.
Please find attached the png. The log is too large to attach but it doesn't have any errors in it. The last section just shows
00:11:30.275 /TM/MaxHzHint 0 Hz
00:11:30.275 /TM/R0/1nsSteps 108722 times
00:11:30.275 /TM/R3/1nsSteps 109358 times
00:11:30.275 /TM/TSC/offCPU0 21095098858 ticks
00:11:30.275 /TM/VirtualSync/CurrentOffset 0 ns
00:11:30.275 /VUSB/0/cUrbsInPool 0 count
00:11:30.275 /VUSB/1/cUrbsInPool 0 count
00:11:30.275 ********************* End of statistics **********************
00:11:30.315 Changing the VM state from 'DESTROYING' to 'TERMINATED'.

Would appreciate any suggestions on what to check
Thanks

[mpack]

We need the entire, unedited log, preferably as a zipped attachment - which gets around the size problem.

[Cabbageman]

Hi

Please find the zipped log attached

Many thanks

[mpack]

The log does in fact contain an error.

00:03:09.422 Guest Additions capability report: (0x4) seamless: no, hostWindowMapping: no, graphics: yes
00:03:09.555 Guest Additions capability report: (0x5) seamless: yes, hostWindowMapping: no, graphics: yes
00:04:15.309
00:04:15.309 !!R0-Assertion Failed!!
00:04:15.309 Expression: RT_SUCCESS_NP(rc)
00:04:15.309 Location : D:\tinderbox\win-4.0\src\VBox\VMM\VMMAll\PGMAllPool.cpp(2476) pgmPoolMonitorInsert
00:04:15.309 PGMHandlerPhysicalRegisterEx 00000001e38ac000 failed with -1701
00:04:15.309 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:04:15.309 !!
00:04:15.309 !! Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)
00:04:15.309 !!
00:04:15.309 !!R0-Assertion Failed!!

I suggest that you update VirtualBox to v4.1.18 (or the new v4.2.0 release candidate), and see if you still get this error. Remember to update the guest additions too.

Another thing you can try is reducing the amount of guest RAM to 6GB or so.

[mpack]

And have a read of these two tickets (i.e. also read the "duplicate" ticket referenced at the end of the first).