Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.os.msdos.misc,comp.sys.ibm.pc.hardware.misc (More info?)
My system has been running great. Until this afternoon!
I was troubleshooting a system card, reseating and so forth. Rebooted
and the boot-up looked fine, counting through all RAM (512k) and loading
device drivers to begin Windows... but just when I should have seen
Win98 desktop I get:
RAM PARITY ERROR - checking for segment - offending segment 0000.
Hit F1 to ignore NMI, F2 to reboot.
Neither key worked. Keyboard frozen. Curser blinks on black screen.
I looked up this error in Google archives but virtually every post I
read was from someone who had just installed memory and was having
trouble with BIOS settings with mixed/matched mem sets; OR had just
enabled Parity/ECC check in their BIOS. Neither applies to me.
1. I do not have Parity/ECC check enabled in BIOS.
2. My BIOS settings have been the same for months.
3. This has all worked flawlessly for months...
HELP! THANK YOU!
My system has been running great. Until this afternoon!
I was troubleshooting a system card, reseating and so forth. Rebooted
and the boot-up looked fine, counting through all RAM (512k) and loading
device drivers to begin Windows... but just when I should have seen
Win98 desktop I get:
RAM PARITY ERROR - checking for segment - offending segment 0000.
Hit F1 to ignore NMI, F2 to reboot.
Neither key worked. Keyboard frozen. Curser blinks on black screen.
I looked up this error in Google archives but virtually every post I
read was from someone who had just installed memory and was having
trouble with BIOS settings with mixed/matched mem sets; OR had just
enabled Parity/ECC check in their BIOS. Neither applies to me.
1. I do not have Parity/ECC check enabled in BIOS.
2. My BIOS settings have been the same for months.
3. This has all worked flawlessly for months...
HELP! THANK YOU!