1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Guide to 64-bit vs. 32-bit Operating Systems (read carefully SLI and CF users!)

Discussion in 'Off Topic' started by Marcel Hulsbergen, Dec 24, 2009.

  1. Marcel Hulsbergen

    Marcel Hulsbergen
    #111 | Roaring Pipes Maniacs Premium Member

    You're probably aware that 64-bit and 32-bit versions of your operating system exist, but apart from ascribing to a bigger-is-better philosophy, you may have no idea what separates the two. The question: Should you use a 64-bit version of Windows, and why?

    More and more frequently, users are installing the 64-bit version of their operating system of choice over the less capable 32-bit version. But most people don't really have a full understanding of what the difference really is. Below, we're taking a look at the most important differences so you can better understand what you gain (and potentially lose) if you upgrade to the 64-bit version of your OS. (The post focuses on Windows.)

    In any 32-bit operating system, you are limited to 4096 MB of RAM simply because the size of a 32-bit value will not allow any more. On a 32-bit system, each process is given 4 GB of virtual memory to play with, which is separated into 2 GB of user space that the application can actually use at a time.

    Savvy readers might point out that modern chips support PAE, a processor technology that allows the operating system to use a little bit more memory—up to 64 GB, but it also requires special application support that most applications don't have or necessarily need.

    A common misconception is that this is a Windows-specific problem, when in fact 32-bit Linux and Mac OS X have the same limitations and the same workarounds. 32-bit Linux uses a mapping table to allow access to the extra memory, and OS X Snow Leopard actually ships by default with a 32-bit kernel that can't access all the memory on older systems, even though most of the rest of the OS runs 64-bit processes.

    The 4 GB limit for Windows, at least, is also a factor of licensing—the home versions of 32-bit Windows, while technically being able to support PAE, have a hard limit of 4 GB for licensing and driver compatibility reasons.

    More Problems with 32-Bit

    Not only does 32-bit have a hard limit for the amount of memory it can address, there's also another problem: your devices, like your video card and motherboard BIOS take up room in that same 4 GB space, which means the underlying operating system gets access to even less of your RAM.

    Windows expert Mark Russinovich found that a desktop running 32-bit Windows with 4 GB of RAM and two 1 GB video cards only had 2.2 GB of RAM available for the operating system—so the bigger and better your video cards get, the less of that 4 GB will be accessible on a 32-bit system.

    What's Different About 64-Bit?

    While 32 bits of information can only access 4 GB of RAM, a 64-bit machine can access 17.2 BILLION gigabytes of system memory, banishing any limits far into the future. This also means that your video cards and other devices will not be stealing usable memory space from the operating system. Windows 64-bit Home editions are still limited to 16 GB of RAM for licensing reasons, but the Professional and Ultimate versions can use up to 192 GB of RAM, so keep that in mind when building that killer system.

    The per-process limit is also greatly increased—on 64-bit Windows, instead of a 2 GB limit, each application has access to 8 TB of virtual memory without any special API, a huge factor when you consider applications like video editing or virtual machines that may need to use enormous amounts of RAM.

    On Windows, the 64-bit versions also come with a technology to prevent hijacking the kernel, support for hardware-enabled data execution protection, and mandatory digitally signed 64-bit device drivers. You also won't be able to use your 16-bit apps anymore, which hardly seems like a loss.

    Do 32-bit Applications Work on 64-Bit?

    The vast majority of your 32-bit applications will continue to work just fine on 64-bit Windows, which includes a compatibility layer called WoW64, which actually switches the processor back and forth between 32-bit and 64-bit modes depending on which thread needs to execute—making 32-bit software run smoothly even in the 64-bit environment.

    There are some exceptions to that rule, however: 32-bit device drivers and low-level system applications like Antivirus, shell extensions that plug into Windows, and some media applications simply won't work without a 64-bit equivalent.

    In practice, the vast majority of your favorite applications will either continue to work, or provide a 64-bit version you can use instead—but you should check to make sure.

    Does 64-Bit Use Double the RAM?

    A common misconception about 64-bit Windows is the amount of RAM that is actually used—some people seem to think it will use double the RAM, while others incorrectly assume a 64-bit system will be twice as fast as 32-bit.

    While it's true that 64-bit processes will take a little extra memory, that is a result of the memory pointers being a little bigger to address the larger amount of RAM, and not an actual double in size. Imagine, if you will, an ancient library filing system that has a card to tell you where to find the book in the library—if you got a bigger box to hold the cards, the library would not double in size, you'd just be able to find the book you were looking for more easily.

    What will increase with 64-bit Windows is the amount of drive space needed for the operating system—with a compatibility layer in place, the base OS will take up a few extra GBs of space, though with today's massive hard drives that should hardly be a concern.

    The Bottom Line, Which Should I Use?

    If you are ordering a new PC with 4 GB or more of RAM, you should probably be running a 64-bit version of Windows so you can use all of the available memory, especially if you want a rig with a large video card—just keep in mind that the Home versions only support 16 GB of RAM (for most people a 16GB limit won't be a problem, but it's worth keeping in mind).

    If you're running Mac OS X, you don't need to worry about 32-bit vs 64-bit, and if you're running Linux, you probably know this stuff already.
  2. great explanaton there, i`m loving my 64 bit system and happerly supprised how many of my old games and stuff run on windows 7 64 bit without any issues.
  3. Even tho I have 4GB ram, I've gone for 32 bits. The reason is drivers. I was not sure how good the 64 bit drivers from Fanatec are, and they need some F8 restarting because they're not approved by MS.

    And yep I knew all the stuff, but I just wanted to be sure about my hardware.

    The 5.9 score is because of my HDD's.. Only SSD's and Raid0 would go higher.
    Afaik, normal HDD's do 5.9 single, and 6.2 in Raid0.
    While a single SSD does 7.6 and in raid0 it does 7.9

    Processor and Mem is 6.7 here
    Graphics is 7.3

    Attached Files:

    • img.jpg
      File size:
      137.6 KB
  4. Same as Johan, I've got 4gb but because of driver's and lots of BSOD with x64 7 I've gone back to x86.
    I use some old hardware as well as old vst plugins, which don't run good at all in x64, get allot of crashes and bugs so had no choice, but ideally I need to use 4gb + ram.

    This is on my main rig though, I've got x64 on one of my other rigs that don't need old drivers and software and it runs like a dream.
  5. Really good and simple explanation!! Thanks!