Re: Random Restarts - Please Help

Teresa,

I am reading the info on KB Article 244780 (Info. about Event ID 51), but
I don't understand all of the code translation. Is it possible for you to
translate it for me? What information do you need in order to do that?

It has already been translated.

An error was detected on device \Device\Harddisk0\D during a paging
operation.

Explanation
An input/output (I/O) request to a memory-mapped file failed and the
operation was retried.

User Action <---------
If these events are logged regularly on a primary system drive, replace the
device. Otherwise, no user action is required. <---------

When your computer pages information to or from the disk, if a generic error
occurs, it logs an Event ID 51 event message.

When an I/O operation to a hard disk is unsuccessful, Windows logs Event ID
51 in the system log. This problem occurs even if the I/O operation is
retried and is subsequently successful.

I only included that info on Event 51 because it was the only event that had
anything to do with hardware.

Event ID 6005 and 6006 happen every time you shut down and reboot if the
Event Log service (EventLog) is set to Automatic and running. They have
nothing to do with automatically rebooting. The events are for information
only to show that the Event Log service stopped and started.

Event Source: EventLog
Event ID: 6005
Message: The Event log service was started.
Explanation
This event is written at system startup after the user initiates an expected
restart or shutdown by clicking Start or pressing CTRL+ALT+DELETE, and then
clicking Shut Down.
User Action
No user action is required.

This event is Information only.

Event Source: EventLog
Event ID: 6006
Message: The Event log service was stopped.
Explanation
This event is written during an expected restart or shutdown after the user
initiates an expected restart or shutdown by clicking Start or pressing
CTRL+ALT+DELETE, and then clicking Shut Down.
User Action
No user action is required.

This event is Information only.

I just reread your first post.

9) It has also been suggested that I might need to upgrade my BIOS.

IMHO, if it ain't broke, don't fix it. I upgraded my BIOS a long time ago
on somebody's advice and it was a waste of time.

What should I do next? Check the RAM first?

Check the RAM and use your hard drive manufacturer's diagnostic tool,
available at their website. You never mentioned the manufacturer.

Memtest86+ is software designed to stress-test an x86-compatible computer's
random access memory for errors. http://www.memtest.org/ as mentioned by
Dave B. You run it from a floppy or CD and it runs without Windows loading.

See this...
Beginners Guides: Diagnosing Bad Memory
http://www.pcstats.com/articleview.cfm?articleID=1565

How to diagnose bad RAM
http://www.technibble.com/how-to-diagnose-bad-ram/

Microsoft has one also.
<quote>
The Windows Memory Diagnostic tests the Random Access Memory (RAM) on your
computer for errors. The diagnostic includes a comprehensive set of memory
tests. If you are experiencing problems while running Windows, you can use
the diagnostic to determine whether the problems are caused by failing
hardware, such as RAM or the memory system of your motherboard. Windows
Memory Diagnostic is designed to be easy and fast. On most configurations,
you can download the diagnostic, read the documentation, run the test and
complete the first test pass in less than 30 minutes.
<quote>
Microsoft Online Crash Analysis - windiag
Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp

With money being a problem I guess taking the machine to a reputable shop is
out of the question.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:3775E9BE-32F3-4F5F-BCBE-F946A7F8837F@xxxxxxxxxxxxx,
tbi3040 <tbi3040@xxxxxxxxxxxxxxxxxxxxxxxxx> hunted and pecked:
Wes,

I am reading the info on KB Article 244780 (Info. about Event ID 51), but
I don't understand all of the code traslation. Is it possible for you to
traslate it for me? What information do you need in order to do that?

I don't know what I would do without the help of you guys on this forum.

I will try to muddle through it until I hear from you of someone else who
can translate it for me.

Teresa
--
tbi3040


"Wesley Vogel" wrote:

ID: 51
Source: disk
Message: An error was detected on device %1 during a paging operation.

Explanation
An input/output (I/O) request to a memory-mapped file failed and the
operation was retried.

User Action
If these events are logged regularly on a primary system drive, replace
the device. Otherwise, no user action is required.

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=51&EvtSrc=disk&LCID=1033

Information about Event ID 51
http://support.microsoft.com/kb/244780

How to troubleshoot event ID 9, event ID 11, and event ID 15 error
messages http://support.microsoft.com/kb/154690

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:44B24684-00A2-4ACA-BBAE-325B84100553@xxxxxxxxxxxxx,
tbi3040 <tbi3040@xxxxxxxxxxxxxxxxxxxxxxxxx> hunted and pecked:
Nass,

I have been keeping very accurate records this morning and I will copy
and paste the two Event ID's that I get every time I have gotten a
re-start today. Please see below...

Unexpected restart at 8:59:52am – the 6005 and 6009 Event
ID’s and one (1) Code 6006 at 8:58:31
Unexpected restart at 9:03:19am – the 6005 and 6009 Event
ID’s Unexpected restart at 9:07:22am – the 6005 and 6009
Event ID’s and one (1) Code 6006 at 9:06:39
Unexpected restart at 9:37:48am – the 6005 and 6009 Event
ID’s and two (2) Code 51’s at 9:37:38 and 9:37:41
Unexpected restart at 9:55:58am – the 6005 and 6009 Event
ID’s Unexpected restart at 10:26:55am – the 6005 and 6009
Event ID’s Unexpected restart at 10:31:39am – the 6005
and 6009 Event ID’s Unexpected restart at 10:48:36am –
the 6005 and 6009 Event ID’s Unexpected restart at 10:55:28am
– the 6005 and 6009 Event ID’s Unexpected restart at
11:10:10am – the 6005 and 6009 Event ID’s Unexpected
restart at 11:27:53am – the 6005 and 6009 Event ID's
and two (2) Code 51’s at 11:27:42 and 11:27:45
Unexpected restart at 12:04:30pm – the 6005 and 6009 Event
ID’s Unexpected restart at 12:26:08pm – the 6005 and 6009
Event ID’s Unexpected restart at 12:45:19pm – the 6005
and 6009 Event ID’s Unexpected restart at 1:07:23pm – the
6005 and 6009 Event ID’s

Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6005
Date: 1/26/2007
Time: 1:07:23 PM
User: N/A
Computer: TSB-NJS-0612
Description:
The Event log service was started.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6006
Date: 1/26/2007
Time: 9:06:39 AM
User: N/A
Computer: TSB-NJS-0612
Description:
The Event log service was stopped.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: ff 00 00 00 ÿ...

Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6009
Date: 1/26/2007
Time: 1:07:23 PM
User: N/A
Computer: TSB-NJS-0612
Description:
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Uniprocessor Free.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 1/26/2007
Time: 11:27:42 AM
User: N/A
Computer: TSB-NJS-0612
Description:
An error was detected on device \Device\Harddisk0\D during a paging
operation.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 00 68 00 01 00 b6 00 ..h....
0008: 00 00 00 00 33 00 04 80 ....3..€
0010: 2d 01 00 00 00 00 00 00 -.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: d8 04 00 00 00 00 00 00 Ø.......
0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ....
0038: 40 00 00 04 00 00 00 00 @.......
0040: 00 20 0a 12 40 03 20 40 . ..@. @
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 16 00 c8 44 cd 82 ....ÈD�‚
0058: 00 00 00 00 98 42 cd 82 ....˜B�‚
0060: 00 00 00 00 27 8d 7c 06 ....'�|.
0068: 28 00 06 7c 8d 27 00 01 (..|�'..
0070: 00 00 00 00 00 00 00 00 ........
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

Nass, just in case I’m missing something, I will try to copy and
paste the whole days Event Log in another message.

Thanks so much for your help,

Teresa

--
tbi3040


"nass" wrote:


Yes, it could be the solution to uninstall and Reinstall SP2, but it
will be better to double click the Error message (X) and get the exact
Text and copy and paste in your next Post for us to have a look.
Or you can go a head and uninstall the SP2 and reinstall it back, also
be sure your system is clean by scanning your machine.
HTH.
Regards,
nass

"tbi3040" wrote:

Nass,

I woke up this morning and cracked open the case, un-plugged and
re-plugged everything back in where I could and I only found one
problem - the red wire on the plug from the back of the CD-Rom to the
mobo is dis-connected. No wonder I could not get the diagnostics done
yesterday on the HD and the RAM. All other wiring seems to be fine and
working my PC seems to be working much better today after doing that
(un-plug and re-plug) this morning.

I've also been into the event viewer after every re-start this morning
(8 so far) and every one of them have had a code 6005 and 6009, every
single time. That tells me that it isn't a hardware problem, it's a
problem with my SP2 install.

Do you agree? I am going do a format of my HD anyway, so I think I
should just go ahead and wipe it clean today. But the real question
is, should I re-install it (SP2)?

Teresa
--
tbi3040


"nass" wrote:



"tbi3040" wrote:

I am at my wits end and any suggestions from an expert would be
greatly appreciated. (I'm sorry if this is the incorrect section of
the forum to post this question.)

1) I am on a PC I bought back in 2001 and I don't have the money to
buy a new one - because of no job and therefore no money.
2) At first, back at the end of 2006, I was just experiencing random
re-starts.
3) I saved my files and formatted my HD. The problem still persists.
4) Bought what I thought would solve my problem - a system optimizer
touted to be the best one according to some reviews, in order to
diagnose my problem. That was a really DUMB move on my part because
it made things worse, I uninstalled it but I'm sure it's down in the
registry and after the fact,
I've read other horror stories about the s/w crashing other peoples
PC's and losing all their data. Thank God that didn't happen to me.
5) I then did some KB research and thought that it could be my
drivers, chipset, a bad piece of hardware or heat issues.
6) I updated the drivers and chipset last week, even thought I
didn't have any "splats" in the device manager. I lost my sound for
a few days, but I got it back when I uninstalled the "new" culprit
driver that was recommended from Driver Agent's w/s.
7) I cracked open the case this past weekend and cleaned it
thoroughly and checked the power supply with a tester - it's still
good. 8) I then thought that maybe it's just as simple as a heat
issue, because I had my tower in a desk cabinet. So, when I finished
the cleaning and power supply
testing, I put it on the floor, underneath the desk about 2-3" from
the side so it would get better air circulation. (BTW, I also know
the fan is working too and no unusual sounds at any re-starts.)
8) About the only thing I have left to check is to see if my RAM is
failing. 9) It has also been suggested that I might need to upgrade
my BIOS. That's way too scary for me to even think about without
consulting an expert on this forum.

Because of all of these changes and I'm sure, that damn optimizer
program I so foolishly bought, I am now experiencing a double count
of the RAM at first boot-up, and "Windows cannot start normally"
black screens twice at first boot-up as well sometimes, and I'm
STILL experiencing random re-starts during the day.

So far today in 2 hours time I had 12 re-starts and it took me
through the double count of the RAM at boot-up again and the
"Windows could not start normally" black screen 7 times before I
could finally boot-up today!!!

PC Stats - OS - MS Windows XP Pro Version - 5.1.2600 SP2
Processor - Intel (810) Celeron, 952Mhz
BIOS Version/Date - Award S/W Int'l., 6.00 PG, 08/28/2000
RAM -512MB

What should I do next? Check the RAM first? Upgrade the BIOS, and
btw, can I get it somewhere for free (from a reputable source
please)? Should I do a clean install first before the BIOS upgrade?
Or maybe I should just drop-kick it into the river and start over
with another tower? (even though I really don't have the moey to do
that)

Please Help!!!

--
tbi3040

Adding to Wes advice, Try to check the cables are fitted firmly
From/To the motherboard.
- Check the power connectors from the Power supply to the motherboard
and to the HDD ( It may be fried I found in some cases).
- Donwload the Diagnoxtic tools for your Hard Drive from the
manufacturer to test the Hard Drive for bad sectors.
- Test the memory by downloading the Memtest and unzip to floppy and
reboot with the floppy in and start the test, sometimes swapping the
Memory sticks in each other slots can help.
- Check the Event Viewer for Error messages (X) and double click it
to get more Info about which Application/Hardware causing it and you
can send them in your next message.
- Check the cable from the power supply to the mains (wall) it is
better if you replace it with another good known working one.
- Check your Video card.
Perform the BIOS Flash after checking all possibilities of
Hardwares/softwares problem.
What ever happen don't interrupt the BIOS Flash procedure read on how
to flash your BIOS then Write down all the steps and create the flash
floppy and restart your machine to flash your BIOS.
Here is a link to download the flash software for your motherboard,
but check first it is the right make and version, there is a
step-by-step guide to flash the BIOS:
http://www.esupport.com/global/
All about the BIOS from pcbuyer:
http://www.pcbuyerbeware.co.uk/BIOS.htm
Here is a link on Repair/Reinstall you may need it:
http://www.michaelstevenstech.com/XPrepairinstall.htm
HTH.
Regards,
nass
-------------
www.nasstec.co.uk

.

Relevant Pages

  • Re: 4GBs of RAM Miscount
    ... If you look in the BIOS at boot time, ... Why can't I see all of the 4GB of RAM in my machine? ... have you ever applied the switch to a SBS 2003 box? ... it increases the 'pointers' for memory handling to allow 32b systems ...
    (microsoft.public.windows.server.sbs)
  • Re: Extra RAM Installation Blues Vol 2
    ... >> & most of the Memory Manufacturers, ... >> Slot, along with various esoteric Info, such as the RAM Timings etc. ... > and even gives the manufacturer. ... along with the BIOS & Chipset etc. ...
    (uk.people.silversurfers)
  • BIOS sees 4GB of RAM, not sure about the OS
    ... I found some information on the net about getting the BIOS to ... I upgraded my computer to 4GB of RAM. ... I enabled "Memory Remapping Feature" in the BIOS, ... I want to say that the kernel I'm using has bigsmp support. ...
    (alt.os.linux.suse)
  • Re: Opteron box and 4Gb memory
    ... The memory was not paired, so the motherboard was not interleaving the access. ... My processors are higher than Rev E0, because the BIOS does not let me choose ... If I activate the 'hardware hole', ... The ram is DDR 400. ...
    (Linux-Kernel)
  • Re: Tracking down memory leaks
    ... 1GB in free memory... ... decrease to a small percentage of available physical RAM, as the system uses that memory to cache as much stuff from disk as possible. ... It's not normal for the system to panic; this often indicates a hardware problem. ... There are some brief suggestions in "man crash" and a chapter in the Handbook on how to diagnose and debug system panics. ...
    (freebsd-questions)