Windows 10: Laptop screen flicker

Hello all,

I noticed that the screen on my laptop flickers every now and then. when it does it, it looks like part of the image cuts out or is garbled. Really, it happens to fast to be able to tell for sure. Oddly enough, it seems to always be towards the bottom of the screen that it happens.

Even weirder is I have a external monitor connected to the system via the docking station. The screen connected will also flicker. As a test, I opened the screen on my laptop while it was on the docking station. The screen set up was to duplicate the displays so the same exact thing appears on both displays. What makes this so weird is that one screen will flicker, and the other wont. One will flicker, then shortly after the other one will, but I never noticed them both flicker at the same time.

Ive already tried a couple different drivers from NVIDIA, they havent made a difference. NVIDIA Optimus (the switchable graphics) is currently disabled so the system just uses the Quadro. The specs for this system are under the second system specs connected to my post.

:)

 

Windows 10 Flicker

I finally updated my laptop as been suggested each time I get on my laptop. Since I did the upgrade, my screen keeps flickering and I can not access anything. I determined it is not the display driver based on the instructions included in the Troubleshoot
Screen Flickering page. How do determine which app is incompatible and how do I fix it if the screen continues to flicker and I can't access anything?

 

Display flickering in Windows 10

I have Lenovo Y50-70 Laptop, At the time of startup when Windows 10 logo screen opens, after log in to Windows 10 logo screen the screen starts flickering on and on still the main desktop screen appears... Flickering still going on.... I updated display
drivers in Device Manager... But this isn't resolve my issues..even Lenovo changed the display of my laptop... Still the flickering persists.... Is this any hardware issue or Operating system issue? Give me any solution....

 

On the Dell website they have Dell diagnostics for each computer.
Please run the full diagnostic studies and post an image of the results into the thread.

In the left lower corner search type reliability and post an image of the reliability control panel into the thread.

See if you can use safe mode for a day and report whether you do or don't have any laptop problems.

When you view the power options what are the settings?
Are you using balanced, power saver, or high performance?

Run though these Dell troubleshooting steps:
Resolving Laptop LCD Issues | Dell US

 

These are screenshots of all the results of the diagnostics:

















Reliability Monitor





Im using the Balanced power plan.

I also ran the DM Log Collector on the chance that some of the info may help:

CHRIS-PMW-09_07_2017_Thu_114206_81.zip

 

The event logs indicate that there were BSOD but there were no mini dumps in the logs.
Windows failed fast startup.

1) open administrative command prompt and type or copy and paste these commands:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials
6) Modify Ccleaner > Windows tab > system > un-check memory dumps
7) In the left lower corner search type: disk cleanup > un-check system error memory dump files
8) perform windows updates > post any failed KB# with error code
9) In the left lower corner search type winver and post the windows version and build into the thread
10) open file explorer > this PC > local C: drive > right upper corner serach > type: C:\WINDOWS\MEMORY.DMP
11) post using one drive or drop box share link the memory dump file
12) On the Dell website using the computer's serial or product number find a replacement driver for netwbw02.sys
13) connect to the internet by ethernet or cat5e wired
14) mechanically turn off wireless
15) uninstall netwbw02.sys
16) download and install netwbw02.sys
17) if you don't have ethernet available you can download to the desktop > mechanically disconnect wireless > update netwbw02.sys


Updating a driver: Microsoft Community






Code: Event[1124]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-09-02T16:57:38.767 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: CHRIS-PMW Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[2260]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-06T09:54:56.385 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: CHRIS-PMW Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff810268be0060, 0xfffff90005e7d8f0, 0xffff810279b1fca0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3b14e1f2-f5d2-49c1-9d7f-a507cd893337.[/quote] Code: Event[2533]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-06T23:07:52.495 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: CHRIS-PMW Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000005a (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 371b828a-c919-4fcc-896a-b85d2e093647.[/quote] Code: 9/7/2017 4:08 Windows Error Reporting Fault bucket 0x5A_tcpip!WfpAleBfeWatchDogCallback, type 0 Event Name: BlueScreen Response: Not available Cab Id: 3df1f7e3-6493-4793-915c-32b98650f548 Problem signature: P1: 5a P2: 0 P3: 0 P4: 0 P5: 0 P6: 10_0_16281 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090617-9265-01.dmp \\?\C:\Windows\TempWER-31218-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FE0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FE2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5021.tmp.txt \\?\C:\Windows\Temp\WER7E25.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_5a_1ca1f5d85d2bf2e2a63e6d2c6205ab59b56188e_00000000_cab_3ffd80d3 Analysis symbol: Rechecking for solution: 0 Report Id: 371b828a-c919-4fcc-896a-b85d2e093647 Report Status: 268435456 Hashed bucket:9/7/2017 4:08 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 5a P2: 0 P3: 0 P4: 0 P5: 0 P6: 10_0_16281 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090617-9265-01.dmp \\?\C:\Windows\TempWER-31218-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FE0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FE2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5021.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_5a_1ca1f5d85d2bf2e2a63e6d2c6205ab59b56188e_00000000_cab_02d9502e Analysis symbol: Rechecking for solution: 0 Report Id: 371b828a-c919-4fcc-896a-b85d2e093647 Report Status: 4 Hashed bucket:[/quote] Code: 9/6/2017 14:55 Windows Error Reporting Fault bucket 0x9F_3_PNP_NOTIFIY_BINDING_IMAGE_tcpip.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: d9948504-533d-4c2d-90c0-97a0ac6d2823 Problem signature: P1: 9f P2: 3 P3: ffff810268be0060 P4: fffff90005e7d8f0 P5: ffff810279b1fca0 P6: 10_0_16281 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090617-8234-01.dmp \\?\C:\Windows\TempWER-86125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF845.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF911.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_6a591519d9d3503d34e761ec2c9d2cc99d78d_00000000_cab_329e4106 Analysis symbol: Rechecking for solution: 0 Report Id: 3b14e1f2-f5d2-49c1-9d7f-a507cd893337 Report Status: 268435456 Hashed bucket:9/6/2017 14:55 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffff810268be0060 P4: fffff90005e7d8f0 P5: ffff810279b1fca0 P6: 10_0_16281 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090617-8234-01.dmp \\?\C:\Windows\TempWER-86125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF845.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8F1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF911.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_6a591519d9d3503d34e761ec2c9d2cc99d78d_00000000_cab_02b9f910 Analysis symbol: Rechecking for solution: 0 Report Id: 3b14e1f2-f5d2-49c1-9d7f-a507cd893337 Report Status: 4 Hashed bucket:[/quote] Code: 9/5/2017 2:00 Windows Error Reporting Fault bucket LKD_0x15E_Mini_Nbl_Leak_IMAGE_Netwbw02.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 5089e262-275e-4944-af34-aaac91b7f767 Problem signature: P1: 15e P2: 30 P3: ffffda86bf95c1a0 P4: ffffda86bc71c060 P5: 0 P6: 10_0_16281 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20170904-2100.dmp \\?\C:\Windows\TempWER-197609-0.sysdata.xml \\?\C:\WINDOWS\LiveKernelReports\NDIS-20170904-2100.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3903.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3903.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3923.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_15e_cb5b42d91a74bbf78d49b53e66f241c5cc72dcf0_00000000_cab_06175c0b Analysis symbol: Rechecking for solution: 0 Report Id: 79591b42-6cdd-45e4-9bfa-35683e4c1317 Report Status: 268435456 Hashed bucket:[/quote] NETwbw02.sys Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter Drivers & Software
Code: NETwNb64 ___ Intel(R) Wireless ___ Intel(R) Wireless Kernel Manual Running OK TRUE FALSE 745,472 2,129,920 0 1/5/2016 03:39:08 C:\WINDOWS\system32\drivers\Netwbw02.sys 4,096[/quote] Code: Name [00000005] Intel(R) Dual Band Wireless-AC 7260Adapter Type Ethernet 802.3 Product Type Intel(R) Dual Band Wireless-AC 7260 Installed Yes PNP Device ID PCI\VEN_8086&DEV_08B1&SUBSYS_44708086&REV_BB\4&4D3057A&0&00E2 Last Reset 9/7/2017 9:05 Index 5 Service Name NETwNb64 IP Address 192.168.0.90, fe80::41a0:47c6:6d2a:e049 IP Subnet 255.255.255.0, 64 Default IP Gateway 192.168.0.50 DHCP Enabled Yes DHCP Server 192.168.0.50 DHCP Lease Expires 1/1/1970 19:00 DHCP Lease Obtained 12/31/1969 19:00 MAC Address ‪AC:FD:CE:E7:0C:61‬ Memory Address 0xF70FE000-0xF70FFFFF IRQ Channel IRQ 4294967289 Driver c:\windows\system32\drivers\netwbw02.sys (18.33.0.1, 3.35 MB (3,515,664 bytes), 1/29/2016 4:05)[/quote]

 

From the Command Prompt; I ran sfc earlier and it turned up nothing.

Microsoft Windows [Version 10.0.16281.1000]
(c) 2017 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 10.0.16281.1000


Image Version: 10.0.16281.1000


[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


C:\WINDOWS\system32>chkdsk C: /scan
The type of the file system is NTFS.
Volume label is OS.


Stage 1: Examining basic file system structure ...
704256 file records processed.
File verification completed.
3731 large file records processed.
0 bad file records processed.


Stage 2: Examining file name linkage ...
14256 reparse records processed.
822052 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
14256 reparse records processed.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
58899 data files processed.
CHKDSK is verifying Usn Journal...
36770008 USN bytes processed.
Usn Journal verification completed.


Windows has scanned the file system and found no problems.
No further action is required.


249478143 KB total disk space.
59617448 KB in 235312 files.
139528 KB in 58900 indexes.
0 KB in bad sectors.
817315 KB in use by the system.
65536 KB occupied by the log file.
188903852 KB available on disk.


4096 bytes in each allocation unit.
62369535 total allocation units on disk.
47225963 allocation units available on disk.


C:\WINDOWS\system32>

Windows updates are all current.





No Memory.dmp file

Fast Startup turned off

Intel wireless driver is updated.

 

Download and install whocrashed:
Resplendence Software - WhoCrashed, automatic crash dump analyzer

Above analyze click on tools > crash dump test > type: ACCEPT

After the dump click analyze > post results into the thread

Post a new zip: BSOD Crashes and Debugging - Windows 10 Forums


Please update the screen flickering. What has changed if anything after turning off fast boot?

If nothing has changed, remove the notebook from the docking station and connect the external monitor directly to the notebook and report the results into the thread.

 

Screen flickering hasnt changed. Along with everything else, I also ran a stress test with Unigine Heaven 4.0 earlier set on Extreme. The test ran for 3 hours while I was gone. No crashes, no errors. Watched it for a while in full screen mode, never noticed a flicker. The GPU temp never got over 61C that I noticed.

 

To me, the fact that these flickers dont show up in any fullscreen benchmarks I run says its an issue with Windows itself. Im wondering if its something in the lastest Insider build. Im waiting to see if a new insider build fixes it.

 

These will all be trial and error to see what alters and improves the flickering.

1) See if the flickering can be altered by switching from balanced power to high performance.

When you updated video drivers how did you do it?
Was it only Nvidia or did you also do Intel?
Did you use DDU?
Did you make a clean install?
Did you install from the Dell website?

2) If you didn't then let us know so that you can update the drivers using this method.

3) If you turn on Optimus does the flicker go away or persist (use both Intel and Nvidia graphics) ?

4) If you think it is windows had you considered an in place upgrade saving files and applications?

5) What happens when you sign on to Windows using a different user profile? Is the flickering different or the same, or does it no longer flicker?

6) Have you evaluated the flickering in either clean boot or safe mode?

 

1) I didnt try the power management mode, but I did everything else. I updated each graphics chipset from the manufacturers website. I tried DDU and clean install, no dice.

3) I re-enabled optimus and now the issue seems to have gone away. Keeping my fingers crossed, but not getting my hopes up.

4) Considered it but havent done it yet.

5) Only one account, save for the built in admin account.

6) I havent tried either. Ill try it ifi it comes back.

So far, it seems to have cleared up. Even programs running on the NVIDIA GPU seem to be fine.

 

Nice.
When you reinstalled the Nvidia driver did you use Dell as the source or Nvidia as the source of the new driver?

To create a new user open administrative command prompt and type: net user test /add
Then reboot and sign on with the new user named test.
If you prefer a different user name change test to the new user name.
This method has no password.

For clean boot using administrative command prompt:
1) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)

2) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

https://support.microsoft.com/en-us/...oot-in-windows

How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

3) shutdown /r (you will reboot the computer so that it is in clean boot)


See post #6 for whocrashed.
After the dump test please post the whocrashed results.
And post a new zip after runing whocrashed.
BSOD - Posting Instructions - Windows 10 Forums

 

NVIDIA was the source for the NVIDIA driver.

I used WhoCrashed earlier to generate a test crash. It wrote a dmp file that was well over 1GB in size. Auto crash dump is selected in the settings.

Ill try the clean boot if the issues come back. Right now Im just happy that it seems to be resolved. Ill leave the thread opened for a bit until Im more certain.

 

Okay.
The whocrashed should have been able to create a mini dump.
Then it should have been able to analyze the mini dump.
The mini dump should be part of the memory.dmp

C:\Windows\MEMORY.DMP
%SystemRoot%\MEMORY.DMP

C:\Windows\minidump
%SystemRoot%\Minidump