virtualbox.org

I was using virtual box version 3 since around three four days for mounting a vdi containing windows server2008 and sharepoint. I was not able to create a shared folder through the vbirtual box. I believe I had installed the guest additions. So I insalled the version 4 of virtual box.But now when i create a new mapping of the vdi file, the os never loads. It shows BSOD with some address and restarts. Please help. I am desperate to get this thing working. Even if I copy and paste a new vdi file and try other options in the virtual box, this problem occurs. In effect, I have not been able to start it since last two days. I have attached the log file

Please post the real VBox.log file as a zipped attachment. The version you posted above has been processed somehow, and truncated long before it got to anything interesting. You can find the "VBox.log" file in your VMs "Logs" subfolder.

Terribly sorry that it was not the actual log. I have attached the correct one now. Please help...

I don't see any evidence of a problem in the log. I do see a reset processed by the VM, presumably this is your BSOD? That means that the VM is working just fine, it is Windows which is crashing.

A few possibilities spring to mind.

If you tried changing the hard disk controller type then it might cause problems like this if you didn't do it correctly. I would try reverting to the basic IDE controller.

You mention "creating a new mapping of the VDI". If this means mounting in another VM then a number of problems can occur: the wrong disk controller issue can arise again. If you used snapshots the data from these would be missing. If you were attempting something strange like sharing the same VDI between two working VMs then there's no telling how many things could go wrong with that.

You should reconfigure Windows so that it no longer automatically resets after a BSOD. That will allow you to get the details of which BSOD it is.

I really didn't quite understand you. I mean, this entire setup was working fine in virtual box 3 except that I couldn't create shared folders in that. So I installed virtual box4. I then copied a fresh copy of the vdi file and started to create a vm again , (clicking on new, etc ). Two days back or so, whenever I used to start the winserver in the virtual box, I used to get a dialog , i don't remember the exact contents, but it was someting about not able to find the mapping or something like that, with two buttons check and ignore. When I clicked on check , it would go to a particular tab, to change some mapping. As I didn't quite understand what it mean't, I would just start the vm and everything would go fine. One day, I decided to delete the mapping as I was getting fed up of this dialog whenever I start the virtual box. So I deleted the mapping and started afresh with a new copy of the vdi, and from then onwards, this problem started happening. ie.e Blue screen containig some error with address and memory dump , then restarts the os again and again. I have not used snapshots. I did however used the same vdi file for two virtual box but not when they were running simultaneosly. But later on , I copied a fresh vdi as soon as I got this error but that also failed. I don't know what you mean't by wrong disk controller. It looks like I have no option other than to reinstall my windows 7 os again and try .

And what's more funny is that, when I click on the vm in the virtual box and then click on settings, the dialog box that comes is three to 4 times of bigger width of my monitor such that I have to click on the title bar and move it to the left, part by part to see the ok and cancel button !!

Sorry. I can't do anything with "some error" and "this dialog". I've commented on what the log tells me. You seem to have confirmed that you created a new VM, and I already indicated things you should look when you do that. If you want me to do more then I'll need precise details of symptoms.

I am posting the link below of the exact error which is got by another person..

oops, the link did not come
Here it is again..
http://coderjournal.com/2012/03/dealing ... irtualbox/

My error codes are EXACTLY the same. And I have tried the solution presented in the link . No use..

Stop 0x7B is usually caused by a hard disk controller change. E.g. if the original VM used IDE and the new VM was configured for SATA, then this might be the result. Or, selecting a different IDE controller type would also do it.

Microsoft support page on stop 0x7B