VS9 keep rebooting my computer

meshuken · Post by **meshuken** » Tue Jan 10, 2006 9:21 am

I really like this program which explains why I've been pulling my hair out for 2 days trying to figure out why VS9 keeps rebooting my computer.

I downloaded the trial version. After install I am able to edit a project for about 10 minutes, and then my screen goes black and the computer reboots. It has been happening when I try and play my clip, usually around 20 or 25 seconds into the clip. I have tried almost everything I can think of and read on this board:

Updated my video driver
Uninstall and reinstall VS9 twice
Turn off Norton Antivirus
Clear all my temp files
Deleated all clips and sound files from on eproject and use all new ones in case previous files were corrupted.
Tried making a video with no sound or titles, only avi clips
Defraged and scan disked my drive

It still reboots my computer with no warning, BANG! right in the middle of viewing my beautiful work... It's done it 7 or 8 times.

It's really a great product otherwise, very intuitive and powerful. I am ready to plunk down the $99 for the full version, but I'm afraid it will keep doing the same crash that it is now.

I have a 2005 built PC
Windows XP - SP2 installed
Abit MB w/ pentium 2.47ghz
1 gig ram
80 GB HD with 30GB used up
ATI graphics card 128
Creative webcam but no other camera input

Just before I installed VS9 one thing strange that did happen a few days ago was that when I tried to update my windows XP with any critical patches from the Microsoft website it said that my Windows code had been reported comprimised - I need to reregister it they said. I have the original box from XP with the code but can't find it. However windows still works fine, all my other programs have no problems...

Any thoughts on how to keep VS9 from crashing would be appriciated. I would really like to have this program on my computer but I'm afraid of spending the $$ just to have Uleans tech support tell me they can't figure it out either.

Thanks

M

maddrummer3301 · Post by **maddrummer3301** » Tue Jan 10, 2006 8:44 pm

It could be your source video your working with (shouldn't reboot though) or a corrupted harddisk where ever your temp and preview fles folders are located.
Your swapfile could also be to small.
Many things could cause a reboot. Most usual cause is defective memory, incorrect memory configurations or defective hardware.

I would check your bios settings and memory settings.
You aren't overclocking the MB or video card maybe? Usually have to increase the core voltage when overclocking on Abit MB's.

Check your log files and look for system and application errors.
Reboots are usually memory or video card related.

MD

rguthrie · Post by **rguthrie** » Tue Jan 10, 2006 8:48 pm

Also, it might be the Power Supply. Check to see that the exhaust fan is still working. I had one a few years back give up the ghost and luckily my motherboard was protecting the system by trying to shut things down.

Ron G.

tyamada · Post by **tyamada** » Tue Jan 10, 2006 8:54 pm

If you have the original Windows XP disk, you can recover you original operating system files by; click on start, run, in the box type SFC scannow.
You have to have the XP disk in a CD Drive, when you ar prompted to insert disk hit the enter key all the way thru untill the on screen for SFC dissappears.

You might also want to reinstall your video drivers.

Post by **Ken Berry** » Tue Jan 10, 2006 9:04 pm

Hate to add to the sense of gloom, but I agree with my colleagues. The dreaded blue screen of death is usually hardware related -- though of course, software may precipitate the problem. Go to Control Panel > Administrative Tools > Event Viewer, and in System, look for serious error messages ("The system has recovered from a serious error" and then giving some further information. Sometimes also a link to Microsoft Help and Support). This information might give some pointers to what is wrong.

On my previous computer, I used to get blue screens and reboots on a very regular basis, and it varied from program to program. But the common thread in the error messages was a memory conflict. I downloaded the Microsoft RAM test, and found that one of my RAM sticks worked erratically -- not totally shot, but not fully functional either. Replaced the stick and all was well.

FWIW, if you want to avoid the reboots (though you won't be able to avoid the program crashing), go to Control Panel > System > Advanced > Startup and Recovery > Settings, and uncheck the 'Automatically restart' box in the 'System Failure' settings.

maddrummer3301 · Post by **maddrummer3301** » Wed Jan 11, 2006 6:11 am

Last week I had a defective ram chip.
Non-ECC memory (UH).
What's confusing is sometimes you can only guess. The system
appeared to boot and operate properly until some functions use those bytes. in memory.

So hard to tell an intermittent chip.
My files that were being downloaded and copied were corrupt.
Good reason to keep backups.

MD