Video drivers crash on cs5

This past week my photoshop has been saying "Video drivers crashed" on startup, and I can't use scrubby zoom or any 3d features.  Every few startups photoshop also crashes.
I tried to update my video drivers, then I did a clean install of them, and no fix.  Then I reinstalled photoshop cs5 and still have the same problems.
Any ideas what could be wrong?  I doubt it is my video card as I have not had any other gpu related problems on anything else.

So you're running Catalyst 11.1 then?  Though I don't have the same card as you, I'm running Catalyst 11.1 (on a 4670) and have no problems.  That doesn't mean much except that ATI certainly can get OpenGL right in at least some of their cards.
Photoshop is clearly unimpressed with the OpenGL implementation on your system if the option won't stay set.
Have you looked at the temperature(s) of your card?  I think the Catalyst Control Center can show you that.
You might try a full remove and install of the Catalyst suite, though to be honest I've seen no failures and I've been through many different versions over the past few years.
-Noel

Similar Messages

  • Intel video drivers crash after update

    Hi all,
    I have S540 ultrabook and I use it with onelinkdock with external screen and laptop screen in extend mode.
    After 8.1 upgrade on boot I receive the error message "Catalyst Control Center stop working", but everythings works fine.
    After Lenovo upgrade (including video driver) I don't receive the message anymore, but using the docking with extend screen, I face frequent black screen on external monitor. After few minutes also the main one became black and I got the message "intel video drivers crash and reset".
    Someone face the same issue?
    Thanks for your help

    I'm having the same issue as well, I'm currently at work so as of right now I can't try to restore mine, but the strange thing with mine is that I updated mine the day the iOS 4.0 came out and had no problems until last night. Now the music and video sections keep crashing after just a few seconds. Also all my Podcast are gone, the only things missing and I even re-downloaded them last night and they're still gone.

  • Tecra M3 video drivers causing crashes

    My Toshiba Tecra M3 is crashing (freezing or blue screen of death) with drivers 71.14, 71.36, and 76.44. It uses an NVIDIA GeForce Go 6600 TE 128M. When I uninstall all video drivers (or boot into safe mode), the laptop runs fine, although of course scrolling is deadly slow and I can't suspend or hibernate. But when I install either of the two WHQL certified drivers from Toshiba's site, 71.44 or 71.36, I can consistently create a crash just by running a 3D screensaver for more than 3 minutes. The same thing happens with the 76.44 non-WHQL driver from laptopvideo2go.com.
    Sorry if this is not the best thread to post on, but I would desperately appreciate any help you can offer on what driver might work reliably. At this point, I'm not at all interested in great graphics performance; I just want a stable laptop to do some work on. Is there perhaps some setting within the driver to turn off whatever fancy features are causing the crash?
    The laptop has a 2.13 GHz Pentium M and 2 GB of RAM. It's running WinXP SP2 with all updates and is using BIOS 1.20, the latest. And I doubt it's a related, but here's a different problem I ran into with the VPN, Wi-Fi, and Matlab.
    Thanks in advance for any help you can provide.
    [Edited by: admin]

    Hi danhkon
    I suppose that your notebook worked properly at the beginning. Can you maybe remember since when the unit started to make these troubles to you? It is not easy to give you a proper opinion or any kind of solution because every problem is caused by some reason.
    First of all I want to say that you should use just display driver given by Toshiba and not some driver that you found on the net. The drivers that you got on Tools & utilities CD or drivers that you can find on Toshiba site are all tested and they should work properly. As far as I know Tecra M3 is a new model and also delivered with SP2. That means that all drivers are also tested to work properly with SP2.
    Before you spend lot of times searching the right solution you should, in my opinion, save your data and reinstall OS using Recovery CD. On this way you will have a stable laptop to do some work on it. If there is no second partition you can make it for data saving using expert mode installation.

  • Youtube is causing my video drivers to crash

    I have a 21.5-inch Imac that I purchased mid 2012. I have created a windows 7 partintion on my computer using Bootcamp. Occasionally, Youtube will cause my video drivers to crash, which also causes my computer to crash. I have updated as much as I could with flash, windows, and my bootcamp drivers, but it still happens. I believe this is due to outdated video drivers, I happen to know that there has not been an update to the bootcamp video drivers since 2011, while AMD has a far more recent driver update. If anyone knows another solution to this problem please let me know; however, I believe the problem is the outdated video drivers. Apple very much needs to remedy this situation, even if it is nt causing my specific issue.

    OK we all have acknowledged the problem, now are there any solutions out there besides switching to firefox? Does Safari have a Flashblock extension, are there any at the ap store, is there a work around or any other ideas? I do have one, if there are no other fix,then we must boycott youtube for the summer and try youtubes compitition. I know of three, never really gave them much of my time though. But seeing as how I'm being forced to by YouTube, I'm sure their compitition would appreciate their, umm, sporting gesture in forcing us to switch

  • Just updated Skype and my Video Drivers and now everything is crashing

    I have seen some of the threads here when i goggled why my computer started crashing and most threads asked for the DxDiag file as well. Just wondering if someone would know what my problem is?I have just updated Skype and my Graphics Drivers today, (read: Radeon 2xx Series Gfx Card, with the proper, and most up to date drivers.) and now I keep getting BSOD's and things when I have a Skype window open, and try to run a game like Warframe on Steam. I have in the past, before these updates even suffered from the Graphics Drivers Crashing when I recieve or make a call with skype, just wondering if that may be an underlying problem as well. All the best and thanks for any help you may have.

    Try to uninstall the currently installed version and install the 6.14.0.104 Skype version using the download links provided here: http://community.skype.com/t5/Windows-desktop-client/ASUS-USB2-0-Webcam-not-recognized-by-Skype-6-18​... Make sure to disable automatic updates:Tools -> Options -> Advanced -> Automatic updates ->Turn off automatic updates

  • BSOD video driver crashing in PPro ONLY

    I'm getting a BSOD crash everytime I create a new seq or try to change seq settings. It has something to do with the seq setting dialog box. I can select any settings but as soon as I click OK, pow BSOD. minidumps point to the nvidia driver (nvlddmkm.sys). I'm using dell m6400, win 7 pro (fully updated), quadro 3700m (1 gig), 12gig mem, CS5.5  PPro 5.5.2 - Master collection (fully updated).  I'm mostly the AE and 3dmax person in our shop and not a PPro regular but we use PPro as our main editor. I have a project I need to do some stuff on in PPro and can't setup a SEQ cause it keeps crashing. I'm not having any issues like this with any of the other adobe software or any other software I'm using and I haven't had this problem in the past with PPro so I assume that there is a problem between PPro 5.5.2 the newer video drivers I'm now using (nvidia 310.90). 
    Any Ideas, suggestions?  I've tried just about everything I can think of. I thought about rolling the drivers back to CS5.5 era drivers (I guess around 285.xx ? ) but I really need the newer drivers for some features in the lastest 3Dmax/directX. Anyone else here had problems with PPro 5.5.2 and nvidia 310.xx?
    Thanks
    Joel

    Have you gone to nVidia to see if there is a newer driver?
    I'm not 100% sure, but I think I've seen mention of a 314.?? driver

  • Constant random BSOD happening due to video drivers

    Since about June a bunch of PCs in our organizations have been crashing. After looking at the dmp files we see that either nVidia, intel, or directx caused the crash. We update the video drivers, but still the PC crashes. The PC would either be a Dell
    (e6420, e6520) or Lenovo(T420s, W530). The majority of the dmp's have the words
    UNEXPECTED_KERNEL_MODE_TRAP. Any help will be appreciated, this has been plaguing us for months.

    Here is the latest crash info:
    Kernel Summary Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
    Machine Name:
    Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`030576d0
    Debug session time: Fri Oct 10 12:20:52.503 2014 (UTC - 4:00)
    System Uptime: 0 days 3:08:53.232
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 7F, {8, 80050031, 406f8, fffff8800322efec}
    *** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for igdkmd64.sys - 
    *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
    Probably caused by : nvkflt.sys ( nvkflt+18fec )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000406f8
    Arg4: fffff8800322efec
    Debugging Details:
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  a
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    EXCEPTION_RECORD:  fffff80002e67e04 -- (.exr 0xfffff80002e67e04)
    ExceptionAddress: 00076675870f40fe
       ExceptionCode: 74ff8548
      ExceptionFlags: 74f68556
    NumberParameters: 1064629893
       Parameter[0]: 001f0fce8b440000
       Parameter[1]: 0f10c783480f8b48
       Parameter[2]: 048154b60f0141b6
       Parameter[3]: 094c0fe083c28b48
       Parameter[4]: c148c28b4810c344
       Parameter[5]: 0090c384094c04e8
       Parameter[6]: e98349c0d1490000
       Parameter[7]: 3824748b48cd7501
       Parameter[8]: 7c8b4830245c8b48
       Parameter[9]: 28c48348c0332024
       Parameter[10]: 90909090909090c3
       Parameter[11]: 244c894c90909090
       Parameter[12]: 8948102454894820
       Parameter[13]: 485741564108244c
       Parameter[14]: 9824b48b4c58ec83
    LAST_CONTROL_TRANSFER:  from fffff80002e89129 to fffff80002e89b80
    STACK_TEXT:  
    fffff800`00ba4d28 fffff800`02e89129 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`02e875f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff880`0322efec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0e1eefd0 fffff880`0322ef1d : fffffa80`103f1570 fffffa80`103f1570 fffffa80`113cc040 00000000`00000000 : nvkflt+0x18fec
    fffff880`0e1ef070 fffff880`0322ef1d : fffff880`0322ee87 fffffa80`103f1970 fffff880`0e1ef280 fffffa80`113cc040 : nvkflt+0x18f1d
    fffff880`0e1ef110 fffff880`0322ed6f : fffff880`0322ee87 fffffa80`113cc040 fffff880`0e1ef8b0 00000000`00000000 : nvkflt+0x18f1d
    fffff880`0e1ef1b0 fffff880`1058baf2 : fffff880`0322ecdd 00000000`00000000 00000000`00000000 00000000`00000000 : nvkflt+0x18d6f
    fffff880`0e1ef250 fffff880`10516a4b : 00000000`00000000 fffff880`00000000 fffff880`0e1ef890 00000000`00000000 : igdkmd64!hybDriverEntry+0x10dcc2
    fffff880`0e1ef7f0 fffff880`104a7133 : fffffa80`11502000 fffffa80`103f8010 00000000`00000000 fffffa80`1512354c : igdkmd64!hybDriverEntry+0x98c1b
    fffff880`0e1ef870 fffff880`03228d11 : 00000000`00000000 fffffa80`11502000 00000000`00000000 fffffa80`1caaf7b0 : igdkmd64!hybDriverEntry+0x29303
    fffff880`0e1ef8e0 fffff880`03228ed7 : fffff880`03228c7f fffffa80`10401c10 fffffa80`11502000 fffffa80`103f1570 : nvkflt+0x12d11
    fffff880`0e1ef980 fffff880`0322905a : fffff880`03228e3e 00000000`00000000 fffffa80`103f1420 00000000`00000001 : nvkflt+0x12ed7
    fffff880`0e1efa30 fffff800`02e859dc : fffff880`03228fc7 fffff880`0e1efe30 fffff880`0e1efb50 fffffa80`0ffe3f00 : nvkflt+0x1305a
    fffff880`0e1efad0 fffff800`02e8be23 : fffff800`02e67e04 fffff880`0e1f0930 fffff880`0e1f0400 fffff880`0e1f0408 : nt!KiInterruptDispatch+0x16c
    fffff880`0e1efc68 fffff800`02e67e04 : fffff880`0e1f0930 fffff880`0e1f0400 fffff880`0e1f0408 00000000`00000000 : nt!memset+0x93
    fffff880`0e1efc70 fffff800`02e57cbc : fffff880`0e1efd50 fffffa80`139667c8 fffffa80`15113148 00000000`00000000 : nt!RtlSidHashInitialize+0x34
    fffff880`0e1efca0 fffff800`02e57dff : fffffa80`139667c8 00000000`00000001 fffffa80`15123000 fffff880`0e1f0408 : nt!SepTokenFromAccessInformation+0xbc
    fffff880`0e1efcd0 fffff880`01cfda3a : fffff880`0e1f03e0 fffff880`01cfd501 fffff880`0e1f0408 fffff880`0e1f0400 : nt!SeAccessCheckFromState+0x9f
    fffff880`0e1f03c0 fffff880`01cfd29f : fffffa80`1515cf48 00000000`00000000 00000000`00000001 fffff880`01cfd434 : NETIO!CompareSecurityContexts+0x6a
    fffff880`0e1f0430 fffff880`01cfd434 : 00000000`00000000 00000000`00000000 fffffa80`13c57be0 fffff880`01cfd753 : NETIO!MatchValues+0xef
    fffff880`0e1f0480 fffff880`01cfd8e2 : 00000000`00000000 fffffa80`1119aa70 fffff880`0e1f06a8 fffffa80`0fa25ca0 : NETIO!FilterMatch+0x94
    fffff880`0e1f04d0 fffff880`01cfe6ec : 00000000`00000000 00000000`00000010 fffffa80`0fa25ca0 fffff880`0e1f0690 : NETIO!IndexListClassify+0x69
    fffff880`0e1f0550 fffff880`01e811c7 : fffffa80`0fa25ca0 fffff880`0e1f0930 00000000`00000000 fffffa80`20ee5e20 : NETIO!KfdClassify+0xa4e
    fffff880`0e1f08c0 fffff880`01e82d94 : fffffa80`0fa25ca0 fffffa80`14b2a800 fffff880`0e1f1348 fffffa80`111c70e0 : tcpip!WfpAleClassify+0x57
    fffff880`0e1f0900 fffff880`01e83125 : 00000000`00000000 fffff880`00000000 00000000`00000000 00000000`00000002 : tcpip!WfpAlepReauthorizeInboundConnection+0x5f4
    fffff880`0e1f0c00 fffff880`01e5a1cd : fffffa80`14b2a800 fffff880`0e1f0d7c 00000001`00000011 fffffa80`111c70e0 : tcpip!WfpAleReauthorizeInboundConnection+0x1f5
    fffff880`0e1f0d60 fffff880`01e556da : 00000000`00000797 fffffa80`111c71d0 fffffa80`13c44ec0 fffff880`0e1f1200 : tcpip!WfpAleReauthorizeConnection+0x63d
    fffff880`0e1f0ec0 fffff880`01e80bfa : fffffa80`14b2a800 00000000`00000002 00000000`00000000 00000000`00000100 : tcpip!TlShimOptionalReauthorizeConnection+0x2ca
    fffff880`0e1f1000 fffff880`01e8deed : fffff880`00000003 fffff880`00000000 fffff880`00000003 fffffa80`20ee5e20 : tcpip!ProcessALEForTransportPacket+0x3ea
    fffff880`0e1f1270 fffff880`01e81e48 : fffffa80`14b2a800 fffffa80`00000000 00000000`00000000 fffffa80`0fa2eb14 : tcpip!ProcessAleForNonTcpIn+0x1ad
    fffff880`0e1f1390 fffff880`01e598b8 : fffffa80`00000011 fffff880`0e1f0002 fffffa80`14b2eb14 00000000`0000fccc : tcpip!WfpProcessInTransportStackIndication+0xb98
    fffff880`0e1f1520 fffff880`01e85fb9 : 00000000`00000018 fffffa80`0fa5b820 00000000`00000000 fffff880`01e865b4 : tcpip!InetInspectReceiveDatagram+0x1d8
    fffff880`0e1f15c0 fffff880`01e85b34 : fffffa80`14bcbb60 fffffa80`1398d160 fffffa80`13f88080 00000000`00000000 : tcpip!UdpBeginMessageIndication+0x89
    fffff880`0e1f16e0 fffff880`01e800de : fffffa80`0ccc7000 00000000`00000018 fffffa80`00000000 fffff880`0e1f1810 : tcpip!UdpDeliverDatagrams+0x2f4
    fffff880`0e1f17c0 fffff880`01e55197 : 00000000`00000000 fffff800`03401a01 00000000`00000001 fffffa80`00000005 : tcpip!UdpReceiveDatagrams+0x18f
    fffff880`0e1f18a0 fffff880`01e54caa : 00000000`00000000 fffff880`01f6ba10 fffff880`0e1f1a60 00000000`00000000 : tcpip!IppDeliverListToProtocol+0xf7
    fffff880`0e1f1960 fffff880`01e54261 : fffff880`01f6ba10 fffffa80`214afa30 00000000`00000011 fffff880`0e1f1a50 : tcpip!IppProcessDeliverList+0x5a
    fffff880`0e1f1a00 fffff880`01e51eef : 00000000`fc0000e0 fffff880`01f6ba10 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x232
    fffff880`0e1f1b00 fffff880`01f36022 : fffffa80`13439590 00000000`00000000 fffffa80`103c9501 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`0e1f1d00 fffff880`01d8db16 : fffffa80`210bb002 fffffa80`210bb010 00000000`00000002 00000000`00000000 : tcpip!IppInspectInjectReceive+0xf2
    fffff880`0e1f1d40 fffff880`04aba7cc : fffffa80`0ccf8570 fffffa80`103c9540 fffffa80`103c9600 fffffa80`214af900 : fwpkclnt!FwpsInjectTransportReceiveAsync0+0x256
    fffff880`0e1f1df0 fffff880`04aba8e5 : fffffa80`103c9540 fffff880`0e1f2700 fffffa80`103c9600 00000000`00000000 : vsdatant+0x137cc
    fffff880`0e1f1e80 fffff880`04ab9c07 : fffffa80`1d645010 fffff880`0e1f2700 fffffa80`1d645010 fffffa80`103c9600 : vsdatant+0x138e5
    fffff880`0e1f1ec0 fffff880`04ab53b4 : fffffa80`103c9540 fffffa80`103c9500 fffff880`0e1f2700 fffffa80`00000000 : vsdatant+0x12c07
    fffff880`0e1f1fd0 fffff880`01d15aaf : fffff880`0e1f26c8 fffff880`0e1f2280 fffffa80`24383ae0 fffffa80`0cceb040 : vsdatant+0xe3b4
    fffff880`0e1f2110 fffff880`01cfcf58 : 00000000`00000018 fffff880`0e1f26c8 fffffa80`111c7138 fffffa80`24383ae0 : NETIO! ?? ::FNODOBFM::`string'+0x7277
    fffff880`0e1f2230 fffff880`01cfe5d2 : 00000000`00000018 fffff880`0e1f26c8 fffff880`0e1f27e0 fffff880`00000000 : NETIO!ArbitrateAndEnforce+0x238
    fffff880`0e1f2300 fffff880`01f006cb : fffff880`0e1f2d18 fffff880`0e1f26c8 fffff880`00000000 fffffa80`24383ae0 : NETIO!KfdClassify+0x934
    fffff880`0e1f2670 fffff880`01eb8102 : 00000000`00000000 fffffa80`14b2a800 fffffa80`111c7240 00000000`00000100 : tcpip!WFPDatagramDataShimV4+0x49b
    fffff880`0e1f29d0 fffff880`01e8deed : fffff880`00000003 fffff880`00000000 fffff880`00000003 fffffa80`24383ae0 : tcpip! ?? ::FNODOBFM::`string'+0x26aa2
    fffff880`0e1f2c40 fffff880`01e81e48 : fffffa80`14b2a800 fffffa80`00000000 00000000`00000000 fffffa80`0fa2eb14 : tcpip!ProcessAleForNonTcpIn+0x1ad
    fffff880`0e1f2d60 fffff880`01e598b8 : fffffa80`00000011 fffff880`0e1f0002 fffffa80`14b2eb14 00000000`0000fccc : tcpip!WfpProcessInTransportStackIndication+0xb98
    fffff880`0e1f2ef0 fffff880`01e85fb9 : 00000000`00000018 fffffa80`0fa5b820 00000000`00000000 fffff880`01e865b4 : tcpip!InetInspectReceiveDatagram+0x1d8
    fffff880`0e1f2f90 fffff880`01e85b34 : fffffa80`14bcbb60 fffffa80`1398d160 fffffa80`13f88080 00000000`00000000 : tcpip!UdpBeginMessageIndication+0x89
    fffff880`0e1f30b0 fffff880`01e800de : fffffa80`0ccc7000 00000000`00000018 fffffa80`00000000 fffff880`0e1f31e0 : tcpip!UdpDeliverDatagrams+0x2f4
    fffff880`0e1f3190 fffff880`01e55197 : fffffa80`138f0007 fffff880`0e1f3301 00000000`00000002 fffff880`00000005 : tcpip!UdpReceiveDatagrams+0x18f
    fffff880`0e1f3270 fffff880`01e54caa : 00000000`00000000 fffff880`01f6ba10 fffff880`0e1f3430 00000000`00000000 : tcpip!IppDeliverListToProtocol+0xf7
    fffff880`0e1f3330 fffff880`01e54261 : fffff880`01f6ba10 fffffa80`21196e80 00000000`00000011 fffff880`0e1f3420 : tcpip!IppProcessDeliverList+0x5a
    fffff880`0e1f33d0 fffff880`01e51eef : 00000000`fc0000e0 fffff880`01f6ba10 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x232
    fffff880`0e1f34d0 fffff880`01e514c2 : fffffa80`13439590 00000000`00000000 fffffa80`13884b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`0e1f36d0 fffff880`01e508ea : fffffa80`13884ba0 fffff880`0e1f3800 fffffa80`13884ba0 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`0e1f37b0 fffff800`02e95878 : fffffa80`20190030 00000000`00004800 fffffa80`2429eab0 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`0e1f3800 fffff880`01e50fe2 : fffff880`01e50810 fffff880`0e1f3c00 fffff880`0e1f3c02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0e1f38e0 fffff880`01cc40eb : fffffa80`138b98d0 00000000`00000000 fffffa80`115af1a0 fffffa80`115af1a0 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`0e1f3950 fffff880`01c8dad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`0e1f39c0 fffff880`01c105d4 : fffffa80`115af1a0 00000000`00000002 00000000`00000001 fffff880`091b300f : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    fffff880`0e1f3e40 fffff880`01c10549 : fffffa80`13884050 fffff880`091b5630 00000000`00000008 fffff880`01c07d9f : ndis!ndisMTopReceiveNetBufferLists+0x24
    fffff880`0e1f3e80 fffff880`01c104e0 : ffff0000`0aaf8d9e 00000000`00000000 00000000`00000000 fffffa80`138b8930 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
    fffff880`0e1f3ec0 fffff880`04abd9f4 : 00000000`00000000 fffffa80`20190030 00000000`00000000 fffffa80`138b8930 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
    fffff880`0e1f3f00 fffff880`04abdb20 : 00000000`0000ff00 fffffa80`00000000 00000001`00000000 fffffa80`138a8670 : vsdatant+0x169f4
    fffff880`0e1f3f70 fffff880`01c10549 : 00000000`00000000 00000000`00000000 fffffa80`138ae020 00000000`00000001 : vsdatant+0x16b20
    fffff880`0e1f3fb0 fffff880`01c104e0 : fffff880`091ed5c0 fffffa80`138b1010 fffffa80`138ae020 00000000`00000001 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
    fffff880`0e1f3ff0 fffff880`091b67ee : fffffa80`138b1010 00000000`00000000 fffffa80`20190030 fffff880`091ed5c0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
    fffff880`0e1f4030 fffff880`01c10549 : fffffa80`11c57260 00000000`00000000 00000000`00000001 00000000`00000001 : nwifi!Pt6Receive+0x296
    fffff880`0e1f4090 fffff880`01c104e0 : fffffa80`1220f028 fffff880`0320a0c7 fffff880`0320b340 00000000`00000010 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nvkflt+18fec
    fffff880`0322efec e85b90feff      call    nvkflt+0x204c (fffff880`0321804c)
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nvkflt+18fec
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvkflt
    IMAGE_NAME:  nvkflt.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  534455e8
    FAILURE_BUCKET_ID:  X64_0x7f_8_nvkflt+18fec
    BUCKET_ID:  X64_0x7f_8_nvkflt+18fec
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_nvkflt+18fec
    FAILURE_ID_HASH:  {852d6a08-1c03-cc24-3abf-2b8e31df551a}
    Followup: MachineOwner
    ---------

  • Video drivers question

    does the onboard chipset video need different drivers than the pcie cards , and does win vista 64 let you install 2 different video drivers ?

    You have three options:
    1)  Disable SLI and use 3 monitors on the VGA cards.
    2)  Keep SLI enabled and use 2 monitors.
    3)  Keep SLI and the onboard enabled with the risk of crashing.
    This is a limitation of the driver/hardware and we can't really change that.
    Quote from: Hans on 12-October-09, 02:00:59
    Same driver.
    I checked the driver, and they do both indeed use the same NV_disp driver:  (Pulled from the driver configuration file.)
    Code: [Select]
    NVIDIA_DEV.084D.01 = "NVIDIA nForce 750a SLI"
    NVIDIA_DEV.0614.01 = "NVIDIA GeForce 9800 GT  "

  • Boot Camp Video Drivers

    Where can I find updated Boot Camp Video drivers? I want to update my video drivers on my MacBook running Boot Camp w/ Windows XP. Can I download XP video drivers from nVidia and install?

    Hi there,
    I recently had XP on my Macbook pro (Late 08) and wanted to update the nvidia GPU drivers. So all I had to do was get the "Correct" ones from the nvidia website and just installed them like normal.
    That being said, I ran into some problems with Windows Vista 64. Constant crashing when booting into the desktop due to incompatible graphics drivers. So what I had to do there was enter the device manager and "Roll back" the graphics driver. THEN restart in safemode and install the updated graphics driver.
    Maybe give that a try and see what happens? Hope we could help you...
    Tony

  • Droste filter crashes AE cs5

    I recently downloaded the Droste filter. Whenever I try to use it, it crashes AE cs5 immediately with the error message: After Effects error: crash occurred while invoking effect plug-in “Droste”.
    Does anyone know how to fix this? Thank you.

    We can't know. you have not provided any system information or otehr details. Since PixelBender uses hardware acceleration, the bog standard answer would be that your graphics hardware is incompatible or at least you need to update your drivers.
    Mylenium

  • Canon DSLR Video in Premiere Pro CS5

    Iam now using Premiere Pro CS5. My Windows PC is running Windows 7 64 bit Pro with two 2.66 Ghz quad core processors, 12 GB RAM and a Nvidia Quadro FX 4800 GPU. I am also running dual EIZO 24 inch monitors vis display port connections.
    I am editing Canon 5D MkII DSLR video. When I place the video in the time line I get the yellow bar across the top of the timeline. Should I be getting the yellow line. All the promo clips I have seen show it with no yellow bar untill you start adding filters etc.
    Also when I play a single time line it does play smoothly but after about 10 to 20 seconds the clip stops palying and I have to restart. Also the clips do not scrub smoothly.
    Any tips would be helpful.

    I have one set of drives set up as Raid 1 and a second set of drives set up as Raid 0. Have tried the video on both sets of drives and get the same problem. Even tried putting the scratch disks on a seperate drive.
    I am runing Windows 7 pro 64 bit, Two 2.66 Ghz quad core processors (not hyper threading) and 12 GB RAM so it is a reasonable sized machine.
    I will double check the drivers for the graphics card but I am sure I have the latest as we only downloaded it last Wednesday (3 days ago).
    This is all starting to sound like a hardware/setup problem in my PC.
    I am sure I have Premiere set up right! The Mercury Engine (GPU mode) is running.
    I am also sure that when I first installed it earlier in the week it was playing OK with the Quadro FX 4800 GPU (maybe I just imagined it). When I first installed CS5 I was running a Nvidia GeForce GTX 280 graphics card, which is not supported, and DSLR video played smoothly on CS5 timeline.
    Things that have changed since I thought it was playing OK with the FX 4800.
    1.     Changed from two Neovo Monitors running via digital output to Two EIZO Monitors running via Display Port output. (tried switching the monitors back - no change)
    2.     Uninstalled Matrox RTX 2 drivers
    3.     Installed Twixtor Pro Version 5
    I don't consider myself a novice with all this  - have been doing this for a number of years (12) but this has me buggered!
    I am about to install CS5 on my laptop (once it has been upgraded to Windows 64 bit) so will be interested to see how video plays on that even though it won't have the Mercury GPU acceleration.
    So for the long diatribe but thought it might be useful.

  • Detecting outdated video drivers?

    Hi folks
    I've just pushed out a large number of updates to a lot of workstations which were EXTREMELY out of date
    And then I got burned by KB2670838 which causes some workstations with out-of-date drivers to crash
    I now have a medium-sized disaster on my hands
    It would be extremely helpful if I could get a list of all my workstations and their video drivers
    Is this possible with Intune?

    OK, that definitely tells me what drivers are installed on a single system
    However it's a highly manual process for one PC. I need to find out pro-actively where a specific incompatible driver has been installed on my network with about 300 workstations
    To do this, I have to click on Groups --> All Devices --> All Computers --> Devices --> right-click a single computer and click "View Properties" --> Hardware and then scroll to Video Controller
    to see if the date on the video driver matches the date on one of the incompatible drivers which I'm trying to eliminate
    This is a pretty manual process and isn't practical when I've got 300 workstations to sort through
    Is there no way to generate a report to extract this data?

  • Unable to install nvidea Video drivers after Bios update - Latitude E6530

    I recently flashed my bios to the newest version
    E6530A16.exe | Windows/DOS (9 MB)
    Release date 23 Oct 2014|Last Updated 23 Oct 2014
    Version A16,A16 
    After that I can't install video drivers.  So I can't connect another monitor to my computer.
    This is the driver I'm trying to install, 
    "nVIDIA Graphics Driver for: Quadro 1/2/3/4000, Quadro 5010M, Quadro K1/2/3/4/5000M, Quadro K11/21/31/41/5100M, NVS 4/5200M, and GeForce GT 720M"
    Version 9.18.13.2762,A07
    I've also tried the Intel driver on the support page.
    I'm running Windows 8.1x64 Professional and am up to date with all Microsoft patches.
    The error I get is "The graphics driver could not find suitable hardware"

    Hi hreinn1000,
    I’d advise that you load defaults in the BIOS. Please follow the steps mentioned below to load the BIOS to defaults to check if the camera gets detected on the system.
    Reboot the computer.
    When prompted during POST, press the <F2> key to enter the setup screen.
    On the System Setup screen, press the <F9> key.
    Press the <Enter> key on Yes to Load Optimized Defaults and restart the computer.
    Also, Also, I would suggest that you run the diagnostics on the computer by following the steps mentioned in the video below and check if there is any issue with the hardware on your system. Please private message us the system service tag so that we could check and assist you further. To send a private message, click on my name and send private message.
    http://dell.to/164l6g4

  • Video drivers issue (dual DVI monitors off bay :: one black and white and one color)

    Hello,
        I have tried everything to try to make these two monitors color. They are both relatively new Dell monitors. Both are DVI, both are connected to the latest Lenovo bay for my T430 laptop. Both worked fine after I initially installed both video drivers (Intel HD Graphics Driver for Windows 7 [64-bit]) and NVIDIA Optimus Display Driver for Windows 7 [64-bit]). Then out of nowhere one of them (Dell 1) decides it wants to be seen in black and white! I initially thought it was the monitor itself, but when swapping monitors (Dell 1, Dell 2) the other monitor  (Dell 2) went black and white when plugged into the DVI formerly used by the Dell 1 monitor. Ok, so now it must be the DVI ports on the bay station (Lenovo) right? Nope. I had a tech bring me a second, brand new bay (identical). Same issue! So this leads me to the video drivers...
    Does anyone have any idea. I disabled each driver and reenabled each to no avail. The drivers are the latest drivers downloaded directly from Lenovo's site. Checked the driver settings/monitor setting using both Windows 7 Professional and Nvidia to see if anything stood out. Nothing.
    Any help would certainly be appreciated. Thank you in advance! :~)

    I got a new laptop and when I plugged it into my docking station the external monitors were all in black & white.  My old computer still worked fine without changing any settings on the monitors.  I found that I needed to go into Control Panel \ NVidia Control Panel \ Display \ Adjust Desktop Color Settings, then select the monitor I wanted to adjust, then set the slider up for Digital Vibrance.  For some reason on the new laptop the NVidia settings defaulted to 0 for this.

  • Dont find the correct video drivers for my T61 + windows 7 ultimate + intel pm965 video card

    Hi Experts,
    I am keep getting the stop error 0x00000116 failing with a blue screen while im browsing. I have observerd this quite a few times and also I could not find the correct video drivers for my t61 thinkpad in the ibm site. I could see the details as wxp & windows vista but not for win 7. Please find the link below which has all the video drivers fro t61. Please help me find the correct customized video drivers fro my t61 + win 7. Hope you understand my problem.
    By the way i just use for home computing and my win 7 is upto date wiht no extra software and games installed. I dont play games at all on my t61.
    my t61 specificaitons : http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67883
    If you see the link http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67853
    if u search in the baove link ,you cannot find the video drivers for t61 + win 7. You have it only for xp & vista in this section. Intel X3100 (940GML, 945GM, GL960, GM965). there are no video drivers for win 7 for t61. my video card info is
    Video chipsets:
    Intel PM965/GM965 graphics. (15.4 inch).
    my video card is Intel PM965 chipset . Please help me to get the correct customized version of the video drivers for my thinkpad as I am getting this problem with video drivers and its getting restarted when I am in the middle of something. But it works find after that. I have tried to install drivers from intel and its saying i have customized version of lenovo drivers and I should contact you guys. I triedcomplete  win 7 update from windows site and installed all patches and still getting the problem intermitently, but after restart it works fine. No hardware or software changes. Its that I need the correct version of video drivers for win 7. Please inform the lenovo about this and ask them to develop the good video drivers for win 7 + t61 model. Hope you understand my situation.
    Please let me know if you need any kind of info so that i can provide.
    thanks for reading the mail.
    Regards,
    Manu

    Are you kidding me ? You dont work for Lenovo and you are an active volunteer here in this forums. I have seen your replied many times and wont get paid by Lenovo, you are really crazy for ur stufee .Anyways thanks a lot for the link and the original lenovo staff were notable to provide the link and you could. Well I have tried that what you have said nd still I could not get the link, here you go..
    http://www-307.ibm.com/pc/support/site.wss/product.do?doccategoryind=50880&template=%2Fproductpage%2...
    Let me install the drivers from your link and I will reply soon, so who ever search in this forum now , there wont be any problems for t61 windows 7 video drivers because of u. You are awsome.wll reply my results soon.

Maybe you are looking for