How important is CPU performance for 3d vision?
  17 / 22    
[quote="tygeezy"]Also, if you note the video, the corruption always happens at the same part. It gets passed the bios screen, the windows logo pops up and then bam. Corruption and then dark screen. Memtest ruled out any errors, although I only did one pass. If there was truly a videocard issue hardware wise I think it would be popping up elsewhere. So far I only had those flickers one time. Although that could be a windows issue as well. I don't think my videocard would always make it passed the bios screen and show windows logo, try to load and then be hit. So i'm with you Bob. Maybe I submit this to Microsoft? Although it isn't generating an error.[/quote] Are you running most recent video driver, 381.65? It looks like Creator's requires a newer video driver too because of changes to the WDDM. That also means you cannot go back to older drivers for any reason. Video corruption and crash could definitely be a video driver problem at that moment. Also, did you let it do the 'upgrade' from Anniversary? For the Anniversary update at least, if you did the 'upgrade' you wound up with a corrupted OS with all sorts of weird problems. Doing clean-metal install of Anniversary fixed innumerable problems. If you haven't already, you should do a clean install from scratch to run the Creator's version.
tygeezy said:Also, if you note the video, the corruption always happens at the same part. It gets passed the bios screen, the windows logo pops up and then bam. Corruption and then dark screen. Memtest ruled out any errors, although I only did one pass.

If there was truly a videocard issue hardware wise I think it would be popping up elsewhere. So far I only had those flickers one time. Although that could be a windows issue as well. I don't think my videocard would always make it passed the bios screen and show windows logo, try to load and then be hit. So i'm with you Bob. Maybe I submit this to Microsoft? Although it isn't generating an error.

Are you running most recent video driver, 381.65? It looks like Creator's requires a newer video driver too because of changes to the WDDM. That also means you cannot go back to older drivers for any reason.

Video corruption and crash could definitely be a video driver problem at that moment.


Also, did you let it do the 'upgrade' from Anniversary? For the Anniversary update at least, if you did the 'upgrade' you wound up with a corrupted OS with all sorts of weird problems. Doing clean-metal install of Anniversary fixed innumerable problems.

If you haven't already, you should do a clean install from scratch to run the Creator's version.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

Posted 04/12/2017 12:42 AM   
[quote="bo3b"][quote="tygeezy"]Also, if you note the video, the corruption always happens at the same part. It gets passed the bios screen, the windows logo pops up and then bam. Corruption and then dark screen. Memtest ruled out any errors, although I only did one pass. If there was truly a videocard issue hardware wise I think it would be popping up elsewhere. So far I only had those flickers one time. Although that could be a windows issue as well. I don't think my videocard would always make it passed the bios screen and show windows logo, try to load and then be hit. So i'm with you Bob. Maybe I submit this to Microsoft? Although it isn't generating an error.[/quote] Are you running most recent video driver, 381.65? It looks like Creator's requires a newer video driver too because of changes to the WDDM. That also means you cannot go back to older drivers for any reason. Video corruption and crash could definitely be a video driver problem at that moment. Also, did you let it do the 'upgrade' from Anniversary? For the Anniversary update at least, if you did the 'upgrade' you wound up with a corrupted OS with all sorts of weird problems. Doing clean-metal install of Anniversary fixed innumerable problems. If you haven't already, you should do a clean install from scratch to run the Creator's version.[/quote]Actually I took this drive from my old computer OS and all and just used it for my new build. Once it booted into windows 10 I then did a clean reinstall from within the OS. That cleanreinstall came with the anniversary edition. I didn't need to subsequently download and install aniversary edition. I purchased another key because my old install was from another motherboard. Everything worked great until the new update. I used Microsofts program called "windows updater" to download the creative update. Interestingly enough there was an update last night that was listed as critical. It came on the same day that the creative update was available to everybody officially. I've done about 7 boots fro ma shutdown since installing that update and haven't had the issue since... We will see if that trend continues because initially using ddu solved the problem. If the problem comes back I will do another clean reinstall from my current creatively updated windows 10.
bo3b said:
tygeezy said:Also, if you note the video, the corruption always happens at the same part. It gets passed the bios screen, the windows logo pops up and then bam. Corruption and then dark screen. Memtest ruled out any errors, although I only did one pass.

If there was truly a videocard issue hardware wise I think it would be popping up elsewhere. So far I only had those flickers one time. Although that could be a windows issue as well. I don't think my videocard would always make it passed the bios screen and show windows logo, try to load and then be hit. So i'm with you Bob. Maybe I submit this to Microsoft? Although it isn't generating an error.

Are you running most recent video driver, 381.65? It looks like Creator's requires a newer video driver too because of changes to the WDDM. That also means you cannot go back to older drivers for any reason.

Video corruption and crash could definitely be a video driver problem at that moment.


Also, did you let it do the 'upgrade' from Anniversary? For the Anniversary update at least, if you did the 'upgrade' you wound up with a corrupted OS with all sorts of weird problems. Doing clean-metal install of Anniversary fixed innumerable problems.

If you haven't already, you should do a clean install from scratch to run the Creator's version.
Actually I took this drive from my old computer OS and all and just used it for my new build. Once it booted into windows 10 I then did a clean reinstall from within the OS. That cleanreinstall came with the anniversary edition. I didn't need to subsequently download and install aniversary edition. I purchased another key because my old install was from another motherboard. Everything worked great until the new update. I used Microsofts program called "windows updater" to download the creative update.

Interestingly enough there was an update last night that was listed as critical. It came on the same day that the creative update was available to everybody officially.

I've done about 7 boots fro ma shutdown since installing that update and haven't had the issue since... We will see if that trend continues because initially using ddu solved the problem.

If the problem comes back I will do another clean reinstall from my current creatively updated windows 10.

Posted 04/12/2017 06:32 PM   
[quote="tygeezy"]Actually I took this drive from my old computer OS and all and just used it for my new build. Once it booted into windows 10 I then did a clean reinstall from within the OS. That cleanreinstall came with the anniversary edition. I didn't need to subsequently download and install aniversary edition. I purchased another key because my old install was from another motherboard. Everything worked great until the new update. I used Microsofts program called "windows updater" to download the creative update. Interestingly enough there was an update last night that was listed as critical. It came on the same day that the creative update was available to everybody officially. I've done about 7 boots fro ma shutdown since installing that update and haven't had the issue since... We will see if that trend continues because initially using ddu solved the problem. If the problem comes back I will do another clean reinstall from my current creatively updated windows 10.[/quote] Uh, that's not a good strategy for doing updates. Moving an HD from one machine to another is rarely successful. There has been specialized software that makes a more universal boot, but normal Windows has never done that well. Win10 might be better in this regard, but it's hard to tell because of all the other problems. If you run into problems, the hot ticket is to download a Win10 ISO directly. You use your license key, and the cloud server builds you an ISO/USB that you can use to boot and install. It's the "Create Windows 10 Installation Media". After this week, it will be creating a Creator's edition only. [url]https://www.microsoft.com/en-us/software-download/windows10[/url] Anything other than using that is an upgrade-in-place, and is prone to conflicts and errors.
tygeezy said:Actually I took this drive from my old computer OS and all and just used it for my new build. Once it booted into windows 10 I then did a clean reinstall from within the OS. That cleanreinstall came with the anniversary edition. I didn't need to subsequently download and install aniversary edition. I purchased another key because my old install was from another motherboard. Everything worked great until the new update. I used Microsofts program called "windows updater" to download the creative update.

Interestingly enough there was an update last night that was listed as critical. It came on the same day that the creative update was available to everybody officially.

I've done about 7 boots fro ma shutdown since installing that update and haven't had the issue since... We will see if that trend continues because initially using ddu solved the problem.

If the problem comes back I will do another clean reinstall from my current creatively updated windows 10.

Uh, that's not a good strategy for doing updates. Moving an HD from one machine to another is rarely successful. There has been specialized software that makes a more universal boot, but normal Windows has never done that well. Win10 might be better in this regard, but it's hard to tell because of all the other problems.

If you run into problems, the hot ticket is to download a Win10 ISO directly. You use your license key, and the cloud server builds you an ISO/USB that you can use to boot and install. It's the "Create Windows 10 Installation Media". After this week, it will be creating a Creator's edition only.

https://www.microsoft.com/en-us/software-download/windows10


Anything other than using that is an upgrade-in-place, and is prone to conflicts and errors.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

Posted 04/12/2017 10:39 PM   
[quote="bo3b"][quote="tygeezy"]Actually I took this drive from my old computer OS and all and just used it for my new build. Once it booted into windows 10 I then did a clean reinstall from within the OS. That cleanreinstall came with the anniversary edition. I didn't need to subsequently download and install aniversary edition. I purchased another key because my old install was from another motherboard. Everything worked great until the new update. I used Microsofts program called "windows updater" to download the creative update. Interestingly enough there was an update last night that was listed as critical. It came on the same day that the creative update was available to everybody officially. I've done about 7 boots fro ma shutdown since installing that update and haven't had the issue since... We will see if that trend continues because initially using ddu solved the problem. If the problem comes back I will do another clean reinstall from my current creatively updated windows 10.[/quote] Uh, that's not a good strategy for doing updates. Moving an HD from one machine to another is rarely successful. There has been specialized software that makes a more universal boot, but normal Windows has never done that well. Win10 might be better in this regard, but it's hard to tell because of all the other problems. If you run into problems, the hot ticket is to download a Win10 ISO directly. You use your license key, and the cloud server builds you an ISO/USB that you can use to boot and install. It's the "Create Windows 10 Installation Media". After this week, it will be creating a Creator's edition only. [url]https://www.microsoft.com/en-us/software-download/windows10[/url] Anything other than using that is an upgrade-in-place, and is prone to conflicts and errors.[/quote]Yeah, just turned it on when I got home and got that issue again... I can put the iso o na thumb drive and do a boot into thumb drive/format/install and use the key I got without issues yes? Or do I need to revoke my key before I do it again? Im assuming i dont need to do that because its being installed on the same motherboard. I had thought the windows 10's built in repair install feature was the same as booting from a usb these days. [img]http://cdn.makeuseof.com/wp-content/uploads/2016/06/Windows-10-Reset-640x375.png?edc8eb[/img]
bo3b said:
tygeezy said:Actually I took this drive from my old computer OS and all and just used it for my new build. Once it booted into windows 10 I then did a clean reinstall from within the OS. That cleanreinstall came with the anniversary edition. I didn't need to subsequently download and install aniversary edition. I purchased another key because my old install was from another motherboard. Everything worked great until the new update. I used Microsofts program called "windows updater" to download the creative update.

Interestingly enough there was an update last night that was listed as critical. It came on the same day that the creative update was available to everybody officially.

I've done about 7 boots fro ma shutdown since installing that update and haven't had the issue since... We will see if that trend continues because initially using ddu solved the problem.

If the problem comes back I will do another clean reinstall from my current creatively updated windows 10.

Uh, that's not a good strategy for doing updates. Moving an HD from one machine to another is rarely successful. There has been specialized software that makes a more universal boot, but normal Windows has never done that well. Win10 might be better in this regard, but it's hard to tell because of all the other problems.

If you run into problems, the hot ticket is to download a Win10 ISO directly. You use your license key, and the cloud server builds you an ISO/USB that you can use to boot and install. It's the "Create Windows 10 Installation Media". After this week, it will be creating a Creator's edition only.

https://www.microsoft.com/en-us/software-download/windows10


Anything other than using that is an upgrade-in-place, and is prone to conflicts and errors.
Yeah, just turned it on when I got home and got that issue again... I can put the iso o na thumb drive and do a boot into thumb drive/format/install and use the key I got without issues yes? Or do I need to revoke my key before I do it again? Im assuming i dont need to do that because its being installed on the same motherboard.

I had thought the windows 10's built in repair install feature was the same as booting from a usb these days.

Image

Posted 04/13/2017 01:00 AM   
I'm doing this shit now Bob. I installed the new dolby atmos and I was playing the video to demonstrate it and the video lagged while the sound played. I couldn't quit out of the media player using control alt delete. I repeatedly had to reset my pc. Unacceptable to me and i'm confident there is an issue with my windows install.
I'm doing this shit now Bob. I installed the new dolby atmos and I was playing the video to demonstrate it and the video lagged while the sound played. I couldn't quit out of the media player using control alt delete. I repeatedly had to reset my pc. Unacceptable to me and i'm confident there is an issue with my windows install.

Posted 04/13/2017 03:41 AM   
My damn USB drive failed when I tried to load it.. So I just did the reset pc option. So, the dolby atmos preview video becoming unresponsive is an NVidia driver issue. Without the drivers installed I don't have an issue. With the newest drivers it causes the video to halt play, but sound plays and I cant exit... Very weird. I'm going to try and secure another usb 3 thumb drive and try the install from that later after playing with this. I'm going to use ddu and go back to the previous driver from March to see if this solves this. Edit: Reverting back to march drivers solved the dolby atmos video/ preview thing. This whole problem might be attributed to the new drivers.....
My damn USB drive failed when I tried to load it.. So I just did the reset pc option. So, the dolby atmos preview video becoming unresponsive is an NVidia driver issue. Without the drivers installed I don't have an issue. With the newest drivers it causes the video to halt play, but sound plays and I cant exit... Very weird. I'm going to try and secure another usb 3 thumb drive and try the install from that later after playing with this.

I'm going to use ddu and go back to the previous driver from March to see if this solves this.

Edit: Reverting back to march drivers solved the dolby atmos video/ preview thing. This whole problem might be attributed to the new drivers.....

Posted 04/13/2017 04:49 AM   
I'm pretty confident it was the new NVidia driver all along. Its behaving slightly differently on boot. Its much faster number one. On successful boots on the newest driver it shows the windows logo, it disappeared and came back before loading windows. While doing that it had the windows loading icon. With this driver it shows the windows icon and just goes right into windows without showing the screen twice and without the loading icon.
I'm pretty confident it was the new NVidia driver all along. Its behaving slightly differently on boot. Its much faster number one. On successful boots on the newest driver it shows the windows logo, it disappeared and came back before loading windows. While doing that it had the windows loading icon. With this driver it shows the windows icon and just goes right into windows without showing the screen twice and without the loading icon.

Posted 04/13/2017 05:50 AM   
@tygeezy corruption windows logo at boot this is a fast boot issue according to Guru3D forums http://forums.guru3d.com/showthread.php?p=5420015
@tygeezy

corruption windows logo at boot this is a fast boot issue according to Guru3D forums

http://forums.guru3d.com/showthread.php?p=5420015

Gigabyte Z370 Gaming 7 32GB Ram i9-9900K GigaByte Aorus Extreme Gaming 2080TI (single) Game Blaster Z Windows 10 X64 build #17763.195 Define R6 Blackout Case Corsair H110i GTX Sandisk 1TB (OS) SanDisk 2TB SSD (Games) Seagate EXOs 8 and 12 TB drives Samsung UN46c7000 HD TV Samsung UN55HU9000 UHD TVCurrently using ACER PASSIVE EDID override on 3D TVs LG 55

Posted 04/13/2017 02:27 PM   
[quote="zig11727"]@tygeezy corruption windows logo at boot this is a fast boot issue according to Guru3D forums http://forums.guru3d.com/showthread.php?p=5420015[/quote]I'll have to check if fast boot is enabled by default because I didn't enable it. I'm having more than just issues with boot though. I have videos freezing too.
zig11727 said:@tygeezy

corruption windows logo at boot this is a fast boot issue according to Guru3D forums

http://forums.guru3d.com/showthread.php?p=5420015
I'll have to check if fast boot is enabled by default because I didn't enable it. I'm having more than just issues with boot though. I have videos freezing too.

Posted 04/13/2017 05:43 PM   
By the way Zig, I posted my video on that thread and a guy with a very similar system is having the same issue with these drivers. What a turd sandwich these drivers are, made me reinstall my os...lol
By the way Zig, I posted my video on that thread and a guy with a very similar system is having the same issue with these drivers. What a turd sandwich these drivers are, made me reinstall my os...lol

Posted 04/13/2017 07:25 PM   
[quote="tygeezy"]My damn USB drive failed when I tried to load it.. So I just did the reset pc option. So, the dolby atmos preview video becoming unresponsive is an NVidia driver issue. Without the drivers installed I don't have an issue. With the newest drivers it causes the video to halt play, but sound plays and I cant exit... Very weird. I'm going to try and secure another usb 3 thumb drive and try the install from that later after playing with this. I'm going to use ddu and go back to the previous driver from March to see if this solves this. Edit: Reverting back to march drivers solved the dolby atmos video/ preview thing. This whole problem might be attributed to the new drivers.....[/quote] Could definitely be the video drivers problem. It's at the right moment in boot. However, going back to older drivers is problematic, because Creator's Update requires a brand new driver. So, you would be running something funny that isn't supported. For USB, you don't need USB 3 drives, any USB 2 drive that is at least 8G will work. It's only a little bit slower to install from that. I don't know enough about the built in 'reset OS' option in Windows 10, but my confidence level in Microsoft getting this right- is zero. It might correctly restore all the system files, but it has no way to know what to do with drivers. It's worth noting that this 'reset OS' option did not work for the Anniversary Update version problems. Something about the upgrade process is completely busted, people moving from 7 to 10 had problems, and from 10 to Anniversary also had problems. It's logical to assume they will botch this one too. Your best bet is still to do a clean install from scratch, using the link I made above. That will also net you a theoretically exactly right WHQL video driver for that version of the OS.
tygeezy said:My damn USB drive failed when I tried to load it.. So I just did the reset pc option. So, the dolby atmos preview video becoming unresponsive is an NVidia driver issue. Without the drivers installed I don't have an issue. With the newest drivers it causes the video to halt play, but sound plays and I cant exit... Very weird. I'm going to try and secure another usb 3 thumb drive and try the install from that later after playing with this.

I'm going to use ddu and go back to the previous driver from March to see if this solves this.

Edit: Reverting back to march drivers solved the dolby atmos video/ preview thing. This whole problem might be attributed to the new drivers.....

Could definitely be the video drivers problem. It's at the right moment in boot.

However, going back to older drivers is problematic, because Creator's Update requires a brand new driver. So, you would be running something funny that isn't supported.


For USB, you don't need USB 3 drives, any USB 2 drive that is at least 8G will work. It's only a little bit slower to install from that.


I don't know enough about the built in 'reset OS' option in Windows 10, but my confidence level in Microsoft getting this right- is zero. It might correctly restore all the system files, but it has no way to know what to do with drivers.

It's worth noting that this 'reset OS' option did not work for the Anniversary Update version problems. Something about the upgrade process is completely busted, people moving from 7 to 10 had problems, and from 10 to Anniversary also had problems. It's logical to assume they will botch this one too.


Your best bet is still to do a clean install from scratch, using the link I made above.

That will also net you a theoretically exactly right WHQL video driver for that version of the OS.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

Posted 04/13/2017 11:49 PM   
[quote="tygeezy"]By the way Zig, I posted my video on that thread and a guy with a very similar system is having the same issue with these drivers. What a turd sandwich these drivers are, made me reinstall my os...lol[/quote] Since you changed both at once, there is no way to know if it's the driver or the OS. NVidia drivers do tend to be tweaky, but my money is on Creator's Update being completely half-baked, like usual.
tygeezy said:By the way Zig, I posted my video on that thread and a guy with a very similar system is having the same issue with these drivers. What a turd sandwich these drivers are, made me reinstall my os...lol

Since you changed both at once, there is no way to know if it's the driver or the OS.

NVidia drivers do tend to be tweaky, but my money is on Creator's Update being completely half-baked, like usual.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

Posted 04/13/2017 11:54 PM   
[quote="bo3b"][quote="tygeezy"]My damn USB drive failed when I tried to load it.. So I just did the reset pc option. So, the dolby atmos preview video becoming unresponsive is an NVidia driver issue. Without the drivers installed I don't have an issue. With the newest drivers it causes the video to halt play, but sound plays and I cant exit... Very weird. I'm going to try and secure another usb 3 thumb drive and try the install from that later after playing with this. I'm going to use ddu and go back to the previous driver from March to see if this solves this. Edit: Reverting back to march drivers solved the dolby atmos video/ preview thing. This whole problem might be attributed to the new drivers.....[/quote] Could definitely be the video drivers problem. It's at the right moment in boot. However, going back to older drivers is problematic, because Creator's Update requires a brand new driver. So, you would be running something funny that isn't supported. For USB, you don't need USB 3 drives, any USB 2 drive that is at least 8G will work. It's only a little bit slower to install from that. I don't know enough about the built in 'reset OS' option in Windows 10, but my confidence level in Microsoft getting this right- is zero. It might correctly restore all the system files, but it has no way to know what to do with drivers. It's worth noting that this 'reset OS' option did not work for the Anniversary Update version problems. Something about the upgrade process is completely busted, people moving from 7 to 10 had problems, and from 10 to Anniversary also had problems. It's logical to assume they will botch this one too. Your best bet is still to do a clean install from scratch, using the link I made above. That will also net you a theoretically exactly right WHQL video driver for that version of the OS.[/quote]Yeah, I will do that method of installing the os again once it gets updated to the newest version with creators. Actually, did it already get updated? It seems like my thumb drive is having an issue, so that's why I thought getting a usb 3.0 one would be both more reliable and faster. Multiple people have come forward and said they have the same issue that my video shows though with creators and the new drivers. These older drivers don't seem to be an issue thus far.
bo3b said:
tygeezy said:My damn USB drive failed when I tried to load it.. So I just did the reset pc option. So, the dolby atmos preview video becoming unresponsive is an NVidia driver issue. Without the drivers installed I don't have an issue. With the newest drivers it causes the video to halt play, but sound plays and I cant exit... Very weird. I'm going to try and secure another usb 3 thumb drive and try the install from that later after playing with this.

I'm going to use ddu and go back to the previous driver from March to see if this solves this.

Edit: Reverting back to march drivers solved the dolby atmos video/ preview thing. This whole problem might be attributed to the new drivers.....

Could definitely be the video drivers problem. It's at the right moment in boot.

However, going back to older drivers is problematic, because Creator's Update requires a brand new driver. So, you would be running something funny that isn't supported.


For USB, you don't need USB 3 drives, any USB 2 drive that is at least 8G will work. It's only a little bit slower to install from that.


I don't know enough about the built in 'reset OS' option in Windows 10, but my confidence level in Microsoft getting this right- is zero. It might correctly restore all the system files, but it has no way to know what to do with drivers.

It's worth noting that this 'reset OS' option did not work for the Anniversary Update version problems. Something about the upgrade process is completely busted, people moving from 7 to 10 had problems, and from 10 to Anniversary also had problems. It's logical to assume they will botch this one too.


Your best bet is still to do a clean install from scratch, using the link I made above.

That will also net you a theoretically exactly right WHQL video driver for that version of the OS.
Yeah, I will do that method of installing the os again once it gets updated to the newest version with creators. Actually, did it already get updated? It seems like my thumb drive is having an issue, so that's why I thought getting a usb 3.0 one would be both more reliable and faster. Multiple people have come forward and said they have the same issue that my video shows though with creators and the new drivers. These older drivers don't seem to be an issue thus far.

Posted 04/13/2017 11:56 PM   
[quote="tygeezy"]Yeah, I will do that method of installing the os again once it gets updated to the newest version with creators. Actually, did it already get updated? It seems like my thumb drive is having an issue, so that's why I thought getting a usb 3.0 one would be both more reliable and faster. Multiple people have come forward and said they have the same issue that my video shows though with creators and the new drivers. These older drivers don't seem to be an issue thus far.[/quote] Hard to say. When you are on the very bleeding edge of updates and software, you can easily be suffering from bugs that will get fixed in a week or so. Microsoft appears to have given up on their traditionally very strong QA, in favor of going with the early beta style releases to the Windows Insiders program. Hint- it's cheaper. So far, that approach has sucked pretty hard. Windows Insiders are not sufficiently representative of the gamut of hardware that is out there, and they've broken stuff in pretty serious ways. Always your call how you like to spend your time, but being on the leading edge is sure to be exciting and full of extra work.
tygeezy said:Yeah, I will do that method of installing the os again once it gets updated to the newest version with creators. Actually, did it already get updated? It seems like my thumb drive is having an issue, so that's why I thought getting a usb 3.0 one would be both more reliable and faster. Multiple people have come forward and said they have the same issue that my video shows though with creators and the new drivers. These older drivers don't seem to be an issue thus far.

Hard to say. When you are on the very bleeding edge of updates and software, you can easily be suffering from bugs that will get fixed in a week or so.

Microsoft appears to have given up on their traditionally very strong QA, in favor of going with the early beta style releases to the Windows Insiders program. Hint- it's cheaper.

So far, that approach has sucked pretty hard. Windows Insiders are not sufficiently representative of the gamut of hardware that is out there, and they've broken stuff in pretty serious ways.


Always your call how you like to spend your time, but being on the leading edge is sure to be exciting and full of extra work.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

Posted 04/14/2017 12:01 AM   
Bob, do you think Microsoft's installation media is updated to creators yet?
Bob, do you think Microsoft's installation media is updated to creators yet?

Posted 04/14/2017 04:17 PM   
  17 / 22    
Scroll To Top