Ms(8871) and Nvidia driver (44.03) problem

Hi.
I have the Gf4 ti4400 (8871) and ive install the driver 44.03.
My problem is when im Logging in my users account in windows xp. It seem like the card trying to detect all the availlable addapter. when its doing this, the screen is flashing a little bit (like other drivers do) and then im ready to work with the computer. But with this driver (4403) when its flashing a bit, the sound gettin repeattitive like: ta di da-da-da-da-da ti da....
Its a little problem but anoying. It didnt do that with all the drivers before.
Anyone have a solution?
Ghislain

Ok i found the problem.
What i think is that in the 44.03 nvidia change the ay they read the configuration of the monitor attached to the card.
the problem is that i have a old 20 inch monitor t hat use BNC connection and ive read that this kind of connection is not plug and play with the card. So that mean the card can't read the info of the monitopr so the card retry 2-3 time and this is waht causing the flashing et the sound distortion.
How i found this? simple!  i just read what i say to you on the net and ive switch with a monitor with normal plug and it work!!
I dont know if nvidia is aware of this but maybe someone should talk to them about this issue...
I hope this help many user who was in my condition and that tech support is happy to learn somthing from a simple users  :D
Ghislain

Similar Messages

  • Both nouveau and nVidia driver problems with Stellarium

    Stellarium v0.12.4 with either xf86-video-nouveau 1.0.9-1 or nvidia (latest driver) and an nVidia MCP78S (GeForce 8200) chip usually results in either distorted graphics and sometimes complete system lock-up.
    The nVidia driver is worse, nouveau sometimes works but its a crap shoot. This has been going on for about 2 months now, and I have tested both drivers.
    With nouveau it dumps these boot errors, but works on other software just fine:
    Oct 21 17:17:48 eagle kernel: nouveau E[ PBUS][0000:02:00.0] MMIO read of 0x00000008 FAULT at 0x10022c
    Oct 21 17:17:48 eagle kernel: nouveau E[ PBUS][0000:02:00.0] MMIO read of 0x00000008 FAULT at 0x100230
    Oct 21 17:17:48 eagle kernel: nouveau E[ PBUS][0000:02:00.0] MMIO read of 0x00000008 FAULT at 0x1002e4
    I cannot use the nvidia driver in general because it sometimes causes graphics faults when using Chromium.
    I don't get any other graphics issues other than with Stellarium (and obviously I cannot run google-earth with nouveau either).
    Any ideas on where to start with this problem would be appreciated.

    Thanks for answering!
    Following your advice, I downloaded and installed the latest driver from Nvidia (http://www.nvidia.fr/object/notebook-win7-winvista-64bit-260.99-whql-driver-fr.html). I'm not sure this is the one I updated on the first place since I don't remember when I did it (it was a few months ago, and as I had internet without using wi-fi, I didn't see that much the BSOD, but now that I'm back to wi-fi, the problem occurs often). Until now, no BSOD, but the first problem "Display Driver Stopped Responding and Has Recovered" is still here, and a little bit more annoying since it can occurs while watching some video files (it didn't happen before).
    For the BIOS problem, it was the one described on the link you gave, but no the problem is over. I was just thinking it could be relevant to understand the others problems.
    I'll let you know if the BSOD is (or seems) definitively gone. In the meantime, if someone knows how to fix the problem of the display driver that stopped responding and was recovered, it would be greatly appreciated!

  • Windows 8 64-bit install on 970a-g46 Mainboard AHCI and NVIDIA DRIVER issues

    My Box:
    MSI 970A-G46
    BIOS 1.9  (AUG 2012) (Tried 1.11 but the nightmare started then)
    AMD FX-6100 (STOCK SPEED AND SETTINGS) WITH OEM HSF
    16GB PATRIOT VIPER 3 (1866) RUNNING @ (1600)
    USED an EVGA 9800GT 1ST AND UPGRADED TO NVIDIA REFERENCE CARD GTX 550 Ti (1GB) WITH SAME ISSUES
    90gb MonsterDigital Daytona SATA III SSD DRIVE (OS and minimal programs)
    Antec HE 550
    I am at a point of pulling my hair out. I decided to upgrade my system to enhance Diablo III game play. I got a combo deal on the mainboard and cpu, and thought the speed of the game caching on a SSD would also help. The first attempt which took a little struggle was Vista 64-bit. Eventually, I was able to get the OS to work with me, and it was smooth.  Since M$ decided to offer the Windows 8 Pro upgrade for only $39.99, I thought, what do I had to lose. Well….lots of time. Now, I am not a newbie, though SSD drives haven’t been more than an interesting thought. So yes, I read many guides on everything from Trim enabled Win 7 and 8, and many other do’s and don’ts. What is driving me to the Netherlands of hell, is the installation and how buggy it has been. It boils down to drivers for the IDE/SATA/AHCI CONTROLLER. First, even thought it “sees”  the SSD on installation drive selection, after pulling the USB installation drive, the system forgets it, and there is a “problem with the boot sector”. If you load the driver from the AMD site, it lets the install occur “fine”, but there is an issue with that driver which causes an irq conflict which leads to D3 audio issues and freeze ups. I did finally get things in order (not sure which driver I choose for that), and things were smooth, except I tried to install the GTX 550 ti and that led to a corrupt file error, which the system runs a check disk and cycles the “preparing to repair” and “diagnosing PC” a few times and never allows me to enter SAFE MODE (shift+f8), to disable the NVIDIA driver that is buggy, and doesn’t allow for the NVIDIA Control Panel to install without losing video, and starts the repair cycles again… Leading to ANOTHER RE-INSTALL...
    My question, for the Windows 8 Pro installation on the 970a-G46 mainboard and then after install is complete, which driver is the correct choice for the AHCI/SATA Controller?  All I find is Win7 64-bit AHCI inf’s, and SB7XX 64-bit inf’s (no SB950 INF). The Driver disk which came with the mainboard is very dated pre Win 8 stuff, ASMEDIA X106 which are not recognized by the OS as written for Win 8. AMD’s latest drivers are the ones causing the IRQ type lags and corruption.
    What version, build and type of Windows 8 installations have you used on this mainboard, and what drivers allowed you install it without the above conflicts? Your input may decrease my insanity… So, thank you in advance…

    Quote from: m0r9h3u5 on 28-January-13, 12:11:16
    I understand what you are telling me,  only the generic drivers deliver subpar results. What is the point of running those drivers instead of windows 8 certified drivers written for said devices. My last install is functioning better, but still windows update fails every attempt, the apps i install (ie. weather bug) on the start screen wont load... to me windows 8 is a big fail....but that is just my view...
    OK...I also own the 970a G46, and my upgrade experience from Win7 x64 AHCI to Win8 x64 AHCI was flawless the first time.  No problems at all.  You are running an AMD chipset board with a nVidia gpu, which means that your chipset drivers are not automatically updated with every gpu driver update you do--this would happen automatically if you owned an AMD gpu because AMD includes them in its gpu driver install packages.  But--all you have to do to get the proper drivers for your motherboard is go here and download them.  You only need the *chipset drivers* from this page--you do not need the RAID drivers, of course.  That's it.  It's no big deal, and back in the days when nVidia was making motherboard chipsets you had to separately download both the motherboard chipset drivers from nVidia and the AMD gpu drivers from AMD if you did not also own a nVidia gpu.
    From your description of your problems it sounds like your installation of Win8 is hosed and you need to format C:\ and clean install from scratch, anyway, so...
    A note about AHCI--the *ideal* way to install the AHCI drivers is prior to installing your OS for the first time, you enter the UEFI and set "AHCI" in the appropriate place, instead of IDE, and *then* you reboot from DVD and install your OS which will automatically install the correct AHCI driver from Windows.  After the driver installation is complete you should then install the updated 970a drivers from AMD as linked above.
    However, it is actually very easy to activate and install AHCI *after* you have installed Windows in normal IDE mode:
    To enable AHCI in existing Windows 8 IDE Installation's
    Caution: Do NOT enable AHCI in UEFI prior to making the following changes in your Registry! If you had AHCI enabled alreadyin UEFI, disable it first and restart your computer!
    Use WinKey + R and type Regedit in the command line and hit the Enter key, this will open the Registration Editor.
    Go to:
        HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/iaStorV
        right click on Start, select Modify and set Data Value to 0
    Close Registration Editor and restart computer.
    While booting,  open the UEFI Page and set the SATA Mode to AHCI from IDE
    Save UEFI settings and restart.
    Windows will now install the AHCI drivers automatically and they should work without issues.
    In order to avoid installation problems just like you have been experiencing, here is what I would do in your shoes:
    1) Set UEFI for normal IDE drive mode
    2) Reboot into IDE mode and install your OS
    3) After you have finished with the installation, you should be having no troubles in IDE mode.  Then go to the instructions above on how to properly enable AHCI *after* you have installed Windows 8 in normal IDE mode.
    4) After everything is coming up roses in AHCI mode and you are having no problems, then install the AMD chipset drivers as linked above and you are golden. 
    Those 4 steps worked perfectly for me the first time (the first time I got them right, that is...).
    There's nothing wrong with Win8--this is strictly operator error caused by insufficient research into what AHCI is and how to properly enable it.  The Internet has some bad info on Win8 registry settings for AHCI because of the developer preview and the consumer preview versions of Win8 that Microsoft released to the public prior to the final shipping build--many "instructions" for Win8 are therefore not valid for the shipping version of Win8.  At first I made some of the same goofs that you did, but now you get to benefit from my hard-won experience...  Good luck! Should work like a charm. And, registry AHCI is done differently in Win8 than it is done in Win7 or Vista.  Also, the registry settings relative to AHCI in Windows 8 for AMD are different from the registry values that must be changed for an Intel controller.
    Parenthetically, My FX-6300 (Vishera) will be here in a couple of days! Yeah!

  • Photoshop CC 14.2.1 and NVidia GTX 660 Display Problems

    I'm having exactly this problem:
    http://forums.adobe.com/message/6264980
    The fix documented at the end of that thread works but the penalty is a loss of performance. In an attempt to fix it, I updated to the latest drivers from NVidia for the GTX 660 and as a result, further problems occur:
    This sometimes happens when using the crop and straighten tool at 100%.
    More often though, irrespective of zoom settings I get:
    This happens quite frequently with the dust and scratches/surface blur tools too. Or even on occasion when duplicating a layer or merging layers.
    The following gets written out to the event log:
    Faulting application name: Photoshop.exe, version: 14.2.1.570, time stamp: 0x52f4a9f2
    Faulting module name: Photoshop.exe, version: 14.2.1.570, time stamp: 0x52f4a9f2
    Exception code: 0xc0000005
    Fault offset: 0x00000000016544bf
    Faulting process ID: 0x274
    Faulting application start time: 0x01cf4c3a592b4439
    Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Photoshop.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Photoshop.exe
    Report ID: d2d101ed-b82d-11e3-bea9-d43d7e2000a1
    Faulting package full name:
    Faulting package-relative application ID:
    For now I'm using the following work around but with some performance penalty:
    Drawing mode: Basic (resolves the issue with mask overlay being patchy and rendering slowly at 100% zoom)
    OpenCL: Disabled (resolves Photoshop crashing with crop/straighten and other tools as described above)
    This needs to be fixed! The reduced performance increases the time I spend editing, particularly a large product shoot undertaken recently for a client.
    System Info:
    Adobe Photoshop Version: 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
    Operating System: Windows 8 64-bit
    Version: 6.2
    System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Physical processor count: 4
    Logical processor count: 8
    Processor speed: 3392 MHz
    Built-in memory: 16344 MB
    Free memory: 12183 MB
    Memory available to Photoshop: 14600 MB
    Memory used by Photoshop: 70 %
    Image tile size: 1024K
    Image cache levels: 4
    Font Preview: Medium
    TextComposer: Latin
    Display: 1
    Display Bounds: top=0, left=0, bottom=1200, right=1920
    Display: 2
    Display Bounds: top=418, left=1920, bottom=1318, right=3360
    OpenGL Drawing: Enabled.
    OpenGL Allow Old GPUs: Not Detected.
    OpenGL Drawing Mode: Advanced
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    AIFCoreInitialized=1
    AIFOGLInitialized=1
    OGLContextCreated=1
    NumGPUs=1
    gpu[0].OGLVersion="3.0"
    gpu[0].MemoryMB=1536
    gpu[0].RectTextureSize=16384
    gpu[0].Renderer="GeForce GTX 660/PCIe/SSE2"
    gpu[0].RendererID=4485
    gpu[0].Vendor="NVIDIA Corporation"
    gpu[0].VendorID=4318
    gpu[0].HasNPOTSupport=1
    gpu[0].DriverVersion="9.18.13.3523"
    gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
    gpu[0].DriverDate="20140304000000.000000-000"
    gpu[0].CompileProgramGLSL=1
    gpu[0].TestFrameBuffer=1
    gpu[0].OCLPresent=1
    gpu[0].OCLVersion="1.1"
    gpu[0].CUDASupported=1
    gpu[0].CUDAVersion="6.0.1"
    gpu[0].OCLBandwidth=1.06425e+011
    gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
    gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
    gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
    gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
    gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
    gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
    gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
    gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
    gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
    gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
    gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
    gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
    gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
    gpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
    gpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
    License Type: Subscription
    Serial number: 90970661089720248614
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\
    Temporary file path: C:\Users\Daniel\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      D:\, 2.64T, 2.47T free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Required\Plug-Ins\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Plug-ins\
    Installed components:
       ACE.dll   ACE 2013/10/29-11:47:16   79.548223   79.548223
       adbeape.dll   Adobe APE 2013/02/04-09:52:32   0.1160850   0.1160850
       AdobeLinguistic.dll   Adobe Linguisitc Library   7.0.0  
       AdobeOwl.dll   Adobe Owl 2013/10/25-12:15:59   5.0.24   79.547804
       AdobePDFL.dll   PDFL 2013/10/29-11:47:16   79.508720   79.508720
       AdobePIP.dll   Adobe Product Improvement Program   7.0.0.1786  
       AdobeXMP.dll   Adobe XMP Core 2013/10/29-11:47:16   79.154911   79.154911
       AdobeXMPFiles.dll   Adobe XMP Files 2013/10/29-11:47:16   79.154911   79.154911
       AdobeXMPScript.dll   Adobe XMP Script 2013/10/29-11:47:16   79.154911   79.154911
       adobe_caps.dll   Adobe CAPS   7,0,0,21  
       AGM.dll   AGM 2013/10/29-11:47:16   79.548223   79.548223
       ahclient.dll    AdobeHelp Dynamic Link Library   1,8,0,31  
       aif_core.dll   AIF   5.0   79.534508
       aif_ocl.dll   AIF   5.0   79.534508
       aif_ogl.dll   AIF   5.0   79.534508
       amtlib.dll   AMTLib (64 Bit)   7.0.0.249 BuildVersion: 7.0; BuildDate: Thu Nov 14 2013 15:55:50)   1.000000
       ARE.dll   ARE 2013/10/29-11:47:16   79.548223   79.548223
       AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
       AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
       Bib.dll   BIB 2013/10/29-11:47:16   79.548223   79.548223
       BIBUtils.dll   BIBUtils 2013/10/29-11:47:16   79.548223   79.548223
       boost_date_time.dll   DVA Product   7.0.0  
       boost_signals.dll   DVA Product   7.0.0  
       boost_system.dll   DVA Product   7.0.0  
       boost_threads.dll   DVA Product   7.0.0  
       cg.dll   NVIDIA Cg Runtime   3.0.00007  
       cgGL.dll   NVIDIA Cg Runtime   3.0.00007  
       CIT.dll   Adobe CIT   2.1.6.30929   2.1.6.30929
       CITThreading.dll   Adobe CITThreading   2.1.6.30929   2.1.6.30929
       CoolType.dll   CoolType 2013/10/29-11:47:16   79.548223   79.548223
       dvaaudiodevice.dll   DVA Product   7.0.0  
       dvacore.dll   DVA Product   7.0.0  
       dvamarshal.dll   DVA Product   7.0.0  
       dvamediatypes.dll   DVA Product   7.0.0  
       dvaplayer.dll   DVA Product   7.0.0  
       dvatransport.dll   DVA Product   7.0.0  
       dvaunittesting.dll   DVA Product   7.0.0  
       dynamiclink.dll   DVA Product   7.0.0  
       ExtendScript.dll   ExtendScript 2013/10/30-13:12:12   79.546835   79.546835
       FileInfo.dll   Adobe XMP FileInfo 2013/10/25-03:51:33   79.154511   79.154511
       filter_graph.dll   AIF   5.0   79.534508
       icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615  
       icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615  
       imslib.dll   IMSLib DLL   7.0.0.145  
       JP2KLib.dll   JP2KLib 2013/10/29-11:47:16   79.248139   79.248139
       libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)  
       libiomp5md.dll   Intel(R) OMP Runtime Library   5.0  
       libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0  
       LogSession.dll   LogSession   2.1.2.1785  
       mediacoreif.dll   DVA Product   7.0.0  
       MPS.dll   MPS 2013/10/29-11:47:16   79.535029   79.535029
       msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428  
       msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1  
       msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428  
       msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1  
       msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428  
       msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       PatchMatch.dll   PatchMatch 2013/10/29-11:47:16   79.542390   79.542390
       pdfsettings.dll   Adobe PDFSettings   1.04  
       Photoshop.dll   Adobe Photoshop CC   CC  
       Plugin.dll   Adobe Photoshop CC   CC  
       PlugPlugOwl.dll   Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit)   4.2.0.36  
       PSArt.dll   Adobe Photoshop CC   CC  
       PSViews.dll   Adobe Photoshop CC   CC  
       SCCore.dll   ScCore 2013/10/30-13:12:12   79.546835   79.546835
       ScriptUIFlex.dll   ScriptUIFlex 2013/10/30-13:12:12   79.546835   79.546835
       svml_dispmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0  
       tbb.dll   Intel(R) Threading Building Blocks for Windows   4, 1, 2012, 1003  
       tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   4, 1, 2012, 1003  
       updaternotifications.dll   Adobe Updater Notifications Library   7.0.1.102 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   7.0.1.102
       WRServices.dll   WRServices Mon Feb 25 2013 16:09:10   Build 0.19078   0.19078
    Required plug-ins:
       3D Studio 14.2.1 (14.2.1 x001)
       Accented Edges 14.2.1
       Adaptive Wide Angle 14.2.1
       Angled Strokes 14.2.1
       Average 14.2.1 (14.2.1 x001)
       Bas Relief 14.2.1
       BMP 14.2.1
       Camera Raw 8.3
       Camera Raw Filter 8.3
       Chalk & Charcoal 14.2.1
       Charcoal 14.2.1
       Chrome 14.2.1
       Cineon 14.2.1 (14.2.1 x001)
       Clouds 14.2.1 (14.2.1 x001)
       Collada 14.2.1 (14.2.1 x001)
       Color Halftone 14.2.1
       Colored Pencil 14.2.1
       CompuServe GIF 14.2.1
       Conté Crayon 14.2.1
       Craquelure 14.2.1
       Crop and Straighten Photos 14.2.1 (14.2.1 x001)
       Crop and Straighten Photos Filter 14.2.1
       Crosshatch 14.2.1
       Crystallize 14.2.1
       Cutout 14.2.1
       Dark Strokes 14.2.1
       De-Interlace 14.2.1
       Dicom 14.2.1
       Difference Clouds 14.2.1 (14.2.1 x001)
       Diffuse Glow 14.2.1
       Displace 14.2.1
       Dry Brush 14.2.1
       Eazel Acquire 14.2.1 (14.2.1 x001)
       Embed Watermark 4.0
       Entropy 14.2.1 (14.2.1 x001)
       Extrude 14.2.1
       FastCore Routines 14.2.1 (14.2.1 x001)
       Fibers 14.2.1
       Film Grain 14.2.1
       Filter Gallery 14.2.1
       Flash 3D 14.2.1 (14.2.1 x001)
       Fresco 14.2.1
       Glass 14.2.1
       Glowing Edges 14.2.1
       Google Earth 4 14.2.1 (14.2.1 x001)
       Grain 14.2.1
       Graphic Pen 14.2.1
       Halftone Pattern 14.2.1
       HDRMergeUI 14.2.1
       IFF Format 14.2.1
       Ink Outlines 14.2.1
       JPEG 2000 14.2.1
       Kurtosis 14.2.1 (14.2.1 x001)
       Lens Blur 14.2.1
       Lens Correction 14.2.1
       Lens Flare 14.2.1
       Liquify 14.2.1
       Matlab Operation 14.2.1 (14.2.1 x001)
       Maximum 14.2.1 (14.2.1 x001)
       Mean 14.2.1 (14.2.1 x001)
       Measurement Core 14.2.1 (14.2.1 x001)
       Median 14.2.1 (14.2.1 x001)
       Mezzotint 14.2.1
       Minimum 14.2.1 (14.2.1 x001)
       MMXCore Routines 14.2.1 (14.2.1 x001)
       Mosaic Tiles 14.2.1
       Multiprocessor Support 14.2.1 (14.2.1 x001)
       Neon Glow 14.2.1
       Note Paper 14.2.1
       NTSC Colors 14.2.1 (14.2.1 x001)
       Ocean Ripple 14.2.1
       Oil Paint 14.2.1
       OpenEXR 14.2.1
       Paint Daubs 14.2.1
       Palette Knife 14.2.1
       Patchwork 14.2.1
       Paths to Illustrator 14.2.1
       PCX 14.2.1 (14.2.1 x001)
       Photocopy 14.2.1
       Photoshop 3D Engine 14.2.1 (14.2.1 x001)
       Photoshop Touch 14.0
       Picture Package Filter 14.2.1 (14.2.1 x001)
       Pinch 14.2.1
       Pixar 14.2.1 (14.2.1 x001)
       Plaster 14.2.1
       Plastic Wrap 14.2.1
       PNG 14.2.1
       Pointillize 14.2.1
       Polar Coordinates 14.2.1
       Portable Bit Map 14.2.1 (14.2.1 x001)
       Poster Edges 14.2.1
       Radial Blur 14.2.1
       Radiance 14.2.1 (14.2.1 x001)
       Range 14.2.1 (14.2.1 x001)
       Read Watermark 4.0
       Reticulation 14.2.1
       Ripple 14.2.1
       Rough Pastels 14.2.1
       Save for Web 14.2.1
       ScriptingSupport 14.2.1
       Shake Reduction 14.2.1
       Shear 14.2.1
       Skewness 14.2.1 (14.2.1 x001)
       Smart Blur 14.2.1
       Smudge Stick 14.2.1
       Solarize 14.2.1 (14.2.1 x001)
       Spatter 14.2.1
       Spherize 14.2.1
       Sponge 14.2.1
       Sprayed Strokes 14.2.1
       Stained Glass 14.2.1
       Stamp 14.2.1
       Standard Deviation 14.2.1 (14.2.1 x001)
       STL 14.2.1 (14.2.1 x001)
       Sumi-e 14.2.1
       Summation 14.2.1 (14.2.1 x001)
       Targa 14.2.1
       Texturizer 14.2.1
       Tiles 14.2.1
       Torn Edges 14.2.1
       Twirl 14.2.1
       Underpainting 14.2.1
       Vanishing Point 14.2.1
       Variance 14.2.1 (14.2.1 x001)
       Variations 14.2.1 (14.2.1 x001)
       Water Paper 14.2.1
       Watercolor 14.2.1
       Wave 14.2.1
       Wavefront|OBJ 14.2.1 (14.2.1 x001)
       WIA Support 14.2.1 (14.2.1 x001)
       Wind 14.2.1
       Wireless Bitmap 14.2.1 (14.2.1 x001)
       ZigZag 14.2.1
    Optional and third party plug-ins: NONE
    Plug-ins that failed to load: NONE
    Flash:
       Mini Bridge
       Kuler
       Adobe Exchange
    Installed TWAIN devices: NONE

    My advice:  Rather that wait hopefully, try some alternate configuration settings.
    Specifically, go into your Preferences - Performance - Advanced Settings panel, and try the different options there, making sure to close Photoshop and restart it after each change, then test.
    It's possible Photoshop asked the nVidia display driver what it can do, and it said it could do something very advanced, but in the driver implementation some part of that advanced operation is run in the CPU, not the GPU.  NVidia has been known to do this!
    Thus it may be that if you choose a lesser drawing mode or change something (e.g., 30 bit display) you might find that particular combination of settings makes things run faster.
    -Noel

  • Error 36 and External Drive File Copy Problem & USB Connections

    In attempting to copy a folder with some 200G+ of files from my iMAC, with OSX 10.6.7, to an external portable WD 1Tb HD, newly formatted to HFS+ (journaled), and connected to the iMAC via a USB cable to the USB port on the iMAC keyboard, I kept getting an error message that Finder could not complete the operation as some data couild not be read or written and transfered, and gave the "Error Code -36". After some searching ont he internet for this error code I came across a host forums discussiong the error code BUT all referred to it being the result of MAC OS hidden "dot-underscore" companioned files being created when the MAC OS X file system copies or moves files to a FAT16 or FAT32 volume. This was not the situaion in my case a both drives were OS X formatted HFS+. Eventually I came across a very vague reference to the error also occuring when the cable connection with the external HD was not solid. I reconnected my external HD and attempted the file transfer again - with the same result. Eventually I decided to plug the external HD into a USB pot on the back of the iMA itself, rather than the keyboard set. Sure enough the error issue disappeared - the transfer successfully completed.
    So my question relates to the "usb connection" challenge with iMAC. the iMAC has only 4 USB ports on the back directly. I did have two desktop external HDs plugged into 2 of these USB ports at the back of the iMAC, as well as a WACOM pad device into the 3rd, and an EPSON 3880 printer into the 4th, and so was forced to employ the ports ont he keyboard for portable HD. So - what's the answer in a situation where the 4 are insufficient and it would appear that the keyboard ports seemed to be unpowered?? Any suggestions?

    It's actually a Time Machine backup drive which is formatted in Mac OS Extended (Journaled). I wish I'd copied the exact error message.
    I believe it was something to the effect of "Error 36: The file could not be copied because some of the date could be be read/written" or something along those lines. Next time it comes up I'll copy it. I have Drive Genius running with DrivePulse, but it doesn't ever seem to start.
    My biggest concern is that this is a sign that the drive is failing. When backing up, it also slows, or stops midway through and just hangs there. Though I haven't done a lot of extensive testing on that because if the drive is failing, I don't want to speed that process up any more.
    To add to the complication, there is a second external drive which Time Machine is also backing up for me. There is one particular file, the Virtual Machine file, I was trying to get off the other external drive and it produced the same problem. That's when I went into Time Machine to try and retrieve the file that way and it did the same thing. The other external drive is making some sounds, but it doesn't sound like a distinct clicking, more like a more pronounced version of the normal constipated hard-drive sound. The Time Machine drive, isn't making any obviously strange sounds at all.
    So, I can't tell whether the drives are failing or if it could actually be that particular file itself causing some strange problems.

  • Macbook shuts off during start-up - can't get through safe-mode, single user mode (fsck -fy) and target-drive shows no problems when running disk utility repair

    Hi everyone,
    I'm simply all out of ideas on what to do - my best guess is the problem is not specifically hard-drive related since all the 'normal' fixes just won't work.
    What could be the cause of my issue? The only way i've managed to keep the Macbook Pro on for longer than a minute is through target drive, where it seems to work just fine - i can access everything. To sum up everything:
    1 - I tried resetting the PRAM
    2 - I tried to go in to safe mode, it shut off before i could type the password
    3 - I tried fsck -fy command from single user mode, sometimes i can get to actually typing it but mostly it shuts off before
    4 - I tried to repair disk via target drive - success, no problems detected (and it didnt fix my issue)
    5 - I reinstalled OS Mavericks.
    The Macbook Pro previously had some problems with the power-button not working properly (a mac-cunning friend of mine had to open up the mac and start it by swiping to metal pins on a specific (battery/power?) part inside it. The problem kinda went away afterwards but it might be related to this?
    This is way off my comfort zone of 'diagnosing' issues, so I'm crossing fingers for some good advice.
    Thanks,
    Aske
    Denmark

    I think you're right.
    If it's hardware related, is it possible to guess at what it might be? It would be nice to know how much I should expect to pay for a repair before actually getting it fixed.

  • T61 nvidia driver causes font problems

    after my last update a new graphics driver for the nvidia quadro 140m was installed.
    the new version (7618) caused bad problems with my fonts. (they could not been displayed)
    -> only squares for each letter 
    it took me a have day to find out, that it was the graphic driver (i didn't expected that).
    After I reinstalled my fontexplorer and repared my windows installation several times,
    it took me another half day to find the download to the old driver again. (7471)
    ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/7kd165ww.exe
    now it works again with the old driver and i hope there will be an update and at least a notice in the thinkpad system update.
    frustrated greets. 

    Hi Puschl636,
    I had a similar problem. I have 3.03a of the presentation director and the most current display driver.
    If I boot with dual screens, the first time I do it, I have to open the lid to the laptop and then close it after startup and it will usually move to the dual screen profile.
    It may be a temp fix, but after that, as long as I have it docked, the dual screens come up.
    Hope that helps!
    Roy 

  • Premiere pro cc and nvidia driver crash... why?

    Hi guys
    Since my new PC configuration, I've been having difficulties making my graphics card (Gygabyte Geforce GTX 650 Ti) enable the mercury playback engine cuda on premiere pro cc. it works for a few moments or it renders 2 3 minutes of my video and vith video hardware acceleration, but after that the video driver crashes and the rendering process and premiere as well. i have the latest driver from nvidia, but also have tried with drivers as old as 310.70 (released december 2012). i use wi 7 sp1, my cpu is intel's [email protected] and intel z77 chipset with 16GB of ram if this is of any relevance. Any ideas on what's the cause of the problem or how i may fix it? (the same thing also happened with premiere pro cs6)
    Thanks for your help !

    From Tweakers Page - Balanced Systems
    What about the amount of VRAM?
    As a rough guide, how much VRAM should be installed on the video card, think along these lines:
    For SD material, 1 GB is enough
    For HD material, go for 1 - 2 GB
    For 3K or 4K, go for 2 - 4 GB
    For 5K+, go for 4 - 6 GB
    Keep in mind that the requirements can vary significantly, depending on the complexity of the timeline. If it happens that the VRAM is depleted (not enough memory), hardware MPE is automatically turned off rather ungracefully and stays off for the rest of the encoding. If you use two video cards in CC, each card uses its own memory and cannot use the memory on the second card. The encoding process works like this: Frame 1 rendered on card 1, frame 2 rendered on card 2, frame 3 rendered on card 1, etc. If either card runs out of memory, again hardware MPE is turned off. Simply put, two video cards with 1 GB each can not be treated as a single card with 2 GB, so the risk of turning off hardware MPE automatically is bigger with these two cards than with a single card.

  • Windows 7 and Nvidia driver installation time-out

    Hey everyone... I'm having issues installing my drivers...
    I've overclocked the 9600 GPU in my 15" unibody quite some time back in windows vista. The thing is, after moving to windows 7, the official drivers from nvidia dont seem to install right. The hang for about 5 to 10 minutes and eventually finish, without completely installing the drivers.
    I've tried manual installations only to receive a "operation timed-out" reply from the windows driver update dialogue. Is there anything anyone can help me out with? Anyone going through the same **?
    I don't want to use drivers from "laptopvideo2go" however... they seem to install correctly but there's something about them that bugs me...
    Thanks in advance!
    Gordo!

    Hey everyone... I'm having issues installing my drivers...
    I've overclocked the 9600 GPU in my 15" unibody quite some time back in windows vista. The thing is, after moving to windows 7, the official drivers from nvidia dont seem to install right. The hang for about 5 to 10 minutes and eventually finish, without completely installing the drivers.
    I've tried manual installations only to receive a "operation timed-out" reply from the windows driver update dialogue. Is there anything anyone can help me out with? Anyone going through the same **?
    I don't want to use drivers from "laptopvideo2go" however... they seem to install correctly but there's something about them that bugs me...
    Thanks in advance!
    Gordo!

  • MBP i5 15" Nvidia driver for Bootcamp problem

    I have performed the following, please advise if i missed something:
    1. installed windows 7 through bootcamp assisant
    2. installed snow leopard drivers for windows
    3. downloaded and installed bootcamp 3.1
    4. removed windows 7 and repeated steps 1-3 (to trouble-shoot)
    WIndows 7 does not regonise the 256MB Nvidia GT 330M in my MBP. What have i done wrong? i don't understand. Please help.

    Uninstall the device driver for the GT330M.
    Well, let's see, you have to install old buggy not official supporting Windows 7 drivers that came out last summer before the RTM, before you can update to BC 3.1, unlike any PC where you just install the latest motherboard drivers.
    As long as the Assistant prepares a proper Master Boot Record and offset, then Windows 7 should install. It is only after installing that anything actually from Apple gets installed and that is where there can be trouble. Newer Macs have later device drivers but they aren't posted and there is no 3.1+ or 3.2.
    You did everything correctly. Support is weak.

  • Any known problems with 2.6.32.5 kernel, xorg 1.7.3.902 and nvidia 190

    Hi everybody.
    Last update I did was when xorg 1.7.x (where x is between 1 and 3, dont remember), and it broke my xorg, I had some glitches with graphics, and x randomly crashed.
    Now xorg 1.7.3, kernel 2.6.32.5 and nvidia 190.53 is here for pretty long time and as arch suer I feel committed to update
    So i read the forum here a bit, and havent found any particular issues that broke the system, but I want to be safe.
    I got nvidia geforce 6600 agp if it does matter.
    So is there any particular issues that can arise after updating?
    Thanks a lot!

    Similar problem here, after updating xorg and nvidia driver the system freezes with nvidia logo on display and caps lock and scroll lock leds blinking.
    I got nvidia geforce 7300.
    Any solution to this besides downgrading?

  • Error message (GT8500- WindowsXP) "affichage defect" because NVIDIA driver (installed 340.52 updated), but 8500GT/PCIe/SSE2 3.3.0 required by Adobe Premiere 10 message ?? What is the problem ? Thank you for help.

    Pourquoi ce message, car le driver de la carte Nvidia GT8500 est à jour !

    fclau
    There is a known major issue with Premiere Elements 10 on a computer that uses a NVIDIA GeForce video card/graphics card. The answer is to roll back the driver version to about May 2013. You do not want an up to date driver in this case. For some computer operating systems like Windows 8 or 8.1 64 bit, this roll back fix is not possible because the video card/graphics card driver versions available do not go back far enough.
    This matter has been written about extensively in this forum for over a year. And, there is an Announcement about this matter at the top of this forum.
    Also see
    ATR Premiere Elements Troubleshooting: PE10: NVIDIA Video Card Driver Roll Back
    and
    NVIDIA Driver Downloads - Advanced Search
    which will help you identify the driver version and download/install it.
    According to what you wrote and assuming that your Windows XP is SP3 32 bit, your NVIDIA drivers page should look like this after you plug in your data.
    And based on history, your choice in the above should be GeForce 320.18 Driver    320.18 May 23, 2013.
    Please review and consider. And, then let us know if we have interpreted your information correctly.
    Thank you.
    ATR

  • N560GTX-Ti Twin Frozr II/OC freezes and got a nVidia driver recover

    Greetings from Taiwan, issue here, just bought it a week ago, N560GTX-Ti Twin Frozr II/OC freezes and get a lot of glitches, had a black screen and nVidia driver failed during watching a movie or youtube, s/n is as below:
    602-V238-16SB1101160284
    (Idle)
    Core Clock: 880MHz
    Shader Clock: 1760Mhz
    Memory Clock: 2100MHz
    Fan Speed: 40%
    # CPU brand: Intel Q6700 2.6GHz OC 3.4GHz
    # Motherboard model: ASUS P5K3-Deluxe
    # Memory brand: GSkill DDR-3 1333 2G*2
    # Video card brand: N560GTX-Ti Twin Frozr II/OC
    # Hard drive(s): Seagate 1TB * 3 SATAII-7200RPM
    # Sound Card: Creative Fata1ity Platium Pro PCI-E version
    # Operating system and version: Windows 7 SP1 64bit
    # Power Supply Unit brand and output in watts and DC output: Seven-Team 750W

    @drugstocowboy
    Do not hijack other people topics! >>Please read and comply with the Forum Rules.<<
    Read >>Posting Guide<< then open new own topic.

  • Stock kernel isn't compatible with nvidia-dkms and nvidia-hook?

    Hello pals
    I'm using linux-ice, linux-lqx and linux-ck kernels with nvidia-dkms and nvidia-hook. Everything is ok, with kde upping.
    I've started from stock kernel. During the dkms (or hook, I don't remember) pacman says that nvidia and nvidia(dkms or hook) were incompatible... remove nvidia? I've selected yes
    After it, stock kernel don't upps the kde... stays on black screen. Login on tty1, 2 or 3 is possible, with ctrl+alt+F1...F3, but, kde with kernel don't works
    no errors appears.
    to force stock kernel been compiled by hook, I wait a while, when using the other kernels, and yesterday I did a "Syyu"
    new kernel, new linux-headers too... but still blank screen
    I only can use stock kernel and Nvidia driver, not dkms/hook installed one?

    Ok, i know little about dkms / mkinitcpio hooks , but best option seems to try and build the nividia module manually to get more info.
    nvidia-hook gets sources from here : https://github.com/alucryd/mkinitcpio-hooks/ ,
    build ()
    _version=$(pacman -Qs '^nvidia$'|sed 's/^[^ ]* \|-[0-9]*$//g;2d')
    echo "Building nvidia modules for ${KERNELVERSION} kernel..."
    dkms install nvidia/${_version} -k ${KERNELVERSION}/_arch
    echo "Ok."
    help ()
    cat<<HELPEOF
    This hook rebuilds nvidia modules. It does nothing to the initrd image.
    HELPEOF
    looks like all the hook does is run dkms install, try running that command manually to get more info.

  • Y510p and problem with Update Nvidia Driver

    Hi everyonei have problem with updating my y510p lenovo laptop nvidia driver ,my current nvidia driver version is 327.62 which i download from lenovo website,Now for better performance in new games like gta v and witcher3 ,i decide to updating nvidia driver,first remove my nvidia graphic driver from add or remove then download nvidia ver 350 from nvidia official web site , which nvidia website confirm it support my graphic card which is Gt755m , then i install new ver and during install i check clean install , after successful install , restart laptop , then there was problem . when i try to open nvidia control panel it wont running and an error showed up and said "You are not currently using a display attached to an NVIDIA GPU" .i try to open a game , game running in really low fps and i find out game run on hd graphic of my laptop and my nvidia graphic wont run .The only way to repair was i install my last nvidia driver 327.62 and run a system restore .guys what is your suggestion and how i can update my y510p nvidia driver ?Thanks   

    Hi Y510Man,
         The video graphics installation order is important. You need to install the Intel Graphics first, and then do the Nvidia. IIRC you should un-install the Nvidia driver, then re-install (or upgrade) the Intel HD Graphics driver. Reboot, and install the new Nvidia driver.
         I don't know why, but every time I upgraded my Y470 Nvidia driver, I had to use this procedure. First install, or re-install, the Intel driver, then install the Nvidia. You can't just upgrade the Nvidia driver without a re-install of the Intel. I think it has to do with the Optimus setting, and the automatic switching.
        Let us know how it goes.
    Cheers
    DragonRider

Maybe you are looking for