UEFI Installation possible on this Netbook?

Right, thanks, I will try that later.

Oh, now even Windows gives me a message, that I should make a backup because the system found problems in the HDD, and down on the window is the name of the HDD, gives me 2 options: start doing the backup or to ask me later. Also, I was running HD Tune and I started an Error scan, and it was horrible, it went for 20% of damaged blocks, and it was still going, but the program itself crashed. Now sometimes even the system restarts itself and then the BIOS doesn't detect the HDD, I opened the back of the netbook to be sure that the disk was correctly connected but it's ok. Would that be enough proof?, need to change my HDD?

Just a last question, even though the system is x64, in my PC properties, it still says that only 3.4 of my 4 GB of RAM is functional, would that be also a faulty RAM stick?, I used memtest+86 as part of my previous diagnostic and all the tests gave 0 errors.

Type Resources in Start Search box, in Resource Monitor click on Hardware tab to see how much is apportioned to Hardware.

I would probably run 32 bit with 4gb RAM for best performance, Bypassing UEFI to Install WIn7

gregrocker said:

Type Resources in Start Search box, in Resource Monitor click on Hardware tab to see how much is apportioned to Hardware.

I would probably run 32 bit with 4gb RAM for best performance, Bypassing UEFI to Install WIn7

You're right, I should use x86 instead. And what's the memory in Hardware used to?, I read in other post that memory in that space could mean a faulty RAM stick?.

Your video chip/card will use some of the RAM unless it has dedicated RAM onboard. Other hardware can also tap the RAM. It is to be expected, and varies per PC.

gregrocker said:

Your video chip/card will use some of the RAM unless it has dedicated RAM onboard. Other hardware can also tap the RAM. It is to be expected, and varies per PC.

Thanks greg, I should've known that, I feel relieved is not a bad stick. Since the problem from the very beginning was a faulty HDD I will close this thread. Thanks again everyone for their help, I really learned a lot.