Interesting problem with nForce...

Printable View

03-06-2003, 11:05 AM
LaValva

Interesting problem with nForce...

Well I called Crucial today about my memory problems: (http://www.sharkyforums.com/showthre...hreadid=181512)

The tech support guy told me they are having a lot of problems with the nForce chipset and their PC-2700. Now does anyone know if this is ALL pc-2700 or if it's just Crucial's? They offered me a refund, so I'm just going to take that for now. Does anyone have an Asus A7N8X or Deluxe and have a good experience with PC-2700 or PC-3200? Thanks for the advice.

EDIT: Now the post in General Hardware has me thinking, should I just get PC-2100? I'm not going to overclock. Would I notice a difference between 2100/2700/3200?
03-06-2003, 02:14 PM
pronade

It is the PC2700 out of spec. Try another good quality brand. I had same problem with some PC2700 memory. PC2700 is faster than PC2100, you can see the difference, very obvious.
03-06-2003, 02:20 PM
muisejt

I would assume he just meant Crucial, I use Samsung PC2700 with my A7N8X Deluxe, no problems here
03-06-2003, 05:10 PM
LaValva

Quote:

Originally posted by pronade
It is the PC2700 out of spec. Try another good quality brand. I had same problem with some PC2700 memory. PC2700 is faster than PC2100, you can see the difference, very obvious.

My question is, will i see the difference without overclocking? I was reading the only way you'll see a performance gain with pc-2700 or 3200 is if you bump up the FSB, is this true?
03-06-2003, 08:32 PM
mcarag

2100, 2700, and 3200 are all different FSBs. 2100 is the RAM bandwidth at 266 MHz FSB; 2700 at 333 MHz; 3200 at 400. So in other words, yes... In order to see the difference between 2100 and 2700, you'll have to run the 2700 at 333 MHz FSB.
11-10-2003, 06:04 PM
Waisztarroz

Woah! I have Crucial 2700 and an Epox 8rda+ (nForce2). I've noticed a lot of memory dumps, especially when I try to overclock. This has caused me to have to reformat a couple times, also, as it damaged the Windows installation. I can't believe this is actually a known issue.

I thought maybe I just had bad sticks or something... wow. It was getting worse and worse where the computer wouldn't boot at stock FSB and "turbo" or "aggressive" timings.

Oh, woops, I did not mean to rez the thread. I was searching for this issue and came across it, then got all excited. Sorry.:o