*** Windows 10 + NVIDIA WHQL Drivers are Killing Alienware and Clevo LCD Panels ***

It's more like partial screen flickering.

Sent from my HTC One using Tapatalk

EDIT: it doesn't happen in all games either. plus i checked the card and reseated it and the cable at the display end to make sure there's nothing loose.

 

@thegh0sts - if you haven't already, double-check your Windows Power Profile and make sure all settings related to dimming are set to 100% and adaptive display brightness is disabled. Sometimes the profile setting can get changed to defaults without knowing they were. If you are overclocking the GPU, try backing off the memory overclock by 100-200MHz and see if the behavior improves.

 

Just wanted to "upgrade" from Build 10240 to 10586 yesterday. While "Driver and Features" were installing my Screen flickered and went off! And then..... nothing!!!

I just thought #§$%& WT holy F***!!! I dunno for sure but my guess was this occurred while WinGoofs was trying to install/enable the NGreedia-Drivers (I was/am on 358.91). Or maybe because I shut all the sh***y stuff off via ShutUp10 and this interfered with the upgrade!?

So turning the rig on brought nothin', just a black Screen and no booting procedure while fans kickin' like mad and constant beeping. So I plugged off the PSU, removed Battery, RAM Sticks and CMOS battery while holding the Power-Button for a Minute. Reinserted everything and powered on again et voilá: Screen was back and WinGoofs was restoring to my previous build, thanks!. On a side note: I am on full CSM without UEFI.

This is it! Good ol' Windows 7 is coming back without dual boot! As soon as DX12 is of concern, I may go with the Phoenix and dual boot Win7/10.

WinGoofs 10/MicroPoop just bores me to death....

@jaybee83: Bro, when you were upgrading to Build 10586 did you disable ShutUp10 before? IIRC you can't prevent WinGoofs 10 from installing " Drivers and Features" during the upgrade, right?

 

Yes, got it running a GTX780m now as the 880 fried itself - I think it may have been the build number, I download Windoze 10 about 2 hours after it was released
Running late Oct build now.

Micro$haft has said win 7 pro will be in service till 2019, mainly for business but good for us.
If they (Micro$haft) are saying that 7 pro will be a relevant OS till 2019 and that decision is geared for business computers, don't you think when DX12 becomes mainstream that Micro$haft wont release a DX12 update for win 7 pro - Of course they will, win 7 pro will be a business model OS by then, graphics designer, game designer - the list goes on as to who will need DX12 for work, micro$haft will HAVE to release an update

Side note - Had to bite the bullet today and install v359.00 as v344.XX would not SLI in Black Ops 3

 

i didnt upgrade, but made a clean install glad u got it back to life!

Sent from my Nexus 5 using Tapatalk

 

guys my 880m is sitting dormant as we speak, is the windows 10 upgrade safe yet?

 

By doing a clean install without using Precision X should be your best bet yet. But to say it's safe,.... it's "mostly" safe,.... perhaps!?

 

When DX12 eventually becomes relevant, there will likely be an update for Windows 7 for DX12 support. For the foreseeable future, most big businesses that care about stability and data security will continue to use Windows 7 and avoid the Windoze OS X malware (p)OS.

 

By the time Dx12 becomes relevant we will be in half a year max from games based on Vulcan which has all OSes supported.

 

And, if my hopes and dreams come true we will have no need of Windows any more and Linux will support any and all Windows games. Never hurts to dream, and if that happens I will be really happy because of it.

 

apparently it's a bug in the driver profile for battlefront.

EDIT: https://forums.geforce.com/default/...-battlefront-flickering/post/4736517/#4736517

will have to see for sure if it works for me.

EDIT: nope, it didn't work....still got the occasional flicker.

 

reverted back 2 driver versions to the blops3 driver and used nvidia inspector to cap the fps in borderless mode.

I have geforce experience installed as an experiment and when i try to check for updates it keeps saying i have the latest version

 

interesting, never noticed that nvidia inspector had an fps capping option

Sent from my Nexus 5 using Tapatalk

 

You have to do it in the driver profile.

Sent from my HTC One using Tapatalk

 

I use it mainly for this You can cap performance on FPS and on temperature basis. On vSynced games I set 61 fps cap.

 

I always used RTSS fps cap and it works very good.

 

hmmm, why would u set an additional fps cap for already vsynced games?

ive only ever used nvidia inspector to create batch files for clock and voltage profiles.

Sent from my Nexus 5 using Tapatalk

 

Answer is here

 

lol nice one

so i presume that the fps limiter in nvidia inspector does not work the same way as vsync and thus reduces input lag hm?

Sent from my Nexus 5 using Tapatalk

 

VSYNC On = 60 fps + input lag
Vsync Off + frame limiter = Some screen tearing + no input lag + 60 fps.
Nvidia Adaptive VSYNC = Gpu is reclocked to the clocks where it maintains about 60 FPS = no screen tearing + no input lag

 

Vsync does not actually reduce gpu render power, allit does is just passing through cherry picked frames which are closest to the time interval of refresh rate. It still can contain 200fps hied under the layer of 60 vsynced. With my experience bigger hied frame rate, the bigger input lag you have.
While frame limit does exactly what it's called.

 

So Nvidia Adaptive VSYNC is the same like G-Sync (no screen tearing + no input lag) ?

 

but the key difference is how the tearing is controlled.

 

G-Sync is hardware based solution, so it doesn't wasting your GPU/CPU resources as much as Adaptive VSYNC do. Also, G-Sync don't limit your fps and works great even with 30 fps.

 

Adaptive vsync = totally same vsync, except it turns off when <60 fps or whatevermonitor refresh rate is.
OK, that was my last offtop for 2 days ahead.

 

Maybe v-sync is causing EDID corruption.
Yeah, that's the ticket... v-sync did it.

 

which vsync was it? adaptive or normal?

 

LOL... Let's inform our friends at Dell so they can add this to their support page and pretend they totally solved this mystery and focus on making gaming machines for their consumers! ...... (Couldn't even repeat what I just wrote with a straight face)

Sent from my Nexus 6P using Tapatalk

 

Dell searching for more bombs in the closet... Remember the certificate mess? They haven't time to fix this problem .

 

so that means we can't use PX, AB, or any type of vsync on Win 10?

 

Pretty sure that was sarcasm and not meant to be taken seriously.

 

oh ok....sometimes sarcasm in text is a bit hard to notice

 

Jesus this whole Dell turned into pile of big sh*t last years. They used to have best suport and best gaming machines but now they just suck.

 

@Mr. Fox , where's my post gone, (you're the mod arent' you), I'd replied to James and now my post has disappeared, the only remnants left have been strangely incorporated into James' post above, the bit that I've bolded - where's the Gremlins!? (P.S. I know V-sync is not relevant to this thread, as I can see from your 'devil pic'!)

 

@Robbo99999

That has happened to a few of my posts before. I think it's a weird glitch on occasion.

 

Yeah, that weird. I have no idea. Maybe there was a check mark in a box where it should not have been and it got merged with his post by accident somehow. I did merge some back-to-back posts by the same person in this thread, so that's my guess is yours had a box checked by accident. It does not show as being deleted. No telling with Xenforo software. It sometimes does strange things. I saw a change log and tried to undo it the last changes and it only made it worse.

Yup we do have some of those now and then, LOL. I have had some of my own posts vanish with no record of deletion. Thankfully, this is not a frequent glitch.

 

Cool, no worries, it was only an off-topic v-sync post anyway. I guess you've still not heard anything from NVidia or Dell, you sent them some corrupted screens a while back I think?

 

I doubt we will hear any more about it. I believe both companies did not want to burn any more calories on the situation and just decided it was EVGA Precision X at fault because they cannot explain it otherwise. I still believe it is Micro$haft's fault, possibly with some help from NVIDIA's cancer drivers. I do not believe Dell/Alienware or Clevo have any responsibility for it whatsoever. Their products are the victims of another brand(s) incompetence. At any rate, once again, the customers that own them are left holding the bag and the responsible entity has zero accountability. I should probably consider closing the thread soon. I do wish AMD would release some mobile products awesome enough to present a threat to NVIDIA, but I suspect that will never happen again. Those good old days are gone.

 

that's a shame that there's no definitive proof of how/why this is occuring. i don't really use PX or AB any more since nvidia inspector is a more less obtrusive way of applying overclocks.

I have some time off in december to give win 10 another go with the only difference being a 120Hz display is now attached instead of a 60Hz display.

 

Inspector is anything but a fluid method for overclocking. Too many clicks required to get the same effect of PX, and the jumps in voltage are 12mV instead of 7.5.

 

I agree. I'm thankful it is available when I need it, but I find it is a time-waster pain in the butt to use. I won't use it manually except to find the right settings for future use. I typically only use Inspector with batch files because I have much better things to do with my time than wear out my left mouse button.

Nothing is better than Precision X for GPU overclocking IMHO. MSI Afterburner may be fine for desktop GPUs, but it is totally worthless and unusable for me since it doesn't offer full overclocking control with voltage adjustment for mobile GPUs like Inspector does and Precision X does.

 

though you don't have a choice if you're on win 10. though for me being still on win 8.1 i don't really need it to be fully fluid, I just set my clocks, set a task to start at login and done...can leave it alone.

 

That's the thing though, once clocks are known, they can be set with shortcuts using inspector. Testing clocks with inspector is about as fun as ramming my head against the wall.

 

not something that can be done if you're on win 10 with PX since it does trigger the EDID corruption. but yes once you know your card's stable clocks then you can use nvidia inspector to set and forget with the help of task scheduler.

 

With little precision on the voltage...

 

i only really ever moved it up by 1 notch on the slider. so 1.075v is fine for my current clocks. i like nvidia inspector cos it doesn't have to be running all the time.

 

None of them have to run all the time. For all you know 1.065 volts would be stable, but you can't because of the 12mV jumps

 

true though having PX running all the time does take up some resources even if it is a little. i don't mind a little bit of voltage overhead so long as i don't over do it and don't kill the card

 

I have information from Nvidia forum that tomorrow's Game Ready driver will contain Fallout 4 SLI profile as well as Just Cause 3. If someone Could dump it I think many users would be grateful

 

here's hoping running win 10 on my AW17 R1 won't be a bad experience