Ralink bsod

jmv2009

New Member
Member
Messages
197
Just got this BSOD myself when unplugging wli-uc-gn (ralink rt2870) with ralink 5.0.0.0 driver dated 09/28/2012. It was downloaded from Station-Drivers: le site de drivers, bios, firmwares avec un forum d'aide. Before this, the usb controller had disabled itself with a currently unknown error code. To reactivate it, I had disabled/enabled it. I can not reproduce it currently, and it has never occurred before. I can not find another reference on the web about this problem.

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Users\Johannes\Desktop\112212-64578-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: SRV*c:\symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
Machine Name:
Kernel base = 0xfffff800`d6c7d000 PsLoadedModuleList = 0xfffff800`d6f47ae0
Debug session time: Thu Nov 22 19:29:20.642 2012 (UTC + 1:00)
System Uptime: 8 days 22:21:16.315
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck A0, {614, fffffa801e822a70, 0, 2}


Probably caused by : USBPORT.SYS ( USBPORT!USBPORTBUSIF_RemoveUsbDevice+66 )


Followup: MachineOwner
---------


3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000614, A driver has requested an active/idle transition on a component
	with an illegal parameter.
Arg2: fffffa801e822a70, POP_FX_DEVICE device
Arg3: 0000000000000000, Component index
Arg4: 0000000000000002, Invalid component index


Debugging Details:
------------------




OVERLAPPED_MODULE: Address regions for 'netr28ux' and 'netr28ux.sys' overlap


BUGCHECK_STR:  0xA0


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  System


CURRENT_IRQL:  0


LAST_CONTROL_TRANSFER:  from fffff800d6e0e91c to fffff800d6cf7740


STACK_TEXT:  
fffff880`1e61b5e8 fffff800`d6e0e91c : 00000000`000000a0 00000000`00000614 fffffa80`1e822a70 00000000`00000000 : nt!KeBugCheckEx
fffff880`1e61b5f0 fffff800`d6e6bd51 : fffffa80`16fc1e00 fffff880`05648069 fffffa80`183daf40 fffffa80`18de3050 : nt!PopFxBugCheck+0x1c
fffff880`1e61b630 fffff800`d6da7432 : 00000000`00000001 fffffa80`1451f010 00000000`00000000 fffffa80`16fc1da0 : nt! ?? ::FNODOBFM::`string'+0x3a500
fffff880`1e61b680 fffff880`0565fff6 : fffffa80`1451f010 00000000`00000000 fffffa80`16fc1da0 fffffa80`165711a0 : nt!PoFxIdleComponent+0xe
fffff880`1e61b6f0 fffff880`056f692a : fffffa80`16fc1da0 fffffa80`1973b020 fffff880`1e61b701 fffffa80`188a60a0 : USBPORT!USBPORTBUSIF_RemoveUsbDevice+0x66
fffff880`1e61b730 fffff880`05715ecb : fffff8a0`00000003 fffff800`32506c75 fffff880`01400000 00000000`00000040 : usbhub!Usbh_HubRemoveUsbDevice+0x2a
fffff880`1e61b760 fffff880`05701353 : fffffa80`1d9c71b0 fffffa80`1d9c7060 fffffa80`1aef5b38 00000000`00000000 : usbhub! ?? ::FNODOBFM::`string'+0xe76b
fffff880`1e61b7c0 fffff880`056dec2b : fffffa80`1973a050 fffffa80`1aef5b38 00000000`00000001 00000000`00000000 : usbhub!UsbhPortDisconnect+0x8f
fffff880`1e61b800 fffff880`056ddbc0 : fffffa80`1aef5b38 00000000`00000001 00000000`0000a1e8 00000000`4e4e4f43 : usbhub!UsbhWaitConnect+0x26b
fffff880`1e61b860 fffff880`056dc596 : 408f4000`3354422a fffff880`1e61b989 fffffa80`192c91e0 00000000`00000000 : usbhub!UsbhHubDispatchPortEvent+0x610
fffff880`1e61b900 fffff880`056dce94 : 00000000`00000100 fffffa80`1973a050 fffffa80`1aef5b50 fffffa80`36314550 : usbhub!UsbhHubRunPortChangeQueue+0x3b6
fffff880`1e61b9f0 fffff880`056dc99a : 00000000`00000000 fffffa80`1aef5b38 fffffa80`1aef5b50 fffffa80`2d2d7170 : usbhub!Usbh_PCE_wRun_Action+0x3a4
fffff880`1e61ba50 fffff880`056de018 : fffffa80`1aef5b38 00000000`00000000 00000000`50447170 00000000`ffffffff : usbhub!UsbhDispatch_PortChangeQueueEventEx+0xfa
fffff880`1e61ba90 fffff800`d6ce349b : 00000000`00000000 00000000`00000000 fffffffe`76999ba7 fffffa80`20d61940 : usbhub!UsbhHubProcessChangeWorker+0x1d8
fffff880`1e61bb10 fffff800`d6d30641 : fffff800`d6f01110 fffffa80`216ff5c0 fffff800`d6ce343c fffff800`d6f01100 : nt!IopProcessWorkItem+0x5f
fffff880`1e61bb80 fffff800`d6c9f625 : fffffa80`13862da0 00000000`00000080 fffff800`d6d30500 fffffa80`216ff5c0 : nt!ExpWorkerThread+0x142
fffff880`1e61bc10 fffff800`d6cdde56 : fffff880`009c0180 fffffa80`216ff5c0 fffff880`009cbf40 fffffa80`1311b740 : nt!PspSystemThreadStartup+0x59
fffff880`1e61bc60 00000000`00000000 : fffff880`1e61c000 fffff880`1e616000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16




STACK_COMMAND:  kb


FOLLOWUP_IP: 
USBPORT!USBPORTBUSIF_RemoveUsbDevice+66
fffff880`0565fff6 488b5c2440      mov     rbx,qword ptr [rsp+40h]


SYMBOL_STACK_INDEX:  4


SYMBOL_NAME:  USBPORT!USBPORTBUSIF_RemoveUsbDevice+66


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: USBPORT


IMAGE_NAME:  USBPORT.SYS


DEBUG_FLR_IMAGE_TIMESTAMP:  505ab323


BUCKET_ID_FUNC_OFFSET:  66


FAILURE_BUCKET_ID:  0xA0_USBPORT!USBPORTBUSIF_RemoveUsbDevice


BUCKET_ID:  0xA0_USBPORT!USBPORTBUSIF_RemoveUsbDevice


Followup: MachineOwner
---------
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p

My Computer

System One

  • OS
    Windows 7 SP1
    System Manufacturer/Model
    Dell XPS 420
    Memory
    6 GB
here should be an intel graphics, a fresco and intel usb

enjoy
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
You gave us 3 minidmps. Two of them indicated that a Microsoft driver was the problem, this is of little help. The third indicated a fresco USB3. I think that this would be a logical starting point. As a test, use the computer as normal, if the BSODs continue disable the USB. Then test, my hunch is that the problem will be resolved. If it is solved, where we go from there, I'm not sure, but we will know the cause of the problem.
 

My Computer

System One

  • OS
    Windows 7 SP1
    System Manufacturer/Model
    Dell XPS 420
    Memory
    6 GB
Actually one of them points to igdkmd64 as well.

Code:
Loading Dump File [C:\Users\Johannes\Desktop\110412-42046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
Machine Name:
Kernel base = 0xfffff802`5140b000 PsLoadedModuleList = 0xfffff802`516d5a60
Debug session time: Sun Nov  4 21:16:01.102 2012 (UTC + 1:00)
System Uptime: 16 days 3:22:27.516
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8013d9b880, fffff880014fa7e0, fffffa8020508490}
Probably caused by : pci.sys
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8013d9b880, Physical Device Object of the stack
Arg3: fffff880014fa7e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8020508490, The blocked IRP
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5010ab1f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000f4b000 pci
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
TAG_NOT_DEFINED_c000000f:  FFFFF88001501FB0
STACK_TEXT:  
fffff880`014fa7a8 fffff802`5159b65e : 00000000`0000009f 00000000`00000003 fffffa80`13d9b880 fffff880`014fa7e0 : nt!KeBugCheckEx
fffff880`014fa7b0 fffff802`5159b691 : fffffa80`1c97c6a0 fffffa80`17e66c70 fffff880`014fa939 fffff802`514b1506 : nt!PopIrpWatchdogBugcheck+0xe2
fffff880`014fa810 fffff802`514b2734 : fffffa80`17e66c70 fffffa80`17e66b00 fffff880`014fab18 fffff880`01544180 : nt!PopIrpWatchdog+0x32
fffff880`014fa860 fffff802`514b2d55 : 00000000`00000000 00000000`00010023 00000000`00140001 00000000`000000dd : nt!KiProcessExpiredTimerList+0x214
fffff880`014fa9a0 fffff802`514b2c08 : fffff880`014d1180 fffff802`51703f80 00000000`0000000d 00000000`032bbbc5 : nt!KiExpireTimerTable+0xa9
fffff880`014faa40 fffff802`514accf6 : fffffa80`00000000 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff880`014faaf0 fffff802`514b13fa : fffff880`014d1180 fffff880`014d1180 00000000`00000000 fffff880`014dcf40 : nt!KiRetireDpcList+0x1f6
fffff880`014fac60 00000000`00000000 : fffff880`014fb000 fffff880`014f5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  0x9F_3_igdkmd64_IMAGE_pci.sys
BUCKET_ID:  0x9F_3_igdkmd64_IMAGE_pci.sys
Followup: MachineOwner
---------
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
Thats Intel, but lets do one step at a time. Follow my previous instructions and lets see if the problem is resolved. If not, we can leave the usb uninstalled and maybe, update Intel or even restore a previous version if any. I have had a few problems with incompatible drivers for 8 (and no compatilbe ones were found) we can Google and see if this may be a problem.
 

My Computer

System One

  • OS
    Windows 7 SP1
    System Manufacturer/Model
    Dell XPS 420
    Memory
    6 GB
The above BSOD's have only occurred once. For all problems drivers have been changed. Will post again if the problems reoccur.
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
Back
Top