PDA

View Full Version : /3GB switch kills quad cores?


paulrus
03-13-2007, 08:58 PM
I've got 4GB of ram on my quad core machine (XP 32bit) and when I use the /3GB switch, my system becomes nearly un-bootable. It takes 10-15 minutes to boot and will crash almost the moment it finally boots up.

Is there a known issue with /3GB and quad core processors?

Thanks

Paul

collapse
03-13-2007, 10:15 PM
you need a X64 System becouse x32 can adress max 4 Gigabytes of virtual memory,
everything of the next few things are tanking a pice of memory of these max 4 gigabyte on x32 (video memory, paging file, ram, every ram of a device which is found in the system.

hope i could help

and no the quad core is not the problem ;)

Randybob
03-13-2007, 10:15 PM
I wouldn't know about that, but it sounds to me like a motherboard defect. Is there a spare 775 processor you could use to test it out?

collapse
03-13-2007, 10:19 PM
I wouldn't know about that, but it sounds to me like a motherboard defect.

LINK OVER HERE (http://www.microsoft.com/windowsxp/using/64bit/russel_exploringx64.mspx)

over there is written why you should use x64 and why x32 does not support more than 4 GB of virtual Memory

you trust me now *GG*

paulrus
03-13-2007, 10:23 PM
So you're saying that every single person who uses the /3GB switch that Microsoft themselves document as a x32 feature is totally wrong?

http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

I was just curious if this was a quadcore problem, since I've known dozens of people running dual core machines and older machines with the /3GB switch and no problems. However when I enable it, my system becomes incredibly unstable.

Thanks for the replies

Paul

collapse
03-13-2007, 10:32 PM
So you're saying that every single person who uses the /3GB switch that Microsoft themselves document as a x32 feature is totally wrong?

http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

I was just curious if this was a quadcore problem, since I've known dozens of people running dual core machines and older machines with the /3GB switch and no problems. However when I enable it, my system becomes incredibly unstable.

Thanks for the replies

Paul

thix method does function yeah but somtimes it could create unstable systems like your's set up a multiboot System and you have a proof.

under x32 if i remember rightly you can allocate max 2 GB Ram per application with that feature (/3 edting in boot.ini like on your page) you can allocate more.

a last thing that I say is that there are a lot of discussions over the internet about this /3 and problems with more/or than/like 4GB RAM ...

have a nice evening i am going to study

so cu

lots
03-13-2007, 11:12 PM
When 32bit windows has 4GB of RAM, it automatically assigns two of it for system use. Leaving the remaining 2GB for user space. Windows can be modified to force the system to use 1GB and leave 3GB for the user (via the /3GB switch), but most 32bit apps are still restricted to 2GB anyway.

To have the full 4GB available to you, you would need 64bit Windows and 64bit software.

As to the main problem (crashes) I can't offer any advice. This is the first time I've heard people having issues with 4 cores and the 3GB switch, but then again I havn't kept tabs on any issues i nthe 4 core world :)

Randybob
03-13-2007, 11:23 PM
LINK OVER HERE (http://www.microsoft.com/windowsxp/using/64bit/russel_exploringx64.mspx)

over there is written why you should use x64 and why x32 does not support more than 4 GB of virtual Memory

you trust me now *GG*
I knew about that, it didn't say anything about the /3GB switch though. If it's only 4 GB of RAM, win32 should still support it.

Srek
03-14-2007, 08:26 AM
The /3G option does not work with all installations. Make sure Aperture Size is correctly set in the BIOS, if this is wrong chances are it won't work at all.
In general the /3GB option is an experimental feature, if it does not work, don't use it.
Cheers
Björn

CGTalk Moderation
03-14-2007, 08:26 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.