Win Explorer crashes due to h264 codec

[DrinkOrDie]

This has been happening fairly consistently. Happens after Super finishes transcoding MKV to Xvid AVI, but not until I start clicking around. Not really causing major problems, it's just irritating is all. See attached pic for more details. Any thoughts on this?

[Chewy]

are you folding during this?

http://www.cpuid.com/download/cpu-z-143.zip

[DrinkOrDie]

Well, yes and no. F@H is running but it's been stuck "attempting to send results" for a couple days. I have 2 work units completed that I haven't been given credit for yet. I already posted on that issue in the "join our team" thread.

[Chewy]

how about some cpu-z screens

[DrinkOrDie]

BTW: your link doesn't work, but I already have cpu-z.
Now this is weird. I get an error when I open cpu-z. This is a first for me. It tells me there was an error loading the driver. It will still open, but not all information will be available. That's never happened before. Basically all it will tell me about the system, is already included in my signature. However it does tell me my current core speed, which constantly changes because I am using AMD cool-N-quiet. It adjusts clock speed up and down depending on workload.

[DrinkOrDie]

Ooops. Dangit. forgot the screenshot. My apologies. Take a look. BTW, f@h is now stuck on saying "Working 0/0". It won't even let me close it.

[DrinkOrDie]

UPDATE: I had HWMonitor running. After I closed it, cpu-z opened without the error message. Also, when I tried to reboot, windows couldn't close F@h because it was not responding. Chose to "END NOW", rebooted, and now it's back to "attempting to send results" *SIGH*

Do you still really need to know more from cpu-z? what does this have to do with the h264 codec causing explorer to crash?

[Chewy]

something is causing your system to be instable, the memory and spd ones were my first suspects

your signature just tells me you have a racehorse or a porche, both take careful setup
to be stable

[DrinkOrDie]

Never saw this error before I started using Super. So I wouldn't say the system is unstable in general. Perhaps this is a problem specific to using Super when converting h264 MKV files. After all, it was the h264 codec involved when explorer encountered an error.

F@h is now working on a new unit, and it appears I have credit for another work unit completed. It looks like it is not stuck anymore.

Here's what I will do: I'm going to go ahead and exit F@h, then I'll try to reproduce the error using Super to convert a MKV file. I'll get back to you.

[Chewy]

mkv, h264 conversion is stretching the envelope,
Chuck Yeager beaman gum time

what's your ram and memory voltage?

[DrinkOrDie]

mkv, h264 conversion is stretching the envelope,
Chuck Yeager beaman gum time...

Say what? are you drunk? (I might be) what the hell is a "beaman gum time"? I don't speak Wookie. Let me be clear. I simply converted a MKV file with h264 video to Xvid AVI, using Super. I direct stream copied the AC3 6 channel audio. I resized the video to 1/2 the original size and same frame rate. I used close to the original bitrate. The resulting Xvid avi turned out great. Looks great, plays great, sounds great.

I did reproduce the error. Here's how I did it: I did the same job using Super. When it was done, I left Super open. I opened the folder containing the converted AVI. Then I played it with WMP. That's when the error message popped up. I already sent a screenshot of the error.

Windows explorer closes, taskbar disappears, then everything goes back to normal within a few seconds. Like I said, more of an irritation than a real critical problem. Funny thing is, if I ignore the error popup, everything continues to run fine. Nothing closes until I press the "close button.

[DrinkOrDie]

UPDATE: This error happens every time I open any avi converted by Super. Doesn't matter if Super is open, doesn't matter if F@h is running. I even rebooted and it happened again. If I remember right, this didn't happen at all until I updated ffdshow last night. It figures. Now I remember why I'm so reluctant to update stuff. If it aint broke, don't fix it.

I still don't understand why the h264 codec is listed when the error occurs. I'm playing an Xvid AVI with AC3 audio. not a mkv, not h264.

I've included a screenshot from cpu-z regarding memory. All slots are the same as this screenshot, except for serial number. One thing I don't understand is why the memory is listed at 400Mhz. I was sure it is 800Mhz. AND it IS running in dual-channel configuration according to my bios.

[atifsh]

I don't speak Wookie.

haha i do some... its a typo i guess he wants u to check some timing thingy, maybe the last line is what he wants or wait for the post reply.

[Chewy]

there's no typo peeps

http://www.imdb.com/title/tt0086197/

yeager's ground man always offered him a stick of beaman's before he took off to stretch the envelope and set speed and altitude secords

what's your bios set for memory voltage, seems like I asked that before
at least now cpu-z answered the other question about which memory and solved the riddle of how many sticks of what size


it's probably just a codec problem tho

[Chewy]

Anyways for future reference, when populating all four ram slots with premium higher voltage memory, it's almost a necessity to raise the memory voltage manually in bios to the higher settings like 2.2 volts, having all 4 slots populated seems to draw down the available voltage

Some motherboards won't even boot in this scenario with 4 sticks

Been there and done this in several forums

Just a thought