- last post: 01.01.0001 12:00 AM PDT
@lamwhie
First of all, simple minded "friend". If you happened to take the time to read the articles in this forum you would know that i am not the only one.
However since there is no search option here it is not that easy to find.
And since you never heard of this, it does not exist ?
Have you ever heard of google, or are you anti google too ?
Try google and type this in the search field :
"vorbis.dll halo exception"
And what do you know, it shows results...
And how is it that i never had this problem before untill after patch 1.07
You are just the usual loud mouth person who thinks he understand something without ever
working with the innerside of an os. How often are you on the microsoft tech site ?
How often do you keep track of bugs, flaws and solutions. The only thing you know is automatic updates. Does kernel mean anything to you ?
Anyway, i read a lot of forums and someone mentioned this possibility that there was a flaw in the way halo handles sounddata. Since i can neither confirm or deny this i asked this question here on this forum to see what comes up.
@Mr Ma5B
Thank you, for your comment.
I had before an soundblaster live 1024 from creative and now i have an audigy 2 OEM of
creative. The OEM is just an audigy 2 without IEEE1394 connector and THX certification .
This vorbis.dll exception that i am getting happened with both soundcards.
I guess it will never be solved since i have the latest drivers for everything. To be honest i tried different driver version (older, newer) for all my hardware, basic windows without personal modifications. It makes no sense at all. I left my hardware original at fsb 333. No difference. I ran memtest for days, cpu test. My system never shows any instability. I guess i will have to do some more searching.