My Ulead Videostudio 9 Keeps Crashing Random Time Intervals
Moderator: Ken Berry
-
Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
Even though your particular computer should in theory be able to do other things, I am not sure you should be running other programs while VS is encoding. I have a not dissimilar computer set up to you (though only a 3.0 processor but 2 GB RAM), and I simply walk away from the computer and let it do its encoding in peace. Never had any problems that way. (Mind you, if I am desperate to use a computer for something, I am lucky that I have a laptop!)
Ken Berry
-
Trevor Andrew
-
Terry Stetler
- Posts: 973
- Joined: Thu Mar 17, 2005 3:34 pm
- Location: Westland, Michigan USA
Let me relate an incident I recently experienced. This falls into the "FWIW" catagory, but you never can tell....
Starting about 2 months ago one of my systems started acting up. This one has an ATI All in Wonder X800, Athlon64 3800+ dualcore, 2 gigs of RAM, a terabyte of storage including a RAID5 etc. etc. In other words a strong system.
It started driving me nutsy with what appeared to be driver crashes for the ATI AIW. The screen would either corrupt or go black and either the AIW's drivers would come back with a "GPU reset" message and keep going or just flat stop with the black screen.
This sometimes happened in Firefox, most times in editing software (it is an editing system after all) and sometimes out of the blue with the system at idle.
I went 'round and 'round with ATI over the card acting squirrely to no avail. New drivers, checked XP Pro 'til I was blue in the face, rolled back drivers etc. etc. and never could resolve the problem.
Getting back into Windows was an interminable frustration as it often took 2 boots to Safe Mode then a boot to VGA Only.
Arrggghhh....!!
Finally on one of these reboot cycles I noticed that the slave HDD on the primary channel, "Exports", had the last few characters of its info line corrupted on the startup screen.
Hmm.....
I took the drive out, put it into a USB drive case and tried it on another system; no problems. It mounted right up and when examined there were no problems with it.
So....I have a system with boot problems and a slave drive on the same cable acting up. Following the K.I.S.S. principle I replace the drive cable.
POOF! Problem fixed. No more crashes in any software and the system can sit at idle for days withlout any problems.
Best I can figure one of the lines in the drive cable was corrupt, perhaps one of the redundent ground lines, and this caused the system to crash with a memory error when the swapfile was hit and it couldn't "see" the HDD....which is common when you're using editing software.
Since editing software uses the display drivers overlay feature a lot this memory error took out the ATI.
Like I said: for what it's worth.
Starting about 2 months ago one of my systems started acting up. This one has an ATI All in Wonder X800, Athlon64 3800+ dualcore, 2 gigs of RAM, a terabyte of storage including a RAID5 etc. etc. In other words a strong system.
It started driving me nutsy with what appeared to be driver crashes for the ATI AIW. The screen would either corrupt or go black and either the AIW's drivers would come back with a "GPU reset" message and keep going or just flat stop with the black screen.
This sometimes happened in Firefox, most times in editing software (it is an editing system after all) and sometimes out of the blue with the system at idle.
I went 'round and 'round with ATI over the card acting squirrely to no avail. New drivers, checked XP Pro 'til I was blue in the face, rolled back drivers etc. etc. and never could resolve the problem.
Getting back into Windows was an interminable frustration as it often took 2 boots to Safe Mode then a boot to VGA Only.
Arrggghhh....!!
Finally on one of these reboot cycles I noticed that the slave HDD on the primary channel, "Exports", had the last few characters of its info line corrupted on the startup screen.
Hmm.....
I took the drive out, put it into a USB drive case and tried it on another system; no problems. It mounted right up and when examined there were no problems with it.
So....I have a system with boot problems and a slave drive on the same cable acting up. Following the K.I.S.S. principle I replace the drive cable.
POOF! Problem fixed. No more crashes in any software and the system can sit at idle for days withlout any problems.
Best I can figure one of the lines in the drive cable was corrupt, perhaps one of the redundent ground lines, and this caused the system to crash with a memory error when the swapfile was hit and it couldn't "see" the HDD....which is common when you're using editing software.
Since editing software uses the display drivers overlay feature a lot this memory error took out the ATI.
Like I said: for what it's worth.
Terry Stetler
-
maso_playboy
thanks guys
sorry that i had to create another account its because i forgot my password so i created one to save time any ways i got so frustrated with teh Ulead Videostduio 9 so i went out and purchased Ulead Videostudio 10 it works alot better and i can fullscreen something else while its encoding and it encodes alot faster not by much but itss till better than nothing so in the future if i have any mopre problems ooo actually will it be best if i unistall Ulead video studio 9 so there are no clashes between the 2.....?
-
Trevor Andrew
-
suzymich
crashing problem with trial version of VS10+
hello I wonder if someone can help.
I am new to video editing and have downloaded the trial version and I am impressed and intend to buy the full version. However I have the same problem - it occasionally crashes, it just shuts down and I am left staring at the desktop. I have tried deactivating the antivirus software and have no other programs running (I think) I read the advice here and did a memory test as I had new memory 3 months ago, but there are not problems with the memory. Do you think that this is a bug with the trial version or is my system not up to the job? I need to know before I pay £50 for the full version.
Many thanks
I am new to video editing and have downloaded the trial version and I am impressed and intend to buy the full version. However I have the same problem - it occasionally crashes, it just shuts down and I am left staring at the desktop. I have tried deactivating the antivirus software and have no other programs running (I think) I read the advice here and did a memory test as I had new memory 3 months ago, but there are not problems with the memory. Do you think that this is a bug with the trial version or is my system not up to the job? I need to know before I pay £50 for the full version.
Many thanks
-
scottphillipsusa
VS 10 keep crashing
I to have this same issue on a new Dell Dimension 510. Has 3 Gig of memory, 2.8Ghz dual core, 250 gig SATA hard drive, nVidia Geforce7300LE with 256mg, Windows XP at SP2 and all subsequent patches. I've tried disabling virus software (Bitdefender Ver 9) and just about everything else in the task bar.
Sometimes I can get an error log like Evnet ID 1000 and Event ID 1001. Usually refering to a fault bucket. Other times VS10 just quits. It can be as simple as looking at the file properties of an inserted video file. Or tonight I was trying to add a title and the system shut down. I've reinstalled VS10 just in case and followed the recommended removal procedures. I've had VS6,VS7, VS8, VS9 and now VS10. I started seeing this problem in VS9 on my old machine so I bought a new machine (it was time anyway for an upgrade). I've sent a note to Ulead but the response was to disable conflicting softwares.
I've actually quit using it for the past 4 months because I just can't figure out what to do. Haven't found any specific posts in the forum that have been any help. Did a memory scan and found no errors with the memory.
Is there a log file that can tell me more of what is going on? I'll paste in the recent error messages from the event viewer if it helps.
Event ID 1001
Fault bucket 319841833.
Event ID 1000
Faulting application vstudio.exe, version 10.0.0.0, faulting module ole32.dll, version 5.1.2600.2726, fault address 0x00118de8.
As a computer professional I'm embarrased that I can't figure out the problem so any help would be appreciated.
Sometimes I can get an error log like Evnet ID 1000 and Event ID 1001. Usually refering to a fault bucket. Other times VS10 just quits. It can be as simple as looking at the file properties of an inserted video file. Or tonight I was trying to add a title and the system shut down. I've reinstalled VS10 just in case and followed the recommended removal procedures. I've had VS6,VS7, VS8, VS9 and now VS10. I started seeing this problem in VS9 on my old machine so I bought a new machine (it was time anyway for an upgrade). I've sent a note to Ulead but the response was to disable conflicting softwares.
I've actually quit using it for the past 4 months because I just can't figure out what to do. Haven't found any specific posts in the forum that have been any help. Did a memory scan and found no errors with the memory.
Is there a log file that can tell me more of what is going on? I'll paste in the recent error messages from the event viewer if it helps.
Event ID 1001
Fault bucket 319841833.
Event ID 1000
Faulting application vstudio.exe, version 10.0.0.0, faulting module ole32.dll, version 5.1.2600.2726, fault address 0x00118de8.
As a computer professional I'm embarrased that I can't figure out the problem so any help would be appreciated.
-
tcvdveer
memory error
ASUS P4RD1-MX - Intel P4.2GHz - 2 GB RAM - 40 GB RAID 0 free disk space. Use VS10+ (demo 
), program crashes regular with before menitioned memory warnings while placing mpeg files / images / titles on the time line and while rendering the movie (creating iso).
), program crashes regular with before menitioned memory warnings while placing mpeg files / images / titles on the time line and while rendering the movie (creating iso).-
meshuken
My VS was crashing quite often - it would actually shut down the entire computer and reboot it, usually while rendering. I had never had thsi happen before with other programs (system is about 14 months old).
I cracked open my case and found that my CPU was packed with dust. After a through cleaning it didn't crash for about six months. Now the other day it just crashed again, so I'm guessing it's time to clean the CPU once more.
I imagine that the rendering was really taxing the processor and the additional heat triggered a safety shutdown.
I cracked open my case and found that my CPU was packed with dust. After a through cleaning it didn't crash for about six months. Now the other day it just crashed again, so I'm guessing it's time to clean the CPU once more.
I imagine that the rendering was really taxing the processor and the additional heat triggered a safety shutdown.