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

[pseudocrat]

Here's the MSINFO32 file.

 

[derekimo]

Thanks, that helps. My post #16 is still a good suggestion when you can get to it.

 

[pseudocrat]

Thanks, that helps. My post #16 is still a good suggestion when you can get to it.

Oh, yes. I already uninstalled the xbox driver, but how do I know which gfx driver to revert back to? I'm not using a beta driver or anything.

I was looking it up and I've received several gfx driver updates over the last month, but I've also been experiencing BSODs off and on for almost all of that time. So, should I just go back one driver version at a time? Or what would you suggest?

 

[derekimo]

Yeah, at this point you're just trying to find a stable driver.

This tutorial is good info as well,

http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

 

[pseudocrat]

Alright, I reverted back to the previous version.

 

[pseudocrat]

I didn't get a BSOD for a couple days, but I just got another one. Did one of those drivers get installed again? I looked for the xbox controller one thinking maybe it got re-installed, but I didn't see it.
--------------------------------------------------------------------------------------

IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffa90`0d7deba8 00000000`00000002 00000000`00000001 fffff800`03a9a72e ntoskrnl.exe ntoskrnl.exe+76e80 NT Kernel & System

Microsoft® Windows® Operating System Microsoft Corporation
6.1.7601.18700 (win7sp1_gdr.141211-1742) x64
ntoskrnl.exe+76e80
C:\Windows\Minidump\013115-9750-01.dmp 8 15 7601 399,768 1/31/2015 3:29:34 AM

 

[Golden]

Please re-run MSINFO, and upload the new .nfo file here please.

 

[pseudocrat]

Msinfo

 

[Golden]

Event[59061]:
  Log Name: System
  Source: Service Control Manager
  Date: 2015-01-31T03:31:13.079
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Kryolith
  Description: 
[B][COLOR="Red"]The PCASp60 NDIS Protocol Driver service failed to start due to the following error: 
The system cannot find the file specified.[/COLOR][/B]

This error message is prevalent in the eventlog, and usually points to some incompatibility in network drivers/devices, or corruption with drivers, and may be related to your BSOD.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa900d7deba8, 2, 1, fffff80003a9a72e}

Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+2ec )

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

5: kd> lmvm e22w7x64
start             end                 module name
fffff880`056ec000 fffff880`0570e000   e22w7x64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\e22w7x64.sys
    Image name: e22w7x64.sys
    Timestamp:        Thu [B][COLOR="red"]Mar 27[/COLOR][/B] 02:29:01 [B][COLOR="red"]2014[/COLOR][/B] (5332F945)
    CheckSum:         00022897
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The .dmp files aren't revealing anything conclusively, but my intuition tells me its network-related.

There has been an upsurge in BSOD's with systems using Killer e2200 Gigabit Ethernet Controller (NDIS 6.30) adapters. My first recommendation is to see if there is a more up-to-date driver, and try that. If not, please try a cheap alternate network adapter to see if the issue is solved.

 

[pseudocrat]

I reinstalled my Killer e2200 ethernet controller, but I just experienced two more BSOD's today.

I figured I'd upload the minidumps and stuff to see if it offered anything conclusive.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        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 : [B][COLOR="red"]bflwfx64.sys[/COLOR][/B] ( 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: [B][COLOR="red"]bflwfx64.sys[/COLOR][/B]
    Timestamp:        Thu [B][COLOR="Red"]Feb 14[/COLOR][/B] 03:34:08 [COLOR="red"][B]2013[/B][/COLOR] (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.

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

Use !analyze -v to get detailed debugging information.

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

Probably caused by :[COLOR="red"][B] hardware[/B][/COLOR] ( Wdf01000!imp_WdfRequestRetrieveInputBuffer+119 )

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

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

 

[pseudocrat]

Another BSOD. Updated minidump logs.

See attached for 2/04

 

[pseudocrat]

This is the link I've been getting the bigfoot driver at:

http://download.gigabyte.us/FileList/Driver/mb_driver_lan_bigfoot_9series.zip

 

[Golden]

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