Problem with the newer version of Intel HD Graphics 4000 driver on Windows Vista Extended Kernel

[com.android.systemui]

I tried to use the Windows 7 version of Intel HD Graphics 4000 driver (which has blue and white control panel window color) on Windows Vista Extended Kernel with NTOSKRNL Emu_Extender and some modifications. I have successfully installed it through the Device Manager driver update. And it turns out that it has worked partially. OpenGL and DX11 work perfectly without glitches, also the driver has no problem at all in Device Manager, but DX9 causes BEX64-related crashes. And until now I still cannot enjoy the Aero theme, screen savers, play videos using Windows Media Player, and some apps or games that require D3D9 won't run (because they need DX9 to work properly). The control panel itself also won't open (BEX64 crashing) unless I renamed or moved out the igdumdim64.dll file from the System32 folder and the igdumdim32.dll file from the SysWOW64 folder.

And when I am trying to show the information center page from the Options and Support menu, the control panel crashes with code 0xc0000096 (STATUS_PRIVILEGED_INSTRUCTION)

Note: I hate the Intel HD Graphics 4000 version which the Control Panel UI looks like the following picture, even though this version fully supports at least Windows XP:

scaling_new.jpg (52.86 KiB) Viewed 3345 times

Because:

• Doesn't support apps or games that require newer OpenGL versions, even if Windows Vista is still supported (maybe they only need graphic cards that support both Windows Vista and newer OpenGL versions)

• Garbage FPS on all PS2 games in PCSX2, and even in BIOS (approx 40 - 50 FPS), even with lowest settings and some speedhacks, high performance plan in power options, and if the CPU usage, EE, GS, and VU percentages are very low. It's very unplayable, and all I have to do is only use the Windows 7 version of Intel HD 4000 driver to enjoy back the full speed

• Terrible graphics in Windows 7 with Aero theme, Windows 8.1, and Windows 10 VM in VirtualBox after installing Guest Additions, making them unoperable at all, and even worser, cause serious vision health problems such as headache, eyestrain, and even epilepsy!!!

[K4sum1]

I'll try taking a look at this soon. I'm guessing you got the driver from Intel's site. I'll try finding slightly older drivers from manufacturer websites and seeing how they fare. I'll also investigate the new driver to see if there's anything obviously wrong.

[K4sum1]

I unintentionally found a newer Vista driver labeled as 7+, maybe you already found it, not sure.

https://download.asrock.com/Drivers/Intel/VGA/VGA_Win8-64_Win7-64(v15.28.6.64.2857).zip

I've tried getting a 15.31.??? driver from 8/23/2013 working, but it has the same issues as your driver. Not sure why DX9 would break before DX11, it's the reverse of AMD's drivers. I'll analyze some of the dlls, but I'm not sure if I would find anything.

[luk3Z]

Vista SP2 ?

Try this (last reply):
https://answers.microsoft.com/en-us/windows/forum/all/error-0xc0000096/4048626b-2246-4ad0-b2ae-5cf7fd4b605a

[com.android.systemui]

I unintentionally found a newer Vista driver labeled as 7+, maybe you already found it, not sure.

https://download.asrock.com/Drivers/Intel/VGA/VGA_Win8-64_Win7-64(v15.28.6.64.2857).zip

I've tried getting a 15.31.??? driver from 8/23/2013 working, but it has the same issues as your driver. Not sure why DX9 would break before DX11, it's the reverse of AMD's drivers. I'll analyze some of the dlls, but I'm not sure if I would find anything.

Sorry bro, but I hate the version which the GfxUI executable icon looks like this:

ighate.png (20.52 KiB) Viewed 3311 times

And instead, I want the version like the following icon:

iglove.png (19.37 KiB) Viewed 3311 times

You may need to take the further investigations although it sacrifices more time and takes me longer to waiting for the Aero...

Vista SP2 ?

Try this (last reply):
https://answers.microsoft.com/en-us/windows/forum/all/error-0xc0000096/4048626b-2246-4ad0-b2ae-5cf7fd4b605a

My Vista is freshly installed and it is installed directly with the latest version of Extended Kernel, no upgrades and modifications at all.

[K4sum1]

Sorry bro, but I hate the version which the GfxUI executable icon looks like this:

That's like saying you hate the control panel that the AMD 13.12 drivers use, because the drivers are kinda mid, but not trying a modified 15.6 with the same control panel.

[com.android.systemui]

What about the 0xc0000096 error when opening the Information Center page?
It's not the Vista OS problem, but it's the driver problem, probably the communication between the user-mode dll files and the igdkmd64.sys driver file

[K4sum1]

What about the 0xc0000096 error when opening the Information Center page?
It's not the Vista OS problem, but it's the driver problem, probably the communication between the user-mode dll files and the igdkmd64.sys driver file

Yeah, I'm guessing that dll handles DX9 in some manner.

[com.android.systemui]

Not sure why DX9 would break before DX11, it's the reverse of AMD's drivers.

Do the AMD drivers also return BEX64 crashes on DX11?

[K4sum1]

Not sure why DX9 would break before DX11, it's the reverse of AMD's drivers.

Do the AMD drivers also return BEX64 crashes on DX11?

Not sure of the exact error, but anything D3D11 doesn't work and can crash like that.

[com.android.systemui]

Not sure why DX9 would break before DX11, it's the reverse of AMD's drivers.

Do the AMD drivers also return BEX64 crashes on DX11?

Not sure of the exact error, but anything D3D11 doesn't work and can crash like that.

There are 3 types of crash problem signature, i.e. APPCRASH (general, reasonable, or cause-and-effect crashes), BEX (DEP-related crashes e.g. because of the buffer overflows), and BEX64 (the 64-bit DEP-related crashes). You could try again and have a look at the problem signature of that crash report details, but you must disable the UAC first. Or you can send the log/screenshot to me.

[K4sum1]

So I forgot that OpenGL is what gives the BEX errors, DX11 is much less descriptive

[com.android.systemui]

So I forgot that OpenGL is what gives the BEX errors, DX11 is much less descriptive

That's 100% exact opposite to me (Intel HD Graphics 4000).
Btw you also can look for the DX11 logs and find out the exact error code and its cause-and-effects (from any program that needs or depends on DX11) if possible.

[com.android.systemui]

Just FYI, this might increase your knowledge only, not an actual event.

https://community.intel.com/t5/Graphics/Intel-HD-530-Driver-Crash-in-Windows-7-64-bit/td-p/392171

Intel HD Graphics 530 driver supports at least Windows 7 with Service Pack 1 (build 7601)
Otherwise, it will cause BEX64 crash although even it's almost supported and successfully installed without any modifications, just like the user in that forum, because he didn't know and checked his Windows 7 detailed version information and build number before.

[K4sum1]

Hmm, I wonder if SP1 introduces the SetDisplayConfig and related functions. I think those are the issue for the AMD drivers currently.

[com.android.systemui]

Hmm, I wonder if SP1 introduces the SetDisplayConfig and related functions.

*It's Windows 7, not to be confused

[com.android.systemui]

I also tried it on Windows 7 Beta (Build 7000), and it also has so many missing functions, especially the kernel-mode igdkmd64.sys file. But immediately I re-tried it with NTOSKRNL Emu_Extender, the aero works successfully, although the taskbar's transparency is so terribly pixellated blur and waves when the window is moving behind the taskbar, unlike the window's transparency, and the 3 bottom options from the desktop right click menu have yellow fonts instead of black, maybe it's a rendering bug or something...
So, it isn't the NTOSKRNL Emu_Extender's fault, and also not the driver's problem...

[K4sum1]

In a few days I'll try RTM with the drivers, see what happens. I don't think it would be as bad as 7000, but I'm curious as to if DX9 works and if there's any missing functions.

[com.android.systemui]

In a few days I'll try RTM with the drivers, see what happens. I don't think it would be as bad as 7000, but I'm curious as to if DX9 works and if there's any missing functions.

I also have tried it in freshly installed RTM and it just work as usual, no need any modifications nor additions like Visual C++ redists, .NET Frameworks, DX runtimes, etc.

[K4sum1]

Does DX9 work under 7000?

[com.android.systemui]

Does DX9 work under 7000?

Yeah, but it has very slight differences.

• Windows 7 Beta build 7000 installed legacy version of Intel HD Graphics 4000 driver (that I hated it) = Windows 7 RTM/SP1 installed legacy version of Intel HD Graphics 4000 driver = Windows 7 RTM/SP1 installed newer version of Intel HD Graphics 4000 driver: Both the taskbar's and the window's aero transparency effects are smooth, no rendering artifacts

• Windows 7 Beta build 7000 installed newer version of Intel HD Graphics 4000 driver: almost like the previous point but has very slight differences, such as the taskbar's aero effect is little bit pixellated, and if the window is moved behind the taskbar, the wave effect will happen, unlike the window's aero effect. It also has a little artifacts like yellow or light green right-click menu text font color instead of black while using aero theme

[K4sum1]

UI is probably DX11 at that point, I'd want to see like Heaven DX9 running on 7000.

[com.android.systemui]

UI is probably DX11 at that point, I'd want to see like Heaven DX9 running on 7000.

If the DX9 is broken, there is no way Aero would work.

[K4sum1]

Windows 7 uses DX11 for Aero

[blueclouds8666]

Windows 7 uses DX11 for Aero

To my knowledge, Aero actually uses the DirectX 9Ex API with Shader Model 2.0 capabilities for its rendering. This allows older graphics card, such as the GeForce 6 series lineup (from 2004), to run Aero despite their core architecture not supporting DirectX 10 or 11 in any capacity.

With that said, it might be possible that an additional DirectX 11 mode was implemented, so newer graphics cards could take advantage of it. Is that what you mean? In that case, I would like to know more about it as i couldn't find any pertaining information to it.

[K4sum1]

Back when I was friendly with win32 and co I heard from one or more of them that 7, when paired with a WDDM 1.1 driver and a capable card, uses DirectX 11 for Aero. I think they would know their shit. Could test with the AMD driver and deleting the DX11 dll on 7.

[blueclouds8666]

Back when I was friendly with win32 and co I heard from one or more of them that 7, when paired with a WDDM 1.1 driver and a capable card, uses DirectX 11 for Aero. I think they would know their shit. Could test with the AMD driver and deleting the DX11 dll on 7.

I will test that on my own. Would be interesting to see if it could be forced to fall back into DX9Ex mode somehow.

[com.android.systemui]

It turns out that DirectX 9 works so awful and messy on Windows 7 build 7000 using the newer version of Intel HD 4000 driver. Some 32-bit D3D9 programs worked but with full of glitches. But once I downgraded to the legacy (hated) version, everything went back normal.
Here are the footages.

• Heaven Benchmark Results
  • DirectX 11/OpenGL
    
    
    
  • DirectX 9
    
    
    
    
    

• Font artifacts
  
  
  
  
  

• Game glitches
  Those are very unplayable...
  • GTA San Andreas
    
    
    

• Crashes
  • When trying to launch the Intel HD Graphics Control Panel
    
  • When trying to play videos with large resolutions using MPC-HC
    
  • When trying to play any video using Windows Media Player (both architectures)
    
  • Visualization crash on Windows Media Player 64-bit
    
  • When trying to open image files using Windows Photo Viewer
    
  • Chess Titans (Windows Games)
    

• Misc
  • Visualization works successfully on 32-bit Windows Media Player
    
  • MPC-HC works successfully with videos on 480p or lower
    
  • Memory-related errors (but didn't terminate the program while running)
    
    
    

[K4sum1]

I'll have to try a bunch of 7 builds to see what all they do, see which one made the driver kinda work, then see which build fixes everything.

Also will have to try AMD on 7000.

[K4sum1]

So I went and tested 6801 first as it's different, and found Intel drivers are black screen and AMD drivers are code 43.

I also had my Z77 board decide PCIe is overrated, and my test SSD commit sudoku.