BSOD Fairly Often. Driver Verifier Enabled = BSOD on Boot Every Time

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {2, 2, 1, fffff80003adeec4}

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

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

0: kd> lmvm bflwfx64
start             end                 module name
fffff880`0449f000 fffff880`045f2000   bflwfx64 T (no symbols)           
    Loaded symbol image file: bflwfx64.sys
    Image path: \SystemRoot\system32\DRIVERS\bflwfx64.sys
    Image name: bflwfx64.sys
    Timestamp:        Thu Feb 14 03:34:08 2013 (511BC788)
    CheckSum:         0001B330
    ImageSize:        00153000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Mmm...different network driver blamed this time.
BigFoot was acquired by Qualcomm 2011....but I can't find a driver on their site. You may have to resort to a 3rd party driver finder (this is not ideal, and my least preferred solution, but unfortunately I see no alternative - use with extreme care).

The bit in red worries me.....I wonder if the adapter is about to die on you.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88000ec65c5, fffff88010840b80, 0}

Probably caused by : hardware ( Wdf01000!imp_WdfRequestRetrieveInputBuffer+119 )

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

I'll see if I can find a reliable driver download.

Mmm...Im sorry, Im really not sure what to suggest, apart from a different adapter.