Stop Error Screen (STOP: 0x00000008E ...) why?

8 of your 11 minidumps are crashing at redbook.sys, and klif.sys. These are the drivers for Redbook Audio Filter Driver, and Kaspersky Labs antivirus.

check for updates sound drivers.

Try checking with the Kaspersky website for any updates/patches.

If that doesn`t work, then uninstall Kaspersky, and try the AVG free antivirus, and the free Sygate firewall.

Regards Howard

hm...

howard_hopkinso said:

check for updates sound drivers.

Try checking with the Kaspersky website for any updates/patches.

If that doesn`t work, then uninstall Kaspersky, and try the AVG free antivirus, and the free Sygate firewall.

Click to expand...

Hm... I'm updating Kaspersky every day, it can't be old.
And I updated sound card today... Now I'm updating motherboard...
So, if this doesn't work, I should "uninstall Kaspersky, and try the AVG free antivirus, and the free Sygate firewall" ?... But why?.. Is the problem in Kaspersky and firewall (windows sp2 firewall) ?

Thanks for care
`ToX`

It is possible that there is a conflict between the drivers I mentioned.

That`s why I suggested uninstalling Kaspersky, and using a different security product.

Regards Howard

Ok

Hm... But earlier everything was Ok... but Maybe... Ok, Thanks, I'll try tomorow and I will write results there

_________
Thank you!
`ToX`

huh?

Look, I have two Kaspersky Labs products - Kaspersky antvirus and Kaspersky Anti-hacker, so I should delete all of them?

__________
`ToX`

Yes you should uninstall both programmes.

Just remember to disconnect from the internet, before you start the uninstall, and don`t reconnect to the internet untill you have installed other security software.

Regards Howard

;\\

nooo.... that doesn't work ... I deleted all Kaspersky products, but Stop Error Screen is appearing.... ;\
hmmmm..?

______
`ToX`

Post your latest minidumps.

Regards Howard

Minidumps

Ok.
But now Kaspersky products are installed, because, when I see, that Kaspersky is not that guilty , I installed it. again.

One of your minidumps crashes at redbook.sys, and klif.sys. Same as before.

The other dump is corrupted. Possible ram problem.

Regards Howard

will check

Ok, I'll check it..

______
`ToX`

I get stop errors like this one when I overclock my PC too much - or to be more precise, if the memory speed is too high. I solved the errors by reducing memory speed from BIOS settings.

I solved the same error problem

Well, I had the same problem on one of my clients's PCs, actually I had more errors. and as a matter of fact I've learnt a lot dealing with that PC

The case of the PC was:
- 0x8E error + other BSOD (0x50) (0x4E) (0x7E) and more, which I managed to solve them all. But the only one remain non solved untill yesterday was the (0x8E)

Microsoft site said that the problem is fixed with SP3 (I don't trust Microsoft that much, but I installed SP3 anyway, and as I expected no change, same errors)

But, I've learnt that Number ONE to deal with errors on Windows XP is to run the (verifier.exe) tool which is a part of windows XP. then check which driver is unsigned.

in my case I had:
1- Klif.sys
2- Unknown Device.
3- UNKNOWN (It is writen that way.)
So, started to deal with these unsigned drivers by disabling or uninstaling, hoping things will be better.

1 - Klif.sys (which belongs to my number one trusted antivirus "Kaspersky")
I found that this a problem with kaspersky (while they mentioned that it is not their problem) I cannot judge because I never faced the problem with any of my working PCs or my clients' PCs which have KAV. (Well, I uninstalled it)

2- Unknown device (Which is the built in sound, and I disabled it and added a sound card instead).

Note: All BSOD errors are fixed that moment except the ugly (0x8E).

3- Unknown (and this killed my brain to know what is it UNKNOWN!!!!!!!!!!!!!)

Note: The Microsoft site is better than microsoft products "I mean the tech net" (may be that microsoft has huge amount of errors which they already know so they prepared a good documentation as a support. Anyway, always refer to microsoft KB. The funny thing is that you have to read all the related pages for a certain error, because they will suggest different solutions for each "same" error. :suspiciou So you have to be smart and make your brain work hard to get the right solution from the bulk of solutions they present. and my advice is, don't always run behind their word of "Faulty RAM", that is not always true. you don't believe me check the cause microsoft suggested at (I couldn't post the link, it is my first post, but u can serach for it on microsoft anyway) I guess this is a way they want to hide behind that the problem doesn't belong to them, and they are the best (I wonder what all these service packs are for )

Of course I checked the PC RAM with 3 different applications and I had no problem with them. But it always stick to my mind the word "Device Driver" which erritates me. the manufacturers always update their drivers and they always add fixes to them. I did all the updates, but the problem remain. and the ugly UNKNOWN remains too.

and for a sudden flashed to my mind a program I installed on the PC (The PowerISO) this program act as a device and it installs drivers to the system So I removed it. That time I didn't have the error any more. NO MORE 0x8E

And, I didn't have the UNKNOWN anymore

The client needs a virtual CD program, so I installed the "Daemon Tool" and the System fall again with the 0x8E BSOD :evil:

I uninstalled it and decided no more Virtual CD tools for this PC.

To Conclude it >>>

So always:
=========
- Check your unsigned drivers with verifier.exe

- Disable the unsigned drivers or uninstall them until your problem fixed.

- Always check the Microsoft site for documentations related to your error (read them all, not only one of them, again all that related to your problem, don't take their word as trusted because that would cost you money while you don't have to).

- Remove any virtual devices if you have UNKNOWN.

That is it, I hope that might help.