Cant Enable PAE mode

Page 4 of 4 FirstFirst ... 234

  1. Posts : 65
    Windows 7 Ultimate x64
    Thread Starter
       #31

    i havent had any driver issues yet :3 (though the onboard video is an nvidia it's disabled) my main videocard is an ATI Radeon HD 5750, and i use a 5$ usb Soundcard i got off Ebay.. no issues there w/ teh 3GB switch on i got Secondlife to use upto 2GB Ram. (a mmo of sourts.. :P its highly known for leaking/eating ram worse than the old chkdsk bug of win7.)
      My Computer


  2. Posts : 5,642
    Windows 10 Pro (x64)
       #32

    Cael said:
    ...chkdsk bug of win7.)
    Its not a bug.
      My Computer


  3. Posts : 65
    Windows 7 Ultimate x64
    Thread Starter
       #33

    ok my bad i never really understood why it does that so i thought it was a bug.
      My Computer


  4. Posts : 5,642
    Windows 10 Pro (x64)
       #34

    When you use the "Repair" option of chkdsk, it uses as much memory as it can to repair the disk as fast as possible. You should only use the repair option if the disk actually needs it, nor should you be using the computer while running a chkdsk.
      My Computer


  5. Posts : 65
    Windows 7 Ultimate x64
    Thread Starter
       #35

    but anyways we can mark it as solved :3
      My Computer


  6. Posts : 173
    Windows
       #36

    yowanvista said:
    The way it works for Memory is it allows an added table the OS can use to add the “same” address in more than one place. Think of this as adding a "street name" to your "address". 1234567890 on table A is not the same as 1234567890 on table B. The limitation is that this *must* be provided for in your programs and drivers in order to work. If your mailman only looks at the '1234567890' but never looks at the street name, then he can and will sometimes deliver a letter to the wrong place. The same thing is true of PAE - If/when then individual program haven’t been coded to look in multiple tables for the needed memory locations in addition to the numerical addresses, messages can and will often go to the wrong place. In Windows, this is a called a “memory access violation”, and results in a blue screen. Additionally, individual programs under PAE can still only use up to 4 GB. Kernels and drivers can be made aware of PAE, but they can still only use 4 GB ranges at a time.
    I came across another forum where this was posted. Where did you get this from? It is simply not how it works.
      My Computer


  7. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #37

    pallesenw said:
    yowanvista said:
    The way it works for Memory is it allows an added table the OS can use to add the “same” address in more than one place. Think of this as adding a "street name" to your "address". 1234567890 on table A is not the same as 1234567890 on table B. The limitation is that this *must* be provided for in your programs and drivers in order to work. If your mailman only looks at the '1234567890' but never looks at the street name, then he can and will sometimes deliver a letter to the wrong place. The same thing is true of PAE - If/when then individual program haven’t been coded to look in multiple tables for the needed memory locations in addition to the numerical addresses, messages can and will often go to the wrong place. In Windows, this is a called a “memory access violation”, and results in a blue screen. Additionally, individual programs under PAE can still only use up to 4 GB. Kernels and drivers can be made aware of PAE, but they can still only use 4 GB ranges at a time.
    I came across another forum where this was posted. Where did you get this from? It is simply not how it works.
    It was posted here on SF by a member :)
      My Computer


 
Page 4 of 4 FirstFirst ... 234

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:19.
Find Us