BIOS and CMOS Error Messages and How to Fix Them
โถ BIOS ROM Checksum error
This error appears when there is a problem with the ROM that stores system information.
It occurs when there is an issue while reading the information stored in CMOS. In this case, enter CMOS SETUP and check whether each setting is configured correctly for the current system state.
After completing the settings, select 'SAVE AND EXIT SETUP' to save the changes.
If the system is old, the ROM itself that stores the BIOS information may be damaged. In that case, it is recommended to have it inspected at a motherboard repair shop or service center.
โถ Press [F1] to continue
This message usually appears when the keyboard or mouse is not connected properly.
Please check whether both devices are connected securely to their connectors.
It is also a good idea to check whether the hard disk information is set correctly in CMOS SETUP.
โถ CMOS memory size mismatch
This error occurs when the system cannot properly recognize the memory (RAM).
When new RAM is added, CMOS usually detects it automatically, but in some cases the correct memory size is reflected only after running CMOS SETUP.
Enter CMOS SETUP, check the settings, and then reboot the system.
โถ NO ROM BASIC
This message appears when an error occurs during booting.
It usually occurs when the system cannot boot from drive A. In this case, you need to insert a bootable floppy disk into drive A or change the boot setting to boot from the hard disk drive.
Similar error messages include 'Diskette Boot Failure' and 'Invalid Boot Diskette'.
โถ CMOS display type mismatch
This error occurs when there is a problem with the graphics-related settings in CMOS.
It happens when the graphics type in the 'Video...' item in CMOS SETUP is not set to EGA/VGA.
Since this is the default setting used by most graphics cards, please make sure to check it.
โถ Cache Memory Bad..
This indicates a problem with the cache memory installed on the motherboard.
Cache memory is used to improve system speed, and on some motherboards, this error may appear if the cache memory fails.
In this case, you can replace the cache memory or try setting the cache memory usage option in CMOS SETUP to 'Disable'.
The same symptom may also appear when cache-related settings such as 'Cache Write' are configured incorrectly, so please check those settings as well.
Today's News/Tips
The "The endpoint device is already in use." Error Appears When Recording Starts
When recording with oCam, you may sometimes encounter problems with sound recording. In particular, when a DAW (Digital Audio Workstation, for example FL Studio) program using Asio4all is running, it may take exclusive control of the system audio, making sound playback or recording unavailable in other programs. As a result, normal sound recording in oCam may become difficult. Below is a detailed explanation of how to solve this problem and record smoothly with oCam.
Asio4all is a driver used for low-latency audio processing and is mainly used in DAW programs. However, when Asio4all is enabled, it takes exclusive control of the system audio, so other programs such as oCam may not be able to capture system sound. To solve this problem, you need to change the audio output device in the DAW program to something other than Asio4all.
The following is how to change the settings:
1. Run the DAW program (for example, FL Studio).
2. In the case of FL Studio, click 'Options' in the top menu, then go to 'Audio Settings'.
3. In the 'Audio Settings' window, check the audio output device and change it from Asio4all to 'Primary Sound Driver' or 'DirectSound'.
4. After saving the settings, play audio in the DAW and then try recording with oCam. The system sound should then be recorded normally.
If you must use Asio4all because of latency issues with a MIDI keyboard, it is best to switch the settings flexibly depending on your working environment. For example:
- When producing music or doing MIDI work in the DAW, use Asio4all to maintain a low-latency environment.
- After finishing your work and when you want to record with oCam, change the playback device in the DAW audio settings to 'DirectSound' or 'Primary Sound Driver' to disable Asio4all.
- After changing the setting, restart the DAW, or reboot the computer if necessary, then confirm that the setting has been applied properly before starting recording with oCam.
Using this method, you can resolve the audio exclusivity issue caused by Asio4all and record system sound smoothly in oCam. If you are working in a DAW and recording at the same time, try switching the audio output device according to the situation to maintain the best environment.