netr28ux.sys throwing BSODs


  1. Posts : 2
    Windows 7 Home Premium 64bit
       #1

    netr28ux.sys throwing BSODs


    Hello, i'm using Edimax's EW-7711USn usb wifi dongle for quite some time but now it started to BSOD my PC.
    I have updated drivers with no result. Same with removing and reinstalling them.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Complicated.

    The device is Edimax nLite Wireless USB Adapter.

    The driver is made by Ralink (that needs to be updated to stop the BSODs).

    Ralink got acquired by MediaTek.

    So I dont know what should be your best choice. If you are aware of the chip type, search for a driver in Downloads - MediaTek

    Otherwise get a new dongle, choose one where the vendor and the driver developer is the same (like Qualcomm Atheros) so that you can get flawless driver updates.
    ______________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff880047ec000, 2, 0, fffff8800283ed6c}
    
    *** WARNING: Unable to verify timestamp for netr28ux.sys
    *** ERROR: Module load completed but symbols could not be loaded for netr28ux.sys
    Probably caused by : netr28ux.sys ( netr28ux+16d6c )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: fffff880047ec000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800283ed6c, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038b8100
    GetUlongFromAddress: unable to read from fffff800038b81c0
     fffff880047ec000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    netr28ux+16d6c
    fffff880`0283ed6c 0fb60410        movzx   eax,byte ptr [rax+rdx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  deluge.exe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  fffff8800783fbc0 -- (.trap 0xfffff8800783fbc0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880047ebffd rbx=0000000000000000 rcx=fffff8800783fe34
    rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800283ed6c rsp=fffff8800783fd50 rbp=fffffa8008142950
     r8=0000000000000000  r9=0000000000000037 r10=fffffa8009d5cc00
    r11=fffffa800ab30030 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    netr28ux+0x16d6c:
    fffff880`0283ed6c 0fb60410        movzx   eax,byte ptr [rax+rdx] ds:fffff880`047ec000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003680169 to fffff80003680bc0
    
    STACK_TEXT:  
    fffff880`0783fa78 fffff800`03680169 : 00000000`0000000a fffff880`047ec000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0783fa80 fffff800`0367ede0 : 00000000`00008001 00000000`00000002 00000000`0004002f fffffa80`0926e1a0 : nt!KiBugCheckDispatch+0x69
    fffff880`0783fbc0 fffff880`0283ed6c : fffffa80`0b5c1190 00000000`00000000 00000000`00000000 fffffa80`0b9b1150 : nt!KiPageFault+0x260
    fffff880`0783fd50 fffffa80`0b5c1190 : 00000000`00000000 00000000`00000000 fffffa80`0b9b1150 00000000`00000100 : netr28ux+0x16d6c
    fffff880`0783fd58 00000000`00000000 : 00000000`00000000 fffffa80`0b9b1150 00000000`00000100 fffff880`01462c60 : 0xfffffa80`0b5c1190
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    netr28ux+16d6c
    fffff880`0283ed6c 0fb60410        movzx   eax,byte ptr [rax+rdx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  netr28ux+16d6c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: netr28ux
    
    IMAGE_NAME:  netr28ux.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f50a794
    
    FAILURE_BUCKET_ID:  X64_0xD1_netr28ux+16d6c
    
    BUCKET_ID:  X64_0xD1_netr28ux+16d6c
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xd1_netr28ux+16d6c
    
    FAILURE_ID_HASH:  {4c33591e-e7b0-e1f3-e206-91c5683bdcb0}
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm netr28ux
    start             end                 module name
    fffff880`02828000 fffff880`029d3000   netr28ux T (no symbols)           
        Loaded symbol image file: netr28ux.sys
        Image path: \SystemRoot\system32\DRIVERS\netr28ux.sys
        Image name: netr28ux.sys
        Timestamp:        Fri Mar 02 16:27:24 2012 (4F50A794)
        CheckSum:         001A5F72
        ImageSize:        001AB000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    I knew chip model before so just updated the driver from MediaTek's website. Works for now, but blue screens were random so i'll wait a few days and see if problem's gone.

    Edit: Updating drivers did the trick.
    Last edited by Demiu; 31 Aug 2014 at 15:22.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:36.
Find Us