New Posts  All Forums:Forum Nav:

E1705 with OCZ2MV6674GK

post #1 of 19
Thread Starter 
I just purchased 4GB of OCZ PC2 5400 RAM (OCZ2MV6674GK) for use in my E1705. However, I'm finding that the machine is just downright flaky. Windows 2003 Server recognizes 3.25GB as expected.

What happens is that I'll log in and the system will work for a couple of minutes and then the mouse will freeze. After about 20-30 seconds the screen will go blank and the entire system is halted. I did run the bios memory tests and didn't find any issues.
post #2 of 19
Tried running it with just one of the 2GB sticks in there?
post #3 of 19
From what I have read, it's the E1705 bios limiting it (and is a problem in some older servers and mobos as well). There's a sticky in this forum that is titled "**E1705/M1710 FREQUENTLY ASKED QUESTIONS** Go here first ".

So, uh, go there first.
http://www.notebookforums.com/thread205763.html


FYI, article explaining the "real" meaning of 4GB limit in x86 os.
http://www.brianmadden.com/content/a...it-really-mean-
post #4 of 19
Thread Starter 
I tried the 2GB sticks individually (1 bank of 2GB) and didn't see any apparent problem. I then tried combining one of the 2GB sticks with a 1GB stick that I had from before and I see the problem again.

I've also tried running diagnostics with the full 4GB and the basic memory tests didn't return any problems. I'm planning on running the extended diagnostic tonight to see what happens.
post #5 of 19
Thread Starter 
[quote=eduncan911;2798873]From what I have read, it's the E1705 bios limiting it (and is a problem in some older servers and mobos as well). There's a sticky in this forum that is titled "**E1705/M1710 FREQUENTLY ASKED QUESTIONS** Go here first ".

So, uh, go there first.
http://www.notebookforums.com/thread205763.html

Thanks - I had already checked that post and *thought* I was following all of the guidelines:

- Up to 4GB PC5400 667Mhz.
- Don't expect the OS to see more than 3.25GB

Did I miss something? I'm seeing the 3.25GB as expected it's just that the system is not operating in a stable manner with 4GB (3.25GB available) installed.
post #6 of 19
Ah, sorry about that. Skipped over the fact of your mouse hanging/unstable.

As someone else suggested, pull a stick and try to operate the system on 2GB. Then switch out the chip and try it again. Not sure which is SLOT0, but both slots do not have to be full (u can leave one empty). So if you try one and the system doesn't post, try the other slot.

If it's still unstable trying it with each stick seperately; still got your old sticks? If so, go back and install them and see if it's unstable.

I remember back in the day I've fried many of ram modules. It's Winter time, which is the time of the year for the highest Static Electricity... You never know.

-E
post #7 of 19
Thread Starter 
Eric,

Thanks. Yes - I did the 'parking cars' routine today. What's throwing me at this point is that the modules appear to work when used individually (single 2GB stick), but fail when combined with each other (2 x 2GB) or with one of my old modules (1 x 2GB + 1 x 1GB).

As such, I can't make a determination if the problem is with the base system (problems above 2GB) or with the modules (timing or dual channel or something other memory-type incompatibility). I would that if the modules work individually they should work in combination also.

Any ideas on conclusive tests that I could perform on each module individually or something I could run against the base system?
post #8 of 19
It is possbile your having some kind of comaptiblity issue with the 2 Gig Sticks, I would consider RMA if it is still in the return windoe and try a different manufacter of Memory
post #9 of 19
Try updating your BIOS to the latest, and if that doesn't fix it, RMA or return the sticks and buy a different brand.
post #10 of 19
Another idea would be go grab CPU-Z and see what the actual timings that your BIOS is setting each stick to per the SPD it decyphers, from each chip.

http://www.cpuid.com/cpuz.php

It may be that the bios is setting them incorrectly. Maybe even get both in the system just long enough to get CPU-Z to spit out what timings it went to, compared to each stick's results. I believe I've read in the forums here that there is a bios update/hack that allows you to adjust the timings manually.

Don't be a hero and try to get the lowest timings. I was doing that and running into stability issues at 2.7v on my desktop trying to get over 1080Mhz with lower-than-stock timings. Highest bandwidth I cranked out was 9.1 GB/s (yes, B=Bytes, not bits there).

Once I relaxed, and even raised-above-stock timings, I was able to get the desktop's memory up to 1200mhz to match the FSB (1:1 FSB:Memory ). And am now cranking out 15.2 GB/s. Unbelievable.

That convienced me that the-lowest-timings-isn't-everything in the game of speed. It was most definantly so back in the DDR days, but DDR2 has taken off and left them in the dust.
post #11 of 19
Did you run memtest? Go to www.memtest86.com

Download and test each stick individually. Take a while - you want to get about 6 passes on each stick. Make sure you test them in different slots as well.

If either of them fail, RMA.
post #12 of 19
EDIT: In response to Buck47's post, on 2.5 hours of sleep, I read, "Did you [mean] memtest?". Hence what caused the post below. Sorry. But non-the-less, some good info is below.

Nope. I meant CPU-Z.

MemTest tests the memory, but I've still had faults in mem chips even after it tested them OK. Not reliable IMO, but then again it's been years since I've used it. I kind of like Prime95 actually for my mem testing (over a few days, that is).

CPU-Z was mentioned for him to check the timing the BIOS is forcing the chips to run at. If it is not adhering to the SPD timings from the manufacturer of the chips, then either the BIOS is detecting a fault or it simply doesn't like the chips and is trying to compensate - or the chips are faulted and the bios is adjusting the timings to compensate "for the most part" until his system hangs.

Basically looking to see what the bios is forcing the timings to vs. the SPD has been a good indication of a detection fault for me. If the timings are dead-on, then it most likely is the chip(s). If the timings are off, I'd look more at the bios/mobo combination and mem compatibility. Most of the time, it's been high-end memory overclocked in mobos that weren't detecting the SPD correctly for me.

I say to review each chip seperately because I've seen mobos take a "matched pair" of sticks, and give different timings (when overclocked) per stick when reviewed individually.


Quote:
Originally Posted by Buck47 View Post
Did you run memtest? Go to www.memtest86.com

Download and test each stick individually. Take a while - you want to get about 6 passes on each stick. Make sure you test them in different slots as well.

If either of them fail, RMA.
post #13 of 19
Thread Starter 

CPU-Z Results

Here are the Chipset & Memory results from CPU-Z. The only difference reported appears to be in the Bank Cycle Time (tRC).

<pre>
Memory TypeDDR2DDR2
Memory Size2048 MBytes4096 MBytes
Memory Frequency332.5 MHz (1:2)332.5 MHz (1:2)
CAS# Latency (tCL)5.0 clocks5.0 clocks
RAS# to CAS# (tRCD)5 clocks5 clocks
RAS# Precharge (tRP)5 clocks5 clocks
Cycle Time (tRAS)15 clocks15 clocks
Bank Cycle Time (tRC)21 clocks20 clocks
Module 1DDR2, PC2-5300 (333 MHz), 1024 MBytes, Hyundai ElectronicsDDR2, PC2-5300 (333 MHz), 2048 MBytes, OCZ
Module 2DDR2, PC2-5300 (333 MHz), 1024 MBytes, Hyundai ElectronicsDDR2, PC2-5300 (333 MHz), 2048 MBytes, OCZ
</pre>
post #14 of 19
Since the SPDs are dead-on, then I'd point a finger at the chips as the culperate (sp ck).

You said the system is stable with just 1 chip in, either chip? If they were a matched pair, ask for another set. Expect to pay shipping (eh, worth the effort).
post #15 of 19
Quote:
Originally Posted by eduncan911 View Post
Since the SPDs are dead-on, then I'd point a finger at the chips as the culperate (sp ck).

You said the system is stable with just 1 chip in, either chip? If they were a matched pair, ask for another set. Expect to pay shipping (eh, worth the effort).
OCZ's Tech support is 2nd to none.
Go here: http://www.ocztechnologyforum.com/fo...splay.php?f=46

Once you join their support forums, post your problem, and you'll most likely get RMA support immediately from OCZTony. Again, you will first need to post your problem and the steps you've taken to troubleshoot.

I've used OCZ modules exclusively since the year after they opened their doors. Great quality and excellent support.
post #16 of 19
Thread Starter 

Could the OS be the problem?

UPDATE: I just installed a couple of sticks of G.SKILL DDRII667 PC2-5300 (CL5-5-5-15) and am seeing the exact same issue.

Since all of the memory tests I've ran don't turn up any errors I'm starting to suspect the OS install (Windows 2003 Server Standard). I'm thinking that I'll do a clean install on a separate drive just to test and see what happens.

Any other ideas?
post #17 of 19
I kind of doubt it's the OS.

austinnichols: Are you trying to enable PAE with 2003?
post #18 of 19
Thread Starter 
No - no additional switches. I'm just trying to get up to 3.25 GB so that I can run a couple of concurrent vmware sessions with acceptable performance. I use the sessions for demos, etc.
post #19 of 19
Argh, i meant the /3GB switch not PAE. For VMWare, you'll want to run /3GB !!

In short: Windows 32bit (2000/2003/XP/Vista) does a 50%/50% split of memory available, up to 4 GB, for the "Kernel" and for the "Applications". Meaning, 2 GB is available for os/kernel (waaay more than enough), and your apps are limited to 2 GB address space. The /3GB switch changes to a 25%/75% rule, where the OS gets 25% of the memory available and the apps get a 75% of memory available. I use the "%" percentage because this works even with less ram of 4GB, but it only goes to the max of 4GB.

The only difference is Vista auto-enables the /3GB now, and I just had to set /PAE using bcdedit.
New Posts  All Forums:Forum Nav:
  Return Home