DXDiag is probably getting that from the Registry or from some direct hardware query, but whatever legitimate DirectX call Blitz makes to get this information obviously returns something different (probably returned from the driver itself).
I imagine I'll be able to find this 'correct' value in the Registry later, though Blitz is doing what it's meant to do... email me so I have a reminder later on!
I imagine I'll be able to find this 'correct' value in the Registry later, though Blitz is doing what it's meant to do... email me so I have a reminder later on!