VOGONS


First post, by AlessandroB

User metadata
Rank Oldbie
Rank
Oldbie

exhist a way to check if some chip of memory (socketed on mainboard) is faulty? system is a socket5 class computer. Something like memtest… tnks

Reply 1 of 5, by PC@LIVE

User metadata
Rank Oldbie
Rank
Oldbie

There is a program for checking the cache, maybe if I remember correctly it's called cachechk, they use it to check the fake caches of the 486 (pcchips), it certainly highlights a problem, but I don't think it can tell you which chip has problems.

AMD 286-16 287-10 4MB
AMD 386SX-33 4MB
AMD 386DX-40 Intel 387 8MB
Cyrix 486DLC-40 IIT387-40 8MB
486DX2-66 +many others
P60 48MB
iDX4-100 32MB
AMD 5X86-133 16MB VLB CL5429 2MB
AMD K62+ 550 SOYO 5EMA+ +many others
AST Pentium Pro 200 MHz L2 256KB

Reply 2 of 5, by dionb

User metadata
Rank l33t++
Rank
l33t++

Yep. It can show if cache is the issue. After that it's a matter of swapping chips until you find the source of the issue.

Reply 3 of 5, by kixs

User metadata
Rank l33t
Rank
l33t

With my experience when one chip is faulty, cache is disabled by the BIOS and you get the error message at boot.

But for troubleshooting...

First try to increase the timings of L2 and maybe also L1 cache. Most instabilities occur with too tight timings.

Then you can also disable L2 cache in BIOS. If everything works fine with L2 disabled, then the L2 cache is probably to blame.

Visit my AmiBay items for sale (updated: 2025-10-29). I also take requests 😉
https://www.amibay.com/members/kixs.977/#sales-threads

Reply 4 of 5, by AlessandroB

User metadata
Rank Oldbie
Rank
Oldbie
kixs wrote on 2024-01-07, 23:43:
With my experience when one chip is faulty, cache is disabled by the BIOS and you get the error message at boot. […]
Show full quote

With my experience when one chip is faulty, cache is disabled by the BIOS and you get the error message at boot.

But for troubleshooting...

First try to increase the timings of L2 and maybe also L1 cache. Most instabilities occur with too tight timings.

Then you can also disable L2 cache in BIOS. If everything works fine with L2 disabled, then the L2 cache is probably to blame.

there is no settings, just "enable" or "disable"