Question : BSOD - Core Server 2008 RS  possibly caused by VM session with wrongly configured RAM

I had a Windows 2008 R2 Core Server BSOD on me twice today. Nothing in event logs. Now this system was installed on the weekend. It runs two VM's - one 2000 server and one 2003 server - both virtualized from physical servers that were not problematic.  The only problem reported prior to the BSOD's was slowness - this had been a problem when the systems were physical as well because of high usage.  We are going to deal with this in the near future by migrating to 2008 which would give us more RAM/CPU's etc. - the current Core Server is a dual Xeon with 24 gig of RAM so that should be well take care.  The day before the BSOD in order to deal with the slowness we bumped up the RAM of the 2000 VM to 4 gig.  On the physical box it had been around there.  However, I have read quite a few posts and it seems that 2000 in some cases - hardware of motherboards -  can only really make use of 3.1 gig or thereabouts.  My question is   that if in fact we gave the 2000 VM more RAM than we should have -( the virtual m/b supports less than the real m/b which apparently can be the case per my readings as the virtual m/b is generic older versus the physical server we migrated from in this case which was fairly new) - could  it cause a blue screen in the host OS - the core server. When I ask 'could it' I would like more than 'it's possible'  - I would like some analysis of what exactly the trail of woe could be that goes from misconfigured RAM in a VM to crash of the host.

Answer : BSOD - Core Server 2008 RS  possibly caused by VM session with wrongly configured RAM

I never heard of the fact that much RAM given by host to guest would cause problems.
Problems could be if one of the RAM sticks are not properly set in connector or the RAM sticks are of different model. And finally if one of the RAM sticks is damaged.