Thanks guys. The IMEI drivers from my board manufacturer were installed, and Intel update tool showed no need for new drivers. However, I installed the package from tygeezy's link, and the problem hardware has been fixed.
It's a strange one.
Thanks guys. The IMEI drivers from my board manufacturer were installed, and Intel update tool showed no need for new drivers. However, I installed the package from tygeezy's link, and the problem hardware has been fixed.
It's a strange one.
Windows 10 64-bit, Intel 7700K @ 5.1GHz, 16GB 3600MHz CL15 DDR4 RAM, 2x GTX 1080 SLI, Asus Maximus IX Hero, Sound Blaster ZxR, PCIe Quad SSD, Oculus Rift CV1, DLP Link PGD-150 glasses, ViewSonic PJD6531w 3D DLP Projector @ 1280x800 120Hz native / 2560x1600 120Hz DSR 3D Gaming.
[quote="RAGEdemon"]Thanks guys. The IMEI drivers from my board manufacturer were installed, and Intel update tool showed no need for new drivers. However, I installed the package from tygeezy's link, and the problem hardware has been fixed.
It's a strange one.
[/quote]
Yeah, I tried the installer from intel and it didn't work. I then decided to go to my motherboards page and snoop around and found that device that Bob was talking about and gave that a go.
[quote="bo3b"]
You might also do a DDU reinstall of video driver. Especially if you are running Win10- it will change video drivers on you, silently.[/quote] This did the trick for me! Now oddly my mouse didn't work in safe mode, so I had to do everything with my keyboard; which was a pain in the ass. Not only did it fix that bootup issue, but I had noticed I had performance degradation. Specifically in Arkham knight. I thought I was going crazy, or maybe it was just a different part of the map that was more demanding. My fps was maxing out the 90 cap before and I was only getting 70-75 fps while panning the camera outside.
I had dropped the fps cap when I noticed this and then I decided to play the game after I used ddu plus installing the drivers again and my fps was going over 100 in the same areas of the map... I never knew that you could have such degradation in performance fro ma seemingly successful driver install. Windows wasn't reporting any issues, and id probably not have used ddu had I not had the boot problems. Arkham knight has a stigma of running like a turd, so I thought that was the issue honestly.
Should we be using ddu for every driver install? It makes me wonder after seeing such a huge performance boost. Albeit in one game. Also, I need to figure out what the deal with my mouse not being available in safe mode is about.
RAGEdemon said:Thanks guys. The IMEI drivers from my board manufacturer were installed, and Intel update tool showed no need for new drivers. However, I installed the package from tygeezy's link, and the problem hardware has been fixed.
It's a strange one.
Yeah, I tried the installer from intel and it didn't work. I then decided to go to my motherboards page and snoop around and found that device that Bob was talking about and gave that a go.
bo3b said:
You might also do a DDU reinstall of video driver. Especially if you are running Win10- it will change video drivers on you, silently.
This did the trick for me! Now oddly my mouse didn't work in safe mode, so I had to do everything with my keyboard; which was a pain in the ass. Not only did it fix that bootup issue, but I had noticed I had performance degradation. Specifically in Arkham knight. I thought I was going crazy, or maybe it was just a different part of the map that was more demanding. My fps was maxing out the 90 cap before and I was only getting 70-75 fps while panning the camera outside.
I had dropped the fps cap when I noticed this and then I decided to play the game after I used ddu plus installing the drivers again and my fps was going over 100 in the same areas of the map... I never knew that you could have such degradation in performance fro ma seemingly successful driver install. Windows wasn't reporting any issues, and id probably not have used ddu had I not had the boot problems. Arkham knight has a stigma of running like a turd, so I thought that was the issue honestly.
Should we be using ddu for every driver install? It makes me wonder after seeing such a huge performance boost. Albeit in one game. Also, I need to figure out what the deal with my mouse not being available in safe mode is about.
Should we be using ddu for every driver install? It makes me wonder after seeing such a huge performance boost. Albeit in one game. Also, I need to figure out what the deal with my mouse not being available in safe mode is about.[/quote]
When I install a new driver I always use DDU.
Should we be using ddu for every driver install? It makes me wonder after seeing such a huge performance boost. Albeit in one game. Also, I need to figure out what the deal with my mouse not being available in safe mode is about.
When I install a new driver I always use DDU.
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
[quote="zig11727"]
When I install a new driver I always use DDU.[/quote]
[/quote]I thought it was overkill to do that so often. Now i'm not so sure. It seems like i'm not the only one having issues with my mouse in safe mode. I saw a post from a guy with the same issue who fixed it by just using another mouse. Which is ludicrous to me because I don't have spare mice sitting around for safe mode use only... Or maybe I do, ill have to look.
zig11727 said:
When I install a new driver I always use DDU.
I thought it was overkill to do that so often. Now i'm not so sure. It seems like i'm not the only one having issues with my mouse in safe mode. I saw a post from a guy with the same issue who fixed it by just using another mouse. Which is ludicrous to me because I don't have spare mice sitting around for safe mode use only... Or maybe I do, ill have to look.
@tygeezy
According to person who wrote DDU you can use DDU normal mode regular windows desktop and then reboot after DDU finishes when the computer reboots run DDU in normal mode again then install the drivers.
This is a solution if you cannot use DDU in safe mode.
According to person who wrote DDU you can use DDU normal mode regular windows desktop and then reboot after DDU finishes when the computer reboots run DDU in normal mode again then install the drivers.
This is a solution if you cannot use DDU in safe mode.
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
Yeah, I [i]always[/i] use DDU when doing driver installs. I'd rather spend a little time up front to avoid nagging stupid shit hard to debug problems. It's completely idiotic that a 3rd party can do a better job here than NVidia. It's mind boggling how lame some of their stuff is.
For the mouse- about 1 in 5 reboots my mouse doesn't power up, even at normal desktop. Old Razer Diamondback. Bad software in the mouse. Sometimes happens in safe-mode, but less often. It's a timing issue.
The way to solve this is to plug and unplug the mouse. Should fire up. In my case, doing that will blue-screen nearly every time. Blue-screen from plugging in a USB? Should be impossible. Yeah, somewhere we've got some really fine software running.
So my alternate path is to bring up Device Manager using the keyboard, and select the yellow bang mouse, and do the disable, then enable, to bring it up.
As a software guy, this shitty code makes me insane, but wattaya gonna do?
Yeah, I always use DDU when doing driver installs. I'd rather spend a little time up front to avoid nagging stupid shit hard to debug problems. It's completely idiotic that a 3rd party can do a better job here than NVidia. It's mind boggling how lame some of their stuff is.
For the mouse- about 1 in 5 reboots my mouse doesn't power up, even at normal desktop. Old Razer Diamondback. Bad software in the mouse. Sometimes happens in safe-mode, but less often. It's a timing issue.
The way to solve this is to plug and unplug the mouse. Should fire up. In my case, doing that will blue-screen nearly every time. Blue-screen from plugging in a USB? Should be impossible. Yeah, somewhere we've got some really fine software running.
So my alternate path is to bring up Device Manager using the keyboard, and select the yellow bang mouse, and do the disable, then enable, to bring it up.
As a software guy, this shitty code makes me insane, but wattaya gonna do?
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
[quote="bo3b"]Yeah, I [i]always[/i] use DDU when doing driver installs. I'd rather spend a little time up front to avoid nagging stupid shit hard to debug problems. It's completely idiotic that a 3rd party can do a better job here than NVidia. It's mind boggling how lame some of their stuff is.
For the mouse- about 1 in 5 reboots my mouse doesn't power up, even at normal desktop. Old Razer Diamondback. Bad software in the mouse. Sometimes happens in safe-mode, but less often. It's a timing issue.
The way to solve this is to plug and unplug the mouse. Should fire up. In my case, doing that will blue-screen nearly every time. Blue-screen from plugging in a USB? Should be impossible. Yeah, somewhere we've got some really fine software running.
So my alternate path is to bring up Device Manager using the keyboard, and select the yellow bang mouse, and do the disable, then enable, to bring it up.
As a software guy, this shitty code makes me insane, but wattaya gonna do?[/quote]Hmmm, I hadn't tried plugging and unplugging. Unfortunately that means I have to get on my hands and knees... Being super lazy here! Yeah, after what I experience I think i'm going to go the ddu route to avoid problems and performance degradation.
Back in the day you always had to uninstall with control panel and then install. So driver installations required 2 reboots minimum. I hadn't noticed any problems by using the "Clean install" function for awhile now. Something is clearly amiss if you can have the problems I had with a simple update of drivers and then properly removing and then installing the same drivers to clear that issue up.
I took a couple of c++ courses, but I haven't tried any other languages. I wrote a simple text program to calculate true shooting percentage for basketball once.
bo3b said:Yeah, I always use DDU when doing driver installs. I'd rather spend a little time up front to avoid nagging stupid shit hard to debug problems. It's completely idiotic that a 3rd party can do a better job here than NVidia. It's mind boggling how lame some of their stuff is.
For the mouse- about 1 in 5 reboots my mouse doesn't power up, even at normal desktop. Old Razer Diamondback. Bad software in the mouse. Sometimes happens in safe-mode, but less often. It's a timing issue.
The way to solve this is to plug and unplug the mouse. Should fire up. In my case, doing that will blue-screen nearly every time. Blue-screen from plugging in a USB? Should be impossible. Yeah, somewhere we've got some really fine software running.
So my alternate path is to bring up Device Manager using the keyboard, and select the yellow bang mouse, and do the disable, then enable, to bring it up.
As a software guy, this shitty code makes me insane, but wattaya gonna do?
Hmmm, I hadn't tried plugging and unplugging. Unfortunately that means I have to get on my hands and knees... Being super lazy here! Yeah, after what I experience I think i'm going to go the ddu route to avoid problems and performance degradation.
Back in the day you always had to uninstall with control panel and then install. So driver installations required 2 reboots minimum. I hadn't noticed any problems by using the "Clean install" function for awhile now. Something is clearly amiss if you can have the problems I had with a simple update of drivers and then properly removing and then installing the same drivers to clear that issue up.
I took a couple of c++ courses, but I haven't tried any other languages. I wrote a simple text program to calculate true shooting percentage for basketball once.
Okay... It's back to doing that video corruption upon trying to boot into windows thing again. Something is definitely messed up hardware related I think. It gets passed the bios screen just fine, it then shows the windows logo and then the purple line corruption... Could this possibly be memory also?
Okay... It's back to doing that video corruption upon trying to boot into windows thing again. Something is definitely messed up hardware related I think. It gets passed the bios screen just fine, it then shows the windows logo and then the purple line corruption... Could this possibly be memory also?
Does it boot up though in spite of the corruption?
If you can get it to boot, the founders update can be installed which is a large overhaul to Win 10. This has a decent chance of fixing the issue if its Win10 related.
I find that new builds easily corrupt the OS because we are crashing the computer a lot trying to find that perfect overclock.
I would also +1 'DDU at every driver install' as bo3b and zig11727 say.
Btw, tygeezy and zig11727, what's your name, if you don't mind my asking? :)
Does it boot up though in spite of the corruption?
If you can get it to boot, the founders update can be installed which is a large overhaul to Win 10. This has a decent chance of fixing the issue if its Win10 related.
I find that new builds easily corrupt the OS because we are crashing the computer a lot trying to find that perfect overclock.
I would also +1 'DDU at every driver install' as bo3b and zig11727 say.
Btw, tygeezy and zig11727, what's your name, if you don't mind my asking? :)
Windows 10 64-bit, Intel 7700K @ 5.1GHz, 16GB 3600MHz CL15 DDR4 RAM, 2x GTX 1080 SLI, Asus Maximus IX Hero, Sound Blaster ZxR, PCIe Quad SSD, Oculus Rift CV1, DLP Link PGD-150 glasses, ViewSonic PJD6531w 3D DLP Projector @ 1280x800 120Hz native / 2560x1600 120Hz DSR 3D Gaming.
[quote="RAGEdemon"]Does it boot up though in spite of the corruption?
If you can get it to boot, the founders update can be installed which is a large overhaul to Win 10. This has a decent chance of fixing the issue if its Win10 related.
I find that new builds easily corrupt the OS because we are crashing the computer a lot trying to find that perfect overclock.
I would also +1 'DDU at every driver install' as bo3b and zig11727 say.
Btw, tygeezy and zig11727, what's your name, if you don't mind my asking? :)[/quote]No, it doesn't boot into windows once I get the corruption. The screen will go black and that's it. I have to power off and then power on and it seems to always boot into windows at that point. Its that first boot after a shutdown that gives me the corruption and then the black screen. I actually already installed the creative update. In fact, I don't remember having this issue before the creators update.
My name is Tyler.
RAGEdemon said:Does it boot up though in spite of the corruption?
If you can get it to boot, the founders update can be installed which is a large overhaul to Win 10. This has a decent chance of fixing the issue if its Win10 related.
I find that new builds easily corrupt the OS because we are crashing the computer a lot trying to find that perfect overclock.
I would also +1 'DDU at every driver install' as bo3b and zig11727 say.
Btw, tygeezy and zig11727, what's your name, if you don't mind my asking? :)
No, it doesn't boot into windows once I get the corruption. The screen will go black and that's it. I have to power off and then power on and it seems to always boot into windows at that point. Its that first boot after a shutdown that gives me the corruption and then the black screen. I actually already installed the creative update. In fact, I don't remember having this issue before the creators update.
I ran 1 pass of memtest last night and it found no errors. Maybe another time I can run the full 4 passes, but that will take 2 hours. That still makes me think it's either the videocard or there was some issue that happened with that windows update.
I ran 1 pass of memtest last night and it found no errors. Maybe another time I can run the full 4 passes, but that will take 2 hours. That still makes me think it's either the videocard or there was some issue that happened with that windows update.
Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
Windows 10 64-bit, Intel 7700K @ 5.1GHz, 16GB 3600MHz CL15 DDR4 RAM, 2x GTX 1080 SLI, Asus Maximus IX Hero, Sound Blaster ZxR, PCIe Quad SSD, Oculus Rift CV1, DLP Link PGD-150 glasses, ViewSonic PJD6531w 3D DLP Projector @ 1280x800 120Hz native / 2560x1600 120Hz DSR 3D Gaming.
[quote="RAGEdemon"]Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
[/quote]Nice to meet you too Shazad. I guess the issue is here is that im not really running much of an overclock. I have turbo set to all cores at the moment, so that's giving me 4.5 ghz across all cores. Also, ive been running it like that for a month without issue. This is a very recent event with not much change other than updating windows. I can hunt down a dvi cable and see if the onboard video gives me the same issue. I haven't encountered anything crazy when windows boots successfully.
Although one time I had flickering desktop icons and such that went away and never returned after a reboot.
RAGEdemon said:Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
Nice to meet you too Shazad. I guess the issue is here is that im not really running much of an overclock. I have turbo set to all cores at the moment, so that's giving me 4.5 ghz across all cores. Also, ive been running it like that for a month without issue. This is a very recent event with not much change other than updating windows. I can hunt down a dvi cable and see if the onboard video gives me the same issue. I haven't encountered anything crazy when windows boots successfully.
Although one time I had flickering desktop icons and such that went away and never returned after a reboot.
[quote="tygeezy"][quote="RAGEdemon"]Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
[/quote]Nice to meet you too Shazad. I guess the issue is here is that im not really running much of an overclock. I have turbo set to all cores at the moment, so that's giving me 4.5 ghz across all cores. Also, ive been running it like that for a month without issue. This is a very recent event with not much change other than updating windows. I can hunt down a dvi cable and see if the onboard video gives me the same issue. I haven't encountered anything crazy when windows boots successfully.
Although one time I had flickering desktop icons and such that went away and never returned after a reboot.[/quote]
Since this was working smoothly before, and you don't have an OC, it seems like the most recent change is the OS as being most suspect
You should setup a dual boot to test an alternate OS, either Win7, or the previous version of Win10.
Microsoft's QA has gone to shit, and they are pushing out seriously broken code in the last year. The last major update to Anniversary disabled people's webcams for example. And broke 3Dmigoto because they changed underlying DX code. The chances that this is specific to the Creator's version is very high.
I'd discourage anyone from being on the leading edge of Microsoft code. It's not the same company as it once was. You are going to get boned, repeatedly.
RAGEdemon said:Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
Nice to meet you too Shazad. I guess the issue is here is that im not really running much of an overclock. I have turbo set to all cores at the moment, so that's giving me 4.5 ghz across all cores. Also, ive been running it like that for a month without issue. This is a very recent event with not much change other than updating windows. I can hunt down a dvi cable and see if the onboard video gives me the same issue. I haven't encountered anything crazy when windows boots successfully.
Although one time I had flickering desktop icons and such that went away and never returned after a reboot.
Since this was working smoothly before, and you don't have an OC, it seems like the most recent change is the OS as being most suspect
You should setup a dual boot to test an alternate OS, either Win7, or the previous version of Win10.
Microsoft's QA has gone to shit, and they are pushing out seriously broken code in the last year. The last major update to Anniversary disabled people's webcams for example. And broke 3Dmigoto because they changed underlying DX code. The chances that this is specific to the Creator's version is very high.
I'd discourage anyone from being on the leading edge of Microsoft code. It's not the same company as it once was. You are going to get boned, repeatedly.
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
[quote="bo3b"][quote="tygeezy"][quote="RAGEdemon"]Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
[/quote]Nice to meet you too Shazad. I guess the issue is here is that im not really running much of an overclock. I have turbo set to all cores at the moment, so that's giving me 4.5 ghz across all cores. Also, ive been running it like that for a month without issue. This is a very recent event with not much change other than updating windows. I can hunt down a dvi cable and see if the onboard video gives me the same issue. I haven't encountered anything crazy when windows boots successfully.
Although one time I had flickering desktop icons and such that went away and never returned after a reboot.[/quote]
Since this was working smoothly before, and you don't have an OC, it seems like the most recent change is the OS as being most suspect
You should setup a dual boot to test an alternate OS, either Win7, or the previous version of Win10.
Microsoft's QA has gone to shit, and they are pushing out seriously broken code in the last year. The last major update to Anniversary disabled people's webcams for example. And broke 3Dmigoto because they changed underlying DX code. The chances that this is specific to the Creator's version is very high.
I'd discourage anyone from being on the leading edge of Microsoft code. It's not the same company as it once was. You are going to get boned, repeatedly.[/quote]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.
RAGEdemon said:Tyler, nice to meed ya man. As you probably know, I'm Shahzad. I remember having a similar issue back in the Intel Conroe days. The problem was that my OC was too high.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
Nice to meet you too Shazad. I guess the issue is here is that im not really running much of an overclock. I have turbo set to all cores at the moment, so that's giving me 4.5 ghz across all cores. Also, ive been running it like that for a month without issue. This is a very recent event with not much change other than updating windows. I can hunt down a dvi cable and see if the onboard video gives me the same issue. I haven't encountered anything crazy when windows boots successfully.
Although one time I had flickering desktop icons and such that went away and never returned after a reboot.
Since this was working smoothly before, and you don't have an OC, it seems like the most recent change is the OS as being most suspect
You should setup a dual boot to test an alternate OS, either Win7, or the previous version of Win10.
Microsoft's QA has gone to shit, and they are pushing out seriously broken code in the last year. The last major update to Anniversary disabled people's webcams for example. And broke 3Dmigoto because they changed underlying DX code. The chances that this is specific to the Creator's version is very high.
I'd discourage anyone from being on the leading edge of Microsoft code. It's not the same company as it once was. You are going to get boned, repeatedly.
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.
It's a strange one.
Windows 10 64-bit, Intel 7700K @ 5.1GHz, 16GB 3600MHz CL15 DDR4 RAM, 2x GTX 1080 SLI, Asus Maximus IX Hero, Sound Blaster ZxR, PCIe Quad SSD, Oculus Rift CV1, DLP Link PGD-150 glasses, ViewSonic PJD6531w 3D DLP Projector @ 1280x800 120Hz native / 2560x1600 120Hz DSR 3D Gaming.
Yeah, I tried the installer from intel and it didn't work. I then decided to go to my motherboards page and snoop around and found that device that Bob was talking about and gave that a go.
This did the trick for me! Now oddly my mouse didn't work in safe mode, so I had to do everything with my keyboard; which was a pain in the ass. Not only did it fix that bootup issue, but I had noticed I had performance degradation. Specifically in Arkham knight. I thought I was going crazy, or maybe it was just a different part of the map that was more demanding. My fps was maxing out the 90 cap before and I was only getting 70-75 fps while panning the camera outside.
I had dropped the fps cap when I noticed this and then I decided to play the game after I used ddu plus installing the drivers again and my fps was going over 100 in the same areas of the map... I never knew that you could have such degradation in performance fro ma seemingly successful driver install. Windows wasn't reporting any issues, and id probably not have used ddu had I not had the boot problems. Arkham knight has a stigma of running like a turd, so I thought that was the issue honestly.
Should we be using ddu for every driver install? It makes me wonder after seeing such a huge performance boost. Albeit in one game. Also, I need to figure out what the deal with my mouse not being available in safe mode is about.
When I install a new driver I always use DDU.
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
I thought it was overkill to do that so often. Now i'm not so sure. It seems like i'm not the only one having issues with my mouse in safe mode. I saw a post from a guy with the same issue who fixed it by just using another mouse. Which is ludicrous to me because I don't have spare mice sitting around for safe mode use only... Or maybe I do, ill have to look.
According to person who wrote DDU you can use DDU normal mode regular windows desktop and then reboot after DDU finishes when the computer reboots run DDU in normal mode again then install the drivers.
This is a solution if you cannot use DDU in safe mode.
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
For the mouse- about 1 in 5 reboots my mouse doesn't power up, even at normal desktop. Old Razer Diamondback. Bad software in the mouse. Sometimes happens in safe-mode, but less often. It's a timing issue.
The way to solve this is to plug and unplug the mouse. Should fire up. In my case, doing that will blue-screen nearly every time. Blue-screen from plugging in a USB? Should be impossible. Yeah, somewhere we've got some really fine software running.
So my alternate path is to bring up Device Manager using the keyboard, and select the yellow bang mouse, and do the disable, then enable, to bring it up.
As a software guy, this shitty code makes me insane, but wattaya gonna do?
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
Back in the day you always had to uninstall with control panel and then install. So driver installations required 2 reboots minimum. I hadn't noticed any problems by using the "Clean install" function for awhile now. Something is clearly amiss if you can have the problems I had with a simple update of drivers and then properly removing and then installing the same drivers to clear that issue up.
I took a couple of c++ courses, but I haven't tried any other languages. I wrote a simple text program to calculate true shooting percentage for basketball once.
If you can get it to boot, the founders update can be installed which is a large overhaul to Win 10. This has a decent chance of fixing the issue if its Win10 related.
I find that new builds easily corrupt the OS because we are crashing the computer a lot trying to find that perfect overclock.
I would also +1 'DDU at every driver install' as bo3b and zig11727 say.
Btw, tygeezy and zig11727, what's your name, if you don't mind my asking? :)
Windows 10 64-bit, Intel 7700K @ 5.1GHz, 16GB 3600MHz CL15 DDR4 RAM, 2x GTX 1080 SLI, Asus Maximus IX Hero, Sound Blaster ZxR, PCIe Quad SSD, Oculus Rift CV1, DLP Link PGD-150 glasses, ViewSonic PJD6531w 3D DLP Projector @ 1280x800 120Hz native / 2560x1600 120Hz DSR 3D Gaming.
My name is Tyler.
I wonder if you still have this issue if you put OC settings back to stock?
Also, the spread spectrum setting comes to mind - If you toggle that, if there are electromagnetic emissions causing it on the hardware side, this could be an alley of investigation.
Windows 10 64-bit, Intel 7700K @ 5.1GHz, 16GB 3600MHz CL15 DDR4 RAM, 2x GTX 1080 SLI, Asus Maximus IX Hero, Sound Blaster ZxR, PCIe Quad SSD, Oculus Rift CV1, DLP Link PGD-150 glasses, ViewSonic PJD6531w 3D DLP Projector @ 1280x800 120Hz native / 2560x1600 120Hz DSR 3D Gaming.
Although one time I had flickering desktop icons and such that went away and never returned after a reboot.
Since this was working smoothly before, and you don't have an OC, it seems like the most recent change is the OS as being most suspect
You should setup a dual boot to test an alternate OS, either Win7, or the previous version of Win10.
Microsoft's QA has gone to shit, and they are pushing out seriously broken code in the last year. The last major update to Anniversary disabled people's webcams for example. And broke 3Dmigoto because they changed underlying DX code. The chances that this is specific to the Creator's version is very high.
I'd discourage anyone from being on the leading edge of Microsoft code. It's not the same company as it once was. You are going to get boned, repeatedly.
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
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.