Originally Posted by jephree

2 weeks ago Microsoft issued about 10 "critical" updates for XP including an IE cumulative fix.

hmm... just wondering if that might have some bearing? I, personaly, have all updates & no problems. Perhaps just a curious coincidence.

Not really. I have automatic updates turned off. I have made no changes to the system whatsoever. This system has been running streaming media flawlessly for the last 8 months with no changes being made then suddenly *poof*. Also, keep in mind this is NOT just affecting IE. It is affecting other internet browsers as well with exactly the same result.

I sincerely think this is the work of some poorly written malware or adware code. I run Microsoft's new adware checking software; it has found nothing. Neither has ad-aware or spybot

Searching your exact error only brings up your own post

Streaming video crashing IE (WMV)



Please let us know if you get a response there.

Maybe post a hijack this log in our Spyware, Adware, Viruses and HijackThis Logs section.

OK, had the exact same error. Here is what I did to fix it.

1. Tools -> Options for WMP. Check Connect to Internet (overrides other settings) on the Player Tab

2. Tools -> Options for WMP. Configure proxy for HTTP for to none.

Hope this helps.

Originally Posted by trickeyone

OK, had the exact same error. Here is what I did to fix it.

1. Tools -> Options for WMP. Check Connect to Internet (overrides other settings) on the Player Tab

2. Tools -> Options for WMP. Configure proxy for HTTP for to none.

Hope this helps.

Thanks for the tip trickeyone

Actually the first step does not appear to be neccessary. I would just try configuring proxy to none for http:.

Thanks for the info tricky, I set my HTTP to none like you said.

However, that's not why I'm here. I got my problem to clear up another way. I had manually set my virtual memory to a fixed size (2000kb). It's been that way for a loooong time. But recently I was testing response times if I moved the virtual memory to another drive. I ran it like that for awhile, no apparent problems. But something must have gotten mixed up with XP and everytime my browser crashed (that I could get a error code) it was always a bad memory address. Knowing that streaming video likes to instantly start writing to virtual memory, I figured this was the key. The only way I could reset everything was to turn automatic vir. mem. handling back on.

This did the trick.