Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Computer Crashes - No Time To Do Anything

  • Please log in to reply
3 replies to this topic

#1 truly


  • Members
  • 2 posts
  • Local time:08:33 AM

Posted 18 October 2006 - 05:58 PM

New here and first post just hoping for a few ideas,
Kids computer windows XP home, updated from windows 98 about 2 years ago i think. Goodness know what they downloaded but we have AVG and firewall on the router so not sure if I am blaming them falsly.

I dont have much technical knowledge so simple please :thumbsup: :flowers:

Starts up as normal then beep and microsoft error report flashes up and it crashes. Dont get time to read report or writing on blue page before it restarts and does the same again.
Dont get time to do system restore or anything else.

Driving me nuts anyone got a clue please

BC AdBot (Login to Remove)


#2 Silivar


  • Members
  • 26 posts
  • Local time:03:33 AM

Posted 18 October 2006 - 06:42 PM

It may not be related to anything that was downloaded, though it's definitely a likely case. However, I'd check the RAM first.

Try Memtest first. You'll need to burn it onto a bootable CD or floppy, and it'll test your RAM. If it shows a problem, then it's likely bad RAM. If not, then we can start looking at software-related problems.

First, try booting into Safe Mode. If I recall correctly, you need to hold F8 at some point during startup. I haven't done it in some time, so I'm not sure. If you can get into Windows in Safe Mode, go to the Control Panel --> Performance and Maintenance --> System --> Advanced --> Startup and Recovery --> Settings, then uncheck the automatically restart box. Then it'll stay on the blue screen, rather than restarting so quickly. That'll help find where the problem is.

After trying that, let me know what happens. If you can get that far, it makes things much easier.

#3 Enthusiast


  • Members
  • 5,898 posts
  • Location:Florida, USA
  • Local time:02:33 AM

Posted 18 October 2006 - 06:53 PM

When does it beep, what exactly what does the beep sound like (IE 1 long 2 short or ?) and what bios is on the computer (it tells you on the screen when it starts booting)?

First thing to do is stop the automatic reboot so you can read the error screen and post exactly what it says here.

When a critical error occurrs in Windows XP, the system will reboot automatically by default. After the reboot, Windows will then usually show a dialogue with the explanation that the system has recovered from a critical error and will offer to submit this error to Microsoft.
Most of the time these spontaneous reboots are rather unique and are not an immediate cause for alert. However, if the situation is recurring, there is probably something wrong in the system configuration. To get a good idea of what is wrong, it is best to disable the option to automatically restart the system after a failure, but to let it show the error message instead.

To do so, please perform the following steps:
1. Right-click My Computer.
2. Select Properties.
3. In the System Properties, select the tab Advanced.
4 In the box called Startup and Recovery, click Settings.
5 A new window will open:

6. Uncheck the box "Automatically restart" in the group System Failure
7. Confirm the changes in both Windows by clicking OK.
Whenever a critical system failure occurs now, you will see a blue screen with a cryptic description of the error. However, the content of this message might help in finding the appropriate solution to the problem.

Note: Most of the critical errors are due to faulty driver installations or incorrect BIOS settings. Especially in case of misbehaving drivers, the blue screens often list the filename of the driver that caused the crash.

How long has this problem been occurring?
If it is less than three weeks you might be able to use System Restore to reset your system state back to a working condition.

To do so, try to boot to Safe Mode with Command Prompt
(start tapping F8 as soon as you boot the computer), boot to safe mode with command prompt.

Log on to your computer with an administrator account or with an account that has administrator credentials.

Type the following command at a command prompt, and then press ENTER:


Follow the instructions that appear on the screen to restore your computer to an earlier, working state.


Let us know.

#4 truly

  • Topic Starter

  • Members
  • 2 posts
  • Local time:08:33 AM

Posted 19 October 2006 - 02:32 PM

Thanks for the advice.

I finally got it to load in safe mode - it was f9 that was safe mode after loads of tapping f8 !! think kids done something else to f buttons lol.
Managed to do system restore as only started having probs tuesday, everything seems ok now.

cheers Truly

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users