amd 64 on win xp sp2 won't play my video files

[codrinutz]

Hi,

I don't know how to stat or even is this place to put this question.

I have a strange problem with my PC. Recently I bought AMD 64 for my PC, I can't play my video files, it keeps crushing, blocking when I trie to open the file. I use the same setting for the codecs and the player and I guest that's not the problem, same is the driver.

I have to say that in win XP 64 I have no problem with the video files, but I have to use the 32 edition because I don't have drivers for my capture card and my printer.

Please tell me witch is the proper solution for my problem. Is this problem a commune one or I have it just me because I did something wrong ?!!!

Thanks!!

[scorps]

Dont know if it would help but there are drivers on the AMD website for their processors in Win xp. I also have AMD 64 but have not had the problem you have.

[Dv8ted2]

It could be a corrupted file.

I have an athlon 64 running XP Pro SP2 and do not have your problems. I am able to watch videos all the time.

[codrinutz]

Okay !

I donn't know if this hellp, but my athlon 64 in on 939 soket. I have worked with other amd proc 64 but on soket 754 and they have done just fine. This problem is beyond my knolege

[Dv8ted2]

Are you taking a 754 pin processor and putting it into a 939 socket? If so, it will not work.

Does this happen for every file or just that one.

If it is just that one, then you have a corrupted file.

If it is more, then look for updated drivers for your video card.

[ROF]

Since you are dual booting does your 32 bit windows have the proper codecs installed under this OS for the video in question?

[codrinutz]

I am able to put the right proc on the corespundind socket !! Thanks a lot DV8ted2

The settings (codecs, drivers) that I made are the same that I was using before brought this processor, with my Pentium 4 proc and MB. I was saying about all kind of video files: avi, mpeg, wmv etc any kind of container or video stream.

Please ask other questions maybe we can figure toghether !!

[Morse2]

Hi Codrinutz;

After a careful re-reading of your post and realizing that your problems manifest themselves upon the first entry to a file rather than after playing it for a while, I want to put a preface on this - have you taken care of the shmedia.dll issue? That driver is notorious for causing system locks when right clicking on a file. Large AVI files have information at the tail end of the file and the antique shmedia.dll driver has issues with any file larger than a CD. The best quick fix for that is to download shellexview which is a freeware program that will let you look at all the shell extension handlers for different file types - then disable anything with the shmedia.dll as an experiment. This is easier to fix and better than the registry hack I was about to post, since you can just "re-enable" something if you need to without risking your registry. ShellExView is a little tough to find, so here's the link: http://www.nirsoft.net/utils/shexview.html

There was also a recent automatic update of Windows that "broke" many systems using HP peripherals, Kerio firewall, etc. so that they crashed upon first opening a window or file. I can't recall the number on it offhand, but I had to fix it on a couple of systems and now leave autoupdate "off" on all systems (only patch once I know the patch won't cause more probs than it fixes).

Now, onto my original post which may be 100% off-target. If so I apologize.
************************************************** *****************************
Just a knee-jerk guess, but could the extra load you're placing on the system be an issue?

IME problems with system stability are often the result of memory issues or PS issues, so I would start there. BIOS issues, and MB driver issues are possible but don't result in the sort of instability you're describing nearly as often as memory/PS problems (again, that's just my experiences for whatever they're worth). There's also an outside chance that you've got an overheating problem somewhere (not necessarily the processor - I've had northbridges where the heatsink was jarred loose and they worked fine - until they got hot....then BSOD city).

Now, you mention that you switched from a P4 to an AMD64. That means new MB, new memory modules for sure - maybe even a new PS. That makes me doubly suspicious of some sort of hardware issue.

So, first download the following freeware: memtest86 prime95 speedfan and Everest. In case you've not used them, the first tests memory modules, the second is an overall system stability test, the third will show temperature and CPU utilization in realtime and the fourth is a general system information utility.

If you can run memtest86 for 12-24 hours without one single memory corruption/error being flagged, we can scratch the memory modules and BIOS timings from the list of culprits. Next, run prime95 and speedfan simultaneously - watch for signs of instability (prime95 will shut down the test the first time you hit an error) and overheating (you can set speedfan to graph temps in real time). If all your system temps are okay and there is no sign of instability after 12-24 hours of monitored testing (do NOT set a system for a stress test and then leave - overheating can cause lots of damage if you do not catch it in time), then we can probably scratch the PS and cooling as possible sources of error.

There is also an outside chance your video card is overheating - this may or may not be caught by speedfan depending on whether or not your card has a temp sensor. Usually video card overheating manifests itself as a corrupted display rather than a reboot, though I have seen systems lock up because of that. 3dmark5 is the usual video card benchmark/stress test tool, but I would save it 'til after you've eliminated memory, PS, and system cooling from the list of potential problems.

If you do all that and have still not found the issue, then and only then should you start batting your head against the wall of "which codec is wrong" or "which dll may be corrupt".

************************************************** *****************************
Even if it is just the old shmedia.dll problem or that cursed xp sp2 patch, doing a proper eval on a new system is still for the best. I've had media files corrupted by memory issues that were subtle and not easily caught - best to find out when you can still easily RMA new components that prove problematic.

Just a start, but I hope this is useful.
All the best,
Morse