Exam 220-1001 topic 1 question 5 discussion

There are a couple of correct answers here. You need more information honestly. Different BIOS actually use different POST code beep combinations, so you'll need to know the BIOS (Or manufacturer) as a RAM error code is sometimes used. On OSX, RAM issues can be signified by POST issues as well. Continuous Reboots can be from a variety of issues (Including a power supply slowly failing). If it occurs after using the computer for a bit, it is not a RAM installation error (Although BSOD can sometimes have a memory error/leak cause a reboot). RAM being installed poorly usually means a computer will just fail to boot (Thus simulating continuously rebooting). Pay attention to little tells though. Do the fans spin up? Do lights turn on? It may look like RAM or the PSU only to be something really unexpected like the CPU overheating from poor thermal paste application and a failed fan only seconds into turning it on.

C. if there is a faulty RAM it fails to boot the OS, therefore continuous reboots.

According to CompTIA Cert master Learn Continous BEEP is most likely a problem with memory modules or memory controller listed in the POST code beep IBM PC table. The only anserw that might be correct is POST code beeps.

the correct answer is c

Answer is C as the as A need to be a beep not beeps

C is wrong. Continuous reboots are most likely caused by the motherboard or CPU failing. It’s possible it’s the RAM, but less likely. The power supply is the least likely cause of the problem in this scenario. - by CompTIA A+ Complete Study Guide Exam 220-1001 and Exam 220-1002 Fourth Edition, Quentin Docter & Jon Buhagiar

Like KingPo said.

Answer is C

A Beep code is a RAM issue. They got this question wrong which I am impressed they manages to do lol. Look it up anywhere, Its A

Se ascolto i beep ho già la soluzione del problema

I think A is definitely right. Some computer manufacturers, such as Dell, have beep code when there is a problem with the machine's memory.

I would say A just because it's what CompTIA teaches, but I have had continuous reboots when I had ram set to it's base 3200 Mhz clock when the mobo supported clocks of up to 2666. So continuous reboots could definitely be an answer, I've lived it. Tricky question here, continuous reboots is valid if there is RAM in the system, and post code beeps is valid if there's no RAM in the system.

You can get “out of memory” errors, POST code beeps, motherboard diagnostic lights or codes, system lockups, system slowdowns, and application locking due to memory problems with any operating system. With any of these problems, no matter which operating system is being used, check the amount of available memory and free hard drive space. Sometimes you must close all applications, reboot the computer, and open only the application that was running when the out of memory error occurred because some applications do not release the memory space they hold. from COMPLETE A+ GUIDE TO IT HARDWARE AND SOFTWARE A CompTIA A+ Core 1 & 2 Textbook 8th Edition by CHERYL A. SCHMIDT page 561 topic "Troubleshooting Memory Problems"

If you have a RAM issue, it will halt during POST with beeping or display two digits(either alphabet or number) at the bottom-right. If you have an issue with PSU or CPU, it will occur a reboot symptom.

onther question poor written... dor me its A because a beep code can tell you what's exactly the problem type.

A- Post Code Beeps

Tricky question but i think the answer should be A:Post code beeps. Although bad memory COULD cause continuous reboots so could a lot of other things. If reboots are the issue the machine could be overheating, there may be a motherboard problem, an OS drive may be failing etc. But the question asks "which of the following symptoms would INDICATE if this is a RAM issue" and the only thing that would indicate that specifically on the list would be the post code beeps. Hard to tell what they mean as a lot of their questions don't really give you enough to go on but going on what the question gives us that's the only option that would allow us to diagnose it as a RAM problem.