If you run HWiNFO in Sensors-only mode, then you don't get the main window, where you can create a Report File. So in that case disable Sensors-only, let it run thru and in the main window menu click Save Report.
Enabling Debug Mode will create an additional file called HWiNFO64.DBG when you close HWiNFO.
I did an additional trial, this time putting the 1060 in the secondary PCIe slot while my 1070 was primary (last time a 750Ti was primary).
Again device manager displays the 1060 as a generic Windows display device with a driver problem
I've made HWiNFO reports and debug files, and attached them to an email to the address shown on the HWiNFO help page. I hope that is satisfactory for your purpose.
I don't mean you haven't thought about this, but have you tried uninstalling all the remnants of possible broken Nvidia GPU driver installations with DDU (running the uninstaller file as administrator, then letting it begin with rebooting into safe mode with networking). http://www.wagnardmobile.com/DDU/download/DDU%20v16.1.0.1.exe
Then let it do the cleaning and another reboot. Then install maybe 368.95 (running the installer file as administrator): http://nvidia.custhelp.com/app/answers/detail/a_id/4202
And if the installation went alright, then yet a final reboot.
I have used DDU on more than one of my unsuccessful attempts with the 1060.
I have not tried the hotfix release 368.95 and was not aware of it until I saw your post. I don't recognize the issue it is stated to address (DPC latency bug on Pascal GPUs), but perhaps I should install it for my 1070's sake. But that issue seems seriously unlikely to cause the failure of the driver installer to see that there is an Nvidia card in the system it cares to attempt to drive.
All of my trials on the 1060 have used 368.81, which was and remains the only driver Nvidia points to from even the beta and older drivers hand search for GTX 1060 on my platform (Windows 10 64-bit).
If you run HWiNFO in Sensors-only mode, then you don't get the main window, where you can create a Report File. So in that case disable Sensors-only, let it run thru and in the main window menu click Save Report.
Enabling Debug Mode will create an additional file called HWiNFO64.DBG when you close HWiNFO.
I did an additional trial, this time putting the 1060 in the secondary PCIe slot while my 1070 was primary (last time a 750Ti was primary).
Again device manager displays the 1060 as a generic Windows display device with a driver problem
I've made HWiNFO reports and debug files, and attached them to an email to the address shown on the HWiNFO help page. I hope that is satisfactory for your purpose.
Thank you.
Got it, thanks.
Will check it and reply via e-mail.
I have a 1060 by MSI on its way. It could be up and running by Tuesday, if it installs and otherwise behaves itself.
Currently your computers are hidden. Would you consider unhiding them so others can observe the early stages of your 1060 work?
By the way, I was able to place an order for an MSRP card at Amazon, so by early next week I should be having my second try with a 1060, this time one which only cost me $250 delivered.
The first three tasks are crunching in parallel on the new 1060. The card is the MSI GeForce GTX 1060 DirectX 12 GTX 1060 GAMING X 6G. Everything is stock. Watts at the wall 125-130W, that's 55-65W for the card. Progress is not exactly lightning fast. I expect on the order of more than 3 hours 30 minutes elapsed time for each of the three tasks, i.e. about 70 minutes elapsed per task. GPU utilization is about 77%, memory manager utilization about 71%, temp in the mid 50 degree range, fans almost never on.
So far so good. Power draw is amazingly low. Cruch times are slower than I expected at stock. Everything looks stable and that alone is a very nice surprise.
This is all using Win 10. The beta driver install had some strange moments.
I'll unhide the computers when I get back to the house.
Yes, they seem much slower than I'd have guessed. The GPU utilization is much lower than I'd expect for 3X also.
Quote:
The beta driver install had some strange moments.
Are you using the 368.95 DPC latency hotfix driver instead of the 368.81 that the driver download page offers for the 1060?
Have you looked for symptoms of memory leak? If your 1060 is like my 1070 and my 970 running on Windows 10 64-bit, it will be adding very steadily to "pool pages bytes" as selectable from Performance Monitor Memory|Pool paged bytes, and if you happen to have poolmon installed, the Vi12 tag will climb steady as the result of hundreds of 239-byte allocs unmatched by frees each second.
Cal, did you free enough CPU ressources to support the card? What slot does it sit in? Does it even boost to its full clock speed? Judging by the power consumption and GPU usage I suppose not.
1st slot, 1.0 CPU per task, all stock at this point. If it doesn't boost to boost then that's just what it does when left to its own devices. I had zero time to mess with settings and I also wanted to have a solid baseline. 81 driver.
RE: If you run HWiNFO in
)
I did an additional trial, this time putting the 1060 in the secondary PCIe slot while my 1070 was primary (last time a 750Ti was primary).
Again device manager displays the 1060 as a generic Windows display device with a driver problem
I've made HWiNFO reports and debug files, and attached them to an email to the address shown on the HWiNFO help page. I hope that is satisfactory for your purpose.
Thank you.
I don't mean you haven't
)
I don't mean you haven't thought about this, but have you tried uninstalling all the remnants of possible broken Nvidia GPU driver installations with DDU (running the uninstaller file as administrator, then letting it begin with rebooting into safe mode with networking).
http://www.wagnardmobile.com/DDU/download/DDU%20v16.1.0.1.exe
Then let it do the cleaning and another reboot. Then install maybe 368.95 (running the installer file as administrator):
http://nvidia.custhelp.com/app/answers/detail/a_id/4202
And if the installation went alright, then yet a final reboot.
RE: DDU Then install
)
I have used DDU on more than one of my unsuccessful attempts with the 1060.
I have not tried the hotfix release 368.95 and was not aware of it until I saw your post. I don't recognize the issue it is stated to address (DPC latency bug on Pascal GPUs), but perhaps I should install it for my 1070's sake. But that issue seems seriously unlikely to cause the failure of the driver installer to see that there is an Nvidia card in the system it cares to attempt to drive.
All of my trials on the 1060 have used 368.81, which was and remains the only driver Nvidia points to from even the beta and older drivers hand search for GTX 1060 on my platform (Windows 10 64-bit).
RE: RE: If you run HWiNFO
)
Got it, thanks.
Will check it and reply via e-mail.
-----
RE: I have a 1060 by MSI on
)
Currently your computers are hidden. Would you consider unhiding them so others can observe the early stages of your 1060 work?
By the way, I was able to place an order for an MSRP card at Amazon, so by early next week I should be having my second try with a 1060, this time one which only cost me $250 delivered.
The first three tasks are
)
The first three tasks are crunching in parallel on the new 1060. The card is the MSI GeForce GTX 1060 DirectX 12 GTX 1060 GAMING X 6G. Everything is stock. Watts at the wall 125-130W, that's 55-65W for the card. Progress is not exactly lightning fast. I expect on the order of more than 3 hours 30 minutes elapsed time for each of the three tasks, i.e. about 70 minutes elapsed per task. GPU utilization is about 77%, memory manager utilization about 71%, temp in the mid 50 degree range, fans almost never on.
So far so good. Power draw is amazingly low. Cruch times are slower than I expected at stock. Everything looks stable and that alone is a very nice surprise.
This is all using Win 10. The beta driver install had some strange moments.
I'll unhide the computers when I get back to the house.
RE: Crunch times are slower
)
Yes, they seem much slower than I'd have guessed. The GPU utilization is much lower than I'd expect for 3X also.
Are you using the 368.95 DPC latency hotfix driver instead of the 368.81 that the driver download page offers for the 1060?
Have you looked for symptoms of memory leak? If your 1060 is like my 1070 and my 970 running on Windows 10 64-bit, it will be adding very steadily to "pool pages bytes" as selectable from Performance Monitor Memory|Pool paged bytes, and if you happen to have poolmon installed, the Vi12 tag will climb steady as the result of hundreds of 239-byte allocs unmatched by frees each second.
Cal, did you free enough CPU
)
Cal, did you free enough CPU ressources to support the card? What slot does it sit in? Does it even boost to its full clock speed? Judging by the power consumption and GPU usage I suppose not.
MrS
Scanning for our furry friends since Jan 2002
1st slot, 1.0 CPU per task,
)
1st slot, 1.0 CPU per task, all stock at this point. If it doesn't boost to boost then that's just what it does when left to its own devices. I had zero time to mess with settings and I also wanted to have a solid baseline. 81 driver.
It's time to Decommission
)
It's time to Decommission those (already obsolete) 1070 - 1080's
and get a pascal Titan X on Aug. 2nd : )
Bill
http://www.tomshardware.com/news/nvidia-pascal-titan-x-details,32323.html