Vista crashes during defrag

[Bradley]

Hello,

My laptop crashes as soon as the defrag finishes the analysis stage and
moves into the defrag stage. I ran a chkdsk and everything is fine. I think
it might have something to do with ReadyBoost and ReadyDrive. Anyone know
how tore solve this problem?

Thanks,
Bradley

 

[Richard Urban]

You are using a 3rd party defragmenter. What does its manufacturer have to
say about this?

 

[LesleyO]

Hello,

My laptop crashes as soon as the defrag finishes the analysis stage and
moves into the defrag stage. I ran a chkdsk and everything is fine. I
think
it might have something to do with ReadyBoost and ReadyDrive. Anyone know
how tore solve this problem?

Thanks,
Bradley

 

[Bradley]

I removed the 3rd party (diskeeper) to get it out of the equation.
Microsoft's defrag also causes the hard drive to stop responding and the
system to eventually lock up. (No BSOD since it just locks up and cant tell
windows about the error code, Vista just knows that it wasnt shutdown
properly.)

If I remove the new Intel Turbo Memory v1.7.0.1029 drivers (found at
http://www.intel.com/support/chipsets/itm/index.htm) completely and dont
install anything then I can defrag and no system crashes. I'm now almost
100% convinced this has to do with the Intel drivers and maybe the Intel
Turbo memory controller.

This is on a ThinkPad T61 laptop. Not sure if that provides any additional
help. Whats also noteworthy is when Vista starts up sometimes the computer
will just hang on the startup progress bar and I'll have to forecibly turn it
off then back on again. Repeatedly sometimes, but eventually it would boot.
Very randomly, about three times a week. Again, no Turbo Memory drivers, no
issues.

Now the turbo memory drivers also install the latest AHCI drivers, so they
could have some play in this also, but I doubt it.

Thanks,
Bradley

 

[Richard Urban]

It seems to me that Intel has had more than their fair share of driver
problems over the years, especially with their application accelerator.

 

[Bradley]

Hi Rich,

I havent had much issues with Intel drivers until this ReadyBoost &
ReadyDrive came into the picture. Do you know if there is someone out ther
who would be willing to figure out the problem? I dont mind assisting with
the troubleshooting. I was thinking either Microsoft or Intel.

I just dont want to spin my wheels with someone who is not that technical
looking up knowledge base articles on stuff that I have already tried.

Thanks,
Bradley

 

[Richard Urban]

For any defragmenter to operate you need at least 15-20% free space on the
partition. If you don't have that much available the defragmenter will
choke.

Just hope that someone jumps in here that has had the exact same problem as
you and has found a fix for it. I can't help you except in generalities.

 

[Paul Montgomery]

Hi Rich,

I havent had much issues with Intel drivers until this ReadyBoost &
ReadyDrive came into the picture.

You've already found that uninstalling the turbo memory drivers STOPS
the problem.

What MORE do you need to know!?

That would certainly be enough to convince MOST troubleshooters that
the problem has been found/fixed.

 

[Bradley]

Hi Rich,

Yeah, I'm hoping also. I have 49% free space on a 320gb 7400RPM Seagate
Momentus hard drive. I have more info now and I think I found the exact
cause! So, now I am running with ReadyBoost enabled and ReadyDrive disabled
and using the original drivers for the hard drive that came with Microsoft
Vista. The culprit is definitely in the drivers for the SATA AHCI disk
controller and not the Intel Turbo Memory on my T61.

Maybe that will help someone figure out my problem?

Thanks,
Bradley

 

[Bradley]

Hi Paul,

I'm interested in figuring out the problem. I'm not your typical end-user.
I've already replaced hardare compontents and have narrowed it down to a
software issue. I've also recently determined it is not the Turbo Memory
drivers, instead, it must be the new sata controller drivers that are from
Intel.

I'm not getting BSOD's so there is nothing logged. Instead I've had to
resort to the pre-windows 2000 trouble-shooting methods of trial/error.

Thanks,
Bradley