Page 1 of 1

T60 hangs on boot, various errors, help!

Posted: Mon Jan 21, 2008 12:03 pm
by ducky2802
Hi everyone,

An interesting problem has cropped up. Out of nowhere, my T60 decided one day to hang on bootup. It just froze. Restarting, and I get the blue screen that ati2dvag is stuck in an infinite loop. No big deal to me, so I decide to update the driver to the latest version after completely uninstalling the ati drivers and catalyst program. Problem gets worse, not better, as now the machine blue screens every time, and if it does manage to boot into windows, I get little tiled images of my desktop, all in corrupted colors, something like an andy warhol painting.

No big deal again, just restore my backup. I restore to my backup point with RR, which was built immediately using full factory recovery image, plus some programs that I have used without a single problem for the past year; I have restored this image at least a dozen times prior without hitch.

And you guessed it, my machines just freezes on boot. Now, I managed to trace the problem to my prefetch folder. It appears if I delete the contents, I boot with no problem at all. But as soon as it starts populating again, I get issues.

So, I figure if my screen works, its likely the ati x1400 is working. I figure if I can get at least a few days on a swapped hdd with a clean factory image w/o error, its most likely a working gpu and just a driver conflict. But, while I have run a few machines without a prefetch folder by setting the registry value to 0, usually, I still see a layout and a nto file in the folder, and its the nto file that gives me that hangs my boot. So I ask you... any advice??? Thank you for your help!

My machine is type 2007, T2500, xp pro, ati x1400, 4gb ram, 100gb hdd.

Posted: Tue Jan 22, 2008 1:53 am
by ducky2802
update... running a bootlog, I find that just about every driver after mup.sys fails to load. Now this seems to be a common problem for xp systems for various reasons from hardware changes to simple server/client networking issues, so the solution could be diverse. In any event, I have never seen this happen before and I hope it isnt a hardware failure!