locked
Win XP's Driver_IRQL BSoD problem RRS feed

  • Question

  • Hi,

    Today all of a sudden three (out of 7 computers) running Windows XP Pro SP3 got the Blue Screen of Death (BSoD), the timing is not at once all three of them, but more like an hour interval one after another got it. It reads as following:

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    Technical information:

    net5213xp.sys - Address F6E70FC8 base at F6E06000

    net5213xp.sys - Address F6E1C8F0 base at F6E06000

    I suspect it has something to do with the WiFi network card? Because those computers are not connected to the server via LAN, but via WiFi. The BSoD only happened once this day, but I'm affraid it'll happen again if I don't sort the problem out.

    Anyone know how to fix this?

    Thanks!


    Dhow here.

    Thursday, February 27, 2014 10:27 AM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask

    Wanikiya and Dyami--Team Zigzag

    Thursday, February 27, 2014 1:35 PM
  • Hi Wanikiya and Dyami - Team Zigzag,

    I'm sorry for the late reply, I've been very busy and the reply notification of this thread was sent to my email's spam box.

    I'm going to try your method, but since the BSoD incident happened a week ago, is your method still works?

    Thanks for your help.


    Dhow here.


    • Edited by Dhow Sunday, March 9, 2014 9:50 AM
    Sunday, March 9, 2014 9:46 AM
  • DR

    The files are still there so yes it still works


    Wanikiya and Dyami--Team Zigzag

    Sunday, March 9, 2014 3:55 PM
  • Wanikiya and Dyami,

    Here's the link for those files you asked, hopefully they're right, if not then please let me know.

    Thanks, I'll be waiting for your reply.


    Dhow here.

    Wednesday, March 12, 2014 5:35 AM
  • Dhow

    These were related to your 2005 net5213xp.sys. Product: NDIS Driver for WinXP. Company:3Com Corporation.  I would install the newest driver available.  If you cant find a newer driver re-install the current driver in compatibility mode

    
    
    
    Debug session time: Thu Feb 27 00:45:02.793 2014 (UTC - 4:00)
    System Uptime: 0 days 3:49:50.859
    
    Loading User Symbols
    Loading unloaded module list
    ...................
    Unable to load image net5213xp.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for net5213xp.sys
    *** ERROR: Module load completed but symbols could not be loaded for net5213xp.sys
    
    Probably caused by : net5213xp.sys ( net5213xp+168f0 )
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: f7b70fc8, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: f7b1c8f0, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 80553d68
    GetPointerFromAddress: unable to read from 80553d60
    GetUlongFromAddress: unable to read from 80558970
     f7b70fc8 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    net5213xp+168f0
    f7b1c8f0 8b56f3          mov     edx,dword ptr [esi-0Dh]
    
    CUSTOMER_CRASH_COUNT:  2
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  Idle
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 00000000 to f7b1c8f0
    
    STACK_TEXT:  
    805499dc 00000000 81bec180 81c92400 81bec188 net5213xp+0x168f0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    net5213xp+168f0
    f7b1c8f0 8b56f3          mov     edx,dword ptr [esi-0Dh]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  net5213xp+168f0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: net5213xp
    
    IMAGE_NAME:  net5213xp.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  42ae8c42
    
    FAILURE_BUCKET_ID:  0xD1_net5213xp+168f0
    
    BUCKET_ID:  0xD1_net5213xp+168f0
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xd1_net5213xp+168f0
    
    FAILURE_ID_HASH:  {9b652040-2a5f-b459-56bd-08779ca2cf5d}
    
    Followup: MachineOwner
    ---------
    
    



    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by ZigZag3143x Monday, June 16, 2014 3:56 PM
    Wednesday, March 12, 2014 5:48 AM
  • Dhow

    These were related to your 2005 net5213xp.sys. Product: NDIS Driver for WinXP. Company:3Com Corporation.  I would install the newest driver available.  If you cant find a newer driver re-install the current driver in compatibility mode


    Wanikiya and Dyami--Team Zigzag

    I don't think there's a newer driver available since it's a quite old WiFi card, infact the 3COM company is no longer exist after they were bought by HP.

    How do you mean by re-install the current driver in compatibility mode?


    Dhow here.

    Wednesday, March 12, 2014 8:17 AM
  • Hi,

    What is your computer model, and what is the VID & PID for the WLAN card?


    With compliments Alexander Solaat Rødland SURFACE 2 Pro 256gb

    Wednesday, March 12, 2014 8:25 AM
  • Hi,

    What is your computer model, and what is the VID & PID for the WLAN card?


    With compliments Alexander Solaat Rødland SURFACE 2 Pro 256gb

    Alexander,

    I build the computer from different parts, I didn't buy a certain build-up branded computers. What those parts are can be seen from the Speccy snapshot at the link I've made available above.

    What are the VID and PID of my WLAN card?


    Dhow here.

    Wednesday, March 12, 2014 11:17 AM
  • Hi Dhow,

    Thanks for the speccy!

    Edit; some devices is shown as VEN and DEV, some as VID and PID.
    Sorry for that.

    To find the info, simply follow these steps;

    1. Open the device manager
    2. Right click the WLAN card and select "Properties"
    3. Select the "Details" tab
    4. In the drop down menu, select "Hardware-ID"
    5. The ID should be provided in a string matching something like "PCI\VEN_14E4&DEV_4359...."


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Wednesday, March 12, 2014 11:53 AM
  • Hi Dhow,

    Thanks for the speccy!

    Edit; some devices is shown as VEN and DEV, some as VID and PID.
    Sorry for that.

    To find the info, simply follow these steps;

    1. Open the device manager
    2. Right click the WLAN card and select "Properties"
    3. Select the "Details" tab
    4. In the drop down menu, select "Hardware-ID"
    5. The ID should be provided in a string matching something like "PCI\VEN_14E4&DEV_4359...."


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Here's the information you asked:

    "PCI\VEN_168C&DEV_001B&SUBSYS_6803A727&REV_01\4&BC67B8D&0&00F0"

    May I ask what is it for?


    Dhow here.

    Wednesday, March 12, 2014 2:59 PM
  • Dhow

    These were related to your 2005 net5213xp.sys. Product: NDIS Driver for WinXP. Company:3Com Corporation.  I would install the newest driver available.  If you cant find a newer driver re-install the current driver in compatibility mode


    Wanikiya and Dyami--Team Zigzag

    I don't think there's a newer driver available since it's a quite old WiFi card, infact the 3COM company is no longer exist after they were bought by HP.

    How do you mean by re-install the current driver in compatibility mode?


    Dhow here.

    If that is the newest driver you may be able to get it to work by installing it in "compatibility mode"

    To Run in compatibility mode do the following:

    Right click the installer>properties>compatibility>choose OS

    http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1


    Wanikiya and Dyami--Team Zigzag

    Wednesday, March 12, 2014 4:34 PM
  • If that is the newest driver you may be able to get it to work by installing it in "compatibility mode"

    To Run in compatibility mode do the following:

    Right click the installer>properties>compatibility>choose OS

    http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1


    Wanikiya and Dyami--Team Zigzag

    Wanikiya and Dyami,

    I don't have the installer, I just have the driver files. And I'm sure that those driver files are for Windows XP, the OS that runs on the computers.


    Dhow here.

    Thursday, March 13, 2014 4:17 AM
  • Dhow

    It has been over a decade since I used XP so I am not positive on how to install a driver.  You should probably Google how.


    Wanikiya and Dyami--Team Zigzag

    Thursday, March 13, 2014 2:55 PM
  • Dhow

    It has been over a decade since I used XP so I am not positive on how to install a driver.  You should probably Google how.


    Wanikiya and Dyami--Team Zigzag


    Sigh.


    Dhow here.


    • Edited by Dhow Friday, March 14, 2014 2:31 AM
    Friday, March 14, 2014 2:30 AM
  • Hi Dhow

    Sorry for my late reply.

    As you don't have the original installer, the first thing I'm trying to here, is to provice you With the generic Atheros drivers (the ID you gave me provided me With the vendor and Product ID).

    Try to uninstall and delete the WiFi drivers, and reinstall the network cardwith the generic drivers:

    http://www.solaat.no/filer/MVP/Atheros_driver.zip
    (It is virus free, but I'm not guaranteeing you that this would work)

    If this does not solve yourproblem, it might be either a faulty hardware, or a sign that it is time to reinstall Windows XP / Upgrade to Win 7 ;)


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Friday, March 14, 2014 10:03 AM
  • Hi Dhow

    Sorry for my late reply.

    As you don't have the original installer, the first thing I'm trying to here, is to provice you With the generic Atheros drivers (the ID you gave me provided me With the vendor and Product ID).

    Try to uninstall and delete the WiFi drivers, and reinstall the network cardwith the generic drivers:

    http://www.solaat.no/filer/MVP/Atheros_driver.zip
    (It is virus free, but I'm not guaranteeing you that this would work)

    If this does not solve yourproblem, it might be either a faulty hardware, or a sign that it is time to reinstall Windows XP / Upgrade to Win 7 ;)

    Alexander,

    Thanks, I'll give it a try.

    But is it compatible? The WiFi card I'm using is 3COM, while the driver you gave me is Atheros. Is it the same? Did 3COM use Atheros' WiFi chip in its card?


    Dhow here.

    Monday, March 17, 2014 4:33 AM
  • Hi Dhow,

    Yes, 3Com used Atheros chips in many of their products.
    This is one of them.

    Let me know the outcome.


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Monday, March 17, 2014 6:38 PM
  • Hi Dhow,

    Yes, 3Com used Atheros chips in many of their products.
    This is one of them.

    Let me know the outcome.


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Alexander,

    Yup, that's my 3COM Wireless Adapter Card alright. :-)

    I've installed the Atheros driver you gave me, but it'll have to wait for quite some time to know wheter it's working or not. The first BSoD happened on February 26th, a day before my first post of this thread, and the next one is yesterday: March 17th, just a day before I used the Atheros driver. So we'll have to wait to see how it goes.

    Thanks for your help.


    Dhow here.

    Tuesday, March 18, 2014 3:11 AM
  • Hi Dhow,

    Great!
    Keep us posted whenever there is something (or nothing) to report :)


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Tuesday, March 18, 2014 6:50 AM
  • Hi Dhow,

    Great!
    Keep us posted whenever there is something (or nothing) to report :)


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Yes of course, I'll keep you guys posted, and definitely mark it as answered if the issue is resolved.

    By the way, I was wondering what should I do with the "Network Address" value in the Wireless Network Adapter Properties at the Advanced tab? As right now, and previously before, it is set at "Not Present" option. Should I change it?


    Dhow here.

    Tuesday, March 18, 2014 7:32 AM
  • Hi Dhow,

    I would not change tis unless a scenario would need me to hange it (e. while troubleshooting errors).


    With compliments Alexander Solaat Rodland Surface Pro 2, 256gb

    Tuesday, March 18, 2014 8:25 AM