BSOD ~weekly while using Outlook,etc unclear cause (Asus G73SW/W7)

[jap]

Hi there,
I need help deciphering the cause of the BSOD in my laptop. The circumstances are not always the same when it happens. Mostly what's open at that time is Outlook 2010, Firefix browser (Typo3 website updates), Pandora (not necessarily playing).

I have done exhaustive hardware tests and no matter how hard or long I stressed it I could not replicate BSOD this way. My suspicion is a driver. I am attaching SF Diagnostic Tool output folder zipped. Please see if you can kindly help!
-J

 

[Arc]

Hi jap.

You need to update the USB3 driver.

The one available with ASUS is even older that the installed one.

Get it from FRESCO LOGIC INC.===Leap into SuperSpeed===

Let us know the situation after updating the driver.
______________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {8, 57ff15c3ed8, 3, fffffa8007a7aa40}

*** WARNING: Unable to verify timestamp for FLxHCIc.sys
*** ERROR: Module load completed but symbols could not be loaded for FLxHCIc.sys
Probably caused by : FLxHCIc.sys ( FLxHCIc+17db7 )

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

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

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000008, An operation occurred on a DMA transaction object while it
    was not in the correct state.
Arg2: 0000057ff15c3ed8, Reserved.
Arg3: 0000000000000003, Reserved.
Arg4: fffffa8007a7aa40, Reserved.

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


OVERLAPPED_MODULE: Address regions for 'EX64' and 'ENG64.SYS' overlap

BUGCHECK_STR:  0x10D_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88000f11aa4 to fffff800032ccbc0

STACK_TEXT:  
fffff880`0357e988 fffff880`00f11aa4 : 00000000`0000010d 00000000`00000008 0000057f`f15c3ed8 00000000`00000003 : nt!KeBugCheckEx
fffff880`0357e990 fffff880`00f0d950 : fffffa80`0ea3c120 fffff880`0357ead0 0000057f`f15c3ed8 fffffa80`0671a660 : Wdf01000!FxDmaTransactionBase::DmaCompleted+0xd8
fffff880`0357ea10 fffff880`0556adb7 : fffffa80`0ea3c120 fffffa80`0e9823b0 fffff800`034722d8 fffff800`034722d8 : Wdf01000!imp_WdfDmaTransactionDmaCompleted+0x114
fffff880`0357ea70 fffffa80`0ea3c120 : fffffa80`0e9823b0 fffff800`034722d8 fffff800`034722d8 fffffa80`0671a660 : FLxHCIc+0x17db7
fffff880`0357ea78 fffffa80`0e9823b0 : fffff800`034722d8 fffff800`034722d8 fffffa80`0671a660 00000000`00000000 : 0xfffffa80`0ea3c120
fffff880`0357ea80 fffff800`034722d8 : fffff800`034722d8 fffffa80`0671a660 00000000`00000000 fffff800`0347001e : 0xfffffa80`0e9823b0
fffff880`0357ea88 fffff800`034722d8 : fffffa80`0671a660 00000000`00000000 fffff800`0347001e fffff800`032d41e3 : nt!ExWorkerQueue+0x58
fffff880`0357ea90 fffffa80`0671a660 : 00000000`00000000 fffff800`0347001e fffff800`032d41e3 00000000`00000000 : nt!ExWorkerQueue+0x58
fffff880`0357ea98 00000000`00000000 : fffff800`0347001e fffff800`032d41e3 00000000`00000000 00000000`00000001 : 0xfffffa80`0671a660


STACK_COMMAND:  kb

FOLLOWUP_IP: 
FLxHCIc+17db7
fffff880`0556adb7 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  FLxHCIc+17db7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: FLxHCIc

IMAGE_NAME:  FLxHCIc.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50938bd6

FAILURE_BUCKET_ID:  X64_0x10D_8_FLxHCIc+17db7

BUCKET_ID:  X64_0x10D_8_FLxHCIc+17db7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x10d_8_flxhcic+17db7

FAILURE_ID_HASH:  {26d0091d-18d6-82a2-201e-93cf661d617d}

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

4: kd> lmvm FLxHCIc
start             end                 module name
fffff880`05553000 fffff880`05594000   FLxHCIc  T (no symbols)           
    Loaded symbol image file: FLxHCIc.sys
    Image path: \SystemRoot\system32\DRIVERS\FLxHCIc.sys
    Image name: FLxHCIc.sys
    Timestamp:        Fri Nov 02 14:31:10 2012 (50938BD6)
    CheckSum:         0003F4FD
    ImageSize:        00041000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[jap]

Just humble thanks!

Hi there,
I so appreciate your super-precise suggestion! I have not had a chance to get to it just yet, but I will shortly, and will keep you posted after I give the new driver a chance to behave itself.
Thank you!!
Jap