![]() ![]()
Strange thing is, the WU drivers seem to actually work, but unless I connect an external monitor, my backlight won't function. Probably also has the dual Intel part thing (didn't even know it was dual!). We will be forcing a "2nd Wave" campaign within the next 2 weeks to raise awareness on this issue.ĪSUS Notebook AMD 6470M here. The battery life and blackscreen (passthrough routing) can be fixed if AMD gets their act together. I personally have my MPC-HC running on AMD. XAML and the Application Lock can be overcome by the unlock that I apply to the UnifL driver packages. " I have however observed that with the "Extend" function there is no lag, while there is with "Duplicate" and "Second screen only" We have had a fix for working HDMI internally on UnifL for quite some time. Unfortunately with the new drivers there is a sort of lag on 1st Gen Intel AMD 5xxx PXAI devices: The issues you mention are all mainly correct. AMD HD 7400M DRIVER WINDOWS 10 WINDOWS 10The issue seems to be that the Windows 10 drivers use dynamic switching, whereas before we could choose if the Intel ot AMD is used, and the other would get automaticallly disabled.ĭalby and me started this campaign on to force AMD into fixing the bootloop that occurred since Windows 8.1 on these devices. As said earlier, teh AMD GPU can't be selected in XAML apps and some other GPU accelerated programz such as MPC-HC and Adobe Premiere.Īll these issue occur on all 1st Gen Intel AMD HD 5xxx laptops regardless OEM or model. Many games just blackscreen and refuse to use the AMD GPU. Even when the laptop is on battery and just idling on desktop with no apps open, the battery lasts according to the meter only 3-4 hours, while on Windows 8.1 I get 6-8 hours of light web browsing when using the Intel GPU.Ģ. Basically, there are three big issues, which are the reasons why I am staying with Windows 8.1 and Catalyst 14.4 for now.ġ. There's a long thread at Windows Insider forum about W10 and the 1st Gen Intel AMD 5xxx here. Intel HD Graphics 3000 (Intel core i3-2330M)ĪMD Radeon 6470M (now referred to by Windows as AMD Radeon 7400M Series) AMD HD 7400M DRIVER WINDOWS 10 FULLWhen I click the full screen button, said app crashes. AMD HD 7400M DRIVER WINDOWS 10 WINDOWS 8Using the application feels normal and fine, except when opening and closing them.Īnother issue is Windows 8 apps (I tried Asphalt 8, specifically) can't run in full screen using the AMD GPU. Whenever I open or close an application that is set to run on the AMD GPU, the computer freezes for a few seconds, and only then moves on. This seems to have fixed the issue where no app is running on the AMD card, but created a new one. Then, I installed AMD first then Intel, again the opposite of what I do usually. To try to fix this, I decided to uninstall both drivers completely, starting with Intel then AMD, the opposite of what I usually do. Now, I just noticed this, but despite my settings in AMD's Catalyst Control Center, no application was running on the "high performance" GPU. AMD HD 7400M DRIVER WINDOWS 10 INSTALL13:18:51.825: Info: Main: Highest software API version: 1.9įor those having Intel HD 3000 with NVidia or just Intel HD 3000 - there is no need to apply AMD Catalyst drivers - you just run Leshcat installer to uninstall pack of drivers (AMD Intel) and later just install Intel ones (manually or via setup.exe).I have a dual GPU laptop, with a power saving GPU, integrated, from Intel and and a "high performance" GPU by AMD. 13:18:51.824: Info: Main: Highest Quick Sync hardware API version: 1.4 13:18:49.824: Info: Main: Intel HD graphics driver: Intel(R) HD Graphics 3000 capabilities (hardware): vsinfo opt1Ĭ:\Program Files (x86)\q264>q264.exe -info preferred implementation: hardware (any) Intel Media SDK hardware: API 1.4 (minimum: 1.3) OpenCL device # 1: Advanced Micro Devices, Inc. Temp Dir: C:\Users\tskon\AppData\Local\Temp\ĭata Dir: C:\Users\tskon\AppData\Roaming\HandBrake Team\HandBrake\0.0.0.0 Since then QSV encoding in Handbrake and q264 in Windows 10 works like a charm ! "Catalyst UnifL – Catalyst Unified Leshcat Drivers" work: average encoding speed for job is 271.954529 fps.įor me the solution was to replace default Windows 10 Intel drivers for HD 3000 (provided by M$ via Windows Update) and replace them with customized ones for HD 3000: below result after applying new drivers): On default W10 Intel drivers for HD 3000 there was no support for Intel QSV (insane fast hardware H264 encoding in short, e.g. GPU: Intel HD Graphics 3000 / AMD Radeon HD 7400M Series ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |