[Home] Bluescreen/Stop Error

I decided to download the newest version of the k-lite codec pack since I had a video file that I couldn't watch on my laptop. I decided to go ahead and download and install in on my desktop(the computer I'm having the problem with) as well. I uninstalled the previous version with no problem. I installed the new version and also had no problems. When I watched a .flv file with media player classic, I noticed there was no sound, so I went into the sound options to adjust some things. Then all of a sudden my computer restarted automatically and I got a message saying something about recovering from a serious error. I went to the event viewer to get more information, but the info and links I was given didn't seem to pertain to my situation directly. One thing mentioned was the error might happen when using diagnostic programs, though it only mentioned things such as regedit. Also, it mentioned it could be related to the sdbot and haxdoor viruses, though I doubt that since I downloaded k-lite from free-codecs.com and my system is clean( I just scanned yesterday). So, is my problem related to media player classic and the k-lite codec pack? I'm using the Full version of the codec pack, FYI.

XP Home/SP2

Did you try System Restore?

Ok, I opened up a .flv file and immediately had my computer reboot. I decided to go to system recovery options and disable my computer from restarting automatically to read what info the stop error gave me if it happened again. I opened a .flv file in media player classic again and went to audio options again and messed with the settings. After hitting "apply", my computer restarted and I got the stop error info. It mentioned something about portcls.sys. From what I know, this is related to audio/video programs in some way, which makes sense since I was using media player classic. I'm not sure if it's the program itself that is causing the problem with the driver or a codec installed with k-lite. I'm going to install the standard edition of the current version, if that doesn't work, I'll try rolling back to a previous version.

Oh, thanks for the reply, Broni, I didn't see it there before I posted again. But, no I haven't tried that yet. I wanted to have an updated codec pack so I would be able to view any new files that are encoded with a codec/updated codec I didn't already have. But I was doing some testing and it seems it happens on my XP machine with any file type I try using media player classic. It doesn't happen on my Vista machine at all.

Check also here: http://support.microsoft.com/kb/950616

Well I restored back to earlier today before I installed the new version of k-lite codec pack. I still had the same problem. So I undid the restoration, uninstalled k-lite first(so as not to get renamed files/folders after another restore) and then restored back to earlier today again. Still the same problem. So after reading the info in your link, I don't know if this was a pre-existing problem before I installed the new k-lite codec pack or if the registry was somehow jacked from the install. When I first uninstalled the new version, the uninstaller said there was an invalid/improper registry key/value. Though, like I said, I don't know if it was a preexisitng probem either. In the past I was able to change audio options such as what speakers are to be used, etc. with no problems. Also, after another stop error, wdmaud.sys was mentioned. So, it would indeed seem my problem is related to audio in some way. The immediate stop error when simply opening a file with media player classic doesn't seem to be happening anymore since I don't have version 3.9 of k-lite installed(only the stop error when changing audio options), so this isn't really that big of a deal anymore. Maybe the fix for this will be included in SP3. Though, I will still wait to install that.

Any errors in Device Manager?
You may try running sfc /scannow

There were no errors in Device Manager. I checked to see if I could mess with audio options again without getting a stop error a couple times before running sfc /scannow and I was able to do it a lot with no stop error, so I didn't bother running it. Weird, to say the least.

You know...computers...ehhh

Hehe, yea :) . Thanks for the quick replies and suggestions, Broni :) .

:)