I’m not over clocking. Stressing the CPU does not seem trigger the problem, crunching video with all 8 virtual CPU whizzing away has not triggered the problem. I’ve never actually been doing anything when it happened.
The first time it happened, I left the computer on overnight and it went down during a Windows update. Now, that was a mess, I had to reinstall an image of the hard drive to get it back going. It’s happened about 3 times since then. It has rebooted OK since then.
If I had a local source for DDR3 1066 memory, I would just pull out the memory and put a new chip in, then install one of the modules. If that fixed the problem, I’d be done.
The last time this happened to me, it was with a home brew computer and I cheaped out on the memory, it took me months to figure out it was the problem.
You missed my point.
I was using that as example, an CPU doesn’t even need to be overclocked to be faulty. Memory is just one of many hardware problems that can cause a memory dump. You shouldn’t automatically eliminate something. You could have a faulty motherboard, cpu, gpu,memory, sound,etc etc. What is important is to either find programs that can check each one or to find and read the .dmp file. Google for better help on that issue.