We’d like to remind Forumites to please avoid political debate on the Forum.
This is to keep it a safe and useful space for MoneySaving discussions. Threads that are – or become – political in nature may be removed in line with the Forum’s rules. Thank you for your understanding.
📨 Have you signed up to the Forum's new Email Digest yet? Get a selection of trending threads sent straight to your inbox daily, weekly or monthly!
Windows 10 blurry text/fonts
Comments
-
As for the OEM. My desktop is a built one from a company called pcspecialists. Its about 6 years old & has an ASUS motherboard, no additional graphics cards. Haven't a clue whether they use modified drivers.0
-
perhaps if you were to tell us the model of motherboard , suitable links for driver might be found
motherboard model often written near PCI slotsSave a Rachael
buy a share in crapita0 -
Could you try the driver installation again but following this procedure and post the log output ?
http://nvidia.custhelp.com/app/answers/detail/a_id/3581/~/driver-installation-failedScience isn't exact, it's only confidence within limits.0 -
Motherboard model is ASUS M4N78-AM0
-
Fightsback - Not sure if i'm posting this right, but below seems to be the failure point in the setupapi.dev log
!!! sig: Failed to install catalog 'NV_DISP.CAT' as 'oem15.cat'. Error = 0x000006BE
sto: {DRIVERSTORE IMPORT END: exit(0x000006be)} 16:08:27.861
! inf: Legacy directive 'RegisterDlls' will be ignored. Code = 2222, Line = 13360 -
Motherboard model is ASUS M4N78-AM4.8kWp 12x400W Longhi 9.6 kWh battery Giv-hy 5.0 Inverter, WSW facing Essex . Aint no sunshine ☀️ Octopus gas fixed dec 24 @ 5.74 tracker again+ Octopus Intelligent Flux leccy0
-
You could also look on asus https://www.asus.com/Motherboards/M4N78AM/HelpDesk/4.8kWp 12x400W Longhi 9.6 kWh battery Giv-hy 5.0 Inverter, WSW facing Essex . Aint no sunshine ☀️ Octopus gas fixed dec 24 @ 5.74 tracker again+ Octopus Intelligent Flux leccy0
-
Fightsback - Not sure if i'm posting this right, but below seems to be the failure point in the setupapi.dev log
!!! sig: Failed to install catalog 'NV_DISP.CAT' as 'oem15.cat'. Error = 0x000006BE
sto: {DRIVERSTORE IMPORT END: exit(0x000006be)} 16:08:27.861
! inf: Legacy directive 'RegisterDlls' will be ignored. Code = 2222, Line = 1336
Looking at the snippet you've posted (would be nice to have the full log to see the whole picture if you can post) it could possibly a driver store (Catroot) issue which might be due crud left over from your win 7 Nvidia driver install or some other problem with catroot. As far I can tell what appears to be happing is a failure to register the driver.
1) What device are you seeing under device manager > display adaptor, Microsoft VGA or Nvidia ? Do you see anything else with a yellow warning ?
2 ) Try this as a solution to start with (irrespective of above) and follow the instructions however I'm less than 50% hopeful it will work:
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
NB select the Nvidia driver in DDU
There are further things to try after this.Science isn't exact, it's only confidence within limits.0 -
Fightsback wrote: »Looking at the snippet you've posted (would be nice to have the full log to see the whole picture if you can post) it could possibly a driver store (Catroot) issue which might be due crud left over from your win 7 Nvidia driver install or some other problem with catroot. As far I can tell what appears to be happing is a failure to register the driver.
1) What device are you seeing under device manager > display adaptor, Microsoft VGA or Nvidia ? Do you see anything else with a yellow warning ?
2 ) Try this as a solution to start with (irrespective of above) and follow the instructions however I'm less than 50% hopeful it will work:
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
NB select the Nvidia driver in DDU
There are further things to try after this.
I wasn't sure how to attach to full log to a post.
Strangely Display adaptor is not appearing at all in Device manager. It was on Thursday, when it was showing just the Microsoft device.
Tried the Device driver uninstaller, but this didn't resolve the issue0
This discussion has been closed.
Confirm your email address to Create Threads and Reply

Categories
- All Categories
- 351.8K Banking & Borrowing
- 253.4K Reduce Debt & Boost Income
- 454K Spending & Discounts
- 244.7K Work, Benefits & Business
- 600.2K Mortgages, Homes & Bills
- 177.3K Life & Family
- 258.4K Travel & Transport
- 1.5M Hobbies & Leisure
- 16.2K Discuss & Feedback
- 37.6K Read-Only Boards