I am using Video Studio 9 and have been for several months with no problems creating 100s of DVDs. The last couple weeks I have been getting a couple memory errors when converting video while creating the DVD. "The instruction at "Ox77f57d185" referenced memory at "Ox73e6d91e". The memory could not be "written"". Sometimes it says "read". The addresses are not always the same and it is happening on several different projects from small (10min) to 2 hour videos). I get this with new and old projects. The error will occur at different percentages in the same project. I have 1.5 GIG of DDR memory on a P4 2.4 GHZ computer running WIN XP PRO. Is this a Video Studio problem a possible memory chip problem? I have tried doing a repair reinstall with no change.
Thanks
Tim
Memeory read and write errors when creating a DVD
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
This may not help, as it may be specific to my computer. But I have received similar error messages, though usually at the stage of first creating the DVD-compatible mpeg-2 file and before opening the burning engine.
As you will see from the system button, I have 2GB of RAM (which I regularly test) and a P4 3.0 Ghz processor. I might also add that I do two-pass encoding, which may or may not be relevant.
However, I usually find I get the error message after I have been playing around on VS9 for a while, editing etc and then trying to produce my mpeg-2. My first inclination was to use the old tried and true method of rebooting the computer, opening VS9, opening my project and going straight to Share > Create Video File, without doing anything more. And this invariably worked. The MPEG-2 file was produced with no further problems. So that's possible solution number one!
Then I started thinking: the memory clash implied by the error messages might be solely internal to VS9, rather than with another program, with my earlier editing etc possibly 'locking up' a particular memory address which the rendering/Share process later tries to access with no success. So I experimented, the next time I got the error message, by simply turning off VS 9, restarting it, opening the project and going straight to Share > Create Video File. And it worked and has continued to work on 4 projects now. So that's possible solution number two.
Now, obviously there is something fundamentally wrong to be getting such clashes in the first place, and it is annoying. But with the apparently work-around being so simple and relatively non-time consuming, I am prepared to live with it.
As you will see from the system button, I have 2GB of RAM (which I regularly test) and a P4 3.0 Ghz processor. I might also add that I do two-pass encoding, which may or may not be relevant.
However, I usually find I get the error message after I have been playing around on VS9 for a while, editing etc and then trying to produce my mpeg-2. My first inclination was to use the old tried and true method of rebooting the computer, opening VS9, opening my project and going straight to Share > Create Video File, without doing anything more. And this invariably worked. The MPEG-2 file was produced with no further problems. So that's possible solution number one!
Then I started thinking: the memory clash implied by the error messages might be solely internal to VS9, rather than with another program, with my earlier editing etc possibly 'locking up' a particular memory address which the rendering/Share process later tries to access with no success. So I experimented, the next time I got the error message, by simply turning off VS 9, restarting it, opening the project and going straight to Share > Create Video File. And it worked and has continued to work on 4 projects now. So that's possible solution number two.
Now, obviously there is something fundamentally wrong to be getting such clashes in the first place, and it is annoying. But with the apparently work-around being so simple and relatively non-time consuming, I am prepared to live with it.
Ken Berry
-
timwulead
Thanks for the input Ken. I have tried everything you mentioned with almost no luck. I have at times have been able to get a couple projects to complete after restarting VS9 and or the computer after the error closes VS9 down. BTW everytime I get the error it is fatal to VS9. The problem is occuring 95% of the time now.
Tim
Tim