PDA

View Full Version : Memory error with 1.27.0


Carpo
15th February 2008, 13:53
I keep getting this little box pop up about an instruction at 0x00034c50 referenced memory at 0x000345c0. The memory could not be read.

It does this with cce and hc, yet if you leave it alone and let it continue it finishes the encode. I have Vista SP1 installed and cant say if it was doing it pre sp1 as this is the first time in a little while i have had the need to use dvdrb.

No other programs are complaining about mem, i have done about 10 encodes using MeGUI and that has eat a lot of mem

Carpo
17th February 2008, 16:42
so no one else is getting this ?

jdobbs
17th February 2008, 16:51
I haven't had any other reports, although I did have one person report a "crash" on a new system he'd just built. I don't see a connection, though. I assume you've updated to v1.27.1?

Carpo
17th February 2008, 18:48
yes i have updated, and this is a new system, i didnt build it though, i will see if 1.27.1 is any different

Sharc
17th February 2008, 19:29
Such message may be due to a Virus Scanner. It can affect any other SW, so it's probably not related to DVD-RB. Which scanner are you using?

Carpo
17th February 2008, 23:45
Eset NOD32 v3 and its never interfered before, not to say that it hasn't just started doing it, although i did have one thought but does dvdrb use any of the .net framework ? if so i have been getting a strange issue with .net3.5 and the solution seems to be to uninstall and reinstall it, which i will do in the morning

jdobbs
18th February 2008, 00:32
No. DVD-RB doesn't use the Net Framework.

Carpo
18th February 2008, 09:34
blows that idea out the water then :p

Carpo
18th February 2008, 18:57
well so far with 1.27.1 and things look to be going OK - norm it would kick up that error within the first 2 - 3 segments, atm its on the 8th and all is well, and to make certain i have used cce basic cce sp2 (6 passes - i know more passes don't equal better picture but it would give a better chance of it kicking up) and hc, so who knows maybe there was a strange little issue with 1.27 that only affect my strange nvidia quad setup :D