PDA

View Full Version : Xvid 1.0 crashes Explorer


adoniscik
2nd June 2004, 19:19
Is it the encoder or the decoder? I just want to know whether installing the next version of xvid will solve the problem with my existing files, or whether I will have to re-encode them.

Nic
2nd June 2004, 19:28
The directshow decoder being used to decode XviD is the cause of the problem. Depending on what that is.

Please post more information and read the sticky post about posting bugs, for the kind of information we need.

-Nic

adoniscik
2nd June 2004, 20:18
Right... the details are:

Codec version 1.0, with (Y,UV) deblocking postprocessing.

xvid causes Windows (XP Pro) Explorer to crash "nvcpl.dll" (Detonator version 56.72), even in List mode with "Details" disabled.

The encoder settings are AS@L5, AVS Best quantizer, MSP6, VHQ1, Turbo, Trellis quantization.

The container is AVI, with AC3 muxed in VirtualDubMod 1.5.10.1

celtic_druid
3rd June 2004, 04:37
Disabling the windows thumbnail shell integration thing should solve it.

RPT
14th October 2004, 05:55
Disabling the windows thumbnail shell integration thing should solve it

How does one do that? I'm having the same problem. thx.

sysKin
14th October 2004, 06:09
I'm still looking for a person who can debug this problem, no luck so far.

I was once told that switching desktop colour depth from 16bits to 32bits fixes this problem. Can someone confirm that, please?

Radek

dragongodz
14th October 2004, 07:09
i found running bigfix
http://forums.divx.com/viewtopic.php?topic=54711&forum=1
and letting it fix any video and audio problems it found(but unticked removing ffdshow etc) fixed instabilities for me.

so it would be nice if someone with the problem could try that aswell and say if it works for them aswell or not.

Yong
14th October 2004, 07:39
Run the registry editor, find the word video thumbnail extractor, rename the key {xxxx...} to {xxxx...}+ or what ever u like(just make it easy to rename back).
Then all video file(ogm, mpg, wmv, avi...) will not display the thumbnail after this action.
This solution should be add to the General AV FAQ or somewhere...:)

Ark
14th October 2004, 09:10
Originally posted by sysKin
I'm still looking for a person who can debug this problem, no luck so far.

I was once told that switching desktop colour depth from 16bits to 32bits fixes this problem. Can someone confirm that, please?

Radek

Unfortunately doing that doesn't change anything on my machine (WinXP Pro), Explorer still crashes. :(

dragongodz
14th October 2004, 12:31
Ark - it would be nice if you could try running bigfix aswell and see if that has any effect.

Ark
14th October 2004, 13:26
Originally posted by Yong
Run the registry editor, find the word video thumbnail extractor, rename the key {xxxx...} to {xxxx...}+ or what ever u like(just make it easy to rename back).
Then all video file(ogm, mpg, wmv, avi...) will not display the thumbnail after this action.
This solution should be add to the General AV FAQ or somewhere...:)

What exactly I've to change?

I found the string "video thumbnail extractor", but in the window where usually you can change the values there're 2 forms, 1 saying "Value_Name"(i guess, because my Windows is in italian...), empty and not editable, and a second named "Value_data" with written "video thumbnail extractor", but even if i change this nothing happens, all video files have tuhmbnail, so XviD ones crash!

stephanV
14th October 2004, 13:42
what also should work is: start-->run and then type "regsvr32 /u shmedia.dll"

this will unregister the thumbnail thingy. it causes problems with more than one video codec and the functionality of it is rather low i think.

if you want to enable it again type "regsvr32 shmedia.dll"

possibly you need to reboot.

hope this helps :)

Sharktooth
14th October 2004, 15:04
Originally posted by stephanV
what also should work is: start-->run and then type "regsvr32 /u shmedia.dll"

this will unregister the thumbnail thingy. it causes problems with more than one video codec and the functionality of it is rather low i think.

if you want to enable it again type "regsvr32 shmedia.dll"

possibly you need to reboot.

hope this helps :)
Yes, that was what i did.
That shmedia.dll is buggy, and will cause instabilities.
Unregistering will not prevent the "preview" and will not harm any OS functionality.
Just kill it... :D
There is nothing wrong in the xvid decoder.

Yong
15th October 2004, 06:51
Sorry for my poor english...

@ark
Run the regedit and find this word "{c5a40261-cd64-4ccf-84cb-c394da41d590}" or "video thumbnail extractor", right-click the key and select "Export".
Backup the registry file and you can safety delete the key now.

stephanV ones also a is a good method.

This will increase windows performnce!!!:D

dragongodz
15th October 2004, 07:13
ok i will say it 1 last time.

MAYBE SOMEONE WOULD LIKE TO TRY RUNNING BIGFIX TO SEE IF THAT FIXES IT FOR THEM INSTEAD OF JUST DISABLING THE THUMBNAIL.

Blue_MiSfit
15th October 2004, 08:36
I have this problem from time to time, but I have found that it's not from the XviD decoder, but from ffdshow.

The latest build (one that was posted on doom9's front page a couple days ago) seemed to crash explorer when i tried to thumbnail...

removing it and reinstalling my previous build solved all problems

doesn't really sound liek you guys are using ffdshow, but if you are, try a different version

~misfit

Ark
15th October 2004, 09:21
The strange thing is that on my machine it happened only with koepi builds (1.0.1 and 1.0.2) and not with gamr builds which i had for some time before getting koepi's 1.0.2...

kurt
15th October 2004, 10:24
Originally posted by dragongodz
ok i will say it 1 last time.

MAYBE SOMEONE WOULD LIKE TO TRY RUNNING BIGFIX TO SEE IF THAT FIXES IT FOR THEM INSTEAD OF JUST DISABLING THE THUMBNAIL.

HI, i had the same problem with ffdshow a few weeks ago...i found out that "disabling" overlay mixer solved my problem of crashing the windows explorer...i'm using now latest milan ffdshow build (http://sourceforge.net/project/showfiles.php?group_id=53761&package_id=59355) (Oct 12 2004) and this fix the problem too (" This build should fix Windows XP explorer crashes. ")

(edited)

dragongodz
17th October 2004, 13:57
my point was that sometimes windows itself(especially xp in my experience) can be part of codec problems. my suggestion to try bigfix was to see if that was the case for others. since nobody wants to even try it i wont bother.

Sharktooth
17th October 2004, 16:10
A sort of bigfix is included in the xvid installation (at least the koepi's build).
Why try bigfix?
shmedia.dll is the problem...

dragongodz
17th October 2004, 16:23
Vid.Cleaner does not correct everything that bigfix does. i tried Vid.Cleaner and still had some instabilities. then ran bigfix and it fixed the problems i was having.

why try ? no reason at all if people are not interested in testing if it fixes some of the problems people are having.

RPT
17th October 2004, 18:49
dragongodz, I downloaded and ran Big fix after I saw your post. It did seem to help, What seemed to solve the problem once and for all was:
1. running Bigfix
2. Disabling Xvid & DivX
3. running ffdshow
Since then I've had no problems. Oddly enough, after doing all of that I reinstalled DivX 5.2 ... AND THE PROBLEM CAME RIGHT BACK!! I uninstalled it, and since that life has been good,:p
Now, I'm a (relative) newbie and I'm sure that there are redundancies and/or inconsistencies in what I did. All I know is that the problems I've had ever since installing SP2 have disappeared.
For what it's worth ...:rolleyes:

RPT
17th October 2004, 18:56
a postscript I forgot to mention ... I can now view avi files within Explorer as thumbnails with no problem at all.

dragongodz
18th October 2004, 04:14
RPT - you should have ran bigfix after installing divx 5.2. my observation has been that windows xp is especially bad at screwing up its codec handling. so when you install or uninstall a codec it can become unstable sometimes. running bigfix in those cases has smoothed it out for me. so i was trying to nail down if it also helped for problems others were having since if so then the problem would be found.