I used VS9 for the first time yesterday, creating a complete video, successfully rendering it to an ISO file and burning a DVD. Today I reopened the project and tried to edit some of the titles, and it just crashes randomly with the"referenced memory at xxxx" type error.
I tried it a couple of times, then rebooted and tried again. No luck. Is this a common issue with VS9? My system is generally very stable, and I've had no trouble with extensive use of VS8.
Should I give up on this, or is there something else to try? I do have the patch from the August timeframe installed.
VS9 Started Crashing
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
Don't know what is the matter but we are getting increasing reports of such behaviour. It could be worthwhile to reinstall the program but not the update patch. I am a great believer in 'if it ain't broke, don't fix it'. I have been using VS9 since soon after it first came on the market and have not applied any of the patches. No problems so far. After the schemozzle of the patches of VS8, I think you only should apply patches if your computer actually demonstrates the sort of problem the patch is designed to fix. 
Ken Berry
Actually I did a "repair" reinstall and the reapplied the patch, and so far it has been working OK. I was able to resume editing on my project and finished that successfully.
I am also usually in the "if it ain't broke camp", but I don't think that they always tell you *everything* that is fixed in a particular patch, so usually just go ahead and apply them. This one's been out since August, so I figured if there was anything wrong with it, it would have been found & fixed by now.
I am also usually in the "if it ain't broke camp", but I don't think that they always tell you *everything* that is fixed in a particular patch, so usually just go ahead and apply them. This one's been out since August, so I figured if there was anything wrong with it, it would have been found & fixed by now.
