Maybe you got a bad stick of memory or some other dodgy hardware. Without having access to your PC there's not much I can do. The DTools forums don't mention this error. I think if you eliminate it then all your issues will be solved. I really think it's a hardware fault though because if it was software related then it would have been experienced by other people using chankast and/or DTools. Also, most Blue Screens are caused by hardware related issues. Normally conflicting/damaged/old drivers or hardware. another common reason for blue screens is overheating due to bad cooling or overclocking. they can also be caused by psu's that aren't delivering enough amps. A good test in these cases is to bare-bones your system. In other words, unplug as much hardware as you can. just leave your cpu, hd and 1 stick of ram, and 1 gfx card. disconnect power, remove all other cards and unplug all other sticks of ram and unplug all other hd's except your boot drive and unplug all cd/dvd units. unplug any stuff you have hanging off usb/serial/parallel. if possible plug another psu in. do your cmos reset and leave everything at default. if you still get the error, switch off and remove the single stick and replace with a different single stick, preferably from a different manufacturer. it looks like you built your own pc so you should be able to do these tests. if you didn't then it would be best not to attempt any of this because i don't want to be responsible for telling you how to kill your pc.
i do pc repair for a living and i'd say 95% of blue screens that i fix are due to bad/incompatible hardware/drivers. the other 5% are due to people attempting to run incompatible software on their os. i.e. running xp only progs on win95. this obviously does not apply to you.
i know this is not the answer you want to hear, and i know that you really would rather not be playing around with the innards of your pc, but these are the best ideas i can come up with. if you came to me to have your error fixed, these are the tests i would do on your pc.
if these tests did not fix the problem, i would plug a different hd, cpu and finally motherboard. this way the error can be tracked down fairly quickly, and the hardware responsible can be eliminated.
here's a few blue screen horror stories i've dealt with recently:
1) amd k62/500 blue screens with irql_not_less_than_or_equal_to error at random intervals. first thing is that k6 chips run at fairly high temperatures so it's important to have good cooling. the second thing i notice is that when i go to pick up the pc, the user has it sitting on a carpet floor. third thing is that the air intake vent is close to the bottom of the tower. when i open it up, i find that the inside is liberally coated with dust and fluff and god knows whatever else. this pc had been acting as an expensive vaccum cleaner. the cpu/heatsink/fan looked like a mound of dirt sitting on a board that looked like a dirt floor. cleaned everything up, removed heatsink/fan/cpu and cleaned all fluff from them. replaced everything and set it up in a room doing benchmarks with a heater going (it's summer here). the ambient temperature was around 42 degrees. 6 hours later it was still going. sent it back, no probs since.
2) celeron 466 freezes up or goes blue screen or does not start at all sitting on a black screen and bleeping some code. can't remember which error. i began by removing all cards and putting my own gfx card in. the problem remained. then i replaced all original cards and removed the single 128MB memory stick and replaced with my own stick. the problem disappeared. so i removed my stick and replaced the original one. the problem did not return. for good measure i cleaned the original stick and socket and replaced them. this is a reminder that even a small piece of fluff or a hair in a socket can cause a problem. it only takes 1 of the many pins in a socket to not make good electrical contact and you will have blue screen problems.
sometimes the act of unplugging and replugging everything can work wonders when it comes to blue screens. i call it reseating. there are a huge number of reasons why reseating is a good idea when you think you have a hardware issue. sometimes pc's get put together using fairy hands and things aren't plugged in as firmly as they should be. turning a pc on and off results in hot/cold cycles. the expansion/contraction of metals due to these cycles can cause plugs to work loose. old pc's which did not have clips to hold ram in used to occasionally have a stick work it's way completely out of it's socket due to this cycling. pci/agp slots can have this problem especially when fairy hands are combined with cycling.
anyway, hope all this helps or at least gives you an idea of where the problem lies.
.
