Windows 7: What causes a PC to have these problems:

When rebooting

1. Produces a tit tit tit sound.
2. No response from the monitor ( nothing displays ).
3. Suddenly shut down by itself.
4. After a successful boot show a CMOS configuration to choose from :
a. PROFILE
B. LAST KNOWN GOOD CONFIGURATION
C. BOOTED 3 TIMES
D. BOOTED 4 TIMES
E. BOOTED 5 TIMES
5. Displays Blue screen with techinical support saying to update.

Sound like the Power Supply is going bad. The tit tit sound can at times be the first indication. Then it could be the MOB gong bad also.

So is there any solutions? I thought it was my RAM . Why happen to my Power Supply then? Sorry im no techy person.

what is MOB gong?

To help you further we need to know you system specs. This in important for us here on the forums because it allows us to determine things that can go wrong. To enter your system spec go to the "CP" at the top of any page click on it then go to the system specs section and enter all the information. Then click on save; now your specs will show up in the left hand corner of your thread under "My System Specs," allowing others to help you. . .

does it helps?

Yes. Now one more question (or a series of one question): how old is the machine. Looking at all the specs it would appear to be several years old. Reading up on the MOB your system was designed to run Vista, and looking at your HDD specs it would appear to be several years old.

So without knowing the age I would put the problem on the HDD. The problems you have mentioned are usually the problems of the HDD going bad. Before doing anything else it is highly recommended you back up all your important files so you don't lose them.

Please if you can give the overall age of your system. And, again it would appear the HDD is going bad.

Once you back up your files attempt to do a defrag on the HDD and run a test to determine if the HDD has any errors. I will check our tutorial section for other answer to your problem.

Here is a tutorial that will help you test your HDD: Disk Check[2]=Performance%20Maintenance. Run this test and let us know how it comes out. This will be easier then me attempting to take you through the process. Good Luck.

I'm not sure what you mean by tit tit tit sound. Where is the sound coming from? Is it beeps produced by your motherboard speaker or click type sounds maybe coming from your hard drive? Does the PC POST (Power On Self Test), do you get a BIOS screen? If you do get a BIOS screen can you enter the BIOS setup menu. If you can get into the BIOS check to see if your hard drive shows up correctly.

Yes i can access to my BIOS and checked that hard drive shows up.

A normal pc produces a sound when open. but mine produces the same sound but continueos

Do you have reset button, have you tried that?

[QUOTE=enyawd;1145080
Yes i can access to my BIOS and checked that hard drive shows up.

A normal pc produces a sound when open. but mine produces the same sound but continueos[/QUOTE]

If you are referring to the single beep you here when you power up your PC, that is a BIOS code signaling everything is OK. If you are now hearing a continuous series of beeps, or a recurring pattern of beeps over and over, that is a BIOS signal of a hardware failure. One thing you can do is re-seat your various internal PC components. If you can help it don't do this standing on a carpet. You want to keep static electricity to a minim. Before you touch anything touch the metal case of you power supply to discharge any static on your body. Now remove each of your memory modules (RAM) and reinstall them making sure they are firmly in the slots. Do the same with any add-in cards like Video, sound, network, etc. While you have the case open double check all your power connectors, SATA cables, etc to make sure they are in good and tight. Also clean out any dust bunnies. The reason you do this is vibration and the effect of heating up and cooling down over and over can cause some components to slowly creep out of their socket. If they move far enough you get a poor connection and things don't work like they should. Try that and post back the results one way or the other and we can go from there.