BSOD after logon, while loading system files

Mojo1094 · 19 Nov 2013

Help please?

I think this is related to my wireless USB adapter, but I could use some help. Anything additional you need from me, please ask.

I've had several blue screens in the past week, showing up in EventViewer as Kernal error 41

Code:

BugcheckCode201BugcheckParameter10x220BugcheckParameter20xfffff880074a0710BugcheckParameter30xfffff9802c748dc0BugcheckParameter40xfffffa800eaa1700SleepInProgressfalsePowerButtonTimestamp0

and 

EventData
BugcheckCode159BugcheckParameter10x4BugcheckParameter20x258BugcheckParameter30xfffffa800cb17040BugcheckParameter40xfffff800047fe510SleepInProgressfalsePowerButtonTimestamp0

What I notice is, my internet connection drops, I get a limited or no connectivity pop up, and if I can shut down, I get a bsod. So I uninstalled the driver, re-installed the latest version from the website and now I'm getting a BSOD whenever I boot into windows normal mode. I have been in safe mode for a while now and everything is fine.

Any help?

Arc · 19 Nov 2013

Hi Mojo.

Update Linksys AE2500 drivers from Official Linksys Support Site.

And update logitech drivers from Logitech Support - Downloads, Manuals, FAQs & More.

Also disable Driver verifier.

Let us know the results.
______________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa800cb17040, fffff800047fe510}

*** WARNING: Unable to verify timestamp for AE2500w764.sys
*** ERROR: Module load completed but symbols could not be loaded for AE2500w764.sys
Implicit thread is now fffffa80`0cb17040
Probably caused by : AE2500w764.sys ( AE2500w764+b6fe )

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

0: 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: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa800cb17040, The thread currently holding on to the Pnp lock.
Arg4: fffff800047fe510, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now fffffa80`0cb17040

DRVPOWERSTATE_SUBCODE:  4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000326e5f2 to fffff8000327ba8a

STACK_TEXT:  
fffff880`031a7ec0 fffff800`0326e5f2 : fffffa80`0cb17040 fffffa80`0cb17040 00000000`00000000 00000000`00000002 : nt!KiSwapContext+0x7a
fffff880`031a8000 fffff800`0327f99f : fffffa80`0db21910 00000000`00000000 ffff9a3b`00000094 fffffa80`c0000120 : nt!KiCommitThreadWait+0x1d2
fffff880`031a8090 fffff880`00ec07b9 : fffff880`00eab000 fffffa80`00000000 fffff880`00ea9600 0000057f`f2d01100 : nt!KeWaitForSingleObject+0x19f
fffff880`031a8130 fffff880`00f03f82 : ffffffff`dc3cba00 fffffa80`0daf1b40 00000000`00000000 00000000`00000006 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x99
fffff880`031a8170 fffff880`00f04efa : fffffa80`0d2fee30 fffff880`00f40730 fffffa80`0d29f010 fffff880`00ee94c8 : Wdf01000!FxUsbPipeContinuousReader::CancelRepeaters+0x6a
fffff880`031a81a0 fffff880`00f28bf9 : fffffa80`0d2fee30 0000057f`f2d011c8 0000057f`f2d011c8 fffffa80`0d29f010 : Wdf01000!FxUsbPipe::WaitForSentIoToComplete+0xca
fffff880`031a81f0 fffff880`00ef60fb : fffffa80`0d2fe901 fffffa80`0d2fee30 00000000`00000000 00000000`00000000 : Wdf01000!FxIoTarget::Stop+0x51
fffff880`031a8230 fffff880`06c406fe : fffffa80`0d2fee30 fffffa80`0d2c7590 00000000`00000000 fffffa80`0dc8d320 : Wdf01000!imp_WdfIoTargetStop+0x177
fffff880`031a82a0 fffffa80`0d2fee30 : fffffa80`0d2c7590 00000000`00000000 fffffa80`0dc8d320 fffffa80`0d2c7590 : AE2500w764+0xb6fe
fffff880`031a82a8 fffffa80`0d2c7590 : 00000000`00000000 fffffa80`0dc8d320 fffffa80`0d2c7590 fffff880`06c3f272 : 0xfffffa80`0d2fee30
fffff880`031a82b0 00000000`00000000 : fffffa80`0dc8d320 fffffa80`0d2c7590 fffff880`06c3f272 00000000`00000006 : 0xfffffa80`0d2c7590


STACK_COMMAND:  kb

FOLLOWUP_IP: 
AE2500w764+b6fe
fffff880`06c406fe ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  AE2500w764+b6fe

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AE2500w764

IMAGE_NAME:  AE2500w764.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d912630

FAILURE_BUCKET_ID:  X64_0x9F_4_AE2500w764+b6fe

BUCKET_ID:  X64_0x9F_4_AE2500w764+b6fe

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

0: kd> lmvm AE2500w764
start             end                 module name
fffff880`06c35000 fffff880`06d6c000   AE2500w764 T (no symbols)           
    Loaded symbol image file: AE2500w764.sys
    Image path: \SystemRoot\system32\DRIVERS\AE2500w764.sys
    Image name: AE2500w764.sys
    Timestamp:        Tue Mar 29 05:52:08 2011 (4D912630)
    CheckSum:         0013392A
    ImageSize:        00137000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, fffff880074f9710, fffff9802d13edc0, fffffa800f546a10}

*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
    This IRP should either have been completed earlier or should have been passed
    down.
Arg2: fffff880074f9710, The address in the driver's code where the error was detected.
Arg3: fffff9802d13edc0, IRP address.
Arg4: fffffa800f546a10, ProviderId.

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


BUGCHECK_STR:  0xc9_220

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`074f9710 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`074f9710 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff9802d13edc0

DEVICE_OBJECT: fffffa800e656850

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff80003486be0 -- (!locks fffff80003486be0)

Resource @ nt!PiEngineLock (0xfffff80003486be0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80003486be0
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000370f4ec to fffff80003282bc0

STACK_TEXT:  
fffff880`031a10a8 fffff800`0370f4ec : 00000000`000000c9 00000000`00000220 fffff880`074f9710 fffff980`2d13edc0 : nt!KeBugCheckEx
fffff880`031a10b0 fffff800`0371958a : fffff800`0370db00 fffff880`074f9710 fffff980`2d13edc0 fffffa80`0f546a10 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031a10f0 fffff800`0371a20f : 00000000`00000220 fffffa80`0f546a10 fffff980`2d13edc0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031a1140 fffff800`0371f7b7 : fffff980`2d13ef20 fffff880`074f9710 00000000`00000000 00000000`00000000 : nt!VfErrorReport10+0x6f
fffff880`031a1220 fffff800`0370f15e : fffffa80`0f1851c8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfWmiVerifyIrpStackUpward+0x67
fffff880`031a1250 fffff800`0371bc3d : fffffa80`0f0bd610 fffffa80`0f185010 fffff980`2d13edc0 fffff980`2d13edc0 : nt!VfMajorVerifyIrpStackUpward+0x6e
fffff880`031a1290 fffff800`0372d61d : fffff980`2d13ef20 fffff880`031a1480 00000000`c00000bb fffff980`2d13ef20 : nt!IovpCompleteRequest2+0xad
fffff880`031a1300 fffff800`032865d1 : fffff980`2d13ef23 00000000`00000000 00000000`000000ff fffff800`03710ffa : nt!IovpLocalCompletionRoutine+0x9d
fffff880`031a1360 fffff800`037252af : fffff980`2d13edc0 fffff880`07503400 fffffa80`0e656900 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`031a1450 fffff880`0787c624 : fffff880`00000013 fffff880`031a1578 00000000`c00000bb fffffa80`0e6569a0 : nt!IovCompleteRequest+0x19f
fffff880`031a1520 fffff880`00000013 : fffff880`031a1578 00000000`c00000bb fffffa80`0e6569a0 fffff980`2d13ef20 : LGVirHid+0x624
fffff880`031a1528 fffff880`031a1578 : 00000000`c00000bb fffffa80`0e6569a0 fffff980`2d13ef20 fffff880`074f9a0f : 0xfffff880`00000013
fffff880`031a1530 00000000`c00000bb : fffffa80`0e6569a0 fffff980`2d13ef20 fffff880`074f9a0f 00000000`00000000 : 0xfffff880`031a1578
fffff880`031a1538 fffffa80`0e6569a0 : fffff980`2d13ef20 fffff880`074f9a0f 00000000`00000000 fffffa80`0e6569a0 : 0xc00000bb
fffff880`031a1540 fffff980`2d13ef20 : fffff880`074f9a0f 00000000`00000000 fffffa80`0e6569a0 00000000`00000001 : 0xfffffa80`0e6569a0
fffff880`031a1548 fffff880`074f9a0f : 00000000`00000000 fffffa80`0e6569a0 00000000`00000001 00000000`00000017 : 0xfffff980`2d13ef20
fffff880`031a1550 fffff880`074f97fb : 00000000`00000000 fffffa80`0e6569a0 fffff980`2d13edc0 fffff880`031a1600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`031a1590 fffff800`0372bd26 : fffff980`00000002 fffff980`2d13edc0 00000000`00000002 fffff800`0372748e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`031a1600 fffff800`0372ad52 : fffff980`2d13ef68 00000000`00000002 fffffa80`0f57a460 fffffa80`0f0260f0 : nt!IovCallDriver+0x566
fffff880`031a1660 fffff800`0372bd26 : fffff980`2d13edc0 00000000`00000002 fffffa80`0f57a310 00000000`00000000 : nt!ViFilterDispatchPower+0x62
fffff880`031a1690 fffff800`0372ae68 : fffff980`2d13edc0 fffffa80`0f57a310 00000000`00000000 fffffa80`0f51ee70 : nt!IovCallDriver+0x566
fffff880`031a16f0 fffff800`0372af52 : fffffa80`0f546a10 fffffa80`0cb0b8e0 fffffa80`0f546a10 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`031a1760 fffff800`037180bf : fffffa80`0f546250 00000000`000007ff fffff800`033c15b8 fffff800`0361bd29 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`031a1800 fffff800`033356a2 : fffffa80`0f546250 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`031a1830 fffff800`0367028c : fffffa80`0f546250 fffffa80`0cb0b8e0 00000000`00000001 00000000`00000002 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`031a1860 fffff800`03671e84 : fffffa80`0f546250 fffffa80`0f546250 fffffa80`0cb0b8e0 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`031a1950 fffff800`03672448 : fffff800`03484560 00000000`00000000 00000000`00000010 fffff800`036723b0 : nt!PipProcessDevNodeTree+0x264
fffff880`031a1bc0 fffff800`03385827 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`0328c261 : fffff800`03385500 fffff800`03579101 fffffa80`0c9f0100 00000000`00000299 : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`0351f2ea : 00000000`00000000 fffffa80`0c9f0170 00000000`00000080 fffffa80`0c9b2b30 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`032738e6 : fffff880`02f64180 fffffa80`0c9f0170 fffff880`02f6efc0 00010200`01020001 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  51d3a2f1

FAILURE_BUCKET_ID:  X64_0xc9_220_VRF_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_220_VRF_HIDCLASS!HidpMajorHandler+0

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

Mojo1094 · 19 Nov 2013

I will get on that as soon as i get home. I did try to install the newest driver for the AE2500 but I'll give it a shot again (somehow, it was an older driver by a couple of days than the one I had).

But I didn't update the Logitech one. It was getting late. I'll do that when I get home and report back. Thanks!

Mojo1094 · 20 Nov 2013

OK. So, the computer is no longer locking up constantly and BSOD-ing. Wireless works great in safe mode and works for a limited time when under a normal boot, but after a few minutes of running i loose internet connectivity. The computer will no longer ping any external sites, nor will it even ping the router. The device itself gets a little warm.

I'm wondering if I'm having a bigger issue with the device at this point. I have tried multiple USB ports (2.0, 1.0, and 3.0).

I do appreciate your help quite a bit. Especially linking me to the sites. I'm pretty good at finding drivers and that but it is nice to have someone take that extra step.

Arc · 20 Nov 2013

In the situation, it is best to try another device as a test basis. If the situation is the same there too, then the issue is with the computer.

Mojo1094 · 20 Nov 2013

Agreed. Unfortunately I don't have a second USB WiFi adapter just laying around. We don't even use them at work so I don't have another one to troubleshoot with at the time being.

I'll mark this as resolved tho, and assume there is an issue with the device. I've had it for 2 years now and it's worked (somewhat) great, or at least ... functional. I've been wanting to upgrade to a better device with an external antenna so this is just a great opportunity? I hope?

Arc · 21 Nov 2013

Device with external antenna? Not a bad idea :)

If you get a device that is made and marketed by the same organization, it will be better for you, cause there will be regular driver updates. I will suggest for Qualicomm Atheros.

Mojo1094 · 21 Nov 2013

Thanks man, I'll look into that.

No more blue screen, but no matter what USB port, while running in windows it stays on for a bit then shuts off. I noticed there was a power setting that windows was allowed to power it down to conserve energy. I turned that off, it rebooted and continued to suck. I noticed something in the Eventvwr, but for the life of me can't remember what it was, but it was consistent with the adapter loosing the connection.

It may be time for a re-image ... but an internal PCi card can not possibly hurt the situation

Arc · 21 Nov 2013

I think if you start a new thread in General Discussion - Windows 7 Help Forums section, you will get some good assistance with the power plan issue.

Though personally I think it is not needed for a desktop PC.

Mojo1094 · 21 Nov 2013

yeah. if the PCi Card doesn't fix the issue, i'll move forward with a topic there.

BSOD after logon, while loading system files

BSOD after logon, while loading system files

Thanks so much