Random Restarts in win 2000

A few months back my system went haywire on me and both my operating systems went down.  I have a multi boot with xp and 2000.  I got both systems back up and running, but ever since that incident my win 2000 platform keeps randomly restarting and i haven't been able to figure out why.  I have tried pulling the ram and that didn't seem to help; Looked to see if there were any IRQ confilicts; and have visited the event log.  There were two devices sharing the same IRQ - my vid card and ethernet card.  So i moved my ethernet card but still no luck.  Below is what i get from the event log:  Error source ftdisk event 49.  Then under the detail description it reads:

Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory. help

and below reads:
0000: 00000000 00560001 00000000 c0040031
0010: 00000003 00000000 00000000 00000000
0020: 00000000 00000000
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don't know if this will help any but since the error mentions the page file



Run regedt32 and go to the following location:

Hkey_local_machine\System\CurrentControlSet\Control\Session Manager\Memory Management

There you will find these entries:

PagingFiles:Reg_Multi_SZ:C:\pagefile.sys 190 380


If the PagingFiles: entry is populated, delete the entire TempPageFile entry then reboot.

Removing Everyone On Root Dir. Leaves Limited Virtual Memory

How to Delete the Pagefile.sys File in Recovery Console

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Also see if you can force a Blue screen error to appear

Right-click My Computer, click Properties, click the Advanced tab, and then click on the Startup and Recovery button and uncheck Automatically Reboot.
Test the RAM

NOTE if this doesn't find anything wrong with the RAM this DOESN'T mean the RAM is good you would need to swap out the RAM with known good modules for testing. However if it does find something wrong then chances are the RAM is bad.

DocMemory PC RAM
Diagnostic Software
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Event 49

Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
Microsoft: "A Memory.dmp file is created when a kernel mode STOP error occurs on a computer that has the "crash dump" feature enabled. If the page file is unable to accommodate a Memory.dmp file, debugging the problem is not possible. The page file is configured for crash dump when your computer starts, and the behavior described earlier in this article is logged when the physical memory on the computer is greater than the size of the Pagefile.sys file.".

read these ms articles:



QuamismAuthor Commented:
I looked for the page file and found it with plenty enough room to handle the phsical ram i have installed.  I did not however find the TimpPageFile that was mentioned in the first post.

I have turned the auto reboot off to try to get the blue screen, so i will just have to wait for that to happen and i will record the error.

I will check the ram and make sure that is not my problem

and the last post mentioned the fix for win 2000 pagefile problem but it didn't look like it was listed.  I sent an e-mail to MS to see if they could direct me to the fix.

Thank you for all your comments and suggestions.
QuamismAuthor Commented:
As suggested i contacted MS and got the hotfix for the pageFile Problem.  When the comp crashed last though it still gave same error.  I did turn off the auto reboot so below is the blue screen error it gave me.

***STOP 0x00000050 (0xE2D45000, 0x00000001, 0x80537890, 0x00000001)  Page_fault_in_nonpaged_area

Address 80537890 base at 804D0000
datestamp 3d4781aa-ntoskrnl.exe

Well, thats it...  Hope all that mean something to someone because i am just about at my wits end trying to figure this thing out.
did you check the ram yet? i saw that you were going to, but i didn't see the results.
This is what MS has to say about that error.


This Stop message, also known as Stop 0x50, occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be read to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.

Interpreting the Message

The four parameters listed in the message are defined in order of appearance as follows:

Virtual address which caused the fault
Type of access (0 = read operation, 1 = write operation)
If not zero, the instruction address which referenced the address in parameter 1
Opaque information about the stop, interpreted by the kernel
Resolving the Problem

Faulty hardware. Stop 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Buggy system service. Often, the installation of a buggy system service is a culprit. Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Antivirus software. Antivirus software can also trigger this error. Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Corrupted NTFS volume. A corrupted NTFS volume can also generate this error. Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

If your system partition is formatted with the file allocation table (FAT) file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve this error.

Microsoft periodically releases a package of product improvements and problem resolutions for Windows 2000 called a Service Pack. Because many problems are resolved by installing the latest Service Pack, it is recommended that all users install them as they become available. To check which Service Pack, if any, is installed on your system, click Start, click Run, type winver, and then press ENTER. The About Windows 2000 dialog box displays the Windows version number and the version number of the Service Pack, if one has been installed.

Occasionally, remedies to specific problems are developed after the release of a Service Pack. These remedies are called hotfixes. Microsoft does not recommend that you install a post-Service Pack hotfix unless the specific problem it addresses has been encountered. Service Packs include all of the hotfixes released since the release of the previous Service Pack. The status of hotfix installations is not indicated in the About Windows 2000 dialog box.
This question is still open and getting old. If any of the comment(s) above helped you please accept it as an answer or split the points who ever helped you in this question. Your attention in finalising this question is very much appreciated. Thanks in advance,


- If you would like to close this question and have your points refunded, please post a question in community support area on http://www.experts-exchange.com/Community_Support/ giving the address of this question. Thank you      


Cleanup Volunteer

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

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.