RAM identification and speeds

Off topic chat and stuff that doesn't fit elsewhere.
Post Reply
User avatar
His Royal Majesty King V
Veteran K6'er
Posts: 444
Joined: Tue Jul 17, 2001 4:06 pm
Location: New Jersey

RAM identification and speeds

Post by His Royal Majesty King V » Thu Aug 31, 2006 9:44 am

All,

Sorry I haven't been here much, but between a really funky job market, and now having a Royal Majesty Prince V, time's been a bit lacking!

Well, onto the questions:

I've got two SDRAM chips I can't quite identify. They're definitely older units.

I've been using Everest Home Edition v2.20, and if you go to Motherboard -> SPD, it'll list the RAM modules installed, and give you quite a bit of information, most importantly to my question Memory Timings.

I'm using a P2-266 as my test-mule, and have thus gleaned quite a bit of info about some old DIMMs that I have (including a 4-chip, single-sided 32MB piece that's brutally fast at 100MHz . . runs 2-2-2-5, which I didn't think such small modules were available at).

Anyway, there are two DIMMS I have that Everest can't identify. One of them is lacking that little SPD chip, though strangely, the other one has one, but Everest still simply won't list it at all.

So, what I'm wondering is, does anyone know, or is there any free software out there, that will tell me what memory timings these two DIMMs will run trouble-free at a given FSB?

The one without the SPD chip has NEC chips, 32MB total, 16 chips (8 on each side), with the following markings:

Code: Select all

NEC JAPAN
D4516821AG5
-A10-7JF
  9805AY007
I believe it's a PC100 unit, but that's all I've been able to determine, and I'm not even 100% sure on that.
There are also 2 stickers on it, each of which fits onto a single one of the chips, one of which reads:
EU32SDRAM808S
and the other:
72.24341.00N


The second DIMM I think is a PC66 unit, though I've come across references stating that some PC66 modules will perform better than some PC100's. This is the one that has an SPD chip on it, but Everest acts as if it doesn't. It's also a 16-chip unit (8 chips on each side), and 32MB. Anyway, the chips on this one read:

Code: Select all

 KOREA C206
 9819 FFF0
HM5216805TT10H
There are also some stickers, one of which fits on one memory chip:
290069
010K
S-DR LD-32-HT
Void if Removed

and the second of which spans 4 of the chips and reads:
RM-DM-SDRAM-32M-S-DRAM LD-32HT
(a UPC bar code, with the following numbers under it: 0 75028 00000 4)
090198-UME-460390

Also printed on the corner directly on the module is:
POWMEM
ASSY IN USA


I've done quite a bit of searching on Google, but it's been mostly fruitless, other than that the former has NEC chips (duh) and is PC100, the latter has Hitachi chips (most likely), and is probably PC66.

Anyone have access to datasheets, or know where I can get software that will definitely identify the SPD-equipped one? I tried searching Hitachi's and NEC's websites to no avail. My goal is really to find out what the ideal timings are at a given FSB.
FIC PA-2103 E-O036, K6-2+ 450 2.0V @ 500 1.9V
FIC PA-2013 E-O036, K6-III 450 2.2V @ 500
Acer quasi-proprietary Mid-tower, P-II 266

User avatar
Uranium235
Senior K6'er
Posts: 183
Joined: Mon Sep 12, 2005 9:59 pm

Post by Uranium235 » Thu Aug 31, 2006 10:09 am

You could try Sisoft Sandra, sometimes that works when Everest won't.

There's also DocMemory SPD Reader 1.4
http://www.majorgeeks.com/DocMemory_SPD ... d4383.html

:)

cake
Bios Fryer
Posts: 217
Joined: Sun Jul 01, 2001 3:12 pm
Location: Stockholm, Sweden
Contact:

Post by cake » Thu Aug 31, 2006 10:12 am

Does this tool work?
http://www.heise.de/ct/ftp/ctspd.shtml

Was a while since I used it myself..

And congratulations on Prince V!! :D
XP-M 2400+ @ 10x220, Epox 8RDA3+
512 MB PC3200 KingMax
15 GB Quantum Fireball LCT + 60 GB Seagate Barracuda IV
Radeon 8500LE

User avatar
His Royal Majesty King V
Veteran K6'er
Posts: 444
Joined: Tue Jul 17, 2001 4:06 pm
Location: New Jersey

Post by His Royal Majesty King V » Thu Aug 31, 2006 3:38 pm

U235: The DocMemory one doesn't seem to work, just hangs. The information at the website does seem to imply that it only works on Intel and SiS chipsets with DDR. My stuff's Intel, but ancient SDR equipment.

EDIT: Sandra works, but doesn't give a whole lot of info. I had to use an older version that would work with Win98se. Just gives CL values.

Cake: The ctspd program worked after a manner. It gives me a LOT of information, though some of it seems to contradict what Everest says. It did however also give me information about that one Hitachi-chipped module, but I don't know how to directly correspond it to what Everest says.

For example, on the 32MB module that Everest *does* recognize, I get the following info:

Code: Select all

Memory Timings:
   @100MHz:   3.0-3-3-5 (CL-RCD-RP-RAS)
   @ 76MHz:   2.0-2-2-4 (CL-RCD-RP-RAS)
However, for that same module, ctspd says:

Code: Select all

                              SPD-EEPROM      66MHz      100MHz
CAS Latency                      2/3            2           3
_RAS to CAS delay tRCD          26 ns           2           3
RAS precharge tRP               26 ns           2           3
RAS cycle time tRC                              8           8
RAS active time tRAS            50 ns           5           5
Ok, so I get which labels correspond to each other between the two, but why do they disagree, specifically with RAS/tRAS?

Here's what the 64MB module says:
Everest:

Code: Select all

Memory Timings:
   @100MHz:   3.0-3-3-5 (CL-RCD-RP-RAS)
   @111MHz:   2.0-3-3-6 (CL-RCD-RP-RAS)
Huh? CL is faster at a higher FSB?!

EDIT: Sandra confirms it as well: CL3 at up to 100MHz, CL2 at up to 111MHz... weird.

ctspd:

Code: Select all

                              SPD-EEPROM      66MHz      100MHz
CAS Latency                      2/3            2
_RAS to CAS delay tRCD          26 ns           2
RAS precharge tRP               26 ns           2
RAS cycle time tRC                              8
RAS active time tRAS            50 ns           5
Apparently this thing's SPD specifically specs it at 66MHz, though it appears to be equal in speed (if not better, if Everest is to be believed) to the previous one.


And here's the one that was an unknown for Everest, so I've only given the ctspd values:

Code: Select all

                              SPD-EEPROM      66MHz      100MHz
CAS Latency                     1/2/3           1
_RAS to CAS delay tRCD          30 ns           2
RAS precharge tRP               30 ns           2
RAS cycle time tRC                              8
RAS active time tRAS            50 ns           5
Again, ctspd seems to think it's "officially" 66MHz only (as shown by the box labeled "PC100 compatible"), but what's with that funky extra-fast CAS Latency, particularly given that RP and RC are a hair slower?

I think I'm more confused than when I started out.

Anyone have any thoughts or insights?
FIC PA-2103 E-O036, K6-2+ 450 2.0V @ 500 1.9V
FIC PA-2013 E-O036, K6-III 450 2.2V @ 500
Acer quasi-proprietary Mid-tower, P-II 266

Jim
K6'er Elite
Posts: 1745
Joined: Wed Jan 21, 2004 7:10 pm
Location: Toronto

Post by Jim » Thu Aug 31, 2006 10:40 pm

Unless you are dead set on using them, I can snail mail you a matched pair of single sided, (8 chips), Infineon 128s I have sitting around that I will never use. I think they are PC100, though they might be 133.
Superpuppy 3
K6-3+ 450 ACZ (6x100)
DFI K6BV3+/66 Rev B2 (2 Meg) w/ 2x28mm Chipset Fans
2x256 Meg PC 133 Hynix SDRAM
1x 20G Maxtor (7200)
2x 80G Maxtor (7200) Ducted w/ 2x486 Fans Mount
52/24/52/16 LG CDR/RW/DVD
8/4/3/12/24/16/32 LG Super Multi
ATI 9000 aiw Radeon AGP
SB Audigy 1 MP3 Sound
CMD 649 IDE Controller
NEC USB 2 Card

User avatar
tazwegion
Veteran K6'er
Posts: 349
Joined: Sat Jun 21, 2003 11:13 am
Location: Victoria, Australia

Post by tazwegion » Sat Sep 02, 2006 7:39 am

It's been a little while since I tested any RAM modules, but Memtest86+ provides information r/t motherboard chipset, processor & memory etc. worth a look in perhaps?

Additionally... I have a matched pair of AOpen 64Mb SDram sticks (PC100) which ran flawlessly @ 133Mhz in an old Soltek Skt. A I used to have ;)
Image

Super_Relay
Site Admin
Posts: 215
Joined: Sat Jun 02, 2001 5:53 pm
Location: Australia

Post by Super_Relay » Tue Sep 05, 2006 5:11 pm

CPUz will also read the SPD data from modules.

I use it at work all the time to figure out what ram i need to upgrade a machine without having to take the case off to look

User avatar
KachiWachi
K6'er Elite
Posts: 507
Joined: Wed Sep 21, 2005 10:53 am
Location: Pennsylvania, USA

Post by KachiWachi » Wed Sep 06, 2006 5:57 am

Just some random thoughts -

SPD modules can be wrong. If the manufacturer programs incorrect data into it, the system would never know it.

No SPD/damaged SPD, no readout in programs that read the SPD. :(

NEC JAPAN
D4516821AG5-A10-7JF
9805AY007
EU32SDRAM808S

D45 = NEC SDRAM
16 =16
8 = x8
2 = 2 bank
1 = LVTTL
A = Revision
G5 = Package (44 pin TSOP II)
-A10 = -10 = 10nS = 100MHz
-7JF
9805AY007 = Date Code (Week 5, 1998)
EU32SDRAM808S = 32MB SDRAM

Datasheet -> http://www.elpida.com/eolpdfs/E0122N10_EOL.pdf

KOREA C206
9819 FFF0
HM5216805TT10H
290069 010K S-DR LD-32-HT
RM-DM-SDRAM-32M-S-DRAM LD-32HT

HM5 = Hitachi
2
16 = 16
8 = x8
05TT
10H = 10 = 10 ns = 100MHz
9819 = Date Code (Week 19, 1998)
Other = 32MB SDRAM

Datasheet -> http://www.elpida.com/eolpdfs/E0168H10_EOL.pdf
Moderator - Wim's BIOS

PC #1 - DFI 586IPVG, K6-2/+ 450 (Cyrix MII 433), 128 MB EDO. BIOS patched by Jan Steunebrink.
PC #2 - Amptron PM-7900 (M520), i200 non-MMX, 128 MB EDO
PC #3 - HP8766C, PIII-667, 768 MB SDRAM
PC #4 - ASUS P3V4X, PIII-733, 256 MB SDRAM
PC #5 - Gateway 700X, P4-2.0 GHz, 768 MB PC800 RDRAM
PC #6 - COMPAQ Evo N1020v laptop, P4-2.4 GHz, 1 GB PC2700 DDR
PC #7 - Dell Dimension 4600i, P4-2.8 GHz, 512 MB PC2700 DDR
PC #8 - Acer EeePC netbook, Atom N270 @ 1.60 GHz, 1 GB RAM
PC #9 - ??? ;)

DonPedro
K6'er Elite
Posts: 575
Joined: Wed Jul 27, 2005 2:11 pm

Post by DonPedro » Wed Sep 06, 2006 5:56 pm

@kachiwachi

of course the spd-data might be incomplete or false, but the program ctspd (cake gave the link to it some posts above) detects faulty information and displays whether the data is complete/incomplete or if the checksum of the data gives an error.

User avatar
KachiWachi
K6'er Elite
Posts: 507
Joined: Wed Sep 21, 2005 10:53 am
Location: Pennsylvania, USA

Post by KachiWachi » Thu Sep 07, 2006 4:55 am

Must be a damn sophisticated program then (for 400 KB)...if it actually runs memory tests and can adjust timing parameters on the fly (to find false/incomplete/faulty information). :wink:

I'm sure all it does is dump the hex code from the SPD, then decodes the parameters...just as Everest (or any other program) would.

In any case...the posted datasheets will tell all.
Last edited by KachiWachi on Fri Sep 08, 2006 4:25 pm, edited 1 time in total.
Moderator - Wim's BIOS

PC #1 - DFI 586IPVG, K6-2/+ 450 (Cyrix MII 433), 128 MB EDO. BIOS patched by Jan Steunebrink.
PC #2 - Amptron PM-7900 (M520), i200 non-MMX, 128 MB EDO
PC #3 - HP8766C, PIII-667, 768 MB SDRAM
PC #4 - ASUS P3V4X, PIII-733, 256 MB SDRAM
PC #5 - Gateway 700X, P4-2.0 GHz, 768 MB PC800 RDRAM
PC #6 - COMPAQ Evo N1020v laptop, P4-2.4 GHz, 1 GB PC2700 DDR
PC #7 - Dell Dimension 4600i, P4-2.8 GHz, 512 MB PC2700 DDR
PC #8 - Acer EeePC netbook, Atom N270 @ 1.60 GHz, 1 GB RAM
PC #9 - ??? ;)

DonPedro
K6'er Elite
Posts: 575
Joined: Wed Jul 27, 2005 2:11 pm

Post by DonPedro » Thu Sep 07, 2006 12:39 pm

no, it does not run memory tests nor does it allow for on the fly changing of parameters.

what it does is it reads out the spd-parameters, checks for completeness and checks whether the data is logically "valid".

why not just downlaod it and give it a try?
Attachments
ctspd.png
ctspd.png (34.53 KiB) Viewed 12359 times

Post Reply