Consistent message of "The system has recovered from a serious error"

Hi Everyone:

       Every time at bootup and restart, I get the following message from my friend's computer:  The system has recovered from a serious error.  A log of this error has been created.  Send Error Report or Don't Send.  Interestingly, this message does not appear within Safe Mode, but, only in Normal Mode.  With that in mind, could it be possible there is a corrupted driver?  After all, there device driver issues with the onboard ethernet and onboard audio which are now resolved within device manager.  But, could there still be some kind of driver issue going on?  I did make some adjustments to the minimal and maximum size area to be reserved for virtual memory as suggested by an expert from a previous similiar post.  I have not changed out the RAM yet though.  

        Any ideas on this will be apprecated.  By the way, I am not sure if there is a connection, but, I had to perform a fresh reinstall of XP because this pc was corrupted with a worm as indicated from a previous closed post.

       George
GMartinAsked:
Who is Participating?
 
guidwayConnect With a Mentor Commented:
try downloading and installing this fix from MS:

http://www.microsoft.com/downloads/release.asp?releaseid=36920
0
 
bmhydro420Connect With a Mentor Commented:
 This is usually fixable by deleting your page file and recreating it.  Got to my computer icon right click on it and choose properties. Under the next menu choose advanced.  Under the next menu choose performance settings then choose advanced again, next choose virtual memory.  Check the box that says no paging file and then choose set.  Ignore the error restart then go back to virtual memory and choose system managed size.
0
 
guidwayConnect With a Mentor Commented:
hi George,

have you checked the Event Viewer to see if any more detailed information is given?

Start->Control Panel->Administrative Tools->Event Viewer

perhaps this will provide more information about what is crashing.

also try this

go to start->run and type

sfc /scannow

to check for corrupted system files

hope this helps
guid
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
GMartinAuthor Commented:
Hi There:

       I did the procedures and experienced the following from the pc:  When the page file was deleted, the error totally disappeared.  However, when I set it to system managed size and restarted, the error message came back.

       Any further thoughts will be appreciated.

       Thank you

       George
0
 
GMartinAuthor Commented:
Hi There:

      After reviewing the Event Viewer, I did find a few things with Error and Warning beside them within the Application and System Categories of Event Viewer.  With respect to the Security Category, I found a few references called Failure Audit.  Since this territory is very new to me, I am not really sure what to do with this information.  

       George
0
 
bmhydro420Commented:
delte the page file again and restart the computer with no page file then recreate again
0
 
sandy_aroraCommented:
Hi Martin

I am sending you some troubleshooting steps which I am sure will help you to solve your problem


Let me describe the symptoms of the problem and ofcourse causes and finally the resolution of the problem. Just follow the instruction given below:

SYMPTOMS
If Windows XP restarts because of a serious error, the Windows Error Reporting tool prompts you to report the problem to Microsoft for troubleshooting purposes. Windows may prompt you to report this information every time that you restart the computer, even if no error occurred during the previous session. After this problem begins to occur, you are prompted to send the information after every restart, even if you do not send the information.

CAUSE
This problem occurs because after a Minidump file is written, the paging file continues to have a flag set that indicates that a Minidump file must be written.

RESOLUTION
To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack
To resolve this problem, download the following file from the Microsoft Download Center:
Download Q317277_wxp_sp1_x86_enu.exe now
Release Date: March 8, 2002

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.


Date         Time   Version      Size       File name     Platform
------------------------------------------------------------------------
25-Feb-2002  15:33  5.1.2600.31  1,842,688  Ntkrnlmp.exe  i386
25-Feb-2002  15:33  5.1.2600.31  1,897,856  Ntkrnlpa.exe  i386
25-Feb-2002  15:33  5.1.2600.31  1,870,848  Ntkrpamp.exe  i386
25-Feb-2002  15:33  5.1.2600.31  1,875,584  Ntoskrnl.exe  i386
25-Feb-2002  15:33  5.1.2600.31  5,721,984  Ntkrnlmp.exe  Itanium 64-bit
25-Feb-2002  15:33  5.1.2600.31  5,665,024  Ntoskrnl.exe  Itanium 64-bit
                              


WORKAROUND
You can solve this problem by recreating the pagefile. To re-create the pagefile, follow these steps: 1. Click Start.
2. Right-click My Computer.
3. Click Properties.
4. On the Advanced tab, in the Performance section, click Settings.
5. In the Virtual Memory section, click Change.
6. For Paging file size for selected drive, click No Paging File, and then click Set.
7. Click Yes after the following warning appears:
If the paging file on volume X: has an initial size of less than xx megabytes, then the system may not be able to create a debugging information file if a STOP error occurs. Continue anyway?

(X is the drive letter and xx is the amount of RAM installed on your computer minus 1 megabyte.)  
8. Click System Managed Size.
9. Click OK four times, and then restart the computer when you are prompted.
For an alternative to this procedure, see the following Microsoft Knowledge Base article:
255205 How to delete the Pagefile.sys file in Recovery Console



Good luck and Have fun
0
 
sandy_aroraCommented:
Hi Martin
You just follow the instruction given below in the link, and just ignore the previous troubleshooting steps as all those steps are included in this link only



http://support.microsoft.com/default.aspx?scid=kb;en-us;317277
0
 
Cyber-DudeConnect With a Mentor Commented:
It could be more of a startup process to me. If it is after 'login' than it could be an application where you may view and edit via the following reg key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Run - where all the startup processes are viewable and editable. If the error appears BEFORE you alledge login the system (though Im nearly sure that the system logs in automaticlly, still there is a login precess taking place on the system) than it must be one of the startup services or devices...

Etherway, I would go into the Event Viewer and see if this error is documented in some sort. This will help us determine what the cause of all this...

Cyber
0
 
Cyber-DudeCommented:
Further digging to your post;

'Failure Audit' may pin point the inability of the OS to messure a resource it supposed to messure. Whether it has been activated manually or by the OS. Please refer to the Event Viewer System and Application log and see whether are there any red marks and what is their message...

Cyber
0
 
visualcoatConnect With a Mentor Commented:
I would go to

START -> RUN
TYPE "msconfig" CLICK 'OK'
CLICK the 'STARTUP' Tab
CLICK 'DISABLE ALL'
CLICK 'OK'
CLICK 'RESTART MY COMPUTER'

than see if you error happens after reboot.
0
 
GMartinAuthor Commented:
Hi Everyone:

        I want to take a moment and tip my hat to all the experts on this one!  Everyone really impressed me with the wide array of possible options and solutions to the problem.  Each idea was rich in content and relevance to this post.  

        With respect to the problem posted, it is now resolved.  Interestingly, it took a scary incident to happen before I finally caught onto what was happening.  Basically, yesterday I started the pc up late after work.  To my surprise, the only thing that was happening was an continuous error beep.  I knew at that point there was some type of hardware problem going on.  So, I took the cover off and found one RAM stick was a little loose and not totally seated into the memory bank slot.  So, I took it out and reseated it and started the pc back up.  Not only did the continuous error beep go away, but, the message that "windows has recovered from a serious error"' was also gone.
Evidently, this was the cause all along.  

         Once again, thanks to all the experts who participated in this post.

         George
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.