Screen flickering on nVidia GPU

AR_4 · Jul 11, 2017

Hello, my GPU started to mess around like this: As I built my new PC i noticed from the first boot some rare, short flickers on Windows 10. They didn`t bothered me until they got worse and worse, holding longer and longer, until they got to BSoD - video_scheduler_internal_error. Specs:
CPU: AMD Ryzen 5 1500X @ stock freq
GPU: MSi GTX 1050 Ti GAMING
MoBo: GIGABYTE GA-AB350M GAMING 3
RAM: Corsair Vengeance LPX 8 Gb 2400Mhz Single Channel
PSU: ThermalTake LITEPOWER 650W
Monitor: LG 29UM58P 21:9
I tried installing other drivers from scratch -> 381.65, 381.89, 382.53, 384.76 to no avail. I tried many registry repairs as I was getting bsod. I also have errors related to directX and errors in Photoshop related to the GPU. I even changed the GPU with a GIGABYTE one (same chipset). The screen just flickers shortly black and then it recovers. This happens mostly when playing a game (featuring directX errors) or just a movie. I am desperate as i intended to work on this PC smoothly... It is a driver problem? It is a hardware problem? Is this related to the fact that I have an ultrawide monitor? It is related to the color modes? Help will be very appreciated.

kookie3010 · Jul 11, 2017

what res do u run the games on?

AR_4 · Jul 11, 2017

kookie3010 :

My monitor is 2560x1080. I run my games on this resolution.

kookie3010 · Jul 11, 2017

AR_4 :

try lowering your res and see if the flicker is still there.also whats the refresh rate of your monitor?also did u try another monitor since u already switch the card?

AR_4 · Jul 11, 2017

kookie3010 :

I tried lowering my res but same thing. My monitor is 60Hz. N.B. Games look awful when on 1080p

kookie3010 · Jul 11, 2017

AR_4 :

sorry i updated my previous post a lil to late.have u try using another monitor since u already switch the card.have u try DDU and clean wipe your driver and reinstalling it.some of this issue can be cause by phsyx as well

AR_4 · Jul 11, 2017

I tried using DDU to no avail. I didn`t tried swapping the monitor (don`t have monitors laying around) nor disabling phisX. I can tell you that this is not a monitor problem since this monitor worked perfectly on my old PC. I will try removing PhysX to see if it does the trick. Maybe FRAPS is doing the flicker too?

kookie3010 · Jul 11, 2017

AR_4 :

ah i see.try disabling fraps and see if that works.

AR_4 · Jul 11, 2017

Hmmm... seems that FRAPS is to blame for now, no more flicker.. going to play something to see if i hit the jackpot...

kookie3010 · Jul 11, 2017

AR_4 :

its depends on what fps monitoring sotfware that u use.i personally use fraps but at times it cause a few issue with games so i switch to rivatuner and msi afterburner.

AR_4 · Jul 12, 2017

Well, the flicker is back and the bsod. I reinstalled the drivers in safe mode without ticking physx, experience, 3d vision. It all went good - no more flicker, directX errors and so on. Now I got another bsod and the flickers are back and more often. What do i miss? How can I see the log file of the BSoD? I also got nVidia control panel errors like nvcplui.exe - Application error. Another thing that i see is that even if i unticked the box with physX when installing the drivers it got installed!! Even if i did say NOT to install it! I am in despair!!

AR_4 · Jul 13, 2017

Crash Dump:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000005, The subtype of the bugcheck:
Arg2: ffffbc0c26ab4000
Arg3: ffffbc0c26e5f9e0
Arg4: 000000000000062e

Debugging Details:
------------------

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x119

PROCESS_NAME: MsiGamingOSD_x

CURRENT_IRQL: 9

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

DPC_STACK_BASE: FFFFF80402262FB0

LAST_CONTROL_TRANSFER: from fffff80bdb96355e to fffff80400173310

STACK_TEXT:
fffff804`02261b18 fffff80b`db96355e : 00000000`00000119 00000000`00000005 ffffbc0c`26ab4000 ffffbc0c`26e5f9e0 : nt!KeBugCheckEx
fffff804`02261b20 fffff80b`dca56962 : ffffbc0c`26e5c000 ffffbc0c`26ab4000 00000000`00000000 fffff80b`de4d6afc : watchdog!WdLogEvent5_WdCriticalError+0xce
fffff804`02261b60 fffff80b`dca4b17a : ffffbc0c`26dcf010 ffffbc0c`26dcbb70 ffffbc0c`26ab4000 fffff80b`de52ed39 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x23e
fffff804`02261be0 fffff80b`dca3ad0d : fffff804`0000062e ffffbc0c`26eaf010 ffffbc0c`26dcf010 00000000`00000000 : dxgmms2!memset+0x517a
fffff804`02261c30 fffff80b`db98bc54 : ffffbc0c`25315030 fffff80b`de4d2102 fffff80b`de3e5944 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d
fffff804`02261c60 fffff80b`de40cc17 : ffffbc0c`25315030 fffff804`02261d69 fffff804`02261df0 ffffbc0c`254ca000 : dxgkrnl!DxgNotifyInterruptCB+0x74
fffff804`02261c90 ffffbc0c`25315030 : fffff804`02261d69 fffff804`02261df0 ffffbc0c`254ca000 fffff80b`de40cba7 : nvlddmkm+0x10cc17
fffff804`02261c98 fffff804`02261d69 : fffff804`02261df0 ffffbc0c`254ca000 fffff80b`de40cba7 ffffbc0c`254ca000 : 0xffffbc0c`25315030
fffff804`02261ca0 fffff804`02261df0 : ffffbc0c`254ca000 fffff80b`de40cba7 ffffbc0c`254ca000 00000000`00000000 : 0xfffff804`02261d69
fffff804`02261ca8 ffffbc0c`254ca000 : fffff80b`de40cba7 ffffbc0c`254ca000 00000000`00000000 00000000`00000000 : 0xfffff804`02261df0
fffff804`02261cb0 fffff80b`de40cba7 : ffffbc0c`254ca000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffbc0c`254ca000
fffff804`02261cb8 ffffbc0c`254ca000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x10cba7
fffff804`02261cc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffbc0c`25315030 : 0xffffbc0c`254ca000

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms2!VidSchiProcessIsrFaultedPacket+23e
fffff80b`dca56962 cc int 3

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms2!VidSchiProcessIsrFaultedPacket+23e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.15063.312

BUCKET_ID_FUNC_OFFSET: 23e

FAILURE_BUCKET_ID: 0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_dxgmms2!VidSchiProcessIsrFaultedPacket

BUCKET_ID: 0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_dxgmms2!VidSchiProcessIsrFaultedPacket

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x119_5_driver_faulted_system_command_dxgmms2!vidschiprocessisrfaultedpacket

FAILURE_ID_HASH: {8a2196f9-e81f-1cf4-52f5-61b7dae1d7c0}

Followup: MachineOwner
---------

AR_4 · Jul 13, 2017

The problem is still manifesting. As I researched, it is a DX 12 error in Creators Update. I have no ideo how to get rid of this error!!

kookie3010 · Jul 13, 2017

I see.the freaking creators update XD.try turning off game mode in the control panel

AR_4 · Jul 13, 2017

I will try the latest chipset and bios drivers and if the problem is still there i will delete everything and install windows 8.1 - if it lets me

AR_4 · Jul 17, 2017

Problem solved -> bought Radeon... shame to nVidia..

ridwanrahmatf · Aug 9, 2018

Search

Screen flickering on nVidia GPU

AR_4

Prominent

kookie3010

Honorable

AR_4

Prominent

kookie3010

Honorable

AR_4

Prominent

kookie3010

Honorable

AR_4

Prominent

kookie3010

Honorable

AR_4

Prominent

kookie3010

Honorable

AR_4

Prominent

AR_4

Prominent

AR_4

Prominent

kookie3010

Honorable

AR_4

Prominent

AR_4

Prominent

ridwanrahmatf

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page