-
-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Erroneous result "No DirectX 12, but WDDM2" #419
Comments
You have DX12 software installed but per your Direct3D, DDI, and Feature level your card does not support DX 12. This is supported per TechPowerUp |
Hi Robert,
Thanks for your prompt reply. I must apologise since I have quoted you the wrong Nvidia card … my laptop has a NVS 4200M.
I’ve just found a more recent driver, so I’m going to install that first.
Regards
Graham
From: Robert C. Maehl ***@***.***>
Sent: 06 July 2021 18:02
To: rcmaehl/WhyNotWin11 ***@***.***>
Cc: Wgrahamt ***@***.***>; Author ***@***.***>
Subject: Re: [rcmaehl/WhyNotWin11] Erroneous result "No DirectX 12, but WDDM2" (#419)
You have DX12 software installed but per your Direct3D, DDI, and Feature level your card does not support DX 12. This is supported per TechPowerUp
https://www.techpowerup.com/gpu-specs/quadro-nvs-420.c1448
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#419 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUX647LRZRVDRHRVLVCKE5LTWMZIHANCNFSM4742I2TQ> . <https://github.com/notifications/beacon/AUX647MH5UKYYE6WTEQUE2DTWMZIHA5CNFSM4742I2T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGQTGAKA.gif>
|
Ah, you have another one of the darn DirectX 12 "API" cards. These cards partially support DirectX 12 but not all of it. This will be resolved by #58 |
Got hold of the latest Windows 10 driver for the NVS 4200M and installed it - WhyNotWin11 gives a green pass for DirectX 12 & WDDM
Although the NVS 4200M still says DirectX 11 Support
Now, I’ll hopefully fix TPM by enabling in BIOS and plan change from MBR to UEFI in BIOS.
Thanks for your time and attention.
Graham
From: Robert C. Maehl ***@***.***>
Sent: 07 July 2021 15:16
To: rcmaehl/WhyNotWin11 ***@***.***>
Cc: Wgrahamt ***@***.***>; Author ***@***.***>
Subject: Re: [rcmaehl/WhyNotWin11] Erroneous result "No DirectX 12, but WDDM2" (#419)
Ah, you have another one of the darn DirectX 12 "API" cards. These cards partially support DirectX 12 but not all of it. This will be resolved by #58 <#58>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#419 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUX647NIOFQ2ALGKNXTYPA3TWROQ5ANCNFSM4742I2TQ> . <https://github.com/notifications/beacon/AUX647N5LBRQWXUOXUGN7KTTWROQ5A5CNFSM4742I2T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGQYT4KA.gif>
|
Closing per confirmed resolution |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running on my Dell Lattitude E6520 (Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz) laptop with an Nvidia NVS 420 graphics card running Windows 10 Build 19043.1081 - I get this result
Whereas if I run dxdiag.exe I get the result in the text file:-
DxDiag(1).txt
--- so WhyNotWinn1 is incorrectly reporting "No DirectX 12, but WDDM2" because on my laptop, the dxdiag shows both DirectX 12 and WDDM.
The Nvidia Control Panel Detaile Information shows:-
NVIDIA System Information 07-06-2021 16-26-45.txt
Regards
Graham
The text was updated successfully, but these errors were encountered: