![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
With the christmas season aproaching it is that time to start editing a years worth of video footage and pictures and creating a DVD to send out. Ive been having some minor issues with my computer rebooting during intense applications over the past few months but when I started converting my video into MPEG4 or any format (I tried divx,xvid, uncompressed AVI) I get a complete system freeze. I took a normal video sample and tried to convert it and it froze.
It gets even worse when I I tried to simply eidt the video and attempt to convert it using the video editing program. I get a complete system crash and automatic reboot. I looked at the event manager and I am lost as to what is causing these crashes.
I have used Sony Vegas studio, Ulead Video, even went the low route and tried just the windows movie maker, and they all crashed when converting.
The system freeze occured while converting my files in several programs. I tried virtualdub, tmpengc, and several other shareware programs to simply see if it was software related.
The notable clue was that while converting vitrualdub is the only program that will not freeze the computer but rather return an error and crash the program.
Any clues as to what is going on.
Windows XP SP2.
Took everything back to basics so no overclocks.
It gets even worse when I I tried to simply eidt the video and attempt to convert it using the video editing program. I get a complete system crash and automatic reboot. I looked at the event manager and I am lost as to what is causing these crashes.
I have used Sony Vegas studio, Ulead Video, even went the low route and tried just the windows movie maker, and they all crashed when converting.
The system freeze occured while converting my files in several programs. I tried virtualdub, tmpengc, and several other shareware programs to simply see if it was software related.
The notable clue was that while converting vitrualdub is the only program that will not freeze the computer but rather return an error and crash the program.
Any clues as to what is going on.
Windows XP SP2.
Took everything back to basics so no overclocks.