Posted on 08/07/2010 4:25:39 PM PDT by dangerdoc
Windows has it’ own mem tester. Just type memory diagnostic in the search bar on the start menu.
That could be anything, including overheated CPU.
Try running Prime95. Run it using Small FFT’s if it’s your CPU it will lock up or start causing errors after awhile or simply reboot.
I ran it twice. Maybe memory testing is a lot faster now or the test is perfunctory, it only took about 10 minutes to run each time.
I’m pretty sure it is flaky memory but it only fails sporadically.
The computer recognizes a problem, does a memory dump and shuts down. It happened today, the last time it did it was a couple of weeks ago. I think the built in memory checker doesn’t check each location enough time to find the weak bit.
Memory dump isn’t always about memory. When I overclock a cpu and the system can’t handle it at that setting and I am able to get into Windows it will sometimes do a memory dump. Windows 7 64 is less forgiving when it comes to CPU issues it seems to me(an opinion).
I had this same problem. Registry Mechanic solved the problem.
K. Re-install linux, and if that doesn't work, take off and nuke it from orbit.
I don't get many repeat customers for complex problems. ;)
/johnny
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.
Just go into the CMOS setup and enable full POST testing and the memory will be tested the next time you boot up.
The default boot usually just counts the memory without testing.
“The computer is just randomly stopping”
If it is happening on reboots from updates when you’re not there, it could also be the display drivers, or the V-RAM.
The display not re-syncing on Windows startup is way more likely than the main RAM failing.
It’s booting fine, just occasional shut downs.
The funny thing is that it worked fine for a couple of months. I thought that the windows update was bad but when I restored the disc image, I had another shut down before I applied and\y new drivers or OS updates. It was my “clean” image made before I started installing programs and surfing the internet.
Like I mentioned above, I have had a computer acting the same before, You may be right about a bad driver but I don’t think it is Vram, when I happened to be there when it happened, I did not lose video sync.
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.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.