[robert1234]

Hello

Dell Dimension windows xp, screen goes black and computer beeps, neeed to restart or it or reboots by itself.

[Advertisements]

Does any of the below examples resemble the beep codes you are getting?

How to Interpret Computer Error Beep Codes

When the computer makes those funny sound via the system speaker, it's not doing it because it wants to be heard.
The computer is trying to talk to the operator/technician and tell them what's wrong.

Beep Codes:

No Beeps: Short, No power, Bad CPU/MB, Loose Peripherals

One Beep: Everything is normal and Computer Posted fine

Two Beeps: POST/CMOS Error

One Long Beep, One Short Beep: Motherboard Problem

One Long Beep, Two Short Beeps: Video Problem

One Long Beep, Three Short Beeps: Video Problem

Three Long Beeps: Keyboard Error

Repeated Long Beeps: Memory Error

Continuous Hi-Lo Beeps: CPU Overheating


Thanks to alandemartino for this tutorial.

[rshaffer61]

Does any of the below examples resemble the beep codes you are getting?

How to Interpret Computer Error Beep Codes

When the computer makes those funny sound via the system speaker, it's not doing it because it wants to be heard.
The computer is trying to talk to the operator/technician and tell them what's wrong.

Beep Codes:

No Beeps: Short, No power, Bad CPU/MB, Loose Peripherals

One Beep: Everything is normal and Computer Posted fine

Two Beeps: POST/CMOS Error

One Long Beep, One Short Beep: Motherboard Problem

One Long Beep, Two Short Beeps: Video Problem

One Long Beep, Three Short Beeps: Video Problem

Three Long Beeps: Keyboard Error

Repeated Long Beeps: Memory Error

Continuous Hi-Lo Beeps: CPU Overheating


Thanks to alandemartino for this tutorial.

[robert1234]

Repeated Long Beeps: Memory Error

[rshaffer61]

OK that helps and now lets check the memory to be sure.
First remove the memory and reseat it to be sure it isn't loose or dust is stopping contact to be made fully.
After that then do the below.

A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[robert1234]

Will start process A...thx

[robert1234]

ok... last stick installed made cpu crash.. guess that was the one?

[rshaffer61]

Yep sounds like you may have found your issue. Just to be sure install just that module and run memtest86 on it alone. That will verify our suspicions and allow you to just replace the one module if you so desire to do that. If it were me I would replace everything with matched pairs and depending on your motherboard memory configuration you might be able to use different memory and less modules.

[robert1234]

crash again... didnt change anything...

[rshaffer61]

Did you run the memtest on the modules?
Is it blue screening or just crashing?
Try this:

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  
  • Error
  • Information
  • Warning

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 3 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
  
  
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) 04 11 2012
  In the To: boxes type today's date (presuming the crash happened today) 04 11 2012
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply


[*] Click the radio button for 'Date of events'
In the From: boxes type today's date (presuming the crash happened today) 9 01 2013
In the To: boxes type today's date (presuming the crash happened today) 9 01 2013
Then click the Run button.
Notepad will open with the output log.
[/list]Please post the Output log in your next reply

[robert1234]

was preparing to mem test when crash occured...
no blue screen, reboot...

reset clock and date on cpu to proper setting...




Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/03/2013 12:29:47 PM
Type: error Category: 0
Event: 34 Source: W32Time
The time service has detected that the system time needs to be changed by -5011202 seconds. The time service will not change the system time by more than -54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com (ntp.m|0x1|192.168.10.2:123->65.55.21.13:123) is working properly.

Log: 'System' Date/Time: 09/01/2013 10:57:51 AM
Type: error Category: 0
Event: 6161 Source: Print
The document Print owned by Robert failed to print on printer Canon MG2100 series Printer. Data type: NT EMF 1.008. Size of the spool file in bytes: 3355180. Number of bytes printed: 3281004. Total number of pages in the document: 3. Number of pages printed: 0. Client machine: \\ROB1-F19FFFFD18. Win32 error code returned by the print processor: 13 (0xd).

Log: 'System' Date/Time: 07/01/2013 10:22:02 PM
Type: error Category: 0
Event: 6161 Source: Print
The document HSWorkbook.pdf owned by Robert failed to print on printer Canon MG2100 series Printer. Data type: NT EMF 1.008. Size of the spool file in bytes: 21025860. Number of bytes printed: 6178536. Total number of pages in the document: 39. Number of pages printed: 0. Client machine: \\ROB1-F19FFFFD18. Win32 error code returned by the print processor: 13 (0xd).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/03/2013 6:07:22 PM
Type: information Category: 0
Event: 4201 Source: Tcpip
The system detected that network adapter \DEVICE\TCPIP_{3AC0FC81-4C5E-4CC1-BA46-743CFCC53008} was connected to the network, and has initiated normal operation over the network adapter.

Log: 'System' Date/Time: 08/03/2013 6:07:00 PM
Type: information Category: 0
Event: 7035 Source: Service Control Manager
The Adobe Flash Player Update Service service was successfully sent a start control.

Log: 'System' Date/Time: 08/03/2013 6:07:00 PM
Type: information Category: 0
Event: 7036 Source: Service Control Manager
The Adobe Flash Player Update Service service entered the stopped state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/03/2013 1:05:52 PM
Type: warning Category: 2
Event: 57 Source: Ftdisk
The system failed to flush data to the transaction log. Corruption may occur.

Log: 'System' Date/Time: 08/03/2013 1:05:52 PM
Type: warning Category: 2
Event: 57 Source: Ftdisk
The system failed to flush data to the transaction log. Corruption may occur.

Log: 'System' Date/Time: 08/03/2013 1:05:52 PM
Type: warning Category: 0
Event: 51 Source: Disk
An error was detected on device during a paging operation.

[rshaffer61]

reset clock and date on cpu to proper setting...

Is this a ongoing issue you have been having?

[robert1234]

week or so, didnt have time to sort it out..

[rshaffer61]

Does it happen when you disconnect power from the system and then 10 to 15 minutes reconnect and start? This could indicate a low cmos battery on the motherboard.
Also after testing the memory can you do the following.

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to Winlogon and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.

[robert1234]

mem test crashed cpu... black screen, still running

[rshaffer61]

Wow it crashed system from booting to the cdrom to doing the test?