Results 1 to 4 of 4

Thread: Event Id: 45 & 49 FTDisk logged in event view after boot up

  1. #1
    Join Date
    Sep 2004
    Posts
    29

    Event Id: 45 & 49 FTDisk logged in event view after boot up

    Started getting the following two different errors or event IDs (whatever they call it) on my Windows XP SP3 since yesterday:

    Event ID: Source FTdisk
    The system could not sucessfully load the crash dump driver.

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

    Event ID:49 IDSource FTdisk
    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.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    As troubleshooting I tried to change the Visual Memory, cleared pagefile and tried renaming atapu.sys under windows\system32\driver but none of them worked me yet.

    I will also like to add that I suspect hibernation is causing these annoying event IDs. What I did is disable and enable the same, since my system is unable to hibernate and these errors started. But now no matter I enable or disable hibernation, the error still coming up.

    Any help would be appreciated.

  2. #2
    Join Date
    Jun 2006
    Posts
    206

    Re: Event Id: 45 & 49 FTDisk logged in event view after boot up

    I think defragmentation would have fixed this issue because hibernation as well as Crash Dump process needs a pre-allocated file that used to save somewhere on your disk. Defragmenting your disk can help your system to fix them. But as you said you already did that and that didnt helpe, I’ll suggest you to download and use JKDefrag for doing the same. It should work.

  3. #3
    Join Date
    Jun 2011
    Posts
    66

    Re: Event Id: 45 & 49 FTDisk logged in event view after boot up

    I don’t know how did you clear the page file and it didnt work. Anyway, instead of clearing the same you must simply create a new pagefile and all things will be sorted. Also remember that before you create a new pagefile you must always note down the current settings of the same cause it may hamper your system a lot. If you are not so techie than better use the option “System managed size”. Now lets start the process:

    • Start by clicking to Start > Control Panel > System > Advanced Tab.
    • Now click on Performance Tab > Settings> Advanced Tab.
    • Here under Virtual Memory, check the settings and note them all. Once done click on Change.
    • Set the value to ‘0’ and click OK.
    • Without leaving this place open Windows Explorer, click on View > Folder Options> checkmark the box for “Show Hidden Files”.
    • Now go back where we were and delete C:\pagefile.sys.
    • Now reboot the system.


    Once it is booted check if there is c:\pagefile.sys or deleted. It should not be there. Now again go back to:
    • Start > Control Panel > System > Advanced Tab.
    • Now click on Performance Tab > Settings> Advanced Tab.
    • Under Virtual Memory, click on Change.
    • Set the value to ‘System managed size’ and click OK.
    • Again restart Windows.


    Now ensure that the pagefile settings are proper and exists with current date and time. Now once you disabled the Hibernation, you also need to delete the C:\ hiberfil.sys and reboot the system to take effects. Once you are back, enable hibernation again.

  4. #4
    Join Date
    Feb 2012
    Posts
    1

    Re: Event Id: 45 & 49 FTDisk logged in event view after boot up

    To anyone else still tearing out their hair trying to solve this one (as was I), here is the solution. The problem is most likely rootkit malware attack.

    To check and remove rootkits, download and run Kaspersky's TDSSKiller:

    http://support.kaspersky.com/downloa...tdsskiller.zip

    I ran this. It found one infection, quaranteened the file, rebooted my computer, and hibernation now works.

    After countless attempts to fix hibernation, this was the only solution that worked for me.
    Last edited by seangriffin; 07-02-2012 at 05:52 PM.

Similar Threads

  1. MSI P67A-GD53 (B3) is crashing getting Kernel Power-Event ID 41 in Event viewer
    By Chellappan in forum Motherboard Processor & RAM
    Replies: 7
    Last Post: 10-12-2011, 11:35 AM
  2. Replies: 3
    Last Post: 25-02-2009, 03:42 PM
  3. Replies: 3
    Last Post: 19-03-2008, 05:42 AM
  4. Event ID: 5721 Event Source: NETLOGON member server windows 2003
    By Edwin Delgado in forum Windows Server Help
    Replies: 1
    Last Post: 08-09-2007, 12:41 AM
  5. Event Log Error: Event Source:WinMgmt Event ID:10
    By BlackSunReyes in forum Small Business Server
    Replies: 2
    Last Post: 01-03-2007, 03:27 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,672,742.78481 seconds with 17 queries