[Psychofurball]

Frankly, I don't know what to look for - but I cleaned out maaany files of the computer, defragmented all the drives, disc clean-ups etc etc.. and I have saved Moviemaker files into regular files with more stuff on the computer...

either the computer just shuts down by itself about halfway into saving the movie file - well, it restarts actually - or if I'm "lucky" enough, an error message pops up saying there's a problem of some sorts and needs to shut down, and then asks if i want to send an error report or not.

Any other bigger operation It even shuts down about twenty times whenever I tried to to perform a disc-cleanup. Does anyone know what the problems is? Please anyone with suggestions? I don't want to reformat, I have stuff I need to keep.

PFB

[Advertisements]

Slow down. Use complete sentences. It is difficult to follow what your issue is.

From your description, what I can grasp, I would say you have a memory failure (system reboots), or an outside shot at a bad driver.

The second is easier to address. Simply update all your drivers

The other,,,,how many sticks of memory do you have? If you feel competent, and have two or more, remove one stick, test, and if the problem goes away, there is your problem. If not, reinsert the stick and pull another.

Always guard against static electricity by grounding yourself.

You could also test your memory with something like memtest86 (google it), though that does not detect everything.

[gerryf]

Slow down. Use complete sentences. It is difficult to follow what your issue is.

From your description, what I can grasp, I would say you have a memory failure (system reboots), or an outside shot at a bad driver.

The second is easier to address. Simply update all your drivers

The other,,,,how many sticks of memory do you have? If you feel competent, and have two or more, remove one stick, test, and if the problem goes away, there is your problem. If not, reinsert the stick and pull another.

Always guard against static electricity by grounding yourself.

You could also test your memory with something like memtest86 (google it), though that does not detect everything.

[dflo404]

The same thing used to happen to me. From what I remember, I updated WMM, and it was fine. I'm not sure if you have updated it at all, but I suggest looking into that if you havent.

(althought I might be too late, I think gerryf might have solved the problem already)