This might happen with corrupted CMOS data. Resetting the CMOS with the jumper should clear this, but that doesn't seem to work in your case. Are you sure the procedure was executed properly?

Does your board have a Dallas RTC with built in battery, or a separate coin cell battery?

If a separate battery, try and remove it and start the PC. Check the battery and perhaps replace it. Check orientation!

You computer worked, something happened and you needed to reset CMOS data, now it acts like this. What forced you to reset the CMOS data? That might give us a hint.

There are many sites that lists the master passwords for various BIOS makers, try these for example:
http://www.schure-shb.de/was-man-wei/hardware … asswoerter.HTML

As for the parity error: since you use non-parity RAM, make sure you have parity disabled in the BIOS. That's apparently not the case.

Thank you very much derSammler ! It worked! The password was alfarome!
Cyrix200+ huge thanks to you too, for your helpful advices.
I really appreciate your help guys.
I will now try to disable parity.
I will contact you again, as soon as possible.

It appears, there is no option, that allows me to disable parity in the BIOS settings.
What am I supposed to do now? Do you need screenshots?
I have yet another question. Is there a way, I can enter the BIOS, without typing the password, each time i'm trying to access it?

Wilius wrote on 2020-01-31, 15:57:

It appears, there is no option, that allows me to disable parity in the BIOS settings.
What am I supposed to do now? Do you need screenshots?

Well, maybe you do have a RAM parity error, as in, one of the RAM sticks you have is fauly. That would explain why the computer stopped POSTing and why the BIOS is behaving strange after CMOS reset. Try with different RAM sticks?

Deunan Thank you! You're might be right. I'm going to test different RAM modules and i'm also going to retest my current modules once again, I will also test every RAM slot one my board, maybe one slot is faulty.
I just find it odd, that all RAM modules are beign detected properly.

It loos like, that Bank 3, might be faulty. (I can't confirm it. I have 4 modules, with each having a capacity of 4mb and 16mb is being detected by this board)
However, bank 0, bank 1 and bank 2 are working fine.
I tested different modules, unfortunately the same error appears.
What I can confirm, is, that all of my RAM modules are working fine, since they all worked without any issues on my a PCChips M571.
Is there a way to disable NMI permanentely?

For the password issue, there should be a setting in BIOS to set/enable/disable the password. If there isn't a setting to disable it, you should be able to change it. If you enter a blank password it should disable it.

Do any of the contacts on the bank 3 slot look dirty or bent? You might want to try spraying some de-oxit or similar electrical contact cleaner on the RAM slots. At the very least, disconnect the power. Better yet would be to remove the motherboard from the case before cleaning it.

Deunan wrote on 2020-01-31, 16:04:

Well, maybe you do have a RAM parity error, as in, one of the RAM sticks you have is fauly. That would explain why the computer stopped POSTing and why the BIOS is behaving strange after CMOS reset. Try with different RAM sticks?

You can not have a parity error with RAM that has no parity! If RAM is bad, the POST would show that instead - and that is different from a parity error which can only occur with 9-bit RAM modules. The BIOS is wrongly assuming that there is parity RAM installed (you can already see this by the segment offset 0000), even though there isn't. So either the CMOS settings are wrong and parity is enabled, or the system can not work with non-parity RAM. But I doubt the latter on a VOBIS Highscreen.

Post a picture of the BIOS screen please that has the settings for RAM and such.

cyclone3d Thank you, the password issue is now completely gone.
I'm going to take the pictures of the Bios screen, this might take me a moment.
The pins of bank 3 looks fine too me.
I'm going to clean the pins, but I don't think I will do this today.
Once again, thank you for your awesome support!

derSammler wrote on 2020-01-31, 16:58:

You can not have a parity error with RAM that has no parity!

Sure you can - socket/RAM stick corrosion, or broken mobo traces (or battery spill corrosion) can very easily confuse the BIOS detection code.
Since this is a 486 system I would also re-seat the CPU (and in general make sure it's not dirty or something). The 486 has a parity detector built-in, the CPU itself will ignore it but the output signal might be used by the mobo. Could be a jumper and not a software setting. And then there are potential issues with having EDO sticks that are not of the same brand, EDO support on 486 boards was not exactly great or stable most of the time.

In other words, I'm not saying it is a partity error, rather, it seems to be RAM-related and faulty RAM can manifest in any number of ways. The BIOS self-test is not very good at finding uncommon failures like a weak cell for example.

For the pictures, what File licence should I choose?

Deunan wrote on 2020-01-31, 17:18:

Sure you can - socket/RAM stick corrosion, or broken mobo traces (or battery spill corrosion) can very easily confuse the BIOS detection code.

You don't seem to know what parity is. Parity checking is a 9th bit on the RAM module for each byte that is set to either odd or even and is checked when reading from RAM. It requires RAM with the additional 9th parity bit, of course. Parity checking must be enabled in the BIOS, otherwise you can not get a parity error. No damage whatsoever on the RAM or the RAM slots can force the BIOS to do parity checking if it isn't enabled. What I said stays true: the system either requires parity RAM or the CMOS is misconfigured. And it's most likely the latter.

The RAM is certainly not bad. The error shows segment offset 0000, so the first 64 kb would be faulty already. Since it's expecting parity, this error message makes sense, as it's already failing testing the very first byte. If the RAM there would be really faulty, the system would not POST at all, as the first 64 kb are *required* to be good for the BIOS to execute. This is checked before even the display is initialized. With an error here, you get two beeps only and no display.

derSammler wrote on 2020-01-31, 18:14:

You don't seem to know what parity is. Parity checking is a 9th bit on the RAM module for each byte that is set to either odd or even and is checked when reading from RAM. It requires RAM with the additional 9th parity bit, of course.

Actually, it's bits 32-35 (counting from zero). But I'm not here to argue. All I wanted to say is, if the PC stops booting and then complains about RAM after a CMOS clear, then checking the RAM is not a bad idea. Usually the parity check is disabled by default, now this BIOS might be different or maybe it's using some auto-detect code. In which case a faulty RAM can be misdetected. Also, it's personal experience but the 486 mobos I worked with were very picky about EDO RAM (and that's the ones that supported it in the first place).

I hope you can see the pictures. I wasn't sure which file licence I should pick.

Here is the second picture.

Wilius wrote on 2020-01-31, 18:59:

I hope you can see the pictures. I wasn't sure which file licence I should pick.

Fifth entry from the bottom, says "Memory parity check" - set it to Disable.

The first thing that caught my eye (and had already been mentioned in the thread) is that you have EDO RAM installed. Swop out the memory with FPM RAM and see what happens.

Also check the manual for different memory configurations. Some motherboards (for example) only accepts dual banked RAM in certain slots.

Show us the memory modules used in this motherboard. The parity feature uses either 3 chips or 9 chips per module and EDO is not supported on 486 since 486 only use FPM type.

Pentium uses FPM or EDO memory.

Cheers,