The kmixer.sys file's has been bothering my friend for quite TEH while.
And when playing more "craving" Call of Duty 2, the blue screen appears more often.
It has something to do with the sound, i believe.
I don't know what though.
He's bought a new soundcard and the problem's still there.
All i'd like to know there's someone out there that knows of a salution. :)?
Thx in advance! ;)
What OS? Also, what exactly is the problem?
Windows XP, and the problem is that every time he plays a game who uses pretty "advanced" audio he gets a bluscreen saying something about kmixer.sys.
=/
Tell your friend to go to BIOS (del at startup) and disable onboard audio. See if that helps any.
Thx, but that's something we've done already... :(
Have you ever managed to take not of what the fatal error code is when Windows generates the screen? Usually each problem that generates error has a code which can tell you what caused it and help lead you toward a solution. If you have the chance, write down the codes so we may be able to help you better. Also, if you don't want to wait to write down the information from the stop error, you can always obtain the information from the dump files Windows creates. To do so, follow these steps:
[list=1][*]Download and install the debugging tools from Microsoft.
[*]Download and run this [URL="http://windowsbbs.com/debugwiz.zip"]utility[/URL].
[*]Select a dump using the tool and 'generate log.'
[*]Open the file c:\debuglog.txt in notepad.[/list]
Your program crash dump is most likely going to be located in C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp. For "blue screens of death" the dump file will be located in C:\MEMORY.DMP
Otherwise, give [URL="http://support.microsoft.com/?kbid=314451"]this[/URL] Microsoft support article a go and see if it solves your friend's issue. This [URL="http://download.microsoft.com/download/c/1/7/c176c59c-6795-458c-bdd2-f969a317c1ea/Windows2000-KB819745-x86-ENU.exe"]executable[/URL] from Microsoft may also solve the issue, if their support article I linked to provides no working solution. Also, have you tried installing the latest soundcard drivers for your hardware or rolling back to the previous version that was installed before the kmixer.sys file began to experience errors?
I have also heard people reseating their RAM and ensuring everything is properly seated in their slots, too. Faulty/unseated RAM has apparently caused errors that mention the kmixer.sys file, although I'm sure that solution may depend greatly on the code given in the stop error. Of course, it might not hurt to ensure that the memory is properly seated and in full working order, though.