000000f4 errors are hardware related and very hard to track down.
I would start by unplugging everything possible, excluding screen, keyboard (no mouse, unless you need it) and video then turn on your machine and try going in to safe mode.
Start Visual Studio. If it works, it most likely is down to a device (could be anything). Try updating the drivers for everything you use and/or start unplugging and disabling items until you discover what the problem is - I personally would unplug everything excluding keyboard, video and power, then try plugging devices in one by one until I see the crash.
If however visual studio does not work in safe mode, it could be because of hardware failure - in particular you will want to check for faulty memory (use memtest86+) or hard drive (go to command prompt and type CHKDSK /F
. - You may want to try both of these first, before you disconnect devices or do anything else.
Lastly, if you are still having problems, as you say you are using XP and I do not know the age of the machine, it may be worth looking for fault capacitors -
Blown capacitors -
Blown capacitors can be the cause of many "random" problems which appear to be completly unrelated, very annoying and hard to diagnose.
The top should be almost flat (with slight indents out embossed sections depending on specification... look at the middle one) but you do not want to see any big bumps such as the first one or any leakage as the last one.
Finally, if that is not the case, the last thing I can think of is a problem with power unit - however, this would not be just when you run Visual Studio, this will be any time your system is strained / under demand... This one is a stretch, but the last thing I can think of.
I hope this helps you!
To what OS did you upgrade? Besides if it's a hardware problem as Wil suggests, there might not be a "solution" other than replacing the defect part – Ivo Flipse – 2010-03-04T09:20:44.513
Could be that VS is the only application which stretches the O/S into the limits of its memory, and the bad memory is causing the crash? – Stabledog – 2010-03-04T13:28:18.920