Well So far so good for me
Here is where I sit. I have had the exact error messages as Martin. As I have said I finally couldn't do anything, including a Norton AV full scan without the computer BSODing. I couldn't check my mail nothing. The only thing that was new to my system was a printer I just bought from my school. A Lexmark X125 all-in-one. About four days after that I got the whole 000000c4 ffdff120 error that this threaded conversation is all about.
I am wondering what is going to happen. I just spent 9 straight hours saving all necessary information to another computer, repartitioing the hard drive, setting up XP pro, talking with microsoft(by the way their advanced support has no idea what it is), and reloading all my old software. I am hoping by reformating (which is the worst case scenerio) it took whatever driver was on the system.
I have a Dell Inspiron 2650, with nVidia GeForce 2Go, Synaptics touch pad, ATA drivers, 3Com ethernet NIC driver, and some other stuff I can't think of right off the top of my head. I reinstalled all the drivers, and still I got the problem. I went one by one and took off all the USB's and still I had the problem. Unfortunately, I believe whole heartedly that the solution is to restart brand new. I understand that you don't have the time to do this. So you proposed saving all the information to an error free hard drive. I believe this will work given you keep only the information that does not apply to the system itself, ie docs and music and no-hardware-software-dedicated files that access the system. It might work.
I would try getting a new harddrive and reloading the OS and the drivers one at a time and rebooting each time. This will give you a definitive answer as to which drivers are courrupting the Kernel Stack.
When you find the driver that is corrupting the system, don't install it next time. You will have to go back and reformat and reinstall the OS for it to have a fresh clean start on things. Then get an upgrade...
Now all of this is tenative at the moment because who knows. I could press reply on here and get a BSOD, knowing my luck.
Let me know if any of this sounds feasible...
-Black