BSOD when trying to update Video Card Drivers

  1. Posts : 18
    Windows 7 Home Premium 64bit

    BSOD when trying to update Video Card Drivers

    Hello. I'm not sure if this belongs here or somewhere else. I am trying to update my video card drivers, but I get a BSOD when I try to do it. My ZIP file contains three crashes, and all three of them have different error codes. The last one (in August) might not be relevant, but the two in October both are.

    My suspicion is that there is a problem in the registry involving the video card drivers, but I don't know how I'd go about fixing this.

    Edit: I ran Memtest86 on my computer recently and there was not a problem involving my RAM.
      My Computer

  2.    #2

    BugCheck CA, {b, fffffa8007ac7080, 1, 0}
    Probably caused by : pci.sys
    0: kd> !drvobj fffffa80076595a0 f
    fffff8000348c010: Unable to get value of ObpRootDirectoryObject
    fffff8000348c010: Unable to get value of ObpRootDirectoryObject
    Driver object (fffffa80076595a0) is for:
    Driver Extension List: (id , addr)
    Device Object list:
    fffffa8007ac6a10: Could not read device object
    DriverEntry:   fffff88000f601a0	pci!GsDriverEntry
    DriverStartIo: 00000000	
    DriverUnload:  fffff88000f5526c	pci!PciDriverUnload
    AddDevice:     00000000	
    Dispatch routines:
    [00] IRP_MJ_CREATE                      fffff800032c0b00	nt!IopInvalidDeviceRequest
    [01] IRP_MJ_CREATE_NAMED_PIPE           fffff800032c0b00	nt!IopInvalidDeviceRequest
    [02] IRP_MJ_CLOSE                       fffff800032c0b00	nt!IopInvalidDeviceRequest
    [03] IRP_MJ_READ                        fffff800032c0b00	nt!IopInvalidDeviceRequest
    [04] IRP_MJ_WRITE                       fffff800032c0b00	nt!IopInvalidDeviceRequest
    [05] IRP_MJ_QUERY_INFORMATION           fffff800032c0b00	nt!IopInvalidDeviceRequest
    [06] IRP_MJ_SET_INFORMATION             fffff800032c0b00	nt!IopInvalidDeviceRequest
    [07] IRP_MJ_QUERY_EA                    fffff800032c0b00	nt!IopInvalidDeviceRequest
    [08] IRP_MJ_SET_EA                      fffff800032c0b00	nt!IopInvalidDeviceRequest
    [09] IRP_MJ_FLUSH_BUFFERS               fffff800032c0b00	nt!IopInvalidDeviceRequest
    [0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff800032c0b00	nt!IopInvalidDeviceRequest
    [0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff800032c0b00	nt!IopInvalidDeviceRequest
    [0c] IRP_MJ_DIRECTORY_CONTROL           fffff800032c0b00	nt!IopInvalidDeviceRequest
    [0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff800032c0b00	nt!IopInvalidDeviceRequest
    [0e] IRP_MJ_DEVICE_CONTROL              fffff88000f50748	pci!PciDispatchDeviceControl
    [0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff800032c0b00	nt!IopInvalidDeviceRequest
    [10] IRP_MJ_SHUTDOWN                    fffff800032c0b00	nt!IopInvalidDeviceRequest
    [11] IRP_MJ_LOCK_CONTROL                fffff800032c0b00	nt!IopInvalidDeviceRequest
    [12] IRP_MJ_CLEANUP                     fffff800032c0b00	nt!IopInvalidDeviceRequest
    [13] IRP_MJ_CREATE_MAILSLOT             fffff800032c0b00	nt!IopInvalidDeviceRequest
    [14] IRP_MJ_QUERY_SECURITY              fffff800032c0b00	nt!IopInvalidDeviceRequest
    [15] IRP_MJ_SET_SECURITY                fffff800032c0b00	nt!IopInvalidDeviceRequest
    [16] IRP_MJ_POWER                       fffff88000f36908	pci!PciDispatchPnpPower
    [17] IRP_MJ_SYSTEM_CONTROL              fffff88000f506e4	pci!PciDispatchSystemControl
    [18] IRP_MJ_DEVICE_CHANGE               fffff800032c0b00	nt!IopInvalidDeviceRequest
    [19] IRP_MJ_QUERY_QUOTA                 fffff800032c0b00	nt!IopInvalidDeviceRequest
    [1a] IRP_MJ_SET_QUOTA                   fffff800032c0b00	nt!IopInvalidDeviceRequest
    [1b] IRP_MJ_PNP                         fffff88000f36908	pci!PciDispatchPnpPower
    There seems to be a problem with the PnP Manager or at least the drivers for the device, and how they are handling certain IRPs. The IRP seems most likely related to the _MJ_PNP Major Function code; IRP_MN_QUERY_DEVICE_RELATIONS seems to be the specific Minor Function code where the problem might have happened. I'm also guessing that a routine was used which took a device object as a parameter, before the a device node was created within the device tree by the PnP Manager for the associated device object.

    0: kd> !stack
    Call Stack : 9 frames
    ## Stack-Pointer    Return-Address   Call-Site       
    00 fffff88002ffda18 fffff8000371cf65 nt!KeBugCheckEx+0 
    01 fffff88002ffda20 fffff8000371d669 nt!PnpProcessRelation+695 
    02 fffff88002ffda90 fffff80003758915 nt!PnpBuildRemovalRelationList+69 
    03 fffff88002ffdae0 fffff8000375987c nt!PnpProcessQueryRemoveAndEject+325 
    04 fffff88002ffdc20 fffff80003642a1e nt!PnpProcessTargetDeviceEvent+4c 
    05 fffff88002ffdc50 fffff800032e5261 nt!PnpDeviceEventWorker+fa1b6 (perf)
    06 fffff88002ffdcb0 fffff80003579bae nt!ExpWorkerThread+111 
    07 fffff88002ffdd40 fffff800032cc8c6 nt!PspSystemThreadStartup+5a 
    08 fffff88002ffdd80 0000000000000000 nt!KxStartSystemThread+16
    A different stack trace from a Stop 0xE4 dump file revealed this:

    0: kd> k
     # Child-SP          RetAddr           Call Site
    00 fffff880`02fda748 fffff800`032417ea nt!KeBugCheckEx
    01 fffff880`02fda750 fffff880`010e457e nt! ?? ::FNODOBFM::`string'+0x1032a
    02 fffff880`02fda790 fffff880`010e3ada PCIIDEX!ControllerQueryDeviceRelations+0x52
    03 fffff880`02fda7c0 fffff800`036474ae PCIIDEX!PciIdeDispatchPnp+0x22
    04 fffff880`02fda7f0 fffff800`0364781a nt!PnpAsynchronousCall+0xce
    05 fffff880`02fda830 fffff800`03649b67 nt!PnpQueryDeviceRelations+0xfa
    06 fffff880`02fda8f0 fffff800`0367a15c nt!PipEnumerateDevice+0x117
    07 fffff880`02fda950 fffff800`0367a768 nt!PipProcessDevNodeTree+0x21c
    08 fffff880`02fdabc0 fffff800`0338d817 nt!PiProcessReenumeration+0x98
    09 fffff880`02fdac10 fffff800`03294261 nt!PnpDeviceActionWorker+0x327
    0a fffff880`02fdacb0 fffff800`03528bae nt!ExpWorkerThread+0x111
    0b fffff880`02fdad40 fffff800`0327b8c6 nt!PspSystemThreadStartup+0x5a
    0c fffff880`02fdad80 00000000`00000000 nt!KxStartSystemThread+0x16

    Start Menu\Programs\Driver Fusion
    These driver update and installation programs usually install incorrect and unstable drivers, please remove the program completely, and only install device drivers from your model support page or the hardware vendor.

    Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

      My Computer

  3. Posts : 18
    Windows 7 Home Premium 64bit
    Thread Starter

    I tried running Driver Verifier but my computer would not start up when it was activated. The Windows 7 splash would come up but when it should have gone to the desktop, the screen remained black. Is this normal?
      My Computer

  4.    #4

    Sorry for my absence, I've been ill most of this week.

    It is in a way, but it should boot normally into Windows. Have you disabled it now?

    I would suggest reinstalling your drivers from the manufacturer's support page.
      My Computer

  5. Posts : 18
    Windows 7 Home Premium 64bit
    Thread Starter

    I'm going to try to get driver verifier to work when I have time for it.

    I can't reinstall or upgrade the drivers because that is what causes the BSOD. It 's like as soon as the install program tries to read the current version of driver installed, it crashes the computer.

    I'll update the thread if I get something from driver verifier.
      My Computer

  6.    #6

    Okay, and have you tried installing the drivers manually?
      My Computer

  7. Posts : 18
    Windows 7 Home Premium 64bit
    Thread Starter

    No I haven't. I haven't heard of this before. I'll try it.
      My Computer

  8.    #8

    Okay, please post an update when finished.
      My Computer


  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 06:44.
Find Us