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.

    Win 7 64-bit Success (q310-4gb Ram) After Much Frustration

    Discussion in 'Samsung' started by rauk, Jun 18, 2010.

  1. rauk

    rauk Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    64-bit install finally successful after 3rd-party (MemScope) RAM test and identification of faulty RAM module!

    I've posted previously on Q310 64-bit. Can hardly believe it, but can report a successful W7 64-bit install after oh-so-many re-installs and repair attempts. Haven't loaded Samsung drivers yet, but I'm so happy (and it's late) that I can't resist posting on a seemingly reliable (sfc /scannow test) 64-bit set-up.

    Along the way, I've been confused by the following:


    ​
    My very 1st 64-bit install held without fault for weeks until I started tweaking, got lost and decide to re-install. No successful 64-bit install since (until now!)


    ​
    Interim 32-bit disk image restores have always worked during the troubles and runs of 'sfc /scannow' have not reported a single non-repairable problem under 32-bit.


    ​
    Windows memory diagnostics has not identified a single problem while running in 32 or 64 bit!!!.

    I decided to dis-believe WMD: downloaded MemScope which reported thousands of RAM errors. Pulled the top-most 2GB Sodimm and then got a faultless Memscope run on remaining 2GB module. So tried another 64-bit install (2GB RAM only): no issues this time, i.e. no sfc "cannot repair" events afterwards. Have since downloaded Win Updates with no subsequent sfc "cannot repair" results. However, have not yet loaded Samsung 64-bit drivers/software. I know I should really have loaded Samsung and/or generic drivers as-well before posting, but (being able to type this at all while running in 64-bit) I couldn't resist an early description of events.

    Summary: My 32-bit installs kept going despite supposed faulty RAM module, but 64-bit would not. I've now installed Win7 Home Premium 64-bit (retail) with a single fault-free 2GB RAM module installed and no faults yet detected. I'm not OS savvy, so guessing the 32 versus 64 bit operability question comes down to the fact that 64-bit can "see" the full corrupted 4GB RAM while W7-32bit sees only 3GB (which happens to be the good 3GB of the 4GB available - or something like that).

    rauk
     
    rauk, Jun 18, 2010
    #1