Disinstallare Catalyst control center

[ibell65]

Buongiorno a tutti,
sono nuovo del forum e piuttosto inesperto di computer. Qualcuno sa dirmi come posso disinstallare Catalyst control center dal computer visto che, pur presente sull'elenco programmi di Start (windows 7), non figura tra le applicazioni da poter disinstallare sul Pannello di controllo?
Grazie mille

[Dylan666]

Prova con questo (NON COMPATIBILE CON WINDOWS
http://benchmark3d.com/amd-catalyst-cle ... ll-utility

Non assicuro nulla

[ibell65]

Ti ringrazio ma.. niente da fare. Non me lo fa scaricare dicendo che provengo da un link esterno. Mi consiglia di utilizzare il loro controllo del sistema on line ma poi mi dice che non riconosce il prodotto (per forza, ho cambiato la scheda video).
Boh, mi sa che me lo tengo. Peccato perchè pensavo che fosse il responsabile dei frequenti Blue screen.

[Dylan666]

Scarica da qui:
http://bal3wolf.centelia.net/DRIVERS/TO ... .2.1.0.exe

[ibell65]

Grande... Finalmente ce l'ho fatta! Ora non mi rimane che aspettare e verificare se la causa dei blue screen fosse davvero lui.
Grazie mille.

[ibell65]

Appena riavviato me l'ha subito rifatto. Segno che non ere il CCC...
Ho avviato Who crashed e riporto i risultati. Chissà se potete aiutarmi a venirne a capo?

Welcome to WhoCrashed (HOME EDITION) v 5.00

System Information (local)

computer name: PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P7P55-M
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3748716544 total
VM: 2147352576, free: 1933033472



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 29/01/2014 07:41:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-15724-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BD2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8C8CBBD2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 29/01/2014 07:41:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!RtlCopyBufferToMdl+0x1C)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8C8CBBD2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 29/01/2014 06:56:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-16146-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BD2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8C956BD2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



Conclusion

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Dylan666]

vedi questo ma non so:
http://www.tomshw.it/forum/windows/3630 ... o-sys.html