Discussion Locked

page file crash dump error in Win2K

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My desktop is having problems during shutdown. Win2K shuts down properly, however does not power-off the box, and leaves a mouse pointer on the screen. I must turn off the box manually, holding the power button for a few seconds. It starts up fine, without any problems.

Here is the Event Log System message:
------------------
Source: Ftdisk
Event ID: 49
Description: 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.
------------------

A search at the MS Knowledgebase instructs you to set the Write Debugging Information setting in the System Control panel object, to none (which I have done) but I am still getting the same result and error message in the Event Log.

If anyone has a fix for this, I'd greatly appreciate your help. This is more of an annoyance, but still.

Thanks,

Tom

12 replies

by kirill lozovatsky

Event ID 49 After You Start Your Computer
MSDN ID: Q260025

SYMPTOMS
The following Event ID may be displayed in the system event log when you start your computer:

Source: Ftdisk
Event ID: 49
Description: 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

CAUSE
This behavior can occur if the Adaptec Take Two version 1.01 software is installed.

RESOLUTION
To resolve this behavior, uninstall the Take Two software and contact Adaptec for a updated version.

For more info refer to:
http://support.microsoft.com/support/kb/articles/Q260/0/25.ASP

-----------
liverepair.com

by tforce

I've already reviewed the four Knowledge Base articles on Event ID 49. Take Two is not installed.

by strakovsky

I suspect you might have one of following situations:

1. On the same disk partition, where you have your WINNT directory, you don't have a pagefile, or the size of existing pagefile < (your physical memory size + 10Mb).

2. Startup and Recoverymissconfiguration

3. Hardware layout problem (driver missing, invalid or not supported - e.g. some old ATX cases/motherboards doesn't comply with power-off feature).

4. A problem clearing pagefile if that option turned on (a disk subsystem failure)

What I would recomend you to do:

1. Check your pagefile settings:
ControlPanel -> System -> "Advanced" -> Performance Options -> Change.
Increase Initial and/or Maximum size on windows partition in case of condition 1) described above.Make sure that you have size "Currently Allocated" >= "Recommended".

2. Check Startup and Recovery settings, turn dumping off in case if you have nothing to do with debug-file.
ControlPanel -> System -> "Advanced" -> Performance Options -> Startup and Recovery.
Check "Write an event to the system log"
Check "Send an administrative alert"
Check "Automatically reboot"
Select in Write Debug Information drop-down "(none)"

3. Check the system for possible hardware problem or resource conflict.
ControlPanel -> System -> "Advanced" -> Performance Options -> Hardware -> Device Manager.

4. Run chkdsk on the next boot

5. Install latest servicepack from M$

by shanghai sam

All good suggestions; all which I have done. I turned off the crash dump setting, and I actually have a large paging file then required. I have installed W2K SP2. I no longer get the system event log message, but the computer still does not power down. I also installed the correct version of Adaptec, with to luck.

This has got to be a registry issue, I'm convinced. Is there a Registry cleaner for W2K, or does someone know the keys for APM or Page File settings?

(As a side note...myfellow IT Techs are stumped by this, as am I.) I am raising the point value of this question substantially to hopefully get a well researched answer.)

by strakovsky

Well. I hope I can help you. Tell me little bit more about your PC. Is it a brandname - sort of Dell, PB or HP? When did you have a problem very first time? Try to go back and remember what did you do right before it happens. Most probably you have a glitchy/inproper/unconfigured HAL. Have you checked vendor's website regarding shutdown issue? Have you tried to perform "repair" system using original W2K CD?

by strakovsky

FYI, if you check your setup log, you're able to see every change performed to your system during the update process. I don't think your trouble caused by only missing registry settings. Looks like you've got an incorrect driver for your VIA chipset. As soon as you provide me your model/chipset info, I'll get you the right one.

by expertpc

1. Is the adaptec card running your system drive? If not temporarily remove the card and go through boot up and shutdown cycle.

2. Does your system go through scandisk like it failed the shutdown process everytime? If so, try a start and shut down in safe mode. The registry can get real confused sometimes if it can never shutdown correctly.

3. Boot into safe mode and create a hardware profile. Boot into it in safe mode. disable half of your devices. boot normally. If it fails, disable theother half. try again. If it starts working then renable half of the remaining devices at a time until you narrow down the culprit. Then address it like its bad drivers (easy) then bad hardware (harder). As for the drivers keep in mind that some software installs, data glitchs, and pig farts, can on occasion, corrupt a driver.

Good Hunting!

This discussion is closed to new replies.