Acer Aspire One AOA150/ZG5, can it run 2GB or more RAM?

Is there any way to get an Acer Aspire One AOA150/ZG5 running with 2GB+ of RAM? I've heard it's not possible and the reason for that is the on board 512MB of RAM, so I was wondering if theres any way around this.

The reason I'd like to increase my RAM is so the thing can run Windows 7. Currently with 1GB total it's able to run it but BSoD's whenever I do anything such as downloads. I've added some virtual RAM but it doesn't seem to help much.

I tried ReadyBoost with a 4GB SD Card, it didn't do anything either. My computer still BSoD's.

k; is there any way to run Windows 7 on just 1GB of RAM without it BSoD'ing constantly?

(like, what I tried was adding virtual memory and using a 4GB SD card for that ReadyBoost thing, but that didn't work)

Zukaro said:

k; is there any way to run Windows 7 on just 1GB of RAM without it BSoD'ing constantly?

(like, what I tried was adding virtual memory and using a 4GB SD card for that ReadyBoost thing, but that didn't work)

Ababsolutely. Im doing it now. If it is BSOD'ing it isnt because of the lack of ram

This machine has been running Windows 7 0n 1GB RAM for a year with no BSODs. I will add that it is running the x86 flavor.
If there are BSODs, try deciphering the problem(s) via Event Viewer or with BlueScreenView.

Edit: Is this machine configured as multi-boot?

joodoo said:

This machine has been running Windows 7 0n 1GB RAM for a year with no BSODs. I will add that it is running the x86 flavor.
If there are BSODs, try deciphering the problem(s) via Event Viewer or with BlueScreenView.

Edit: Is this machine configured as multi-boot?

Yes, I've got Linux Mint 12 dual booting along side Windows 7. However, for a time I did have Windows 7 on there only and it still BSoD'ed just as frequently.

...try deciphering the problem(s) via Event Viewer or with BlueScreenView.

joodoo said:

zigzag3143 said:

joodoo said:

...try deciphering the problem(s) via Event Viewer or with BlueScreenView.

Just an FYI. Blue screen view often ceremoniously blames OS files. WinDbg is the gold std

Thanks for this.
Although BlueScreenView has been a great boon to me and many others, I will give WinDbg a whirl.

Edit: After installing .net 4 (required) and running the SDK (WinDbg) installer (which failed 3 times), I have decided to stick with BlueScreenView (no installation necessary-just point and click) for now. I shall try again at a later date....
Final Verdict: SDK is not for the average PC enthusiast-like me.

You dont need SDK to install WinDbg, and many "enthusiasts" are being led astray. With more than 10,000 DMPs under my belt I see them doing useless installs, driver updates, and procedures by its use.

Should you ever want to install WinDBg I would be happy to help you.

WinDbg (when attached to the local machine) runs rings around BSV, who crashed, etc.

It is the gold standard for the serious user.