By what logic do you come to the conclusion that it is up to Steinberg to fix this? You are attempting to run Cubase on hardware that does not have drivers that are compatible with Windows 10. It seems to me that the fault lies with the manufacturer of your graphics hardware for not providing updated drivers, so either hp, Intel or AMD, or all of them, but not Steinberg.
The fact that you’re only perceiving the problem with Steinberg software is probably because all your other software is either older or less demanding, and doesn’t use the more modern capabilities of Windows 10, nevertheless somebody may have a tweak to get things working. Did you try the AMD driver version 15.7.1 and creating a profile for Cubase as Fabio suggested?
Hello, please check this link: LoadLibrary Failed With Error 1114: 6 Confirmed Fixes to Use.
I’m under the impression you tried most of that trouble-shooting already, I don’t know if it’ll help you, but has been useful to quite a few (also to those who get the same issue with NVIDIA cards).
The problem is a. the software needs Direct3D 11.2 and the GPU must support that and b. hardware that is not actually supported by the manufacturer on Windows 10.
This has not been discussed much, but Intel does not support 1st and 2nd Gen CPUs on Win 10, while Ivy Bridge (3rd) is only supported if the OEM manufacturer supports the upgrade to Win 10 (Does My Intel® Processor Support Microsoft Windows® 10?). Windows 10 is actually very smart with “bridging” drivers and libraries and I do believe this works incredibly well, but there are a few issues.
Honestly, it is very unlikely that this will be ‘solved’, to modify an application to support hardware that is not supported on the OS where that software is supposed to run on can be very risky business.
Yes Mr Soundman I did try both driver as advised and the same issue occurs.
By what logic do you come to the conclusion that it is up to Steinberg to fix this?
(because out of over 200 applications I have on my computer including Reason, Reaper, Studio One, Cubase is the only app that I can’t read a sub menu. This is not some moving fast gaming graphic. A basic static menu that should be simple to read - so excuse me if I’m asking too much)
Thank you again Fabio - I will look at later when I’m back at home.
Still stuck, would downloading Direct X help?
Here is my system information if this helps?
Installing DX won’t help. The problem is not with Direct3D missing, the needed version is built-in in Windows 10 (it’s actually in 8.1, too): the problem is the hardware not supporting the needed feature level and drivers being outdated.
The only chance is to use the AMD for Cubase as discussed previously, sorry.
Am I doing something wrong Fabio, here is a copy of current settings where I get the DLL error for Cubase but not Hailon.
The other settings are either High Performance or Based on Power Source which will allow Cubase to run but won’t be able to read sub menu?
Cubase should be set to high performance, not power saving.
Looks like there are libraries that won’t be loaded when on power saving mode.
Are the menus blank also on high perf?
Yes, just a white back ground as per the very first photo I put on the beginning of the forum. Really want to use Cubase as my main DAW as being using Reason for the last 9 years but Cubase looks very slick and wondering if the CPU will cook less there?
Can anyone think of anything else, if other DAWs and vast amount of apps I already have can display things correctly, surely it’s not a big ask for Cubase to do the same?
Hi. As you can see from my signature I have the same cpu and intel graphics. It is old kit and I too have had graphics glitches with cubase from v9.0 onwards. Actually the present version 10.0.x has been fairly glitch free but there are still the odd ones [black background in the inspector plugins faders] but I can live with them. Of course yours is a different machine with different chip set hardware and drivers so it may manifest graphics glitches differently. I sympathise with you but the fact is that I know my hardware is old and it will have to be replaced at some point if it fails or just simply cannot cope with modern demands of one or more pieces of software. C’est la vie.
Just something to check though. If you go to Device Manager and click on Display Adaptors, check to see what version of driver you have for Intel hd3000. The latest intel driver available from their site is v9.17.10.4429 which supports W8.1 - I did have that one on my machine for sometime before Microsoft updated. It should have been updated automatically by Microsoft to v9.17.10.4459 dated 19/05/2016. This is the latest - strictly speaking Intel does not support hd3000 under W10 - but this driver is only available from Microsoft. If your machine has an earlier driver, force it to update. Or google ‘Intel hd 3000 9.17.10.4459’ and it will lead you to the Microsoft update catalogue where you can download the graphics driver. If you already have the latest graphics drivers then there is nothing more I can advise.This is the only help I can offer you. Best of luck.
Thank you for your suggestion Wanderer but alas I do have 9.17.10.4459 already installed. It looks like I have no choice but to upgrade to a more modern computer. Talking to a company that get unused PC equipment from businesses that might be able to give me a decent Dell within my budget.
Fabio or anyone else, gonna be getting a Dell T3610 quad core xeon E5, 1607 CPU, with 32GB RAM - it has a Nvidia K2000, 2g gddr5 ram graphic card. Will that be fine regarding the sub menu reading problems and will it be a good system that can handle a lot of plugins on Cubase?
Thank you for any answers and the help already suggested.
That XEON is a Sandy Bridge, same generation as your current one.
For fully supporting Win 10, you’d need a Haswell CPU minimum (4th Gen. AKA i5/i7 4xxx series).