RAM probs under Win 7 64 bit.

R

Rebecca

Yousuf Khan said:
Well, there is a memory tester menu option available through the Windows 7
boot menu, but that tester seems to be just some kind of placebo. It shows
Microsoft can make a memory tester too, but like so much about Microsoft,
there's a lack of usefulness behind the flashiness.

Yousuf Khan
Can you give some cites? or is this just your opinion?
 
J

Jumbo Jack

well unbelievable, the BIOS had the memory set to AUTO 1066....so he set it
to MANUAL 1333 and all is now working at 8gb.

thanks for all your help and pointers.
 
L

Leythos

Son is having memory problems.

With 4 x 2GB sticks installed the BIOS sees 8GB but Win7 blue screens.

With 3 x 2GB + 1 x 1GB Win7 runs no problems.

When Googling there appears to be 100's Win7-64bit users with similar
problems and numerous suggestions to fix.

Anyone have a similar problem and did they fix it and how.
I've seen the same issue and it has nothing to do with Windows, it's
that the motherboard you're using only supports 8GB Max and maps the On-
Board video into that 8GB memory space.

You have two choices, assuming that this fits your situation:

1) Use less than 8GB memory
2) Purchase a video card and stop using the on-board video
 
C

Char Jackson

I've seen the same issue and it has nothing to do with Windows, it's
that the motherboard you're using only supports 8GB Max and maps the On-
Board video into that 8GB memory space.

You have two choices, assuming that this fits your situation:

1) Use less than 8GB memory
2) Purchase a video card and stop using the on-board video
The situation you describe shouldn't result in a BSOD. It should
simply result in Windows reporting less than 8GB available.
 
B

Brian Gregory [UK]

Jumbo Jack said:
well unbelievable, the BIOS had the memory set to AUTO 1066....so he set
it to MANUAL 1333 and all is now working at 8gb.

thanks for all your help and pointers.
That's pretty weird, in that it apparently seems to work better running
faster.
Maybe there is one of the timings that comes out marginally slower running
at 1333 when rounded up to the nearest cycle.
 
Y

Yousuf Khan

Can you give some cites? or is this just your opinion?
I wouldn't be saying this if it weren't something I experienced.

Yousuf Khan
 
P

Paul

Leythos said:
I've seen the same issue and it has nothing to do with Windows, it's
that the motherboard you're using only supports 8GB Max and maps the On-
Board video into that 8GB memory space.

You have two choices, assuming that this fits your situation:

1) Use less than 8GB memory
2) Purchase a video card and stop using the on-board video
A P45 doesn't have onboard video. There would already be a video card
of some sort.

Paul
 
J

Jumbo Jack

Paul said:
A P45 doesn't have onboard video. There would already be a video card
of some sort.

Paul
Yes, correct.

I have posted the good news in that all is now 100% after setting the memory
frequency to Manual 1333 thanks.
 
C

charlie

Yes, correct.

I have posted the good news in that all is now 100% after setting the memory
frequency to Manual 1333 thanks.
If the problem re-appears, consider cleaning the RAM sockets and
connectors. (Power really and completely off, naturally!) There is a
remote possibility of this type of problem occurring due to more than
desired resistance edge connector pin(s) to socket.
Alcohol, such as 90 proof "Golden Grain" on a lint free paper towel
seems to work well for the RAM edge connector. If you mate the connector
with the connector wet, it helps clean the socket.
(Just don't fire things up until everything dries out.)

This type of issue seems to occur more often when the price of gold is
high and the connector and board mfrs skimp on the gold coatings. The
normal resistance is a very few milliohms across the pin/connector
connection. If it gets too high, the connection becomes more of a
capacitive connection, explaining why it might work at a higher speed
and not at a lower speed.
To be honest, the last time I ran into the problem was with socketed
memory chips and edge card connectors. We found both silicon
contamination on the mating surfaces, and pits and fissures in the gold
plating. (Also, plating thickness was less than normal) HP also found
some sort of mold or fungus on pins in some systems in California about
the same time. The silicon may have come from the base metal used to
make the contacts, or from lubrication used in the forming process.
Some "tuner cleaner" also contained silicon.
 
J

Jack

Nil said:
You haven't said what you experienced.
I started Windows 7's memory test and went outside. I tripped while I was
outside; it was the fault of the Windows 7 memory test. I'll never run it
again! I could have been seriously injured.
 
G

Gene E. Bloch

I started Windows 7's memory test and went outside. I tripped while I was
outside; it was the fault of the Windows 7 memory test. I'll never run it
again! I could have been seriously injured.
Yes, but if you had been running MemTest86, you *would* have been
seriously injured.

QED :)
 
N

Nil

I started Windows 7's memory test and went outside. I tripped
while I was outside; it was the fault of the Windows 7 memory
test. I'll never run it again! I could have been seriously
injured.
Loser! If you used Linux you would never have tripped.


Actually, it's more like,

Loser! If you used Linux you would never have gone outside!
 
R

relic

Nil said:
Loser! If you used Linux you would never have tripped.


Actually, it's more like,

Loser! If you used Linux you would never have gone outside!
ROFL
 
G

GreyCloud

Son is having memory problems.

With 4 x 2GB sticks installed the BIOS sees 8GB but Win7 blue screens.

With 3 x 2GB + 1 x 1GB Win7 runs no problems.

When Googling there appears to be 100's Win7-64bit users with similar
problems and numerous suggestions to fix.

Anyone have a similar problem and did they fix it and how.
Did you use an anti-static wrist strap installing the ram sticks?
It is very easy to cause damage to a ram stick from static discharges...
even tho you aren't aware of it. One of the sticks is most likely bad.
Get an anti-static repairmans kit and then attach the wrist band
ground strap to chassis ground... and of course also have the
anti-static mat underneath the computer. Then move the one stick into
the first slot that you had previously removed (up above) on the mobo.
Then see if the machine will boot. If it doesn't, then you've found the
bad ram stick. On unix systems, when a kernel panic happens, it means
99% of the time it is bad memory. OTW, the os can't access the memory
correctly. And the most probable reason for your BSOD.
 
J

Jumbo Jack

Jumbo Jack said:
Son is having memory problems.

With 4 x 2GB sticks installed the BIOS sees 8GB but Win7 blue screens.

With 3 x 2GB + 1 x 1GB Win7 runs no problems.

When Googling there appears to be 100's Win7-64bit users with similar
problems and numerous suggestions to fix.

Anyone have a similar problem and did they fix it and how.
Well the move from 1066 to 1333MHz he thought had fixed the prob did not
last more than 3 or 4 restarts.

He's now done the Memtest86 on all 2Gb modules and found one giving numerous
errors.....oh dear....back to the supplier.
 
Y

Yousuf Khan

You haven't said what you experienced.
Well, what's there to say about a RAM tester? I had a known bad RAM, and
the Windows memory tester didn't even notice it -- gave it an all-clear.
Memtest86+ picked it up within seconds.

Yousuf Khan
 
Y

Yousuf Khan

Well the move from 1066 to 1333MHz he thought had fixed the prob did not
last more than 3 or 4 restarts.

He's now done the Memtest86 on all 2Gb modules and found one giving numerous
errors.....oh dear....back to the supplier.
That has happened to me more than once. You think you've got the problem
licked, because it worked once, and then the problem reappears and bites
you in the gluten again, from out of nowhere. :)

The good thing about RAM is that when it goes wrong, they often give you
a lifetime warranty.

Yousuf Khan
 
N

Nil

Well, what's there to say about a RAM tester? I had a known bad
RAM, and the Windows memory tester didn't even notice it -- gave
it an all-clear. Memtest86+ picked it up within seconds.
I've had bad RAM that Memtest86+ didn't detect.

So, what's your point?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top