The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Help with using setup1.x for RAM (code 12) issue.

    Discussion in 'e-GPU (External Graphics) Discussion' started by Smorejohn, Jan 11, 2013.

  1. Smorejohn

    Smorejohn Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    I'm running a Sony Vaio VGN-FW139e p8400 intel core 2 duo @2.26 2.27

    Built in ATI radeon mobility 3400 with a gtx 650ti eGPU sucessfully running @x1 using

    Only boots with 2gb of ram unfortunately. Trying to get 3gb working at the moment I also have a 4gb stick I want to try once I get this compaction issue working.

    So ive tried the DSDT override and don't understand how to implement it into my registry without errors. Stuck with BSOD when using setup 1.x for compaction. I have a TOLUD of 3.0gb and only 128mb of valid pci space. When I run the 36bit compaction on the eGPU (ignore dgpu) I can get it to read 256mb of valid pci space. It doesn't work using 32bit or 32bitA compaction though. When I run the startup.bat/ chainload MBR or win7 it successfully boots but with BSOD. I can hear windows startup sounds just stuck with no display.

    Heres what my startup.bat looks like.

    call vidwait 60 10de:11c6

    call vidwait -d 10de:11c6

    call pci

    call grub4dos MBR or win7 (both give me bsod)

    I'm kinda lost using this program any advice on getting my setup to accept more ram? My comp runs like trash with only 2gb.
     
    Smorejohn, Jan 11, 2013
    #1
  2. Flammis

    Flammis Newbie

    Reputations:
    0
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Win7 x32 or x64? Because I think x32 runs out of memory allocation and therefore won't work.
    Correct me if I'm wrong...
     
    Flammis, Feb 1, 2013
    #2