During my battle with some malware this morning, I found out I can no longer
boot into safe mode? In looking at the event log during this time I see 2
ftdisk errors - first one was - "The system could not sucessfully load the
crash dump driver.", second one was "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." It had been quite some
time since I've tried to boot into Safe Mode, so I'm not sure when it may
have started.

Any ideas?

Windows XP Pro with SP3 and all updates
IE 8 with updates.
Dell Dimension, 512 MB RAM, 80 gig harddrive but only using 9.72.

--
Allen Hardy III

"Old age and treachery always wins
over youth and skill" -
Willie Nelson and Waylon Jennings

On Nov 10, 11:38*am, "skeet3" <adss...@adssuck.net> wrote:
> During my battle with some malware this morning, I found out I can no longer
> boot into safe mode? In looking at the event log during this time I see 2
> ftdisk errors - first one was - "The system could not sucessfully load the
> crash dump driver.", second one was "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." *It had been quite some
> time since I've tried to boot into Safe Mode, so I'm not sure when it may
> have started.
>
> Any ideas?
>
> Windows XP Pro with SP3 and all updates
> IE 8 with updates.
> Dell Dimension, 512 MB RAM, 80 gig harddrive but only using 9.72.
>
> --
> Allen Hardy III
>
> "Old age and treachery always wins
> over youth and skill" -
> Willie Nelson and Waylon Jennings

Who won the battle?

Reduce the chances of malicious software by running some scans.

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

These can be uninstalled later if desired.

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste
the information back here.

There will be some personal information (like System Name and User
Name), and whatever appears to
be private information to you, just delete from the pasted
information.

This will minimize back and forth Q&A and eliminate guesswork and
assumptions.

skeet3 wrote on Tue, 10 Nov 2009 11:38:07 -0500:
> During my battle with some malware this morning, I found out I can no longer
> boot into safe mode? In looking at the event log during this time I see 2
> ftdisk errors - first one was - "The system could not sucessfully load the
> crash dump driver.", second one was "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." It had been quite some
> time since I've tried to boot into Safe Mode, so I'm not sure when it may
> have started.
>
> Any ideas?
>
> Windows XP Pro with SP3 and all updates
> IE 8 with updates.
> Dell Dimension, 512 MB RAM, 80 gig harddrive but only using 9.72.

So Allen, when are you going to be a big believer in making makeups to
get rid of these messes? There are some great free ones out there too.

Acronis True Image Seagate Edition (DiscWizard)
http://www.seagate.com/www/en-us/sup...ads/discwizard

Acronis True Image WD Edition
http://support.wdc.com/product/downl...ad&wdc_lang=en

Paragon DriveBackup Express 9 (free)
http://www.paragon-software.com/home/db-express/

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)

On the battle with the malware - I won. Info from system as follows:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
System Name XXXXX
System Manufacturer Dell Inc.
System Model Dell DM051
System Type X86-based PC
Processor x86 Family 15 Model 4 Stepping 4 GenuineIntel ~2793 Mhz
BIOS Version/Date Dell Inc. A05, 3/31/2006
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
User Name xxxxxxxxxxx
Time Zone Eastern Standard Time
Total Physical Memory 512.00 MB
Available Physical Memory 214.15 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.95 GB
Page File Space 1.22 GB
Page File C:\pagefile.sys

"Jose" <jose_ease******.com> wrote in message
news:33d4a095-13b2-471e-9bb7-051cf396551c@b2g2000yqi.googlegroups.com...
On Nov 10, 11:38 am, "skeet3" <adss...@adssuck.net> wrote:
> During my battle with some malware this morning, I found out I can no
> longer
> boot into safe mode? In looking at the event log during this time I see 2
> ftdisk errors - first one was - "The system could not sucessfully load the
> crash dump driver.", second one was "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." It had been quite some
> time since I've tried to boot into Safe Mode, so I'm not sure when it may
> have started.
>
> Any ideas?
>
> Windows XP Pro with SP3 and all updates
> IE 8 with updates.
> Dell Dimension, 512 MB RAM, 80 gig harddrive but only using 9.72.
>
> --
> Allen Hardy III
>
> "Old age and treachery always wins
> over youth and skill" -
> Willie Nelson and Waylon Jennings

Who won the battle?

Reduce the chances of malicious software by running some scans.

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

These can be uninstalled later if desired.

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste
the information back here.

There will be some personal information (like System Name and User
Name), and whatever appears to
be private information to you, just delete from the pasted
information.

This will minimize back and forth Q&A and eliminate guesswork and
assumptions.

"skeet3" <adssuck@adssuck.net> wrote in
news:u#6hFSiYKHA.2188@TK2MSFTNGP04.phx.gbl:

> During my battle with some malware this morning, I found out I can no
> longer boot into safe mode? In looking at the event log during this
> time I see 2 ftdisk errors - first one was - "The system could not
> sucessfully load the crash dump driver.", second one was "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." It had been quite some time since I've tried to boot into
> Safe Mode, so I'm not sure when it may have started.
>
> Any ideas?
>
> Windows XP Pro with SP3 and all updates
> IE 8 with updates.
> Dell Dimension, 512 MB RAM, 80 gig harddrive but only using 9.72.

I posed a similar question just a few days ago. Someone directed me to
SafeModeFixer from moonvalleysoft.com. It cost me $11.90. It didn't work at
first but after 3 or 4 emails back and forth with their support people we
got it working. They told me to run ComboFix (a free root kit cleaner)
first and then run the Safe Mode Fixer utility. I did and it worked. I have
done that twice again on other people's computers. I have an idea that
ComboFix alone might have done the trick, but at least I got $11.90 worth
of technical support from moonriversoft.com.

--
--- Long live Fat32! ---

BillW50 <BillW50@aol.kom> wrote in
news:#7Ms$miYKHA.2172@TK2MSFTNGP06.phx.gbl:

> skeet3 wrote on Tue, 10 Nov 2009 11:38:07 -0500:
>> During my battle with some malware this morning, I found out I can no
>> longer boot into safe mode? In looking at the event log during this
>> time I see 2 ftdisk errors - first one was - "The system could not
>> sucessfully load the crash dump driver.", second one was "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." It had been quite some time since I've tried to
>> boot into Safe Mode, so I'm not sure when it may have started.
>>
>> Any ideas?
>>
>> Windows XP Pro with SP3 and all updates
>> IE 8 with updates.
>> Dell Dimension, 512 MB RAM, 80 gig harddrive but only using 9.72.
>
> So Allen, when are you going to be a big believer in making makeups...

:-)

--
--- Long live Fat32! ---

On Nov 10, 1:23*pm, "skeet3" <adss...@adssuck.net> wrote:
> On the battle with the malware - I won. *Info from system as follows:
>
> OS Name Microsoft Windows XP Professional
> Version 5.1.2600 Service Pack 3 Build 2600
> OS Manufacturer Microsoft Corporation
> System Name XXXXX
> System Manufacturer Dell Inc.
> System Model Dell DM051
> System Type X86-based PC
> Processor x86 Family 15 Model 4 Stepping 4 GenuineIntel ~2793 Mhz
> BIOS Version/Date Dell Inc. A05, 3/31/2006
> SMBIOS Version 2.3
> Windows Directory C:\WINDOWS
> System Directory C:\WINDOWS\system32
> Boot Device \Device\HarddiskVolume2
> Locale United States
> Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
> User Name xxxxxxxxxxx
> Time Zone Eastern Standard Time
> Total Physical Memory 512.00 MB
> Available Physical Memory 214.15 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.95 GB
> Page File Space 1.22 GB
> Page File C:\pagefile.sys
>

That information all looks reasonable from here.

See how those particular two malware scans run.

In your debugging efforts, did you adjust any of the Startup and
Recovery settings for System failure and/or Write debugging
information?

In your debugging efforts, did you use msconfig to adjust anything on
the BOOT.INI tab?

Do you have Recovery Console installed as a boot option, a bootable XP
installation CD or a bootable XP Recovery Console CD from which to run
chkdsk /r?

See inserts after your questions!

"Jose" <jose_ease******.com> wrote in message
news:0ec6c4b4-31ac-4e82-b1c7-0544efb69ca0@a31g2000yqn.googlegroups.com...
On Nov 10, 1:23 pm, "skeet3" <adss...@adssuck.net> wrote:
> On the battle with the malware - I won. Info from system as follows:
>
> OS Name Microsoft Windows XP Professional
> Version 5.1.2600 Service Pack 3 Build 2600
> OS Manufacturer Microsoft Corporation
> System Name XXXXX
> System Manufacturer Dell Inc.
> System Model Dell DM051
> System Type X86-based PC
> Processor x86 Family 15 Model 4 Stepping 4 GenuineIntel ~2793 Mhz
> BIOS Version/Date Dell Inc. A05, 3/31/2006
> SMBIOS Version 2.3
> Windows Directory C:\WINDOWS
> System Directory C:\WINDOWS\system32
> Boot Device \Device\HarddiskVolume2
> Locale United States
> Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
> User Name xxxxxxxxxxx
> Time Zone Eastern Standard Time
> Total Physical Memory 512.00 MB
> Available Physical Memory 214.15 MB
> Total Virtual Memory 2.00 GB
> Available Virtual Memory 1.95 GB
> Page File Space 1.22 GB
> Page File C:\pagefile.sys
>

That information all looks reasonable from here.

See how those particular two malware scans run.
((I actually used Spybot and Malwarebyte scans to remove the problem
malware - it seems very doubtful that the malware I had would be causing the
safe mode problems))

In your debugging efforts, did you adjust any of the Startup and
Recovery settings for System failure and/or Write debugging
information?

((I really haven't done a lot of debugging. I've uninstalled IE8 including
updates and ran hardware diagnostics using Dell CD that came with computer -
no problems detected - but there is still no change in the inability to
boot into safe mode.))

In your debugging efforts, did you use msconfig to adjust anything on
the BOOT.INI tab?

((The only thing I used msconfig for was to initiallly disable the malware
executable in the startup group. I actually disabled this executable before
I ran any malware scans because I recognized it as being a problem. No
changes were made to boot.ini))

Do you have Recovery Console installed as a boot option, a bootable XP
installation CD or a bootable XP Recovery Console CD from which to run
chkdsk /r?

((I have no recovery console in boot options and only XP CD is the OEM
reinstallation disk, which I really don't want to use. I'm not sure exactly
how long I've had the problem of being unable to boot into safe mode - I've
used it very little. My system originally came with XP Pro, SP2 - and the
only major changes I've made other than all the MS updates occurred several
months ago - the system came with an onboard CD writer. I started having
problems with the system finding the CD writer drive on restarts. the
writer was also giving me intermittent problems with creating CD's. I
finally got fed up with it's antics disabled it in device manager, unplugged
it from the motherboard and disabled it in the BIOS. However, I did not
remove it from the cabinet. Could this have something to do with the safe
mode problem? It sure hasn't effected the normal windows startup or
operation. For the record, when I try to boot into safe mode, I get a blue
screen of death with a stop error identified as 0x0000007E, 0xc0000005,
0x80537009, etc.))

On Nov 11, 10:07*am, "skeet3" <adss...@adssuck.net> wrote:
> See inserts after your questions!

>
> ((I have no recovery console in boot options and only XP CD is the OEM
> reinstallation disk, which I really don't want to use. *I'm not sure exactly
> how long I've had the problem of being unable to boot into safe mode - I've
> used it very little. *My system originally came with XP Pro, SP2 - and the
> only major changes I've made other than all the MS updates occurred several
> months ago - the system came with an onboard CD writer. *I started having
> problems with the system finding the CD writer drive on restarts. *the
> writer was also giving me intermittent problems with creating CD's. *I
> finally got fed up with it's antics disabled it in device manager, unplugged
> it from the motherboard and disabled it in the BIOS. *However, I did not
> remove it from the cabinet. *Could this have something to do with the safe
> mode problem? *It sure hasn't effected the normal windows startup or
> operation. For the record, when I try to boot into safe mode, I get a blue
> screen of death with a stop error identified as 0x0000007E, 0xc0000005,
> 0x80537009, etc.))

You should run MBAM and SAS as suggested. That way we won't wonder
about it.

I generally do not suggest things just for the heck of it or suggest
things to try, or things that might work maybe or things that could
be. There is a method to my madness.

Please supply the "etc." part regarding your BSOD. All BSODs are not
the same.

Disable Automatic restart on system error to stop the error on your
screen so you can see it:

Right click My Computer, Properties, Advanced, Startup and Recovery
Settings.

In the System failure section, untick the Automatically restart box,
OK, OK.

Here are some BSOD blue screen of death examples showing information
you need to provide:

http://www.codinghorror.com/blog/ima...ws_XP_BSOD.png
http://techrepublic.com.com/i/tr/dow...ges/bsod_a.jpg

Send the information pointed to with the red arrows (3-4 lines
total). Skip the boring text unless it looks important to you. We
know what a BSOD looks like, we need to know the other information
that is specific to your BSOD.

If you can only boot in Safe Mode, choose the option:

Disable automatic restart on system failure


Create your own bootable XP Recovery Console CD and run chkdsk /r as
indicated below:

You can make a bootable Recovery Console CD by downloading an ISO file
and burning it to a CD.

The bootable ISO image file you need to download is called:

xp_rec_con.iso

Download the ISO file from here:

http://www.mediafire.com/?ueyyzfymmig

Use this free and easy program to create your bootable CD:

http://www.imgburn.com/

It would be a good idea to test your bootable CD on the computer that
is working.

You may need to adjust the computer BIOS settings to use the CD ROM
drive as the first boot device instead of the hard disk. These
adjustments are made before Windows tries to load. If you miss it,
you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD...

The Windows Setup... will proceed.

Press 'R' to enter the Recovery Console.

Select the installation you want to access (usually 1: C:\WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:\WINDOWS folder. This is the same as the C:
\WINDOWS folder you see in explorer.

RC allows basic file commands - copy, rename, replace, delete, cd,
chkdsk, fixboot, fixmbr, etc.

From the command prompt window run the chkdsk command on the drive
where Windows is installed to try to repair any problems on the
afflicted drive.

Running chkdsk is fine to run even if it doesn't find any problems.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find. It may take
a long
time to complete or appear to be 'stuck'. Be patient. If the HDD
light is
still flashing, it is doing something. Keep an eye on the percentage
amount to
be sure it is still making progress.

Remove the CD and type 'exit' to leave the RC and restart the
computer.

You do not have to adjust the BIOS again to boot on the HDD since the
CD will
not be present.

Took me a while to get back to you! Made a fatal mistake when using SAS.
Tried their bootsafe app and managed to get myself into a continuous loop of
blue screens. Bottom line is I used my original OEM disk and reinstalled XP
Pro, couldn't use the recovery module on it because it would not operate in
safe mode. In any event, had to go thru reinstalling all the updates as well
as the SP3 Service Pack. Didn't really lose much other than some e-mails and
address book, and a few XP tweaks which I had to redo. Bottom line is
everything is back working now, including the ability to boot into safe
mode. Live and learn!

"Jose" <jose_ease******.com> wrote in message
news:fb5b3b94-eb28-4178-a08e-7ff0054e0b45@b2g2000yqi.googlegroups.com...
On Nov 11, 10:07 am, "skeet3" <adss...@adssuck.net> wrote:
> See inserts after your questions!

>
> ((I have no recovery console in boot options and only XP CD is the OEM
> reinstallation disk, which I really don't want to use. I'm not sure
> exactly
> how long I've had the problem of being unable to boot into safe mode -
> I've
> used it very little. My system originally came with XP Pro, SP2 - and the
> only major changes I've made other than all the MS updates occurred
> several
> months ago - the system came with an onboard CD writer. I started having
> problems with the system finding the CD writer drive on restarts. the
> writer was also giving me intermittent problems with creating CD's. I
> finally got fed up with it's antics disabled it in device manager,
> unplugged
> it from the motherboard and disabled it in the BIOS. However, I did not
> remove it from the cabinet. Could this have something to do with the safe
> mode problem? It sure hasn't effected the normal windows startup or
> operation. For the record, when I try to boot into safe mode, I get a blue
> screen of death with a stop error identified as 0x0000007E, 0xc0000005,
> 0x80537009, etc.))

You should run MBAM and SAS as suggested. That way we won't wonder
about it.

I generally do not suggest things just for the heck of it or suggest
things to try, or things that might work maybe or things that could
be. There is a method to my madness.

Please supply the "etc." part regarding your BSOD. All BSODs are not
the same.

Disable Automatic restart on system error to stop the error on your
screen so you can see it:

Right click My Computer, Properties, Advanced, Startup and Recovery
Settings.

In the System failure section, untick the Automatically restart box,
OK, OK.

Here are some BSOD blue screen of death examples showing information
you need to provide:

http://www.codinghorror.com/blog/ima...ws_XP_BSOD.png
http://techrepublic.com.com/i/tr/dow...ges/bsod_a.jpg

Send the information pointed to with the red arrows (3-4 lines
total). Skip the boring text unless it looks important to you. We
know what a BSOD looks like, we need to know the other information
that is specific to your BSOD.

If you can only boot in Safe Mode, choose the option:

Disable automatic restart on system failure


Create your own bootable XP Recovery Console CD and run chkdsk /r as
indicated below:

You can make a bootable Recovery Console CD by downloading an ISO file
and burning it to a CD.

The bootable ISO image file you need to download is called:

xp_rec_con.iso

Download the ISO file from here:

http://www.mediafire.com/?ueyyzfymmig

Use this free and easy program to create your bootable CD:

http://www.imgburn.com/

It would be a good idea to test your bootable CD on the computer that
is working.

You may need to adjust the computer BIOS settings to use the CD ROM
drive as the first boot device instead of the hard disk. These
adjustments are made before Windows tries to load. If you miss it,
you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD...

The Windows Setup... will proceed.

Press 'R' to enter the Recovery Console.

Select the installation you want to access (usually 1: C:\WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:\WINDOWS folder. This is the same as the C:
\WINDOWS folder you see in explorer.

RC allows basic file commands - copy, rename, replace, delete, cd,
chkdsk, fixboot, fixmbr, etc.

From the command prompt window run the chkdsk command on the drive
where Windows is installed to try to repair any problems on the
afflicted drive.

Running chkdsk is fine to run even if it doesn't find any problems.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find. It may take
a long
time to complete or appear to be 'stuck'. Be patient. If the HDD
light is
still flashing, it is doing something. Keep an eye on the percentage
amount to
be sure it is still making progress.

Remove the CD and type 'exit' to leave the RC and restart the
computer.

You do not have to adjust the BIOS again to boot on the HDD since the
CD will
not be present.

On Nov 12, 2:47*pm, "skeeterh3" <skee...@bellsouth.net> wrote:
> Took me a while to get back to you! *Made a fatal mistake when using SAS.
> Tried their bootsafe app and managed to get myself into a continuous loopof
> blue screens. *Bottom line is I used my original OEM disk and reinstalled XP
> Pro, couldn't use the recovery module on it because it would not operate in
> safe mode. In any event, had to go thru reinstalling all the updates as well
> as the SP3 Service Pack. Didn't really lose much other than some e-mails and
> address book, and a few XP tweaks which I had to redo. *Bottom line is
> everything is back working now, including the ability to boot into safe
> mode. Live and learn!
>

Truly tragic.

It is not a fatal mistake, it is just misdiagnosed resulting in
radical and unnecessary treatments.

If you use the SAS BootSafe option, is essentially does the same thing
as adjusting the Boot Options in msconfig and if your computer has a
certain malicious software, adjusting the boot.ini using any method
would render your system unable to boot in any mode until you fix it
properly. It is a bad idea IF you have a certain malware which seems
to be quite popular lately.

Recovery Console is the method - either booting from the XP
installation CD (which a lot of folks don't have) or from a Recovery
Console you can make (easy instructions already provided).

Or you can reinstall/repair, but I would never suggest that to anyone.
Well, I did once, but it was recommended for security purposes but not
absolutely necessary once the original problem(s) were fixed.

Maybe you will go ahead and make a Recovery Console CD after this
experience for the future and/or, install RC as a boot option if you
have the means ;). Coulda' saved you, me thinks.

In
news:8179de04-1238-4c3f-a460-80fc4fa4a714@a21g2000yqc.googlegroups.com,
Jose typed on Thu, 12 Nov 2009 13:26:33 -0800 (PST):
> On Nov 12, 2:47 pm, "skeeterh3" <skee...@bellsouth.net> wrote:
>> Took me a while to get back to you! Made a fatal mistake when using
>> SAS. Tried their bootsafe app and managed to get myself into a
>> continuous loop of blue screens. Bottom line is I used my original
>> OEM disk and reinstalled XP Pro, couldn't use the recovery module on
>> it because it would not operate in safe mode. In any event, had to
>> go thru reinstalling all the updates as well as the SP3 Service
>> Pack. Didn't really lose much other than some e-mails and address
>> book, and a few XP tweaks which I had to redo. Bottom line is
>> everything is back working now, including the ability to boot into
>> safe mode. Live and learn!
>>
>
> Truly tragic.
>
> It is not a fatal mistake, it is just misdiagnosed resulting in
> radical and unnecessary treatments.
>
> If you use the SAS BootSafe option, is essentially does the same thing
> as adjusting the Boot Options in msconfig and if your computer has a
> certain malicious software, adjusting the boot.ini using any method
> would render your system unable to boot in any mode until you fix it
> properly. It is a bad idea IF you have a certain malware which seems
> to be quite popular lately.
>
> Recovery Console is the method - either booting from the XP
> installation CD (which a lot of folks don't have) or from a Recovery
> Console you can make (easy instructions already provided).
>
> Or you can reinstall/repair, but I would never suggest that to anyone.
> Well, I did once, but it was recommended for security purposes but not
> absolutely necessary once the original problem(s) were fixed.
>
> Maybe you will go ahead and make a Recovery Console CD after this
> experience for the future and/or, install RC as a boot option if you
> have the means ;). Coulda' saved you, me thinks.

Better yet, buy a backup drive and make routine backups. ;-)

--
Bill
Asus EEE PC 702G8 ~ 2GB RAM ~ 16GB-SDHC
Windows XP SP2

I wanted to post the resolution I found to this problem to save someone
else some brain damage searching the web for a solution. I believe I
successfully solved this, so far so good. I also run xp, sp3, dell
ispirion 6400 and use firefox. I was getting bsod when booting to safe
mode but booting in normal mode to xp worked fine. When I'd click on a
link in my google search it would redirect me to other search engines or
website, mostly advertising. I noticed the favicon of these redirects
usually was a green globe looking thing or a little curly que. I also
had the same errors in event viewer (ftdisk error 45 and 49).

First I went start/run type cmd. I ran a chkdsk /R, rebooted and
waited for it to complete. This did not fix my issue but I wanted to
list my full troubleshooting steps because it doesn't hurt to do (in
fact I had some issues it repaired).

Then I cleaned my pagefile. Not sure if that was necessary since I just
ran a chkdsk but I wanted to be thorough. To do this I clicked
start/control panel/administrative tools (I am in classic view). Then
click "local security policy". Then in the left windows expand "local
policies" then click "security options". On the right window scroll
down to "shutdown: clear virtual memory pagefile" Right click then
enable then okay and reboot. Once rebooted I went through those same
steps and disabled this option again to put it back to the original
state.

What I believe resolved the issue is this next step. I tracked down my
issue to be with atapi.sys (based on the event id error research). I
could not replace it while windows was up because it was saying the file
was in use although I am not running any virtual drives nor have
software installed that should lock it up. I had to boot to my os cd,
get into the system recovery command prompt, switched over to the cd
drive (in my case I typed e: ) Command prompt changed to e:\ then I
typed "cd i386" once in that directory I typed "expand atapi.sy_
c:\windows\system32\drivers\" --do not include the quotes when you type
the command. This asked me if I was sure I wanted to replace atapi.sys.
I said Y and after that completed I typed exit and rebooted to the hard
drive, not cdrom. CAVEAT- you need to make sure your atapi.sys is
located in the default location of c:\windows\system32\drivers.

At this point I was able to boot into safe mode without a bsod. I re
ran Malwarebytes and Norton internet security scans just to be thorough.
After completing I rebooted into normal mode, logged on and the last
step I did was right click on my computer, go to properties, click the
system restore tab and check mark "turn off system restore on all
drives". I then rebooted to remove all the old restore files. After
logging back on I went through those steps again and UNchecked "turn off
system restore on all drives" in order to set it back to its original
state.

Anyway, I am not an expert in windows by no means but I do think I
resolved my google redirect issue. Good luck. :)

--Danica