Actual Tools
Логотип Actual Tools
 ГЛАВНАЯ 
 ПРОДУКТЫ 
 СКАЧАТЬ 
 КУПИТЬ 
 ПОДДЕРЖКА 
 КОМПАНИЯ 
Actual Tools
Новости в формате RSS Новости
Главная / Форумы / Technical Support
Список форумов
Новые темы
Список тем
Поиск по форумам
Помощь
Войти
Регистрация

Сообщения 1 - 10 из 25
Начало | Пред. | 1 2 3 | След. | Конец 

Тема: «[FIXED] Desktop Composition Causing 8.4 Mirror Hangs , Desktop Composition Causing 8.4 Mirror Hangs » в форуме: Technical Support   Просмотров: 16025
 
Mark Squires
 
Всего сообщений: 9
Дата регистрации: 24.08.2015
Создано: 24.08.2015 08:21:43
 
 
Hi,

I've downloaded the trial of AWM 8.4 to my three screen PC set up (i5-4470 + 4Gb 1600 Ram + SSD = Asus H81M-Plus running Win7 x64) I'm using the on-board intel 4400 graphics to drive monitors 2 & 3, the main monitor is driven by a Nvidea GTX670.

I've set up the AWM program to mirror an area of Screen 1 to an area of Screen 2 - and everything is fine as long as I do not try to tick the Hardware box in the mirroring set up, if I do the program immediately crashes. Sadly as I am using this to mirror part of a game the software driven mirror is not fast enough and introduces performance issues.

I've found that if I disable desktop composition the software runs fine and I can tick the hardware box but this introduces other issues with my set up. The AWM software is pretty much configured as stock, Windows snapping is disabled as are the general profiles. I've read through the forum and following other advice threads I have tried magnifier and that works fine on all screens. The crash happens every time mirroring is activated and hardware composition is enabled, if mirroring is paused AWM will run and support other functions apart from mirroring. The situation is replicable 100% of the time and takes place with no other code running, any ideas or help would be appreciated.

M
 
Наверх
Alex Fadeyev
Администратор

Moderator
 
Всего сообщений: 1452
Дата регистрации: 30.09.2005
Создано: 26.08.2015 15:53:06
 
 
Hi Mark,

Thank you for the report. Please answer the following questions:

1. What are the "Mirroring Settings" of the mirror you created (the "Scale" setting, in particular)?

2. If you create a mirror that mirrors area of Screen 2 to Screen 3 - will it work as expected?

Thank you.
 
Наверх
Mark Squires
 
Всего сообщений: 9
Дата регистрации: 24.08.2015
Создано: 26.08.2015 18:49:06
 
 
The mirroring settings are:

- Part of Desktop
217
18
857
180

- Variable Scale

- Enable Hotkey
Ctl+3

Nothing else checked.

The same behaviour occurs if mirroring screen 2 to screen 3

Thank you for your attention.
 
Наверх
Vasiliy Ivachev
Администратор
-retired-
 
Всего сообщений: 2073
Дата регистрации: 09.11.2010
Создано: 27.08.2015 17:00:14
 
 
Hello Mark,

Please check whether the problem persists using the following scale settings:
1. Scale = Fixed scale x1;
2. Scale = Fixed scale x2;
3. Scale = Fixed scale x1/2.
 
Наверх
Mark Squires
 
Всего сообщений: 9
Дата регистрации: 24.08.2015
Создано: 28.08.2015 05:44:16
 
 
Yes the same behaviour exists on all three of the fixed scale points you mention. The only variable I can find that affects the programs function would seem to be desktop composition, as soon as it is disabled the program functions flawlessly. As I understand it this feature composes screens in a separate area of the memory and then Windows draws the completed screen in one pass to stop tearing on the frame refresh. All I can think of is there must be an issue between the two graphic cards on this refresh cycle.
 
Наверх
red devil
 
Всего сообщений: 19
Дата регистрации: 08.07.2010
Создано: 31.08.2015 03:34:26
 
 
I get a crash after updating to the latest nvidia drivers and when running actual manager's mirroring for the secondary monitor. Hardware acceleration is enabled.

Faulting application name: ActualWindowManagerShellCenter64.exe, version: 8.5.0.0, time stamp: 0x55de2a48
Faulting module name: nvd3dumx.dll, version: 10.18.13.5560, time stamp: 0x55c42222
Exception code: 0xc000041d
Fault offset: 0x00000000008e0d62
Faulting process id: 0x230c
Faulting application start time: 0x01d0e343022edd01
Faulting application path: C:\Program Files (x86)\Actual Window Manager\ActualWindowManagerShellCenter64.exe
Faulting module path: C:\Windows\system32\nvd3dumx.dll

Reverted back to nvidia driver 353.30 and the problem was resolved. Please fix so that latest nvidia drivers can be used.

Thanks and Regards.
 
Наверх
Vasiliy Ivachev
Администратор
-retired-
 
Всего сообщений: 2073
Дата регистрации: 09.11.2010
Создано: 31.08.2015 15:50:29
 
 
Mark, please specify versions of your videocards drivers.

red devil, please specify which version of nvidia drivers you installed before reverting it back to 353.30.
 
Наверх
Mark Squires
 
Всего сообщений: 9
Дата регистрации: 24.08.2015
Создано: 31.08.2015 19:28:12
 
 
I'm using 353.82 and I can confirm Red Devil's finding i.e. reverting back to 353.30 cures the issue. Therefore as the issue can be created by the driver version and toggled by enabling/disabling desktop composition my assumption is one of the nvidea dll's is making an invalid call.
 
Наверх
red devil
 
Всего сообщений: 19
Дата регистрации: 08.07.2010
Создано: 01.09.2015 13:10:04
 
 
Failed versions were: 353.62 and 355.60.
 
Наверх
Vasiliy Ivachev
Администратор
-retired-
 
Всего сообщений: 2073
Дата регистрации: 09.11.2010
Создано: 02.09.2015 11:10:25
 
 
Hello gentlemen,

The problem has been confirmed. We'll try to fix it and inform you about our results.

Best regards.
 
Наверх

Сообщения 1 - 10 из 25
Начало | Пред. | 1 2 3 | След. | Конец 

Читают тему
гостей: 2, пользователей: 0, из них скрытых: 0


Список форумов
Новые темы
Список тем
Поиск по форумам
Помощь
Войти
Регистрация