Dxdiag incorrectly reports DirectX 11 devices as DDI 10.1 when using Win 7

[Mussels]

thanks for that eastcoast, kinda shitty feck up on MS's part


me and my brother have 5870's OTW, so i hope we dont get hit with this.

 

[FordGT90Concept]

I wonder why whomever is responsible hasn't fixed it yet. Does that number literally mean nothing or is it impossible to patch?

 

[Mussels]

I wonder why whomever is responsible hasn't fixed it yet. Does that number literally mean nothing or is it impossible to patch?

supposedly fixed in 7 SP1

 

[FordGT90Concept]

So it is an issue with the OS, not DirectX? Why didn't they release a hotfix on Windows Update to fix it?

 

[Mussels]

So it is an issue with the OS, not DirectX? Why didn't they release a hotfix on Windows Update to fix it?

... did you not read the thread? there is a hotfix.

 

[FordGT90Concept]

That doesn't work (or works intermittently) and is not on Windows Update.


Edit: According the the MS article, the problem is in DirectX Diagnostics Tool (dxdiag.exe along with dxdiagn.dll). Like I said way back in this thread, the DDI number is incorrectly reported but it doesn't matter. The value games read and the like isn't in dxdiag. This is why Micosoft hasn't rushed to fix it. It is a minor issue that affects virtually nothing. Unless, of course, the article is misleading.

 

[EastCoasthandle]

Per my post earlier in this thread I've noticed a difference in Dirt 2. So I'm of the opinion there is more to then just DDI number.

 

[Mr McC]

Shit: just checked this (W7 64, Powercolor PCS+ 5870) and DirectX is displaying as 10.1 in the diagnostic tool. Are we reduced to waiting for a working fix in a Windows update?

 

[TRIPTEX_CAN]

hmm.. I'll have to check this out later but I have the feeling this issue probably exists on my system and will piss me off greatly.

What has been seen cannot be unseen. :shadedshu

 

[EastCoasthandle]

The fix is in the OP.

 

[New Guy]

DX11 not reporting as DDI 11

Since getting advice on here I have no longer had the problem, no doubt it took ages to sort, but it can be solved, quick re-cap
1. disable all page files.
2.uninstall the hotfix if you have in on system.
3. uninstall cat drivers, and then run win in low res mode, uninstall again any drivers windows puts on there.
4. then install whatever version of cat driver you want. restart
5. run win in normal mode. check dxdiag, 10.1?? install hotfix! should now say 11, it did for me at this point, then save the system information from dxdiag on desktop (just what I did, and still have it there). restart.
6. still ddi 11? great. enable page files again. restart.
7 should be hot to trot.

The fix if def here in the thread just just need to stick at it until it works, with guidance it only took me a few hours to finally fix.
been monhs since i did this and no probs.

best of luck.

 

[Mr McC]

The fix is in the OP.

Yes I read that, but have you got it to remain on DirectX 11 without reverting back?

 

[EastCoasthandle]

Yup, just like New Guy posted no problems.

 

[20mmrain]

Okay I had this exact problem and I was about to give up..... I did 5 or 6 driver installs I asl did two Complete windows Reinstalls..... But none of it worked..... I couldn't even get Microsofts update to run. Well..... after trying one more time.....

I found out that the way Microsoft decides which Update is correct for your system is by what Internet browser you are using.

For example.... if you are using a 64 bit browser..... they will know to give you the 64 bit update.

Even if you tell them you are using 64 bit from a 32 browser they will still give you the wrong Update.

So I used the 64 bit IE re downloaded and now got it to work..... yeah for me!!!!

Just thought I would relay this message.

 

[Mussels]

That doesn't work (or works intermittently) and is not on Windows Update.


Edit: According the the MS article, the problem is in DirectX Diagnostics Tool (dxdiag.exe along with dxdiagn.dll). Like I said way back in this thread, the DDI number is incorrectly reported but it doesn't matter. The value games read and the like isn't in dxdiag. This is why Micosoft hasn't rushed to fix it. It is a minor issue that affects virtually nothing. Unless, of course, the article is misleading.

did you not read crusaders posts? he cant run several games in DX11 (stalker for example) when this bug kicks in.

 

[ComradeSader]

did you not read crusaders posts? he cant run several games in DX11 (stalker for example) when this bug kicks in.

Call of Pripyat, Aliens vs Predator and possibly Bad Company 2 (no real way to check that afaik since it isn't in the options and you need to change it via a text file).


For clarification..

DDI = 10.1 = No option in either CoP or AvP for DX11 settings.

DDI = 11 = Option in both CoP and AvP for DX11 settings.

Edit: According the the MS article, the problem is in DirectX Diagnostics Tool (dxdiag.exe along with dxdiagn.dll). Like I said way back in this thread, the DDI number is incorrectly reported but it doesn't matter. The value games read and the like isn't in dxdiag. This is why Micosoft hasn't rushed to fix it. It is a minor issue that affects virtually nothing. Unless, of course, the article is misleading.

Typical M$ BS. It DOES matter, as shown in this post and entire thread. They need to htfu and fix it, a PROPER, WORKING fix, not this useless hotfix crap that occasionally works until you restart your fucking PC.

 

[LiveOrDie]

what is this for all this to just fix a small bug

Crusader
if it was more than just a bug in dxdiag, DX11 wouldn't work meaning all the benches i've done with only DX11 demos wouldn't work!

 

[Mussels]

what is this for all this to just fix a small bug

Crusader
if it was more than just a bug in dxdiag, DX11 wouldn't work meaning all the benches i've done with only DX11 demos wouldn't work!

it breaks programs that auto detect. EG, games that work in 11, 10.1 and 10.0

You are testing programs that FORCE detection of 11, with no fallback - so they are working.

 

[LiveOrDie]

it breaks programs that auto detect. EG, games that work in 11, 10.1 and 10.0

You are testing programs that FORCE detection of 11, with no fallback - so they are working.

you are wrong Heaven Benchmark v2.0 default to DX11 with DX11 cards so does bf bc they all default to DX11

 

[gaximodo]

Mine with DDI 10.1 as well, dirt 2 dx 11 works perfectly.

 

[LiveOrDie]

more likely a driver bug for ati in the 4XXX cards

 

[TRIPTEX_CAN]

I never had any problems running DX11 games but DDI was reporting 10.1 on my system. I had already recently purged the registry of all ATI keys so I manually removed hidden display devices in DEVMGMT.msc and ran the x64 hotfix from MS. After several reboots DDI still correctly shows 11.

 

[LiveOrDie]

well i installed the hotfix and it changed it with no problems at all, if any one whats the hotfix for windows 7 x64 here a link i uploaded it.

DX 11 Hotfix x64

 

[EastCoasthandle]

Mine with DDI 10.1 as well, dirt 2 dx 11 works perfectly.

Dirt 2 worked but when I added the DDI hotfix I no longer noticed any stuttering from the tessellated crowds (at the end of a race animation) and when dirt is kicked up from the cars during replay. As mentioned earlier in this thread.

 

[gaximodo]

In my case Dirt 2 worked but when I added the DDI hotfix frame rates improved. As mentioned earlier in this thread.

will test this tomorrow, with two 5850 everything maxed out and 8Xaa FPS jumps between 45 to 60 which disappointed me alot, looks like a bug tho, but with 4xaa everything was fine. It ran with 16 QsAA with my 275 SLI before and FPS never dropped below 60, I know it wasn't DX11 but now the game is unplayable with only just 8xaa, constant frame drops gets really annoying..And I notice MSI afterburner in game monitor never worked with DX11 games, will test this with dirt2 and BC2 tomorrow.