Blue screen of death

Reprogramming computer blue screen of death, switched hard drives, turned off bios no matter what I do Goes into Windows program then BSOD then shuts down.
Reformated drive 3 times, pulled battery set 3 days

Help appreciated

 

It sounds like a hardware problem to me. Unless your program somehow disturbed the BIOS chip or burned out the CPU or some other component by overuse, it was likely unrelated to your programming, and you should probably run a hardware diagnostic and post in the hardware section if you need more help. They would probably know which ones are best for your case. If you were doing something that might have contributed, and are more specific, we might be able to help determine the problem better, but the diagnostic should be enough.

An exception would be that if you were programming some attached device, it could need a hard reset. If it's fried or won't completely reset, you could unplug it, disconnect it physically from the computer, and maybe temporarily disable its driver and run in Windows safe mode as a test. If that fails, I'd say it's hardware as before. If it works, try out of safe mode with the driver disabled, and then enabled, then with the device connected again, then using it, to see where it fails. If it's the device, it sometimes works to use it with another computer, as the interface might be different enough to work. You could actually do this with cards and drives you have installed, if you don't mind working in the case, if the software diagnostic doesn't show anything. That's just a brief description. You should check the hardware forums for a better idea of how to check yours.

 

Where do I put it ??? This is an absolutely wiped disk turn computer on the only thing you'll get is A: NOTHING ON THIS COMPUTER AT ALL

 

The diagnostics you should use are likely the ones that you burn to CD, and boot from, with no need of hard drives. If you have more questions, as I said, the software or hardware areas are better for this kind of information. This one may only be more help if you were more specific about what kind of programming you were doing, to speculate about what might have happened, in case it happens to lead to some fix. The other sections seem to be more help getting systems working regardless of the problem. They would have better recommendations about which diagnostics to use and how to use them, and more people tend to read the topics.