Ftdisk Error Event ID 49 - Config. page file for crash dump failed... 2

[RVStevenson]

Getting error in event viewer. Ftdisk error - event id 49 - Configuring file for page dump failed. Make sure there is a page file on the boot partition and that it is latge enough to contain all physical memory.

I have already made sure that virtual memory is at least 1.5 times RAM amount. I have also tried to select none under write debugging information, and neither solution fixed the problem in my instance.

Are there any suggestions?

Thanks,
Ryan V. Stevenson
Consumer Options
RVStevenson@ameritech.net

 

[welshguy]

A suggestion ..

If you have Nero installed this can cause this error - if you have try uninstalling it or delete nerocdnt.sys.

There is also a KB article on fixing this problem but you have already covered the steps in this.

Otherwise system account permissions (a guess!) ?

Cheers

 

[RVStevenson]

Thanks for the info but i'm still having trouble with it.. Nero is not installed. What exactly were you thinking reguarding the system account permissions.. Not my area of expertise so any suggestions are appreciated. Thanks,

Ryan V. Stevenson
Consumer Options - Managed Money - NSN
RVStevenson@ameritech.net

 

[pbxman]

You need to make sure your C: drive has permissions for the "system" account.

Right-click on c: drive, go to properties, security, permissions, and make sure "system", or "everyone" has full control.

I dont think this is the problem though. The 2 things you've tried should be sufficient. When you changed the pagefile, you pressed the "set" button right?

Did you recently add more memory? Make sure the pagefile is on a drive with permissions to read it as well.
The solution must be a simple one... Please let Tek-Tips members know their posts were helpful. Thanks!

Pbxman
Systems Administrator

 

[welshguy]

Ryan

It was just a stab in the dark that your NTFS permissions
for the drive were wrong and the system was not able to write to the page file. Just right click/properties security and check that the system is not restricted from
writing to the root directory or /winnt. If it's set to everyone or system has rights then barking up wrong tree.

It's normally due to adding more Ram or a new program being installed - I think another was Adaptecs Take two caused the error.

Have you installed anything recently that might have caused this caused this ?

Cheers

 

[RVStevenson]

Thanks for the ideas, i'll check it out and post again with a status.

Thanks,

Ryan V. Stevenson
Consumer Options - Managed Money - NSN
RVStevenson@ameritech.net