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

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 24
    Windows 7 Ultimate x64
    Thread Starter
       #21

    Here's the MSINFO32 file.
      My Computer


  2. Posts : 17,322
    Win 10 Pro x64
       #22

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


  3. Posts : 24
    Windows 7 Ultimate x64
    Thread Starter
       #23

    derekimo said:
    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?
      My Computer


  4. Posts : 17,322
    Win 10 Pro x64
       #24

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

    This tutorial is good info as well,

    NVIDIA Drivers - Avoid Problems
      My Computer


  5. Posts : 24
    Windows 7 Ultimate x64
    Thread Starter
       #25

    Alright, I reverted back to the previous version.
      My Computer


  6. Posts : 24
    Windows 7 Ultimate x64
    Thread Starter
       #26

    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
      My Computer


  7. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #27

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


  8. Posts : 24
    Windows 7 Ultimate x64
    Thread Starter
       #28

    Msinfo
      My Computer


  9. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #29

    Code:
    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: 
    The PCASp60 NDIS Protocol Driver service failed to start due to the following error: 
    The system cannot find the file specified.
    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.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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 Mar 27 02:29:01 2014 (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.
      My Computer


  10. Posts : 24
    Windows 7 Ultimate x64
    Thread Starter
       #30

    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.
      My Computer


 
Page 3 of 4 FirstFirst 1234 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:28.
Find Us