megaugly Posted December 22, 2014 Posted December 22, 2014 Hello!I am looking for a soultion to get my new R9 270x running on Vista Ultimate 64without those user32 and powrprof errors. i do not need CrossfireI just replaced all files as instructed. but i get some errors.After reboot:"CCC: Monitor program" not runningandwhen starting catalyst center:"Catalyst Control Centre: Command Line Interface" not runningCCC Omega 14.12driver version 14.501.1003.0driver date 20.11.2014(HDMI Hotfix not installed)
smeezekitty Posted December 22, 2014 Author Posted December 22, 2014 (edited) I am looking for a soultion to get my new R9 270x running on Vista Ultimate 64without those user32 and powrprof errors. i do not need CrossfireI just replaced all files as instructed. but i get some errors.I don't have a solution to the user32.dll errors. I know it is not the most elegant to have an unclean bootbut the user32 error doesn't cause any functional problem. powrprof on the other hand causes big problemsand will even crash 3rd party programs. Your driver version looks good. Did you update the other catalyst components in addition to the manual driver install? (the normal installer does this)You have to update it before installing files. Also, just to make sure, you did follow the 64 bit instructions and not the 32 bit ones? Edited December 22, 2014 by smeezekitty
megaugly Posted December 22, 2014 Posted December 22, 2014 I updated the CCC from 14.9.1 Beta to 14.12 omega- custom Intsallation with all options activated and modified the win7 .inf file for vista. then i downloaded your 32 and 64 bit filesi followed your instructions from post #12
smeezekitty Posted December 22, 2014 Author Posted December 22, 2014 After reboot:"CCC: Monitor program" not runningWhat happens if you run MOM.EXE manually?Any DLL errors? Or crashes?
megaugly Posted December 23, 2014 Posted December 23, 2014 when i start mom.exe i see the same error when i reboot windows "monitor" does not run (anymore) the vista event manager reports: MOM.exe Frameworkversion: v4.0.30319System.Reflection.TargetInvocationExceptionRuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])at System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)at System.RuntimeType.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[], at System.Reflection.ParameterModifier[], System.Globalization.CultureInfo, System.String[])at System.Type.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[])at ATI.ACE.MOM.EXE.MOM.Main(System.String[])
smeezekitty Posted December 24, 2014 Author Posted December 24, 2014 I'll see what I can find out. But it will probably have to wait until after Christmas. Lacking a 64 bit Vista test system makes it a lot harder to troubleshoot
megaugly Posted December 25, 2014 Posted December 25, 2014 sure after Christmas i will try a clean reinstall of the drivers perhaps something went wrong with the update from 14.9.
megaugly Posted December 25, 2014 Posted December 25, 2014 (edited) I am finish with the cleanup:-express removed all ccc software and drivers-manualy deleted all ati/amd files and folders-manualy deleted "your" files from windows/system32 and syswow64 folder-removed all ati/ amd registry keys-ccleaner-windows reboot-started full ccc setup in custom mode-reboot windows "Disable Driver Signature Enforcement"-and installed display drivers from amd omega drivers 14.12. with [ATI.Mfg.NTamd64.6.0] modificationnow i am at the point i get the annoying error messages :at windows bootup:"QueryDisplayConfig" USER32.dlland everytime i start 3rd party software (firefox or any games)"PowerSettingUnregisterNotification" POWRPROF.dlli replaced all your files from your 32 and 64 bit patchmom and cli do not run (again)windows vista64 ultimate (all service packs and updates installed until today 25.DEC.2014).net Framework64 v4.0.30319 version 4.5.50938 ( i hope this is correct )CCC 14.12 Omegadriver version 14.501.1003.0 (or 14.501.1003-141120a-177998c)driver date 20.11.2014AMD CCC version 2014.1120.2123.38423 Edited December 25, 2014 by megaugly
smeezekitty Posted December 25, 2014 Author Posted December 25, 2014 now i am at the point i get the annoying error messages :at windows bootup:"QueryDisplayConfig" USER32.dllThat message doesn't go away but luckily it only occurs on boot and when clicking some options in CCCand everytime i start 3rd party software (firefox or any games)"PowerSettingUnregisterNotification" POWRPROF.dllThat is normal before the patchi replaced all your files from your 32 and 64 bit patchmom and cli do not run (again)To be sure, you are putting the 32 bit version of powrwrap.dll in SysWow64 and the 64 bit version of powrwrap.dll in System32 (ironic name) Without meaningfully errors, it is exceedingly difficult to troubleshoot
megaugly Posted December 25, 2014 Posted December 25, 2014 (edited) yes 32bit goes to syswow64and 64bit goes to system32 the eventmanager shows the same message as posted on #20 CLI.exeFrameworkversion: v4.0.30319System.Reflection.TargetInvocationExceptionStack:at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])at System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)at System.RuntimeType.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[], System.Reflection.ParameterModifier[], System.Globalization.CultureInfo, System.String[])at System.Type.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[])at ATI.ACE.CLI.EXE.CLI.Main(System.String[])MOM.exeFrameworkversion: v4.0.30319System.Reflection.TargetInvocationExceptionstack:at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])at System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)at System.RuntimeType.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[], System.Reflection.ParameterModifier[], System.Globalization.CultureInfo, System.String[])at System.Type.InvokeMember(System.String, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object, System.Object[])at ATI.ACE.MOM.EXE.MOM.Main(System.String[]) are this errors meaningfull enough? i have no idea where i can get more information about the MOM and CLI crash Edited December 25, 2014 by megaugly
smeezekitty Posted December 26, 2014 Author Posted December 26, 2014 Those don't tell me much. (Windows fault, not yours) I upgraded to a Radeon 7850 on Christmas. I had to reinstall the patched files but it is still working perfectly. I have a spare hard drive so I might be able to install Vista x64 on it: http://getintopc.com/softwares/operating-systems/windows-vista-home-premium-download-iso-32-bit-64-bit/I don't think I'll need to activate it since it shouldn't take more than a few days. Anyway, it might take me a few days to set it up
megaugly Posted December 26, 2014 Posted December 26, 2014 (edited) i am wondering why blazer78 has no errors and his catalyst is still runningi need the catalyst not for crossfire but i need it for OC and monitor the temps also i use catalyst for my chipset and OC my Phenom CPU perhaps my system runs with a few different dll files because of the AMD chipset drivers?(SATA, SOUND, ONBOARD VGA) Edited December 27, 2014 by megaugly
smeezekitty Posted December 27, 2014 Author Posted December 27, 2014 (edited) Ok. Run this batch file and post the contents of powrprof_sysinfo.txt after it finishes It will look for any powrprof.dll dependencies in your System32, SysWow64 and AMD foldersas well as collect some other info. It might take several minutes to execute depending on the speedof your hard drive. Please ignore any file not found errors. I don't know if the chipset has anything to do with it. I thought AMD stopped bundlingthe chipset drivers with the graphics drivers but you never know. Crossfire or not shouldn't really matter.ppf.zip Edited December 27, 2014 by smeezekitty
megaugly Posted December 27, 2014 Posted December 27, 2014 (edited) Datenträger in Laufwerk C: ist Vista64 Volumeseriennummer: 2812-276E Verzeichnis von C:\Windows\System3210.04.2009 23:11 123.392 powrprof.dll21.12.2014 23:31 44.032 powrwrap.dll 2 Datei(en), 167.424 Bytes 0 Verzeichnis(se), 77.443.055.616 Bytes frei Datenträger in Laufwerk C: ist Vista64 Volumeseriennummer: 2812-276E Verzeichnis von C:\Windows\SysWow6410.04.2009 22:28 98.816 powrprof.dll10.12.2014 21:25 38.912 powrwrap.dll 2 Datei(en), 137.728 Bytes 0 Verzeichnis(se), 77.443.051.520 Bytes freiGREP C:\Windows\System32:GREP C:\Windows\SysWow64:TASK DATA there is something missing...grep reports msys-1.0.dll is missing Edited December 27, 2014 by megaugly
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now