BSOD (when plugging in eathernet cable)

Status
Not open for further replies.

smarty18

Posts: 9   +0
Hi All

I Am after some help.
My computer has been working fine using a wireless card, but i recently moved and have an ongoing problem with broadband speed, so The tech guys at Bt asked me to plug it directly into the router via eathernet.

Problem occured as soon as i plugged it in, i got an instant BSOD error message

IRQL_NOT_LESS_0R_EQUAL stop 0x0000000A (0xBBBBBBBB,0X0000001C,0X00000000,0X804FABE8)

I followed thw advice and tried rebotting leaving eathernet plugged in, but i got another BSOD while booting
DRIVER_IRQL_NOT_LESS_OR_EQUAL stop 0x000000D1 (0XBBBBBBBF,0X00000002,0X00000000,0XB7D9A50A)

I have tried disconnecting my wireless pci card and then connecting eathernet but still does the same, I have updated my bios and my LAN Controller driver but still the same, if i disable my Lan controller in device manager i do not get the screen? but obviously i cant use LAN?

I do not know what else to try. PLEASE HELP

Thanks for your time.
 
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
Hi Broni

I have done as you sugested, here are the results,.


Dump File : Mini021710-01.dmp
Crash Time : 2/17/2010 5:49:00 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xbbbbbbbf
Parameter 2 : 0x00000000
Parameter 3 : 0x805b9507
Parameter 4 : 0x00000002
Caused By Driver : hal.dll
Caused By Address : hal.dll+2d43
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021710-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021610-02.dmp
Crash Time : 2/16/2010 7:17:12 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xbbbbbbbb
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x806e6a2a
Caused By Driver : hal.dll
Caused By Address : hal.dll+2a2a
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021610-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021610-01.dmp
Crash Time : 2/16/2010 6:15:31 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xbbbbbbb7
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x80502367
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021610-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

None of that means anything to me. lol
Thanks for your help.
 
Thanks for help mate, Did not get anywhere though.

So thought i would do a fresh install of windows xp, only to find when i tried to boot from cd i get a pci.sys error... ARGHHHH

So i installed a copy of vista instead, installed ok but will not reconise my network, just get "unudentified network" so can only get local connection...

What a disaster, all because of slow download speed......
 
Did you install all drivers, starting with chipset driver?
Any errors in Device Manager?
 
Yes i have installed all drivers, No errors showing in device manager. Wireless works fine but just unidentified network on LAN... Limited connection. There is alot of info about setting up manual ip address for vista as i believe this is a commen problem. But i just cant get my head around it all....
 
Yes, my laptop is running xp and connects wirelessly, It works fine if i plug it into the ethernet cable though...
 
Sorry that was not very clear.
My laptop connects to router/modem with both ethernet and wireless fine, And everything working ok.

My desktop connetcs fine using wireless, but when connecting with ethernet comes up as a unidentified network (limited connectivity)
 
You may have a look at the network settings as well; sometimes its the little things which get ignored; if that doesn't work then Broni's advice is next logical step.
 
Finally managed to get win xp back on there with a stremlined sp3 disc, But still got the same problem with Eathernet so ordered a new pci card today. Hope that solves the problem.

Thanks all for your advice..
 
Ok
Eathrnet pci card installed, all seemed to we working ok untill late yesterday evening when i got BSOD again, This just seem to happen randomly as everything seemed to working fine.
Error codes

Dump File : Mini022410-01.dmp
Crash Time : 24/02/2010 01:34:30
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xfffffffc
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xba61dbfa
Caused By Driver : NDIS.sys
Caused By Address : NDIS.sys+15bfa
File Description : NDIS 5.1 wrapper driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-0852)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini022410-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini022310-02.dmp
Crash Time : 23/02/2010 23:31:07
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xfffffffc
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xba61dbfa
Caused By Driver : NDIS.sys
Caused By Address : NDIS.sys+15bfa
File Description : NDIS 5.1 wrapper driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-0852)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini022310-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini022310-01.dmp
Crash Time : 23/02/2010 19:29:09
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xfffffffc
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xba61dbfa
Caused By Driver : NDIS.sys
Caused By Address : NDIS.sys+15bfa
File Description : NDIS 5.1 wrapper driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-0852)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini022310-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

Beginning to think maybe i should just stick to wireless, My comp was fine all weekend without ethernet pci card...

AARGGHHHHHHHHHHHHHHHHHHH:mad:
 
I'm assuming you also installed the Ethernet card's correct drivers. However, in one of your earlier post's you said that you get PCI.Sys error while installing XP; I am just wondering perhaps something to do with your slot itself; try changing Ethernet card's slot and see what happens (before you do that uninstall any drivers you installed with it; then reinstall them after changing slot)
 
Yes i installed all drivers that came with card, I will try swapping my cards over, i will put the wireless pci card into to slot now occurpied by the ethernet card and visa versa.
Although i dont think if this would explain why i had the problem at the beginning, because at the start i only used one of the pci slots, the ethernet port that caused the problem initially was direct on the motherboard..

I will try anyway..

Thanks
 
Status
Not open for further replies.
Back