Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Driver IRQL xcpip.sys BSOD


  • Please log in to reply

#1
HDL

HDL

    Member

  • Member
  • PipPip
  • 24 posts
I'm using a Packard Bell iStart 2369 with Windows XP. I don't use wireless.

When I try to connect to the internet it will frequently refuse to authenticate my username/password giving me "Error 721: The remote computer is not responding." When I receive phonecalls it will disconnect me from the internet. (This is relatively new).

The largest problem is that I seem to have a 1 in 2 chance of my entire computer crashing the moment it does connect to the internet. On the blue screen when it crashes I get the "driver irql not less or equal" message. Sometimes it will also point to xcpip.sys but usually that's blank.

I have not installed any new hardware, save for 1GB of RAM which was purchased and installed after I started to have frequent crashes (I removed the old memory). The new memory appears to have fixed another crashing issue I was experiencing when I was getting blue screens when booting up. It's not helped with the internet issues at all though.

Please can someone help.

Edited to add: I found WhoCrashed from reading the other threads. I'm not sure if it's relevant or not in my case but I ran it anyway and have posted what it told me below.

On Wed 18/07/2012 08:27:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071812-06.dmp
This was probably caused by the following module: alcan5wn.sys (alcan5wn+0x8A17)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\alcan5wn.sys
product: SpeedTouch USB
company: THOMSON
description: WAN Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alcan5wn.sys (WAN Driver, THOMSON).
Google query: alcan5wn.sys THOMSON CUSTOM_ERROR




On Wed 18/07/2012 08:23:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071812-05.dmp
This was probably caused by the following module: xcpip.sys (xcpip+0x1555)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x0, 0xFFFFFFFFED9FD555)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\xcpip.sys
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on xcpip.sys


A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: xcpip.sys .
Google query: xcpip.sys CUSTOM_ERROR




On Wed 18/07/2012 06:58:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071812-04.dmp
This was probably caused by the following module: alcan5wn.sys (alcan5wn+0x8A17)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\alcan5wn.sys
product: SpeedTouch USB
company: THOMSON
description: WAN Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alcan5wn.sys (WAN Driver, THOMSON).
Google query: alcan5wn.sys THOMSON CUSTOM_ERROR




On Wed 18/07/2012 06:53:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071812-03.dmp
This was probably caused by the following module: xcpip.sys (xcpip+0x1555)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x0, 0xFFFFFFFFEDD5B555)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\xcpip.sys
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on xcpip.sys


A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: xcpip.sys .
Google query: xcpip.sys CUSTOM_ERROR




On Wed 18/07/2012 06:31:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071812-02.dmp
This was probably caused by the following module: xcpip.sys (xcpip+0x1555)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x0, 0xFFFFFFFFED9F3555)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\xcpip.sys
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on xcpip.sys


A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: xcpip.sys .
Google query: xcpip.sys CUSTOM_ERROR




On Wed 18/07/2012 04:02:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071812-01.dmp
This was probably caused by the following module: alcan5wn.sys (alcan5wn+0x8A17)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\alcan5wn.sys
product: SpeedTouch USB
company: THOMSON
description: WAN Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alcan5wn.sys (WAN Driver, THOMSON).
Google query: alcan5wn.sys THOMSON CUSTOM_ERROR




On Sat 14/07/2012 10:40:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071412-01.dmp
This was probably caused by the following module: xcpip.sys (xcpip+0x1555)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x0, 0xFFFFFFFFEE0F5555)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\xcpip.sys
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on xcpip.sys


A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: xcpip.sys .
Google query: xcpip.sys CUSTOM_ERROR




On Fri 13/07/2012 19:35:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071312-01.dmp
This was probably caused by the following module: xcpip.sys (xcpip+0x1555)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x0, 0xFFFFFFFFEE2E6555)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\xcpip.sys
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on xcpip.sys


A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: xcpip.sys .
Google query: xcpip.sys CUSTOM_ERROR




On Wed 11/07/2012 09:06:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071112-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7AAE2)
Bugcheck code: 0x100000C5 (0x0, 0x2, 0x1, 0xFFFFFFFF80551AE2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 10/07/2012 14:16:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071012-01.dmp
This was probably caused by the following module: avgidsdriver.sys (AVGIDSDriver+0x947C)
Bugcheck code: 0x100000C5 (0x0, 0x2, 0x1, 0xFFFFFFFF805519E9)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\avgidsdriver.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgidsdriver.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o. ).
Google query: avgidsdriver.sys AVG Technologies CZ, s.r.o. CUSTOM_ERROR




On Wed 04/07/2012 12:32:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070412-02.dmp
This was probably caused by the following module: alcan5wn.sys (alcan5wn+0x8A17)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\alcan5wn.sys
product: SpeedTouch USB
company: THOMSON
description: WAN Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alcan5wn.sys (WAN Driver, THOMSON).
Google query: alcan5wn.sys THOMSON CUSTOM_ERROR




On Wed 04/07/2012 12:23:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070412-01.dmp
This was probably caused by the following module: alcan5wn.sys (alcan5wn+0x8A17)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\alcan5wn.sys
product: SpeedTouch USB
company: THOMSON
description: WAN Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alcan5wn.sys (WAN Driver, THOMSON).
Google query: alcan5wn.sys THOMSON CUSTOM_ERROR




On Tue 03/07/2012 19:00:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070312-02.dmp
This was probably caused by the following module: alcan5wn.sys (alcan5wn+0x8A17)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\alcan5wn.sys
product: SpeedTouch USB
company: THOMSON
description: WAN Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: alcan5wn.sys (WAN Driver, THOMSON).
Google query: alcan5wn.sys THOMSON CUSTOM_ERROR




On Tue 03/07/2012 18:44:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070312-01.dmp
This was probably caused by the following module: xcpip.sys (xcpip+0x1555)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x0, 0xFFFFFFFFEF93A555)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\xcpip.sys
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on xcpip.sys


A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: xcpip.sys .
Google query: xcpip.sys CUSTOM_ERROR




On Wed 20/06/2012 04:07:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini062012-09.dmp
This was probably caused by the following module: pxhelp20.sys (PxHelp20+0x11C4)
Bugcheck code: 0x1000000A (0xFFFFFFFF805D5107, 0x2, 0x0, 0xFFFFFFFF805D5107)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\pxhelp20.sys
product: PxHelp20
company: Sonic Solutions
description: Px Engine Device Driver for Windows 2000/XP
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: pxhelp20.sys (Px Engine Device Driver for Windows 2000/XP, Sonic Solutions).
Google query: pxhelp20.sys Sonic Solutions CUSTOM_ERROR

Edited by HDL, 18 July 2012 - 10:23 AM.

  • 0

Advertisements


#2
Ztruker

Ztruker

    Member 5k

  • Technician
  • 7,065 posts
Info: What is the "alcan5wn.sys" ?

For xpcip.sys, a lot of hits from a Google search indicate this can be caused by malware. Please go to the Virus, Spyware, Malware Removal forum, read the first post and follow instructions.

Come back here once you get a clean bill of health if you still have problems.
  • 0

#3
HDL

HDL

    Member

  • Topic Starter
  • Member
  • PipPip
  • 24 posts
Thanks very much. I'll get onto doing that.
  • 0

#4
HDL

HDL

    Member

  • Topic Starter
  • Member
  • PipPip
  • 24 posts
Thanks. It was definitely malware. My computer's stopped crashing now the malware's cleared up. This can be marked as closed or whatever. Thanks for pointing me at the right forum.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP