And the worst is that the OS will install/Update the display drivers even if you disable this option on Advanced System Properties > Hardware.
This happened once :/
Maybe just a bug.
Type: Posts; User: WinInsiderBeta
And the worst is that the OS will install/Update the display drivers even if you disable this option on Advanced System Properties > Hardware.
This happened once :/
Maybe just a bug.
I read somewhere that the "Fast Ring" is also used to update drivers. Maybe 368.20 is available only for insiders, and will eventually hit the general public.
I may be wrong though.
Yep, seems the drivers are WHQL. Maybe WDDM 2.1 and D3D 11.4 are specific for Redstone and require this specific driver version to be enabled?
I couldn't find much info about this too.
No one?
The nvidia drivers have been updated on WU, to version 368.20.
I opened DXDiag and noticed WDDM was also updated to v2.1 and the DirectX DDI to v11.4.
Is this a beta driver? Or is DxDiag...
If i understood correctly, the CPU is actually required to close the circuit to make the network card work?
Yep, i knew this question would sound silly.
But i really didn't know a mobo needs a CPU even for the most basic tasks such as lighting an LED.
I'm still very noob and this is my first ever...
Oh well, Looks like i'll have no way to know until next week then.
Thanks everyone. :)
The mobo actually turns on without the processor, all fans work, HDD works, DvD drive works... but the network LEDs don't.
I don't have the CPU yet :D, it will arrive next week, i'm unable to...
Dumb question: does the network card require a CPU to be able to recognize network activity?
In my previous mobo, the ethernet port's green and orange LEDs would always be lit. Even if the computer was powered off.
But i noticed that this new mobo doesn't do this. I connected the network...
It's from Zogis, model ZOGT730-2GD3H12.
I didn't mean to sound like an nvidia hater or something like that.
As i said, i was wrong about this. It was not an issue with the card, but with the monitor and/or It's cable.
But when i first encountered the issue, i thought the GPU was the culprit.
I...
Now this is a surprise. Looks like this GeForce GT 730 really was defective after all.
I was playing a little with Mac OS X, then due to chipset compatibilty problems i decided to go back to...
Looks like i'll need a new PSU as well, don't want to risk damaging any of the components.
I just hope to finish this upgrade before the July 29 Windows 10 upgrade deadline. (As i won't be able to...
It's an ATX-650-P2L from the brand Mtek. It's about 4 years old.
Yep, this PC has fans for PSU, GPU and CPU. I'll see if this power supply will do it, if not, i may have to buy a new one.
I will do the following upgrades:
- New ASUS M5A78L-M LX/BR AM3+ mobo;
- New AMD FX-6300 3.5GHz CPU;
- 2x4GB DDR3 1600MHz Corsair Vengeance RAM Kit, for a total of 8GB.
I'll be doing...
I know this sounds like a hassle, but going back to build 14295 and then upgrading again to 14342 fixed the initial 0x80073CF3 error and i was able to install the new 11604.1000.27.0 update. Since...
Could be a nice fresh Fast Ring build! :D
Yep, got this update here too. Interesting.
I think we'll have a Feedback Hub post about this patch in a few hours.
I followed your tip of uninstalling the existing driver before installing the new one, and it works! No black screens and no need to force restart the PC.
These are the steps i took:
-...
Was looking at BuildFeed, this is the last build listed there:
10.0.14346.1000.rs1_release.160512-1748
Since it looks like RS1 is pretty much feature complete, could this build be the final...
Ok, then i'll disable the automatic driver updates in Windows and download newer versions straight from nvidia. Or even use the built-in GeForce Experience utility.
I think i found a possible reason for the problem:
Today i upgraded to build 14342, and the same driver that caused the black screen in 10586 and 14295, installed flawlessly in the latest build.
...