bigmuscle

Yes, this seems to be related with nVidia driver, because (according to minidumps and crashlogs), the dwm process is stuck in nvwgf2umx.dll file waiting for something. I just don't understand what the problem is because it does not touch my code at all (and neither one of running threads does).

So try this: http://leteckaposta.cz/302887755 When you press F11, it will generate approx. 170 MB file minidump.dmp. Send it to me. After you generate minidump. create registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM: NoInternalHooks (DWORD 0x1) and try what happens.

It seems to be stuck in video driver. I tried a few changes, could you test it? http://leteckaposta.cz/uploaded/329367334 Also add following registry settings: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM: NoFillPath (DWORD 0x1), then restart dwm process.

thread.log is just the one important... However, I must admit that I don't understand it at all. Nody has a problem except of Tusticles and two guys who registered here right now. Debug logs say that everything is correct, also threads.log from lolchampion does not show that it should be stuck up somewhere in my code. So there is probably some secret magic, some special combination how to reproduce this problem. Do you have something special in your computer? Any special settings, any special theme etc... ?

Ok, so please, use default settings (no additional key in registry, no specific device feature level) and install this version http://leteckaposta.cz/723577425 When blackscreen appears, hold F11 for approx. one second and it starts generating file threads.log. It can take a while, because it will download public debug symbols from Microsoft servers (which are several MBs). Then it will automatically kill the process (which will result in dwm.exe restart, so it will be probably stuck with another black screen, so hold CTRL after pressing F11. I hope this will work and it will help to fix the problem :-) And of course, then send me threads.log file.

Fine, now I have to find the real reason of the black screen. I will create debug version which makes more detailed log as this settings will go away in next version.

It makes no difference. "crashfix" just fixes crash from your crashlog.txt.

What happens when you add registry settings HKCU\Software\Microsoft\Windows\DWM: callBlurShapes (DWORD set to 0x1) ?

Did 0.9 really work or you just had native blur enabled ?

do you use startisback or something like that?

Here is the temporary fix for a crash http://leteckaposta.cz/670122308 Could you test it so we can confirm whether it is cause of the black screen?

Ok, if the crashlog is the reason than it could help. I know how to reproduce it. However, it is weird that it happens on startup :-/

no crashlog.txt generated? What happens when you hold ctrl during black screen (so you don't force restart), does it work or not?

I tried those but ColorizationColorBalanceInactive is the only key that allowed me adjust the inactive frame so that the black captions are readable...Is there a way to get a white blurry outline around the window caption only? Or is that part of the theme? ColorizationAfterglowBalanceInactive influences it too (but minimally) but you should ensure that the sum of both won't be higher than 100 else it can result in weird things. Caption glow effect is a theme thing. DeviceFeatureLevel depends on your graphic card. If your graphic card does not support selected feature level, you will end up with the black screen. If you set DeviceFeatureLevel lower than default, you just switch your graphic card to backward-compatibility mode which can result in unexpected behavior (someone reported here that Metro application does not have to work correctly), degraded performance and other things. The final version will not have this setting at all, so I would like to fix all related issues as soon as possible.

There must be something else, because there is no native blur mode in RC0 (UseNativeBlur setting is completely ignored).

ColorizationBlurBalanceInactive + ColorizationAfterglowBalanceInactive, both influence the level of the transparency.

So, to anyone having problem to open desktop with 64-bit build, what is your version of shell32.dll ? Also post your debug.log (better, delete the file first and then restart your PC to have clean log)

Because your have invalid colorization settings for inactive frames. Just post a screenshot of your registry key HKCU\Software\Microsoft\Windows\DWM and we will see where the problem is ;-) Here is is: clickOne thing I see there is the duplicate UseNativeBlur entry (removed the one with 0x1) What will happen if I delete the ColorizationColorInactive entry? Of course, that's it. You have set your inactive color to RGB(99, 150, 191) which is some shade of blue. I don't even know why you have double UseNativeBlur, this has no sense.

Because your have invalid colorization settings for inactive frames. Just post a screenshot of your registry key HKCU\Software\Microsoft\Windows\DWM and we will see where the problem is ;-) Yes, there is no native blur now. Why? I said it million-times that this mode is not supposed to be used at all and that all versions are intended for testing only. So what is the purpose of your testing when you disable the code to test? Do you have 32-bit version? If yes, then it is possible because several versions of 32-bit system DLLs contains different optimizations which can totally break everything. If this is true, please send me your shell32.dll (via PM) + there should be crashlog.txt in the same folder as you extracted dwmglass.dll.

Yeah, I checked again and function DWM2 (which is the new one in RC0) is really not compatible with version 9.2.9200.16384 of uDWM.dll. I've fixed the issue but since it is old version of uDWM, it is not so important. You can fix it by windows update (to have version 16420).

And did it display "DWM is incompatible" message box when the error appeared?

There is more things I don't understand. I had udwm.dll version 16420, now I checked and it is 16384 (some automatic downgrade?) and I also found udwm.dll in winsxs folder of version 20521. But all of them seem to be compatible.

Yeah, I want to do this (+ add some automatization such disabling when on battery etc.). My algorithm is prepared for it, so it is just about adding checkbox somewhere into GUI. Currently, it can be done by setting ColorizationBlurBalance and ColroizationAfterglowBalance to 0x0 and restarting DWM (but I don't remember if it is the only needed change.)

Your udwm.dll is compatible, it is even absolutely same as mine, so unless there is a bug (which would appear for other users too), then the real reason is ... hmm, weird

This can happen for one certain reason.... but, rather send me you c:\windows\system32\udwm.dll (via PM) so I can check the exact reason