Moving titles causes "memory could not be read" er
Moderator: Ken Berry
-
crichardson
Moving titles causes "memory could not be read" er
When trying to move or change a title or audio, I get a small box next to my mouse cursor, then the error message asking if I want to send a message to Microsoft comes up. Then the error message: 'The instruction at "ox73ddllc7" referenced memory at "ox00000004". The memory could not be "read" click ok to terminate' Then it kicks me out of VS9. I get this on two projects I am working at random times. Is my file corrupted? I have 1 gb memory, 250 gb hard drive with 180 free on a new HP 630 Pentium pc. VS9 worked for 2 months then started with this. I have uninstalled all programs I installed during that time and reinstalled VS9 including patches. Any ideas?
-
claproods2
maybe this will help
I didn't have exactly your problem, but I had many mystery halts and lockups with audio, and I found several quirks with u-lead not in their documentation:
Some audio files will lock u-lead. not sure why, but they seemed to be mpg files from itunes most of the time. I had 2 mpg files out 20 that would hang my prohject up everytime. to troubleshoot try just using one of the canned audios from u-lead and see if it works. If it does try converting your audio to some other format.you can use a freeware program called goldwave to do conversions.
don't use anything but jpegs for photos. PDD files and some others cause u-lead to hang up when you are moving things in the time line.
Check to make sure the jpg files are not hidden or read only. This also caused problems in the time line.
I found you have to do a lot of trial and error before you can get this tool to work.
good luck. maybe someone else will have some tips.
Some audio files will lock u-lead. not sure why, but they seemed to be mpg files from itunes most of the time. I had 2 mpg files out 20 that would hang my prohject up everytime. to troubleshoot try just using one of the canned audios from u-lead and see if it works. If it does try converting your audio to some other format.you can use a freeware program called goldwave to do conversions.
don't use anything but jpegs for photos. PDD files and some others cause u-lead to hang up when you are moving things in the time line.
Check to make sure the jpg files are not hidden or read only. This also caused problems in the time line.
I found you have to do a lot of trial and error before you can get this tool to work.
good luck. maybe someone else will have some tips.
- 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
Just to clarify a minor technical confusion introduced by claproods2's otherwise helpful suggestions. The problem experienced in Ulead by some people using iTunes is not exactly with 'mpg' files, but more precisely with MP3, and the problems with MP3 are if anything more often caused by the codec which created them (particularly Lame MP3). Just in case the original poster is a newbie and does a search for 'mpg' files and is surprised when the search only seems to turn up video files and not audio ones with an .mp3 extension.
As for converting them, the format which always seems to work is .WAV
As for converting them, the format which always seems to work is .WAV
Ken Berry
Re: Moving titles causes "memory could not be read"
You never know, it may even be defective RAM. You should be able to find a utility to check your RAM.crichardson wrote:When trying to move or change a title or audio, I get a small box next to my mouse cursor, then the error message asking if I want to send a message to Microsoft comes up. Then the error message: 'The instruction at "ox73ddllc7" referenced memory at "ox00000004". The memory could not be "read" click ok to terminate' Then it kicks me out of VS9. I get this on two projects I am working at random times. Is my file corrupted? I have 1 gb memory, 250 gb hard drive with 180 free on a new HP 630 Pentium pc. VS9 worked for 2 months then started with this. I have uninstalled all programs I installed during that time and reinstalled VS9 including patches. Any ideas?
Also, try looking in XP "Event Viewer" which may give some further clues.
JVC GR-DV3000u Panasonic FZ8 VS 7SE Basic - X2
