2 odd Windows issues

[DarkJedi664]

So I'm currently running XP x64 Edition; and I'm having two really odd issues; and one is x64 specific. First, I have tons of HD movies on my pc, and each one is about 10GB each; however, when I open them with any DirectShow player; it has to access the hard drive first, and can take about 1-5 minutes just to open the video. Now it doesn't always happen, and it doesn't matter the file size; but it happens, and it's REALLY annoying. I'd say out of the 40+ movies I have, about 2/3's of them have this problem. The average time to open the video is about 1 minute; but some have taken about 5 minutes to load; and some open instantly. I know it's not codec related because my h264 videos have the same issue as my MPEG-2 ones. I don't know what causes it, and I don't know how to fix it. This issue happens on both x64 and 32bit XP. I don't recall this issue on Vista (though I can't use that yet because of my 8800).

My second issue is directly related to x64, and I'm not sure that anyone has had this problem. I've noticed recently, that if I try to access ANY file over 1GB in size; my memory usage gets ballooned up to 98%. At first I thought it was because of my HD movies or something like that; but I noticed when installing FEAR, it happened too! (since the main Arch00 file is about 3GB in size) Now once I'm done accessing the file, memory shoots back down to about 20%, but Windows still acts a bit slow for a bit. At first I thought this was related to Server 2003 (as that was the OS I first found this issue on); but I just installed XP x64, and found out the issue still happens. It's only x64 related because it doesn't happen to me on 32bit XP. I think it might have something to do with the fact that I'm running 2GBs; but again, I don't know the cause, and I don't know how to fix it. THIS is my biggest problem right now. I'm using my G15 to see the memory usage. Any help would be appreciated. Thanks.

[retsam]

So I'm currently running XP x64 Edition; and I'm having two really odd issues; and one is x64 specific. First, I have tons of HD movies on my pc, and each one is about 10GB each; however, when I open them with any DirectShow player; it has to access the hard drive first, and can take about 1-5 minutes just to open the video. Now it doesn't always happen, and it doesn't matter the file size; but it happens, and it's REALLY annoying. I'd say out of the 40+ movies I have, about 2/3's of them have this problem. The average time to open the video is about 1 minute; but some have taken about 5 minutes to load; and some open instantly. I know it's not codec related because my h264 videos have the same issue as my MPEG-2 ones. I don't know what causes it, and I don't know how to fix it. This issue happens on both x64 and 32bit XP. I don't recall this issue on Vista (though I can't use that yet because of my 8800).have you tried to open them up with another player... ie vlc?




My second issue is directly related to x64, and I'm not sure that anyone has had this problem. I've noticed recently, that if I try to access ANY file over 1GB in size; my memory usage gets ballooned up to 98%. At first I thought it was because of my HD movies or something like that; but I noticed when installing FEAR, it happened too! (since the main Arch00 file is about 3GB in size) Now once I'm done accessing the file, memory shoots back down to about 20%, but Windows still acts a bit slow for a bit. At first I thought this was related to Server 2003 (as that was the OS I first found this issue on); but I just installed XP x64, and found out the issue still happens. It's only x64 related because it doesn't happen to me on 32bit XP. I think it might have something to do with the fact that I'm running 2GBs; but again, I don't know the cause, and I don't know how to fix it. THIS is my biggest problem right now. I'm using my G15 to see the memory usage. Any help would be appreciated. Thanks. whe it does this you need to start up task manager and watch what process is causing this behavor of high cpu....without that info we cant really say what the issue might be.

[DarkJedi664]

Ok, I have used VLC, and it opens perfect and instantly with EVERY file I've used; but I think it's because VLC is not a DirectShow player. I've tried WMP, MPC, and Zoom Player. All of those are DirectShow players. I don't really like VLC because it doesn't let me choose different decoders.

What's really odd about the second issue is; it's doesn't use any CPU; and the process doesn't use insane amounts of memory; it's just the physical memory is being eaten up; and I have no idea why. And what's odd is; the eaten memory doesn't happen right away; it's just grows as the file is being accessed.

[retsam]

--------------------------------------------------------------------------------

Ok, I have used VLC, and it opens perfect and instantly with EVERY file I've used; but I think it's because VLC is not a DirectShow player. I've tried WMP, MPC, and Zoom Player. All of those are DirectShow players. I don't really like VLC because it doesn't let me choose different decoders.
i dont get it why do you need to use direct show if VLC does what you need it todo?



What's really odd about the second issue is; it's doesn't use any CPU; and the process doesn't use insane amounts of memory; it's just the physical memory is being eaten up; and I have no idea why.oh im sorry i thought you said cpu...but if its memory, sounds like a memory leak from a process. do what i stated up there and look at the memory usuage, you might need to watch this for a little while..

[DarkJedi664]

I don't like VLC because I can't use PureVideo with it; and thus I lose Hardware Acceleration of my 8800.

I just loaded an HD movie now, and just watching the first few minutes of it; BAM happened again. I looked at the MPC process, and it didn't move a single bit in terms of mem usage. No process at all moved in mem usage. Before I closed it, it was using 57% RAM, when I did close it; it dropped down to 44%. And this was just after watching for about 2 minutes. My friend with 2GB and XP x64 had a similar issue when playing FEAR (as my bug occurs when playing FEAR because of the file size); but it didn't get to 98% like on mine.