Log in

View Full Version : access violation error [updated with more info]


joedan
21st November 2003, 14:47
hi :)

i am using avisynth to frameserve to vdub and i keep getting this 'access violation while trying to read <hex value>'. its strange because i didn't used to get this error a couple days ago when i was using the same .d2v.

i have tried: creating a new .d2v, re-ripping the vobs, installing the latest avisytnth (2.5.3), defragging
but i always end up with this error.

does anybody know how to stop this error and why it keeps appearing?

thanks for your help :D

update:

i am using:
Decomb510.dll
MPEG2Dec3.dl
avisynth 2.5.3
vdub 1.5.4
dvd2avi 1.77.3

also, i just got this message:
An out-of-bounds memory access (access violation) occurred in module 'MPEG2Dec3'.

thanks for any info you can provide

Wilbert
21st November 2003, 22:59
I guess you didn't move the d2v file.

What version of mpeg2dec3.dll are you using?

joedan
22nd November 2003, 16:20
what do you mean i didnt move the d2v file?

i am using v1.10 of mpeg2dec3.

this weird thing about this error is that the more i play around and test different files that have always worked fine, the more i feel like it has something to do with windowsxp

in any case its real annoying because i essentially can't do any encoding at all right now - it fails on everything!

DDogg
22nd November 2003, 19:28
You may want to try Donald Graft's new matched set of dvd2avi and mpeg2dec3. DVD2AVIdg fix (http://neuron2.net/fixd2v/decodefix.html)

joedan
22nd November 2003, 20:04
thanks for your help but i still get the same problem

this is definilty windows related :/ i cant perform a complete pulldown or wav>mp2 without crashing ...
if im not doing anything encoding-related im perfectly stable... stupid windows :angry:

sh0dan
22nd November 2003, 21:42
Have you tested your system with Prime95?

Just search for it (here or Google).

joedan
23rd November 2003, 16:21
whoa prime95 only ran for 3minutes before stopping due to an error.. i will try removing ram and let you know what happens

vigi_lante
23rd November 2003, 17:58
Try to install a old version of AVISynth 2.5 (the first one)...review your script again too.

Wilbert
23rd November 2003, 18:02
Is your system overclocked?

sh0dan
23rd November 2003, 20:47
Sound like RAM or CPU problems.

@vigi_lante: His system isn't stable - what's the point?

joedan
24th November 2003, 17:56
my system is not overclocked.

i am running prime95 and removing different ram sticks - i will keep you guys updated and let u know if it leads to prime95 running as it should.

i have just run CPU stability test for 20hours without crash - when i got to my computer today it had rebooted - i assume it eventually crashed.

i hope this turns out just being a case of bad ram

if you can think of any other stress testing and/or hardware i should try to remove, let me know.

i wont have time to complete these tests until thursday so i will let you know then if removing a ram stick solved the instability issue.

Boulder
24th November 2003, 19:36
If you want to test the RAM only, use memtest86. That way you'll see if it's the memory sticks or something else.

http://www.memtest86.com/

joedan
25th November 2003, 04:34
thanks for that link Boulder.

i have run prime95 on each ram stick and it always fails after about 5 minutes.

i have now also gone through a couple passes of memtest86 without any errors.

so i guess that the problem is my cpu? are there any programs to verify this? cpu stability test is nice but it doesn't seem to give any information - it just runs until it crashes.

later this week i will try putting in an older spare cpu and i will let you guys know how it goes.

thanks for the help :)

sh0dan
25th November 2003, 10:19
(Redirecting to the Hardware forum)

I had a similar problem, but I had to replace the motherboard, as replacing the CPU didn't help.

joedan
28th November 2003, 21:30
ok so the other day i buy a new case, and i put my pc in it and.... now no problems?! :confused:

i can encode fine, no access violations, prime95 runs np...

wtf :confused: :confused: :confused: this doesn't make any sense but i'm glad everything is working smoothly again.

Boulder
29th November 2003, 10:17
New case = new power supply unit! (you probably don't get a case w/o a PSU unless you specifically ask for it)

Your older PSU probably wasn't up to the task. The more CPU cycles are spent, the more power is required to keep everything running smoothly and without odd crashes.

joedan
30th November 2003, 17:37
nono thats what im saying: the only thing different is the case! my whole pc (including powersupply) is the same! :confused:

this is so weird lol

Boulder
30th November 2003, 17:47
Then the only logical reason is that the air flows through this new case differently and keeps some component (most likely the CPU) cooler than in the previous one?