What has happened to my Graphics Card (GTX-670)

Hi there,

Two days ago I was playing Modern Warfare 2, had to pause, returned after 10 mins and the screen was black. Had to force shut down on my PC. On starting it again, green and red dots appeared all over the display.
The Windows 7 device manager told me there is a code 43 error with my Nvidia GTX 670.
I also cannot find my monitor in the device manager (LG IPS235).

I compiled the pc with help from someone in on this forum last summer and bought it from CCLonline. I also contacted them but until now I was only told that a code 43 is an unspecific error.

I tried update, uninstalling, re-installing the Nvidia drivers. The only time the dots disappeared was after I uninstalled HD audio, video and graphics drivers. I'm running the pc this way right now - no dots!

However, I still cannot use my GPU and my monitor won't show either.
Can anyone help me, please?!

Biba

P.S. The guy from CCLonline asked for my system specifications, so I send him a dxdiag file I attach to this post, too.

------------------
System Information
------------------
Time of this report: 7/14/2012, 17:45:12
Machine name: BENJAMIN-PC
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120503-2030)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: To be filled by O.E.M.
BIOS: BIOS Date: 02/21/12 15:12:36 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.8GHz
Memory: 8192MB RAM
Available OS Memory: 8152MB RAM
Page File: 1932MB used, 14371MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode


---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 670
Manufacturer: NVIDIA
Chip type: GeForce GTX 670
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1189&SUBSYS_28401462&REV_A1
Display Memory: 4043 MB
Dedicated Memory: 1995 MB
Shared Memory: 2047 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: IPS235
Monitor Id: GSM587D
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0013.0125 (English)
Driver Version: 8.17.13.125
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 4/4/2012 15:30:00, 17984320 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
42 answers Last reply
More about what happened graphics card
  1. Install chipset driver.
    and Update windows .Automatically detect and install latest best driver and fix all issues.
    Update bios.
    Update hdd/ssd firmware.
    Update Gpu firmware .
    Full Scan system with "SUPERANTISPYWARE" Freeware.
  2. That`s a heck of a long post, but I guess you were thorough.
    Anyway as a note it looks like the Direct x files have srcewed up in windows. You may want to try to re install Direct X. The card its self is Reporting as working since the Gpu is listed and the memory size is also, Plus the Nvidia drivers are all installed.
    So there must be corrupted Dx files that may be causing the problem.
  3. have you tried running sfc /scannow to see if you have any errors?

    open command prompt as administrator

    type sfc /scannow and press enter

    theres a space between sfc and /scannow
    have you tried driver sweeper?

    http://www.guru3d.com/content_page/guru3d_driver_sweeper.html

    uninstall nvidia drivers then run this

    reboot in safe mode run sweeper again

    then install new driver

    also right click nvidia driver installer and run as administrator
    Full Scan system with http://majorgeeks.com/download.php?det=5756
  4. bigcyco1 said:
    have you tried running sfc /scannow to see if you have any errors?

    open command prompt as administrator

    type sfc /scannow and press enter

    theres a space between sfc and /scannow
    have you tried driver sweeper?

    http://www.guru3d.com/content_page/guru3d_driver_sweeper.html

    uninstall nvidia drivers then run this

    reboot in safe mode run sweeper again

    then install new driver

    also right click nvidia driver installer and run as administrator
    Full Scan system with http://majorgeeks.com/download.php?det=5756


    Hi bigcyco,

    I ran sfc/ scannow but it couldn't find any errors.
    I uninstalled all Nvidia drivers, ran driver sweeper twice (incl. once in safe mode), downloaded and installed the recent Nvidia driver package (310.70). On reboot green and red dots reappeared.
    I did a full scan with Mbam but only found this
    Malwarebytes Anti-Malware (Trial) 1.70.0.1100
    www.malwarebytes.org

    Database version: v2012.12.30.07

    Windows 7 Service Pack 1 x64 NTFS
    Internet Explorer 9.0.8112.16421
    Benjamin :: BENJAMIN-PC [administrator]

    Protection: Enabled

    30/12/2012 15:08:14
    mbam-log-2012-12-30 (15-08-14).txt

    Scan type: Full scan (C:\|Q:\|)
    Scan options enabled: Memory | Startup | Registry | File System | Heuristics/Extra | Heuristics/Shuriken | PUP | PUM
    Scan options disabled: P2P
    Objects scanned: 430995
    Time elapsed: 44 minute(s),

    Memory Processes Detected: 0
    (No malicious items detected)

    Memory Modules Detected: 0
    (No malicious items detected)

    Registry Keys Detected: 0
    (No malicious items detected)

    Registry Values Detected: 0
    (No malicious items detected)

    Registry Data Items Detected: 0
    (No malicious items detected)

    Folders Detected: 0
    (No malicious items detected)

    Files Detected: 1
    C:\Users\Benjamin\Downloads\aglotze3\flv.exe (Riskware.NetTool) -> Quarantined and deleted successfully.

    (end)
  5. weaselman said:
    That`s a heck of a long post, but I guess you were thorough.
    Anyway as a note it looks like the Direct x files have srcewed up in windows. You may want to try to re install Direct X. The card its self is Reporting as working since the Gpu is listed and the memory size is also, Plus the Nvidia drivers are all installed.
    So there must be corrupted Dx files that may be causing the problem.


    Hi weaselman, could you please tell me how to reinstall Direct X11 in Windows 7.

    Regards
    Biba
  6. Right, I was hoping to the issue sorted before the New Year. I scanned the system with SUPERAntiSpyware and it found this:

    SUPERAntiSpyware Scan Log
    http://www.superantispyware.com

    Generated 12/31/2012 at 08:05 AM

    Application Version : 5.6.1014

    Core Rules Database Version : 9806
    Trace Rules Database Version: 7618

    Scan type : Complete Scan
    Total Scan Time : 00:24:32

    Operating System Information
    Windows 7 Home Premium 64-bit, Service Pack 1 (Build 6.01.7601)
    UAC Off - Administrator

    Memory items scanned : 635
    Memory threats detected : 0
    Registry items scanned : 75812
    Registry threats detected : 0
    File items scanned : 48579
    File threats detected : 4

    Adware.Tracking Cookie
    C:\Users\Benjamin\AppData\Roaming\Microsoft\Windows\Cookies\1GW0ALDN.txt [ /atdmt.com ]
    objects.tremormedia.com [ C:\USERS\BENJAMIN\APPDATA\ROAMING\MACROMEDIA\FLASH PLAYER\#SHAREDOBJECTS\9FK2HBYA ]

    Trojan.Agent/Gen-Koobface[Bonkers]
    C:\USERS\BENJAMIN\APPDATA\LOCAL\TEMP\{ED577243-49E7-4E38-A02E-50168D1B39C8}\{49BF48CC-ABB6-4795-9B35-B5DE005D8612}\SETUPCFG.EXE

    Rogue.Agent/Gen-Nullo[DLL]
    C:\WINDOWS\SYSTEM32\NVHDAP64.DLL

    Are the Trojan- and Rogue agent false positives? I tried finding out googling but didn't get very far.

    Greetings
    Biba
  7. o.k. sorry it did not help i have no idea what else to do other then reinstall OS Code 43 Error Message

    The Code 43 error is one of several Device Manager error codes. The Code 43 error will almost always display in the following way:

    "Windows has stopped this device because it has reported problems. (Code 43)"

    Details on Device Manager error codes like Code 43 are available in the Device Status area in the device's properties:

    Important: Device Manager error codes are exclusive to Device Manager. If you see the Code 43 error elsewhere in Windows, chances are it's a system error code which you should not troubleshoot as a Device Manager issue.
    Cause of the Code 43 Error

    A Code 43 error is generated when Device Manager stops a hardware device because the hardware reported to Windows that it's having some kind of unspecified problem.

    This extremely generic message could mean there's a true hardware issue or it could simply mean that there's a driver problem that Windows isn't seeing as such but that the hardware is being affected by.
    Error Code 43 Troubleshooting

    Restart your computer if you haven't done so already.

    There is always the chance that the error Code 43 you're seeing on a device was caused by some temporary problem with the hardware. If so, a restart of your computer might fix the Code 43 error.



    Did you install a device or make a change in Device Manager just before the Code 43 error appeared? If so, it's very possible that the change you made caused the Code 43 error.

    Undo the change if you can, restart your PC, and then check again for the Code 43 error.

    Depending on the changes you made, some solutions might include:

    Remove or reconfigure the newly installed device.
    Roll back the driver to a version prior to your update.
    Use System Restore to undo recent Device Manager related changes.
    Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a possible solution to a Code 43 error.
  8. OK.

    D/L GPUz from http://www.techpowerup.com/downloads/2181/TechPowerUp_GPU-Z_v0.6.6.html

    Load it up, take a screen shot and post it on here please.
  9. Hi cygone,

    Here is the screen shot:

    http://gpuz.techpowerup.com/12/12/31/c63.png

    Greetings
    Biba
  10. OK something seriously wrong here. your GPU clock and Memory clock should match your default clocks.

    Do you knkow how to &/or confortable with flashing your card with a new bios (well same stock bios you have, just a reload)
  11. cygone said:
    OK something seriously wrong here. your GPU clock and Memory clock should match your default clocks.

    Do you knkow how to &/or confortable with flashing your card with a new bios (well same stock bios you have, just a reload)


    Hi again,

    Yes I know how to do it. I used a flash drive yesterday to update my older Bios (F8 if I remember correctly) to the recent F18. So you want me to reload Bios version f18 from the same flash drive?
  12. No, go get a stock bios from the GPU listings at techpowerup
    http://www.techpowerup.com/vgabios/index.php?page=1&architecture=NVIDIA&manufacturer=&model=GTX+670&interface=PCI-E&memSize=0

    find your stock bios and d/l it, save it to the flashdrive and use nvflash to flash the GPU.

    e.g DONT use the bios you already have, get a nice fresh new one. Dont worry which one you use, we can always find you a better bios if this works,
  13. Ok guys, you scared me!
    My motherboard came with a cd, on it a program for updating BIOS via the internet in Windows 7 called @BIOS. Before, I downloaded and installed the BIOS F18 from the Gigabyte Download Center. I have a Z77-D3H motherboard and I am offered to reload Bios with Intel Z77, AMI BIOS Ver.F18.
    SHould I go ahead ... I told you, you scared me!
  14. STOP

    We are talking at cross purposes, you are talking about BIOS flashing your motherboard, we are talking about BIOS flashing your GPU.

    If you DONT know how to flash the GPU bios, I would suggest you dont try it. (it is easy, but a little complicated at the same time), I am willing to write you a step by step guide on how to do it if you want.

    Tho it might be a good idea to claim on its warranty
  15. Were talking about reflashing your video card bios not motherboard
  16. cygone said:
    STOP

    We are talking at cross purposes, you are talking about BIOS flashing your motherboard, we are talking about BIOS flashing your GPU.
    :lol: we must of been typing at the sametime you beat me to it though.
  17. bigcyco1 said:
    :lol: we must of been typing at the sametime you beat me to it though.


    Yeah im hanging around TRYING to get some input on my problem, but no one is helping =(
  18. cygone said:
    Yeah im hanging around TRYING to get some input on my problem, but no one is helping =(
    Someone will hopefully if not try posting on this fourm http://www.overclock.net/
  19. thread is here,

    http://www.tomshardware.co.uk/forum/385079-15-nvidia-drivers-monitor-range

    Its also up on EVGA forums, oc.net was my next point of call.
  20. am not sure I am going to manage on my own just now, ccl have not been very attentive and helpful until now, so I would be more than happy if you tell me step by step if you tell me how to flash my gpu
  21. cygone said:
    STOP

    We are talking at cross purposes, you are talking about BIOS flashing your motherboard, we are talking about BIOS flashing your GPU.

    If you DONT know how to flash the GPU bios, I would suggest you dont try it. (it is easy, but a little complicated at the same time), I am willing to write you a step by step guide on how to do it if you want.

    Tho it might be a good idea to claim on its warranty


    Ok, just had a look at MSI support and found this:
    http://uk.msi.com/service/download/bios-19814.html
    Along come a read me which is fairly comprehensive so I think I can manage.
  22. Guess I have to say Happy New Year! by now
    I dl the bios from uk.msi.com and flashed the GPU after creating a bootable USB drive.
    In DOS I typed
    nvflash NV284MS101.rom
    - it wouldn't do anything
    so I tried
    nvflash -b NV284MS101.rom
    It copied something but the screenshot from earlier remains the same
    http://gpuz.techpowerup.com/12/12/31/9xs.png

    Did I do something wrong?

    Biba
  23. biba82 said:
    Guess I have to say Happy New Year! by now
    I dl the bios from uk.msi.com and flashed the GPU after creating a bootable USB drive.
    In DOS I typed
    nvflash NV284MS101.rom
    - it wouldn't do anything
    so I tried
    nvflash -b NV284MS101.rom
    It copied something but the screenshot from earlier remains the same
    http://gpuz.techpowerup.com/12/12/31/9xs.png

    Did I do something wrong?

    Biba


    If you flashed it correctly, it should ask you to confirm, use the following cmd line.

    nvflash -4 -5 -6 nv284ms101.rom (I think this file name is to long due to DOS only liking 8bit strings - type '/dir' and you will likly find it is called NS284~1.rom)
  24. What 670 do you have
  25. @ bigcyco My 670 is this one
    http://www.cclonline.com/images/MediaPool/Sycrq95kGi8SP9L8K3wZNg-3d-3d_LargeProductImage.jpg

    @ cygone I used the command line you suggested and I was apparently able to flash the GPU. However I do not see any difference, still red and green dots on the display ... all the time
    http://gpuz.techpowerup.com/13/01/01/env.png
    Does it look correct now?
  26. bios was definatly flashed, but still screwed, your going to hav e to make a warranty claim
  27. Well let's see if we can narrow this down using the Event Viewer. Start -> Right-click Computer -> Manage. In Computer Management, click on Event View (left-pane) -> Windows Logs -> Applications. You will see a list of all of the applications and their installations. Scroll down until and check out the "MsiInstaller" entries under the "Source" column. You should see ones with an error (red !). Read the bottom pane and see what happened.
  28. Check in Device Manager See a yellow exclamation point next to a device in Device Manager? Don't worry, it's not that uncommon. There are many reasons that a yellow exclamation point might show up in Device Manager - some more serious than others.
    Answer: A yellow exclamation point next to a device in Device Manager means that Windows has identified a problem of some kind with that device.

    The yellow exclamation mark provides an indication of a device's current status and could mean that there is a system resource conflict, a driver issue, or any number of other things.

    The yellow mark itself doesn't give you any valuable information but what it does do is confirm that a Device Manager error code has been generated. To fix whatever problem is going on, you'll need to view this code and troubleshoot accordingly.

    To view the Device Manager error code that was generated for this piece of hardware, you'll need to view the device's status in Device Manager.


    Note: I often get asked about the "yellow question mark" in Device Manager. The yellow question mark appears as the full sized device icon and will appear when a device is detected but not installed. You can solve this problem by updating the drivers for the device.

    There is also a green question mark that can appear in some situations but only in Windows Millennium Edition (ME).

    Also, in case you're really paying attention in Device Manager, it's not a yellow exclamation point at all - it's a black exclamation point on a yellow background. The yellow background is triangle shaped in Windows 7 and Windows Vista and a circle in Windows XP.
    More Related to the Yellow Exclamation Mark
  29. bigcyco1 said:
    Well let's see if we can narrow this down using the Event Viewer. Start -> Right-click Computer -> Manage. In Computer Management, click on Event View (left-pane) -> Windows Logs -> Applications. You will see a list of all of the applications and their installations. Scroll down until and check out the "MsiInstaller" entries under the "Source" column. You should see ones with an error (red !). Read the bottom pane and see what happened.


    This is what I found:
    Log Name: Application
    Source: MsiInstaller
    Date: 29/12/2012 21:36:27
    Event ID: 11719
    Task Category: None
    Level: Error
    Keywords: Classic
    User: Benjamin-PC\Benjamin
    Computer: Benjamin-PC
    Description:
    Product: Etron USB3.0 Host Controller -- Error 1719.Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">11719</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-12-29T21:36:27.000000000Z" />
    <EventRecordID>10097</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Benjamin-PC</Computer>
    <Security UserID="S-1-5-21-1765326389-524560061-2523818408-1002" />
    </System>
    <EventData>
    <Data>Product: Etron USB3.0 Host Controller -- Error 1719.Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled.</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
    <Binary>7B44464242373338432D373144382D344443352D423844322D4436354333373638304532377D</Binary>
    </EventData>
    </Event>

    I also searched for any errors occurring around the time of Modern Warfare crashing causing all this red adn green dots. This seems to be the one.

    Log Name: Application
    Source: Microsoft-Windows-WMI
    Date: 28/12/2012 21:55:07
    Event ID: 10
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: Benjamin-PC
    Description:
    Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
    <EventID Qualifiers="49152">10</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-12-28T21:55:07.000000000Z" />
    <EventRecordID>8397</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Benjamin-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>//./root/CIMV2</Data>
    <Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99</Data>
    <Data>0x80041003</Data>
    </EventData>
    </Event>
  30. I tried figuring out what the Code 43 error in the device manager under display adapter is supposed to mean and how to fix it also using google but to no avail. Updated the driver software for the GTX 670 in the device manager, still the same issues.
  31. Try reformat yourr hard drive and fresh install os if you do not want to try that rma it
  32. bigcyco1 said:
    Try reformat yourr hard drive and fresh install os if you do not want to try that rma it


    Do you think a repair install would do, too? Don't really have the time to organize back up of personal data. Also, I figure that rma would easily take a week if not more.
  33. biba82 said:
    Do you think a repair install would do, too? Don't really have the time to organize back up of personal data. Also, I figure that rma would easily take a week if not more.
    I don't think so you could try it at this point rma is the route i would go. It's up to you.I'm sorry wasn't of any help.
  34. bigcyco1 said:
    I don't think so you could try it at this point rma is the route i would go. It's up to you.I'm sorry wasn't of any help.


    No worries bigcyco1!
    I removed the graphics card before supper, just to try out the recommendation from the CCL customer service guy - didn't change anything. However, when using the on-board graphics, I was able to install the monitor drivers.
    I'll contact CCL by mail tonight and phone tomorrow. Just hope that the graphics card is the only problem.

    Thank you for your support and advice!
    I will post an update later on.

    Biba
  35. o.k. good luck!
  36. bigcyco1 said:
    o.k. good luck!


    WTF!!!! I just played a bit around whilst in safe mode and when I restarted, everything seemed to be fine ... the resolution is still a bit funny but otherwise seeming ok ... already told the guys at CCL I would like to RMA.

    Even gpuz seems good now!
    http://gpuz.techpowerup.com/13/01/01/53v.png

    Ok, just tried Modern Warfare 2 again, running it under "optimal video and audio", actually not that optimally looking on my screen. That reminds me that when I started playing it, I changed the audio/video settings to high levels of detail and resolution. Could it be that that knocked out my gpu in the first place.
    I shall try some other games now, too.

    Would you still consider RMA now that it happened once?

    Funny but the fridge in the little room called office changed its mode and made the monitor turn black for a few seconds. Haven't seen that before.
  37. Found this in Windows Action Center, might be the trigger for my problems

    Description
    A problem with your video hardware caused Windows to stop working correctly.

    Problem signature
    Problem Event Name: LiveKernelEvent
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 2057

    Files that help describe the problem
    WD-20121228-2123.dmp
    sysdata.xml
    WERInternalMetadata.xml

    View a temporary copy of these files
    Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

    Extra information about the problem
    BCCode: 117
    BCP1: FFFFFA80077DF190
    BCP2: FFFFF8800F225A88
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1
  38. After playing a bit more than an hour of Modern Warfare 1 and 2 on 1680x1050 I can report that there have been three or four occasions with the odd pixel here and there and one with a multi-coloured diagonal stripe. They all went away though.
    I will update the nvidia drivers tomorrow and see if that resolves the matter or makes it worse.
  39. bigcyco1 said:
    o.k. good luck!


    Hi there,
    The guys at CCL were great, offering RMA and further support, I decided to wait a little while because I actually managed to get everything to work again twice (even if only for a short while). Also, after surfing through various forums, it didn't seem to be hardware related to me.
    This evening I updated to Nvidia 310.90 drivers and everything seems (touch wood) to be working well :wahoo:

    Hopefully problem solved
  40. biba82 said:
    Hi there,
    The guys at CCL were great, offering RMA and further support, I decided to wait a little while because I actually managed to get everything to work again twice (even if only for a short while). Also, after surfing through various forums, it didn't seem to be hardware related to me.
    This evening I updated to Nvidia 310.90 drivers and everything seems (touch wood) to be working well :wahoo:

    Hopefully problem solved
    Great news. I am glad it all worked out. :)
  41. After successfully running various games on high settings for roughly a week without major problems, I had a few BSOD's trying to play Dead Island. So today, the graphics card went back to CCL. Am curious to see if a new card will really solve the issue.
  42. Don't know if people are still on the thread but 310.90 has been causing a *** ton of bsod's for me try an olfder driver just not the one you were on before
Ask a new question

Read More

Nvidia Graphics