Nicholas Woods
Всего сообщений: 3
Дата регистрации: 22.10.2013
|
Создано:
22.10.2013 00:38:14
|
 |
I am unable to replace the Primary Taskbar when using Actual Window Manager 8.0.3. I have the checkbox marked in AWM but when it loads, I receive another taskbar and the system one stays up. Along with this, the system tray never loads for any taskbar other than the one provided by the system. I have tried upgrading to the new 8.1 Beta version and uninstalled / reinstalled after cleaning the registry to no avail. Along with this, I am receiving multiple instances where windows are being loaded underneath an AWM taskbar.
I was able to successfully replace the Primary Taskbar and could see the system trays when using version 7 (from what I remember) but once I did the auto-upgrade to 8 I started receiving these oddities. I do have "Show the notification area" checked as well.
Unfortunately, I didn't back up my configuration when it was working (and that's a lesson well learned). I also sometimes get a Windows app crash notification when loading AWM but the software loads and seems to work fine. I'll look through my Event Viewer and find out the exact message and place it here along with a screenshot (if desired). Any ideas or thoughts would be appreciated.
Tech Specs:
OS: Windows 7 SP1 X64
AWM: 8.0.3 / 8.1 Beta
Video: Nvidia NVS 3100M
RAM: 8GB
Event Viewer Log for version 8.1
Faulting application name: ActualWindowManagerCenter64.exe, version: 8.1.0.0, time stamp: 0x525d494d
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000005
Fault offset: 0x0000000000029ca5
Faulting process id: 0x1e1c
Faulting application start time: 0x01cece76a6abf05c
Faulting application path: C:\Program Files (x86)\Actual Window Manager\ActualWindowManagerCenter64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e58a3cd2-3a69-11e3-bba3-005056c00008
Event Viewer Log for version 8.0.3
Faulting application name: ActualWindowManagerCenter64.exe, version: 8.0.3.0, time stamp: 0x5233fd4e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0x0eedfade
Fault offset: 0x000000000000940d
Faulting process id: 0x233c
Faulting application start time: 0x01cece736c2c86a0
Faulting application path: C:\Program Files (x86)\Actual Window Manager\ActualWindowManagerCenter64.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: b15eba0e-3a66-11e3-9217-005056c00008
|
Bogdan Polishchuk
Администратор
Всего сообщений: 4114
Дата регистрации: 04.04.2012
|
Создано:
23.10.2013 14:47:25
|
Hello Nicholas
Are you able to see the ActualWindowManagerCenter64.exe process in the list of processes of the Task Manager?
Could you make sure that the following option is enabled:
Control Panel > System and Security > Action Center > Change Action Center Settings > Problem Reporting Settings > Each time a problem occurs, ask me before checking for solutions
Then next time the application (ActualWindowManagerCenter64.exe) will crash, select the "View problem details" item. In the details area there should be the path to the crash dump file. Send this file to us manually.
Best regards.
|
Nicholas Woods
Всего сообщений: 3
Дата регистрации: 22.10.2013
|
Создано:
24.10.2013 19:39:23
|
I currently see the following running processes:
ActualWindowManagerCenter.exe
ActualWindowManagerShellCenter64.exe
I don't see the process you list as ActualWindowManagerCenter64.exe. I can see the ActualWindowManagerCenter64.exe as in my Actual Windows Manager install folder but I noticed it's hidden for some reason. Manually opening that process only causes it to close out a second later.
Whenever the next crash happens I will get you the file.
Thank you for your help.
|
Nicholas Woods
Всего сообщений: 3
Дата регистрации: 22.10.2013
|
Создано:
01.11.2013 21:28:21
|
Well, the application hasn't crashed since. I re-installed version 7 and it worked for a day or two (and ActualWindowManagerCenter64.exe was running) but then the same issue with ActualWindowManagerCenter64.exe no longer running occured.
I forgot to test deleting my user profile on the system to make see if it was just a user thing before I reinstalled the whole OS. After reloading Windows 7 and installing version 8 once again, I've had no issues whatsoever.
Sorry to those looking for more information or having the same issue as I did for not doing my due diligence in troubleshooting the profile thing.
Thanks again Bogdan, for your help.
|
