OldProf wrote:I've just noticed a new folder on my primary drive named $Windows.~BT, which contains sub-folders dating between July 10 and July 30. So far, not a lot of content. Could this be the Win10 download in progress?
trev123 wrote:OldProf wrote:I've just noticed a new folder on my primary drive named $Windows.~BT, which contains sub-folders dating between July 10 and July 30. So far, not a lot of content. Could this be the Win10 download in progress?
To see these you have to have show hidden files turned on.
GSkid wrote:Well I've scanned the forums and some Dell users are having the same sleep mode issues as HP users. Nvidia has come up a lot.
I also found out my laptop stopped reading a newer SanDisk thumb drive of mine under 10 that it did read under 8 before the upgrade. The same thumb drive still works with my other win 7 and 8 laptops I own. I tried a few of my other thumb drives (including a different SanDisk) on my 10 laptop and they work fine. Windows 10 started the process of searching and installing a driver in each USB port I installed the newer SanDisk in.....but never showed up in "This PC" as even being plugged in so I can access it. My other thumb drives popped up no problem and with no need to find and install drivers.
trev123 wrote:My Windows 10 PC only stays in sleep mode for a couple of hours then turns itself on.
_o_OOOO_oo-Kanawha wrote:What nVidia driver version ships with W10?
Is the "9" screen still corrupted with using SSAA 2x2 etc?
_o_OOOO_oo-Kanawha wrote:What nVidia driver version ships with W10?
Is the "9" screen still corrupted with using SSAA 2x2 etc?
_o_OOOO_oo-Kanawha wrote:What nVidia driver version ships with W10?
Is the "9" screen still corrupted with using SSAA 2x2 etc?
trev123 wrote:_o_OOOO_oo-Kanawha wrote:What nVidia driver version ships with W10?
Is the "9" screen still corrupted with using SSAA 2x2 etc?
Yes. I have read somewhere that DTG have been in contact with Nvidia about the issue. As a temporary fix set AA to FXAA+8xMSAA. I'm using the
353.62 drivers. I did the W7 to W10 upgrade so the 353.62 drivers were still used sort of, as I had to click on them in device manager to get them to work as already mentioned.
Users browsing this forum: No registered users and 1 guest