JEDEC Manufacturer's ID codes addition for unknown RAM manufacturers

[x86fr]

JEDEC JEP106 Manufacturer ID list is very long and many brands are defunct since years or even decades.
We had to create a short list with the most well-known manufacturers. Others will reported as "Unknown".

If your RAM Module are detected as Unknown, or if you are a RAM manufacturer with a JEDEC ID Code and want Memtest86+ to detect your brand, please post a screen shot of the unknown module or your JEDEC ID here. It will added as soon as possible.

[Fantu]

on my test of today don't recognizes one ram module, also dmidecode don't show manufacturer field (show "0000"), is one module added after buying the notebook, is: https://www.amazon.it/gp/product/B0145WDNI4/
I don't know if is possible do something

[x86fr]

That's not uncommon for unbranded memory modules to have the manufacturer field not set (set to 0x0000 or 0x1f7f).
I will add a special case to distinguish "Unbranded" from "Unknown".

[x86fr]

PS: can you post a screenshot?

[Fantu]

second image here: https://imgur.com/a/W4trF1X

[x86fr]

This has been solved some commit ago. It should not display anything when jedec_id is blank.

[sstscrypto]

We are a manufacturer of computer memory, but your software does not show our JEDEC ID, our JEDEC ID is 08d0

[x86fr]

Will be added on next release

[sstscrypto]

thank you so much

[sstscrypto]

Will be added on next release

i download the Memtest86+ v6.00 Beta 3
no my JEDEC ID show in the test screen
My JEDEC ID is 08d0
Can we add our JEDEC ID to the list of recognizable ones?

[Nable80]

Is it actually 0x0850 ("Heoriady") which becomes 0x08D0 after adding a parity bit?
https://github.com/memtest86plus/memtest86plus/blob/main/system/jedec_id.h#L1101

[sstscrypto]

Is it actually 0x0850 ("Heoriady") which becomes 0x08D0 after adding a parity bit? https://github.com/memtest86plus/memtest86plus/blob/main/system/jedec_id.h#L1101

Dear Heoriady:
In response to your request I have assigned the following JEDEC Manufacturer ID number to your
company:
80 decimal (bank nine)
1101 0000 binary
D0 hex

These are my responses from JEDEC!

[sstscrypto]

screenshot

[sstscrypto]

Can you delete the comment next time? in JEDEC.H

[x86fr]

Will do, but what's the name of your company ? Is "Heoriady" correct ?

[sstscrypto]

Will do, but what's the name of your company ? Is "Heoriady" correct ?

YES correct is "Heoriady"

[Nable80]

@sstscrypto I have an off-topic question regarding memory manufacturing, can I contact you somehow, please?

I can also ask it here if it's allowed by maintainers. Maybe someone else knows the answer.

[01e3]

Can we also add 0x0313, "Golden Empire"?

If it helps, I can send a patch.

[x86fr]

I can also ask it here if it's allowed by maintainers. Maybe someone else knows the answer.

Create a new discussion. I can also help (I have a Jedec ID for my company)

Can we also add 0x0313, "Golden Empire"?

Will do. I have a global update planned soon.

[Nable80]

Create a new discussion. I can also help (I have a Jedec ID for my company)

Thank you very much! Created it there: #127

[sstscrypto]

@sstscrypto I have an off-topic question regarding memory manufacturing, can I contact you somehow, please?

I can also ask it here if it's allowed by maintainers. Maybe someone else knows the answer.

Sure you can contact me by E-mail hynix.cn@live.cn

[virxkane]

Is it possible to uncomment this line?

memtest86plus/system/jedec_id.h

Line 1327 in 18f1211

// { 0x0A3A, "Foxline" },

SPD: Foxline FL2400D4U17-8G.zip

[x86fr]

will be done on next update

[tatokis]

I have this Mushkin DDR2 991760 RAM. The vendor ID (0x577) is commented out and thus shows as unknown.

memtest86plus/system/jedec_id.h

Line 766 in c411590

// { 0x0577, "Avant Technology" },

It appears that Avant Technology is still the correct vendor, as according to http://www.avanttechnology.com/Home/index.php/our-company:

Avant, Edge, Mushkin and Avant de Mexico operate under the Avant Technology Corporate Umbrella.

In addition, memtest86+ v5 recognised the sticks as F6456U61E5800F. In v6 the field is completely blank (even after uncommenting the jedec id). I'm not sure which is the correct behaviour, since decode-dimms also shows no part number.

I have attached the SPD in case it helps.
991760.bin.gz

[x86fr]

I will add Avant Tech. for the next update.

About the Part Number String not displaying, your SPD dump shows a malformed string. The two first bytes of the JEDEC Part Number String (Bytes #73-#90) are end-of-string characters. Your module's SPD is not JEDEC compliant and can't be decoded properly. Memtest86+ v5 used another way to display this string, without checking the end-of-string chars.

[01e3]

So, what we have there:
00 00 46 36 34 35 36 55 36 31 45 35 38 30 30 46 00 00

Even if we change the logic, I'm not convinced that F6456U61E5800F would be actually a desired thing to show. This does not look like anything that can be considered a part number, even https://www.google.com/search?q=F6456U61E5800F says "About 0 results (0.21 seconds) ".

[Edit: it now points to this very bug]

[CMCanavessi]

I don't know if it's the same module, but that part number is actually on the sticker, with an "AV" prefix and a "9-SPHP" and the end.

Looks like the part number is "AVF6456U61E6800F9"

Edit: Oh, I see there's a difference "5800" vs "6800"... might even be a typo in the string.

[01e3]

Great catch!

http://www.avanttechnology.com/pdf/DataSheets/AVF6456U61E5800F9-AP.pdf says "AVF6456U61E5800F9"

So, the first two 00 00 characters should be "A" and "V" (0x41 and 0x56) - AV=AVANT, and perhaps we are missing "9" (0x39) at the end - REV=9.

Either EEPROM is corrupted or (more likely) coding / programming error?

[01e3]

(just noticed your edit)

There seem to be multiple flavors of this module:

• DDR2-800 CL5: http://www.avanttechnology.com/pdf/DataSheets/AVF6456U61E5800F9-AP.pdf
• DDR2-800 CL6: http://www.avanttechnology.com/pdf/DataSheets/AVF6456U61E6800F9-AP.pdf

See also: http://www.avanttechnology.com/pdf/DDR2-Decoder.pdf

So, not a typo! :)

[CMCanavessi]

Nice, that clears it up a bit

[FranciscoPombal]

Is there a technical limitation that prevents adding the full known list? What limitations are in play here?

[x86fr]

95% of the list are defunct manufacturers and adding them would add hundreds of KB of useless strings to the code.

[FranciscoPombal]

Sorry, let me rephrase the question: what would be the performance/compatibility/etc implications of adding those KB's? What are the current limitations preventing such an addition from being "zero cost" (i.e. regressions are not observed elsewhere when those added strings are not actually being used/accessed in some way).

[daiaji]

95% of the list are defunct manufacturers and adding them would add hundreds of KB of useless strings to the code.

Not surprisingly, quite a few memory manufacturers (some of them even produce DRAM chips) were destroyed by dumping by Samsung after South Korea increased its subsidies to Samsung.
Qimonda and Elpida, these are the two more famous Samsung victims.
There are countless unknown DRAM manufacturers.
Let alone OEM.
To be honest, these JEDEC IDs may be the last traces they left in this world.: (

[Nable80]

Can you uncomment ID 0x0356, please? https://github.com/memtest86plus/memtest86plus/blob/6799bfb/system/jedec_id.h#L481

One of my memory modules has this identifier: Slot 0: 256MB DDR-400 - Unknown (0x356)

[x86fr]

Will do before next update.

[BoDrate]

Could you uncomment 0x0671, "InnoDisk Corporation", please? We are using their memory modules.

[x86fr]

Noted for next update

[CMCanavessi]

95% of the list are defunct manufacturers and adding them would add hundreds of KB of useless strings to the code.

I was thinking about this. Would it be feasable to make that list of old manufacturers external? Say, memtest will look for a text file named a certain way, and if it exists, it will use it (together with its internal list). This way you could keep memtest with the more up-to-date list of vendors, but have the possibility of manually adding the older ones in a text file without altering the main binary. Best of both worlds imho.

[debrouxl]

memtest86+ has no concept of file access. Doing it in a portable way - that is, even for non-UEFI computers - requires implementing disk drivers, filesystem drivers, etc.

[bjlockie]

It is Silicon Power DDR4 8GB 3200MHz (PC4-25600) CL22 SODIMM 260-Pin Gaming Laptop RAM Notebook Computer Memory.

[nickos222]

Hello guys, please uncomment the following IDs:

memtest86plus/system/jedec_id.h

Line 34 in 18f1211

// { 0x0010, "NEC" },

memtest86plus/system/jedec_id.h

Line 114 in 18f1211

// { 0x0060, "LG Semi (Goldstar)" },

memtest86plus/system/jedec_id.h

Line 208 in 18f1211

// { 0x0140, "Viking Components" },

These have been verified on the real h/w with a patched memtest build.

[x86fr]

Will be added on next update

[TAbdiukov]

I can confirm that the line for "Strontium",

memtest86plus/system/jedec_id.h

Line 901 in 18f1211

// { 0x0703, "Strontium" },

Needs to be uncommented, too.

• Memtest86+ nondetection, https://imgur.com/NqL7aGq

More Proof that this is Strontium (A Singaporean small flash memory enterprise):

• CPU-Z: https://imgur.com/mfr8xUB
• AIDA64: https://imgur.com/3l9zjQu

[dstarr5d]

This is four sticks of Teamgroup ‎CTCED532G6400HC32ADC01

[ed806]

Please add our Jedec ID: 0E51 brand: Xiaoli.AI
Thanks!

[x86fr]

Add previous manufacturers added in commit 2d3b14e

[grkngkc]

Please add our Jedec ID: 0E58h brand: Trium Elektronik Bilgi Islem San Ve Dis Tic Ltd.
Thank you

[KevinKLL]

Please add our JEDEC Manufacturer's ID: 8FB3 Company: Xllbyte
in Memtest show:0xf33

Thanks!