Have you tried running a RAM tester? There are a few in the archive: http://www.club100.org/library/libutl.html
I have used both RAMCHK.BA <https://ftp.whtech.com/club100/utl/ramchk.ba> and RAMTST.BA <https://ftp.whtech.com/club100/utl/ramtst.ba> to find bad RAM modules. Although if the bad RAM happens to be the one where they load it will not work. They do a very simple test which does not take into account chip select failures or 'standard RAM¹ failure, but they might help isolate the problem to a bad RAM module or eliminate the RAM as an issue. On 4/3/20, 11:32 PM, "M100 on behalf of Willard Goosey" <[email protected] on behalf of [email protected]> wrote: >In article ><camcmnv4gvqd_2xfyjmyvxnbb2dyw5ffyovgan5raehni+41...@mail.gmail.com>, > Stephen Adolph <[email protected]> wrote: >> Willard, I assume this all happens only when REX is installed? > >Huh, no! With or without REX. > >I'm suspecting a bad RAM or power supply issues. > >Neither amuse me. :-( > >> Assuming that there is no defect with REX, then * what release of >> firmware is running? IE the REXMGR software load version. There is no >> way to know directly but you can report the Checksum value and that >> should correlate. > >it says : >Software 4.0 cs=6e83 >model: rex >firmware: 6(1) > >> * is your socket healthy? are the pins making good >> contact? > >Seems to be. REX works fine! > >-- >Willard Goosey [email protected] >Socorro, New Mexico, USA >I search my heart and find Cimmeria, land of Darkness and the Night. > --Robert E. Howard
