virtualbox.org

I am afraid that in a virtual environment and on a 32 bit host 1.5 is going to be the max you can use. I am stuck in that as well, but hey I have also found that Windows works fine with lower memory in VBox. Actually it works with almost 1/2 as much memory and performs the same for me.

Hi,

Thanks for the information. My poblem is not yet solved...

After the steps I mentioned yesterday, I did a TMP and Registry cleanup, then proceeded to reinstall Oracle, which went successfully....

Then I proceeded to downloading many setup files from an FTP (GB of data). I ran it and watched it going for a while with no problem. I left it going and went to bed.

When I went to see the status this AM, I got the same memory BSOD.

I rebooted and tried downloading again from the FTP, and same thing... BSOD...

I have my memory set to 1024MB now...


Any help?

Thanks,

Simo

It appears that you ran out of memory. I have no idea why. Maybe you should create a ticket in Bugtracker and send the screen shot of the BSOD along with your VBox log files. You will need to setup an account there I am afraid. It is on a different system. Link to Bugtracker is at the bottom of my post.

I think I pinpointed the source of the problem to a single 2.5GB file that is downloaded from the FTP. I now know that it crashed while that file was downloading. I am trying to download it again and wondering if it will crash @ 1GB

Right after I finished writing the previous post, I brought focus back to the VM and here is what I saw :


The 2.5GB file had reached 890MB.

And here are the latest log files

Note that I was able to resume after rebooting the VM. If it crashes again when it reaches about 1780MB, then I will know where the problem is...

Thanks,

Simo

Try a different lan adapter for the VM.

Hi,

I will try different LAN adapters later. Meanwhile, the latest news :
- The 2.5GB file completed successfully.
- I have been running the VM with no problem until I went on lunch, when I came back, it was on BSOD again, but this time it was an IRQL error:


I will submit this in BugTracker as suggested and will let you know if I get any information.

Thanks,

Simo