Free Republic
Browse · Search
General/Chat
Topics · Post Article

To: dangerdoc

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).


25 posted on 08/07/2010 6:34:51 PM PDT by aft_lizard (Barack Obama is Hugo Chavez's poodle.)
[ Post Reply | Private Reply | To 24 | View Replies ]


I had this same problem. Registry Mechanic solved the problem.


26 posted on 08/07/2010 6:56:42 PM PDT by webboy45
[ Post Reply | Private Reply | To 25 | View Replies ]

To: aft_lizard

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.


28 posted on 08/07/2010 7:38:37 PM PDT by dangerdoc
[ Post Reply | Private Reply | To 25 | View Replies ]

Free Republic
Browse · Search
General/Chat
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson