Error Ftdisk Event Id 49
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 11 Oct 2016 14:18:45 GMT by s_ac15 (squid/3.5.20)
in here. The browser version you are using is not recommended for this site.Please consider upgrading to the latest version of your browser by clicking one of the following links. Safari Chrome IE Firefox Support Navigation Support Support Home Drivers and Software Product Specifications Warranty Warranty Center Track Warranty Status Submit a Warranty Request Support Community Contact Us Support by Product Boards and Kits Education Emerging Technologies Graphics Drivers Network and I/O Processors Server Products Services Software Solid State Drives Technologies Wireless Networking Other Intel Products Identify My Product Support Support Home Intel® Server Products RAID Products Windows Server http://answers.microsoft.com/en-us/windows/forum/windows_xp-performance/event-id-45-49-ftdisk-error/16a40e65-b4c5-430e-a3a3-465faad58998 2003* Cannot Generate Dump Files for Intel® Integrated RAID Modules and Intel® RAID Controllers Last Reviewed: 02-Mar-2016 Article ID: 000008316 Symptom(s): For Intel RAID Controllers or Modules using the Intel RAID Software stack 3, under Microsoft Windows Server 2003*: If driver version 5.x or later is installed, Windows Server 2003 cannot generate dump files. On system boot, these errors are logged in the Windows Event Log: Event ID: 45 Source: Ftdisk http://www.intel.com/content/www/us/en/support/server-products/raid-products/000008316.html The system could not successfully load the crash dump driver Event ID: 49 Source: Ftdisk Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition, and that it is large enough to contain all physical memory. Cause: With the release of the ir3 driver v5.x for Windows Server 2003, the driver changed from a SCSIport driver to a Storport driver. Solution: Install the Microsoft hotfix for Windows Server 2003 to generate dump files using the Storeport virtual miniport.
This article applies to: Intel® Integrated Server RAID Module AXXRMS2AF080 Intel® Integrated RAID Module RMS25PB040 Intel® Integrated RAID Module RMS25CB080 Intel® Integrated RAID Module RMT3CB080 Intel® Integrated RAID Module RMS25CB040 Intel® Integrated RAID Module RMS25PB080 Intel® Integrated RAID Module RMS3CC080 Intel® Integrated RAID Module RMS3HC080 Intel® Integrated RAID Module SROMBSASMR Intel® Integrated RAID Module RMS3JC080 Intel® Integrated RAID Module RMS3CC040 Intel® Integrated Server RAID Module AXXRMS2AF040 Intel® Integrated RAID Module RMT3PB080 Intel® RAID Controller SRCSASBB8I Intel® RAID Controller RS3UC080 Intel® RAID Controller RS2MB044 Intel® RAID Controller RS2WC040 Intel® RAID Controller RS3DC080 Intel® RAID Controller RS2VB040 Intel® RAID Controller RT3WB080 Intel® RAID Controller SRCSAS144E Intel® RAID Controller SRCSAS18E Intel® RAID Controller RS3DC040 Intel® RAID Controller RS3WC080 Intel® RAID Controller RS2PI008 Intel® RAID Coboot up 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. Event ID:49 IDSource http://www.pcreview.co.uk/threads/event-id-45-49-ftdisk-logged-in-event-view-after-boot-up.3946648/ 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://www.techtalkz.com/windows-help/65066-event-id-45-49-ftdisk-logged-event-view-after-boot-up.html http://go.microsoft.com/fwlink/events.asp. i changed the virusal memory to system managed & no dice, i tried to rename atapy.sys in windows\system32\driver & no dice using 500GB HD 2 gig ram XP Pro Sp3 this is annoying i tryed to clear pagefile also event id @ shutdown & no dice what else can cause this? thanks Doc J, Jan 3, 2010 #1 Advertisements Doc J Guest I need to add that hibernation is causing this error i disable it then renable it but pc wont hibernate & cause this error? when i disable hibernation the error still came up then i enabled it created the error again there a way to fix hibernation? thanks "Doc J" <> wrote in message news:%... >I get ftdisk event id these 2 errors after boot up > > 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. > > 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. > > > > i changed the virusal memory to system managed & no dice, i tried to > rename atapy.sys in windows\system32\driver & no dice > > using 500GB HD 2 gig ram XP Pro Sp3 > > this is annoying i tryed to clear pagefile also @ shutdown & no dice > > > > what else can cause this? > > > > thanks > > > > Doc J, Jan 3, 2010 #2 Advertisements Swifty Guest Doc J wrote: > I need to add that hibernation is causing this error i disable it then > renable it but pc wont hibernate& cause this error? Both hibernation (and presumably rge Crash Dump process) require a pre-allocated file that is contiguous (i.e. in one piece on disk). You may be able to fix this problem by defragmenting your disk. I would use the free JKDef
Id: 45 & 49 FTDisk logged in event view after boot up Windows XP LinkBack Thread Tools Display Modes 01-03-2010, 09:30 AM #1 Doc J Guest Posts: n/a Event Id: 45 & 49 FTDisk logged in event view after boot up I get these 2 errors after boot up 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. 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. i changed the virusal memory to system managed & no dice, i tried to rename atapy.sys in windows\system32\driver & no dice using 500GB HD 2 gig ram XP Pro Sp3 this is annoying i tryed to clear pagefile also @ shutdown & no dice what else can cause this? thanks Sponsored Links 01-03-2010, 10:30 AM #2 Doc J Guest Posts: n/a Re: Event Id: 45 & 49 FTDisk logged in event view after boot up I need to add that hibernation is causing this error i disable it then renable it but pc wont hibernate & cause this error? when i disable hibernation the error still came up then i enabled it created the error again there a way to fix hibernation? thanks "Doc J"