Recommended Posts

hello i have just got this card and got it installed and everything but i am having issues with the TV out. When i boot up the boot process shows on my TV like it did with the last one but when windows is loaded i get nothing on screen. I open up display properties and set it to expand the desktop over to the TV but when i click apply nothing happens.

Update the CCC opens but the same as with disp props

Anyone know what might be wrong?

thanks.

--==Its fixed due to faffing==--

Dear mods kill this thread if you want

post-84923-1201728422.jpg

Edited by yurithedragon
Link to comment
https://www.neowin.net/forum/topic/616876-new-graphics-card-problems/
Share on other sites

ok i am having a new problem here with Direct3D tests done with Dxdiag

test 1
---------------------------
DirectX Diagnostic Tool
---------------------------
This test will use hardware-accelerated Direct3D 7 interfaces.
---------------------------
OK   Cancel   
---------------------------

res 1

---------------------------
DirectX Diagnostic Tool
---------------------------
Test failed at step 8 (Creating 3D Device): HRESULT = 0x80004005 (Generic failure)
---------------------------
OK   
---------------------------

test 2

---------------------------
DirectX Diagnostic Tool
---------------------------
This test will use hardware-accelerated Direct3D 8 interfaces.
---------------------------
OK   Cancel   
---------------------------

res 2

---------------------------
DirectX Diagnostic Tool
---------------------------
Test failed at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code)
---------------------------
OK   
---------------------------

test 3

---------------------------
DirectX Diagnostic Tool
---------------------------
This test will use hardware-accelerated Direct3D 9 interfaces.
---------------------------
OK   Cancel   
---------------------------

res 3

---------------------------
DirectX Diagnostic Tool
---------------------------
Test failed at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code)
---------------------------
OK   
---------------------------

so what could be the issue i have uninstalled and reinstalled the drivers and still i get these issues

post-84923-1201798465.jpg

I had this problem YESTERDAY! What happened was, I updated the Chipset drivers (Windows XP) and I was getting the same error. Have you upgraded your drivers for the MB? If yes, roll back to the previous drivers, if not.. update the chipset drivers. Hope that helps. Are you by chance using a MB with a VIA chipset?

JESUS CHRIST man! Do you READ?

I had this problem YESTERDAY! What happened was, I updated the Chipset drivers (Windows XP) and I was getting the same error. Have you upgraded your drivers for the MB? If yes, roll back to the previous drivers, if not.. update the chipset drivers. Hope that helps. Are you by chance using a MB with a VIA chipset?

I was TRYING to help.. but you didn't respond, and I just told you how to friggin fix it. I JUST had that SAME problem.. and it was the GOD DAMN CHIPSET drivers! Same error you are getting... SAME ****ING THING!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • KDE Plasma 6.5 will notify you if your printer's ink is low by David Uzondu This week, the KDE team continued work on the upcoming Plasma 6.5.0 as well as Plasma 6.4's fourth bug fix release, 6.4.4. As usual, both Plasma versions saw several UI tweaks, bug fixes, and performance improvements. The most notable changes are discussed in this article. Let's start with Plasma 6.5. The desktop environment is getting a useful feature that tells you when your printer is low on ink. This works by having the system check the Common Unix Printing System, or CUPS, for marker levels after a print job is created or completed. CUPS stores attributes like marker-levels in its printers.conf file, and once a level is determined to be low, it triggers a marker-supply-low-warning that Plasma will now use to inform you. UI improvements scheduled for 6.5 include disabling key repeat for certain global shortcuts, like toggling Overview, to prevent rapid screen flashing that could be a seizure risk. There is a better "Someone started sharing this screen" notification that now appears only after a connection is fully established. You will also find standard KDE styling with the "Confirm deleting network connection" dialog, and more consistent spacing in the Global Menu widget. As for bug fixes in 6.5, a layout bug that caused visual overflow in the printer setup page has been corrected. An issue that stopped you from using the virtual keyboard in the Application Dashboard search field is fixed, and XDG portal-using apps can now request screencasts of new virtual outputs. Finally, the clipboard configuration window's size and position information has been moved from the state config file to the settings file. Moving on to 6.4.4, the hitboxes for desktop items now correctly match their visual styling. This means no more accidentally selecting an invisible box around a file. And when you mark a notification as low priority, it will now correctly appear in your history if it arrived during Do Not Disturb mode, so it does not just vanish. If you're experiencing a Kwin crash on login, particularly in a QEMU virtual machine, 6.4.4 has a fix for that on the way. Other bug fixes 6.4.4 brings include: A fix for the Global Menu widget's single-button mode for X11 users. The search field in the Wayland version of the Global Menu widget works again. An annoying bug in the Global Shortcuts XDG portal that made apps think they had no shortcuts has been resolved. Plasma Browser Integration's built-in Share feature has been repaired. Plasma 6.4.4 will drop on the 5th of next month. You can find more details on the official KDE Blog.
    • I just remember wondering how she was ever a bridge officer at all with all of her insufferable insecurities. I am sure she's a wonderful person in real life, but the character was poorly written. They even had to dedicate a whole episode to her being forced into taking the responsibility of leading cadets out of a problem of some sort as if to show how she is "growing" into her function. Never bridge officer material and I just rolled my eyes at her scenes and eventually stopped watching the show altogether, but also because of all the lead character's cry/whisper/talking that frustrated me.
    • Didnt know it was coded/decoded so my bad.
  • Recent Achievements

    • Week One Done
      Homayoun Hotak earned a badge
      Week One Done
    • Dedicated
      Profit earned a badge
      Dedicated
    • One Month Later
      hhgygy earned a badge
      One Month Later
    • Week One Done
      hhgygy earned a badge
      Week One Done
    • One Year In
      NIKI77 earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      641
    2. 2
      ATLien_0
      241
    3. 3
      Xenon
      168
    4. 4
      neufuse
      149
    5. 5
      +FloatingFatMan
      123
  • Tell a friend

    Love Neowin? Tell a friend!