Memory Error Message in Video Studio 10 Plus

Moderator: Ken Berry

Post Reply
Stephen Quick

Memory Error Message in Video Studio 10 Plus

Post by Stephen Quick »

Hi there everyone on this forum, I have been reading through lots of your posts on here and there seems to be a great deal of experianced users on here. So may be someone could answer my question.

SUBJECT: Error Message in Video Studio 10 Plus

Full CD Boxed Version

Nature of the problem : Getting and error code randomly when I am using the software after doing various things.

Properties of your source files : MPG2 files from Sony HDD camcorder. PAL

Error Codes is as follows:

Red X in a Circle POPUP

The instruction at "0x00000000" referenced memory at "0x00000000".
The memory could not be "read"
Click ok to terminate the program.

OK


System information:

Alienware Area 51 PC

Intel D875PBZ MOTERBOARD

Intel Pentium 4 3.00GHz

2Gb of DDR PC3200 Ram

ATI Radion 9600 XT 128Mb

Windows XP

Thank You In Advance.
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
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

Post by Ken Berry »

If indeed the addresses in the error message are all zeros, then I would be very suspicious about one of my RAM sticks being defective. That sort of message can either indicate that there is a conflict with another program trying to acess the same RAM address at the same time as VS; OR it can indicate that the address simply can't be accessed by the program because it is defective. And if the address is absolute zero, this tends to imply (at least to me!) that VS simply can't address the RAM stick at all.

Do a Google search for a free RAM test program. Microsoft has a free one, though I don't have the URL for it, I am sorry...

Otherwise, as a work around, you would have to remove one stick of RAM, and run VS for a while and see if the problem recurs. If it does not, you could remove that stick and replace it with the other one. If the problem recurs with that stick, then that would appear to be your culprit. The good news is that RAM is pretty cheap these days.
Ken Berry
Post Reply