Does WindowFX v6.02 actually support Windows 10 fully yet? It doesn't even have its own forum.
Anyway, I just wanted to report an issue I only seem to have when I enable WindowFX. I seem to get intermittent flashing of my screen to black when exiting some apps and games but ONLY while WindowFX is enabled. If I turn WindowFX off (but leave the service still running) then I do not see this issue at all. I am using Windows 10 Pro v1511 64-bit and have an i7-4770K, 16 GB, EVGA NVIDIA GeForce GTX 980 Ti SC graphics using the v365.19 driver.
I started getting these issues a week ago when I re-enabled WindowFX. I disabled it again two days ago and in the time I have not experienced the issue so they seem to almost certainly caused/triggered by WindowFX on my system.
The Event log shows the following errors whenever this screen flashing occurs:
Faulting application name: dwm.exe, version: 10.0.10586.0, time stamp: 0x5632d756
Faulting module name: udwm.dll, version: 10.0.10586.122, time stamp: 0x56cc0ec3
Exception code: 0xc0000005
Fault offset: 0x0000000000016f41
Faulting process ID: 0x248
Faulting application start time: 0x01d1c7904cba6baf
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\SYSTEM32\udwm.dll
Report ID: 963cfbd2-33dd-4163-8e9a-3c436762ee1d
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: dwm.exe, version: 10.0.10586.0, time stamp: 0x5632d756
Faulting module name: dwmcore.dll, version: 10.0.10586.306, time stamp: 0x571af4a5
Exception code: 0xc0000005
Fault offset: 0x00000000001285b3
Faulting process ID: 0x3910
Faulting application start time: 0x01d1c79c99b79541
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\system32\dwmcore.dll
Report ID: b1216fbc-0745-46dc-b7bb-3af415cc8594
Faulting package full name:
Faulting package-relative application ID:
I agree with it.... IT's clearly link to one of your product.
To be more precise I have the flashing black screen when reopen a universal app like the courrier appor ajusting with different games in window mode on 2 different screens.It's intermittent of course but it's clearly there.
This is not because of faulty videos drivers because I had that for 2 computers and on several edition of the nvidia drivers....
Nom de l’application défaillante dwm.exe, version : 10.0.14393.0, horodatage : 0x578999ab
Nom du module défaillant : udwm.dll, version : 10.0.14393.0, horodatage : 0x5789987f
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000033f0f
ID du processus défaillant : 0x4394
Heure de début de l’application défaillante : 0x01d20878f2076343
Chemin d’accès de l’application défaillante : C:\Windows\system32\dwm.exe
Chemin d’accès du module défaillant: C:\Windows\SYSTEM32\udwm.dll
ID de rapport : 56a93b4a-cde2-44da-965a-592789f8883c
Nom complet du package défaillant :
ID de l’application relative au package défaillant :
and that's the message of Dwminit:
Le processus Gestionnaire de fenêtrage a été quitté. (Code de sortie du processus : 0x000000ff, nombre de redémarrages : 1, ID de périphérique d’affichage principal : NVIDIA GeForce GTX 970)
that the windows error reporting message :
Récipient d’erreurs 120515965039, type 4
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0
Signature du problème :
P1 : dwm.exe
P2 : 10.0.14393.0
P3 : 578999ab
P4 : udwm.dll
P5 : 10.0.14393.0
P6 : 5789987f
P7 : c0000005
P8 : 0000000000033f0f
P9 :
P10 :
Fichiers joints :
\\?\C:\Windows\Temp\WER5EE.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER61D.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_7ab9814313204e7f1984218719bf8aed36d6a8e0_e69b2600_cab_71b6064a\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_7ab9814313204e7f1984218719bf8aed36d6a8e0_e69b2600_cab_71b6064a\triagedump.dmp
Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_7ab9814313204e7f1984218719bf8aed36d6a8e0_e69b2600_25921473
Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : 56a93b4a-cde2-44da-965a-592789f8883c
Statut du rapport : 0
Récipient avec hachage : 327eeeae0bf411677ab212522e9984f6
Stardock Forums
