I'm wondering if it is the PCANDIS5.sys driver because 0xC2 as stated is due to buggy software or faulty drivers.

Again:

The driver cited as the cause of your issues is PCANDIS5.sys file belongs to PCAUSA Rawether for Windows (http://www.rawether.net/) if it's legitimate. There have been known trojans by the same name.

You should be able to see the process in Control Panel > Admin Services > Services. You can stop it from there but it's not a visible service. It's a NDIS (Network Driver Interface Specification) protocol driver.

Again we are back to networking/internet. It may not be your card but this software PCAUSA Rawether.

Never seen it as bad drivers... this is commonly hardware error.

Thanks raybay; much appreciated. Your earlier post to remove the offending card may very well be the correct answer.

rosagio, it could very well be it is your wireless card because updating the drivers aren't working.

They are not expensive to replace. Go to the person who assmled it and ask them how much it will cost you to replace said card. Often you can find it cheaper and it isn't that hard to install.

Hello,

I have changed my wifi card (USB) and the result is still the same

ndis.sys error (blue screen BAD_POOL_CALLER)

see minidump file join

I have decrease the cpu frequency (+3%->-1%)
but I don't understand the problem????????????????????
ANY IDEA?????

Rosagio
motherboard P5Q deluxe

See Post #21 because it is another 0xC2 - and these are caused by faulty drivers or buggy software -- and the same PCANDIS5.SYS driver cited as the cause of your issues.

This is more and more looking like this driver and the software that it belongs to.

hello Route44,
first thanks for your help!!

do you think that i must update my ndis.sys drivers
v6.0 exists???? for Xp sp3???
where can i find it?

and how i be sure that my ndis.sys drivers come from "PCAUSA Rawether"??

@+ Rosagio

First, ndis.sys is a Windows Operating System driver. It is a network layer driver crucial for network interface controllers that access the internet.

PCNDIS5.sys is different in that it belongs to the PCAUSA Rawether software. The issue is with this software, particularly this driver. I would contact PCAUSA Rawether tech support and a) tell them of your issies and b) the minidump error codes and that their driver pcndis5.sys was specifically cited as the cause of your issues.

hello Route44,
if you can help me, you are welcome!

is there a PCAUSA Rawether tech support??

Rosagio

See this link: I am not sure if they will answer your inquiry because their main page does not provide a specific tech support option for trouble shooting. Anyway, I didn't find one; could have missed it.

http://www.pcausa.com/products/ordering.htm