I don't think EDO ram that's too big can destroy a chipset. If you have beep codes, then the chipset is probably still working. Maybe you could get a POST card first to check on which step your BIOS is stuck, maybe your problem isn't related, or maybe you damaged something else in the process (the RAM pins can be bent and it's hard to see it when it happens).

According to the award POST codes, the problem is RAM related : https://www.computerhope.com/beep.htm#award

Can you put a picture of the RAM area of your computer ? What kind of ram did you put now ? did you put matching pairs ?

Deksor wrote on 2021-09-05, 20:15:

I don't think EDO ram that's too big can destroy a chipset. If you have beep codes, then the chipset is probably still working. Maybe you could get a POST card first to check on which step your BIOS is stuck, maybe your problem isn't related, or maybe you damaged something else in the process (the RAM pins can be bent and it's hard to see it when it happens).

According to the award POST codes, the problem is RAM related : https://www.computerhope.com/beep.htm#award

Can you put a picture of the RAM area of your computer ? What kind of ram did you put now ? did you put matching pairs ?

I don't have pictures on me but I can send a link to what I bought. I've tried all of the EDO memory I have, 3 CPUs, and 2 different powersupplies. I believe the chipset is okay, but the northbridge, the chip in between the EDO slots and the cache, is the one I believe is dead. The post code does seem to be ram related and it does not matter what I put in, it will NOT go away. Also the issue I believe is the memory I put in may be a different standard that uses the EDO socket, however you'd have to correct me on that. I was under the assumption that if it didn't fit right it wouldn't work, and if it did, it would. The motherboard manual is very clear and explicit in saying to NOT used dual height EDO(Although I don't remember where it says it), which makes me think that could have messed it up. Manual link: http://www.tsukumo.co.jp/20thanniversary/comp … ASUS_manual.pdf

Link to what I bought:
https://www.ebay.com/itm/303649179445?hash=it … L0AAOSwRAlfMNlD

As far as a post card, I do not have one. Would this suffice? https://shorturl.at/mvxJO

Take a very close look at the memory slots, I got the "infinite beep loop" once on a motherboard despite the modules being known working ones and compatible. The problem was that the contacts in the SIMM slots were mangled and were likely shorting something there. Replacing the slot fixed the issue.

TheMobRules wrote on 2021-09-05, 20:46:

Take a very close look at the memory slots, I got the "infinite beep loop" once on a motherboard despite the modules being known working ones and compatible. The problem was that the contacts in the SIMM slots were mangled and were likely shorting something there. Replacing the slot fixed the issue.

I'm not at home for a week but I'll check for sure when I get back. If you accidentally inserted the modules backwards would it break anything? I may have also done that.

Deksor wrote on 2021-09-05, 20:15:

I don't think EDO ram that's too big can destroy a chipset. If you have beep codes, then the chipset is probably still working. Maybe you could get a POST card first to check on which step your BIOS is stuck, maybe your problem isn't related, or maybe you damaged something else in the process (the RAM pins can be bent and it's hard to see it when it happens).

According to the award POST codes, the problem is RAM related : https://www.computerhope.com/beep.htm#award

Can you put a picture of the RAM area of your computer ? What kind of ram did you put now ? did you put matching pairs ?

Also I have been using mismatched memory for awhile. For reference the post code is the same regardless of ram being in the computer or not.

Thorad wrote on 2021-09-05, 20:42:

I don't have pictures on me but I can send a link to what I bought. I've tried all of the EDO memory I have, 3 CPUs, and 2 diffe […]
Show full quote

Deksor wrote on 2021-09-05, 20:15:

I don't think EDO ram that's too big can destroy a chipset. If you have beep codes, then the chipset is probably still working. Maybe you could get a POST card first to check on which step your BIOS is stuck, maybe your problem isn't related, or maybe you damaged something else in the process (the RAM pins can be bent and it's hard to see it when it happens).

According to the award POST codes, the problem is RAM related : https://www.computerhope.com/beep.htm#award

Can you put a picture of the RAM area of your computer ? What kind of ram did you put now ? did you put matching pairs ?

I don't have pictures on me but I can send a link to what I bought. I've tried all of the EDO memory I have, 3 CPUs, and 2 different powersupplies. I believe the chipset is okay, but the northbridge, the chip in between the EDO slots and the cache, is the one I believe is dead. The post code does seem to be ram related and it does not matter what I put in, it will NOT go away. Also the issue I believe is the memory I put in may be a different standard that uses the EDO socket, however you'd have to correct me on that. I was under the assumption that if it didn't fit right it wouldn't work, and if it did, it would. The motherboard manual is very clear and explicit in saying to NOT used dual height EDO(Although I don't remember where it says it), which makes me think that could have messed it up. Manual link: http://www.tsukumo.co.jp/20thanniversary/comp … ASUS_manual.pdf

Link to what I bought:
https://www.ebay.com/itm/303649179445?hash=it … L0AAOSwRAlfMNlD

As far as a post card, I do not have one. Would this suffice? https://shorturl.at/mvxJO

That shorturl link is broken unfortunately.
I don't want a link of someone else's picture, I want to see exactly how you've installed memory in your computer and how the slots look like 😀
How many RAM sticks did you install ?

Deksor wrote on 2021-09-05, 22:35:

That shorturl link is broken unfortunately. I don't want a link of someone else's picture, I want to see exactly how you've inst […]
Show full quote

Thorad wrote on 2021-09-05, 20:42:

I don't have pictures on me but I can send a link to what I bought. I've tried all of the EDO memory I have, 3 CPUs, and 2 diffe […]
Show full quote

Deksor wrote on 2021-09-05, 20:15:

I don't think EDO ram that's too big can destroy a chipset. If you have beep codes, then the chipset is probably still working. Maybe you could get a POST card first to check on which step your BIOS is stuck, maybe your problem isn't related, or maybe you damaged something else in the process (the RAM pins can be bent and it's hard to see it when it happens).

According to the award POST codes, the problem is RAM related : https://www.computerhope.com/beep.htm#award

Can you put a picture of the RAM area of your computer ? What kind of ram did you put now ? did you put matching pairs ?

I don't have pictures on me but I can send a link to what I bought. I've tried all of the EDO memory I have, 3 CPUs, and 2 different powersupplies. I believe the chipset is okay, but the northbridge, the chip in between the EDO slots and the cache, is the one I believe is dead. The post code does seem to be ram related and it does not matter what I put in, it will NOT go away. Also the issue I believe is the memory I put in may be a different standard that uses the EDO socket, however you'd have to correct me on that. I was under the assumption that if it didn't fit right it wouldn't work, and if it did, it would. The motherboard manual is very clear and explicit in saying to NOT used dual height EDO(Although I don't remember where it says it), which makes me think that could have messed it up. Manual link: http://www.tsukumo.co.jp/20thanniversary/comp … ASUS_manual.pdf

Link to what I bought:
https://www.ebay.com/itm/303649179445?hash=it … L0AAOSwRAlfMNlD

As far as a post card, I do not have one. Would this suffice? https://shorturl.at/mvxJO

That shorturl link is broken unfortunately.
I don't want a link of someone else's picture, I want to see exactly how you've installed memory in your computer and how the slots look like 😀
How many RAM sticks did you install ?

I started out with 4 plus the 128 stick. I had, I believe, two 32mb sticks, one 16, and one 128 all in at once when I originally started having the problem. From there I moved to using one 128mb stick. Then I tried reverting to two 16s and two 32s. Then I tried a single stick in every channel. Then I tried no ram. All of the above led to the same ram error postcode. As far as pictures I have none because this originally happened in January. I was pretty sad and put it away and only pulled it out a few weeks ago. I don't have access to it now but in a week I can send pics of everything 😀

Not supported configuration.

Pentium boards requires 2 matched set of 72 pin. if 4MB, this needs two 4MB sticks, or two 8mb sticks, or two 16MB sticks so on. You do not have two 16MB or two 128MB. But you have two matched 32MB sticks. Use this only.

Cheers,

pentiumspeed wrote on 2021-09-06, 01:01:

Not supported configuration.

Pentium boards requires 2 matched set of 72 pin. if 4MB, this needs two 4MB sticks, or two 8mb sticks, or two 16MB sticks so on. You do not have two 16MB or two 128MB. But you have two matched 32MB sticks. Use this only.

Cheers,

I think that may be my problem.....

Yes, pentium need matching pairs to work, anything else (single stick, unlatching sticks) will fail and cause the memory error you're getting 😀 (unless you have a specific chipset that manages to support single stick configurations but they're not made by intel).

Somewhere around last January I replaced TX chip to Gigabyte GA-586T2.

The only place I found it available was Aliexpress, https://www.aliexpress.com/item/4001085831705.html
Chip was genuine and now the board is working fine.

I'm sure I saw HX chips there also. At least I can find FW82439HX. Maybe you should check it out if you still need some.

It is 99% mismatched RAM.

Deksor wrote on 2021-09-06, 08:25:

Yes, pentium need matching pairs to work, anything else (single stick, unlatching sticks) will fail and cause the memory error you're getting 😀 (unless you have a specific chipset that manages to support single stick configurations but they're not made by intel).

That indeed was the case! My system is now quite chipper again at its default memory configuration. Currently reinstalling windows 98. Need to go find another zip drive and the floppy cage for my system though as I kinda lost both. Booted right up with my K6 😀

Glad we could help 😀

Yay!

Cheers,