dante
Junior member
 Offline
Posts: 23
|
 |
« il: 18 Dicembre 2006, ore 21:49 » |
|
Ciao a tutti.
Ho comprato un notebook hp dv6162ea...un regalo di natale per mia sorella.
Vi dico subito che il famoso sibilo si sente, ma solo se si mette l'orecchio sulla tastiera o quasi.
Quindi non causa nessun fastidio.
Con la batteria si sente un p? di pi?, ma ? sempre ad un livello tollerabile.
Ho per? un problema con il media center.
Aprendo il programma mi da questo errore:
ehExtHost.exe Common Language runtime debugging service
Poi si apre e sembra andare tutto bene.
Se vado nella sezione video per? non mi riesce a far vedere tutti i dvix la maggior parte non li vede... sembrerebbe un problema di codec, ma non credo siano loro il problema.Infatti ho installato il codec k-lite full pack e windows media player e altri programmi visualizzano bene i dvix che media center non visualizza. Inoltre ho eseguito anche un test di media center il quale mi da conferma che tutti i codec sono installati.
se faccio altre cose il media center spesso si blocca dandomi ancora l'errore che ho scritto sopra.
Su internet ho trovato forse una soluzione al mio problema.
Per? non la capisco bene... potreste aiutarmi a capire dicendomi cosa devo esattamente fare?
How to resolve ehExtHost crashes that can occur when launching Media Center
I have heard from a few customers in recent weeks who received an error dialog every time they launched Windows Media Center. This dialog had the following title and text:
Title: ehExtHost - Common Language Runtime Debugging Services
Text: Application has generated an exception that could not be handled.
Windows Media Center was usable after dismissing this dialog, but it was really annoying to have to dismiss it each time Windows Media Center was launched. Since I have seen this issue multiple times recently, I wanted to describe some troubleshooting steps that can be used to resolve this issue in many instances.
The ehExtHost process is a hosting process for Windows Media Center add-ins. When it crashes, it typically means that the add-in itself has crashed inside of its process space. Windows Media Center supports a type of add-ins known as background add-ins. These add-ins are launched when Windows Media Center is launched and run in the background as long as the main Windows Media Center process is running on system. When ehExtHost crashes immediately after Windows Media Center is launched, it typically means that an add-in registered in the background category has crashed.
In many cases, users may be unaware of what add-ins are installed on their systems, particularly in the case of Windows Media Center systems purchased from an OEM or system builder because the manufacturer may pre-install add-ins. Without knowing what add-ins are installed on the system, it is a bit more difficult to determine which add-in is causing ehExtHost to crash.
In the cases I have seen, I narrowed down the issue by looking in the registry to determine which add-ins are installed in the background category. Windows Media Center stores information about registered add-ins in the following registry sub-hives:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility
These hives normally have 3 sub-keys:
Applications
Categories
Entry Points
Add-ins that are registered in the background category will appear in a sub-key named ...\Extensibility\Categories\Background. The structure for a specific add-in looks like the following (and it is valid for this structure to appear in HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE even though I only list HKLM below):
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility\Applications\{application_guid}]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility\Categories\Background\{entrypoint_guid}]
AppId={application_guid}
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility\Entry Points\{entrypoint_guid}]
The {application_guid} value and {entrypoint_guid} values must match in the 2 places they are listed above, and together they represent a specific entry point for an add-in.
In the cases of the customers I talked to, they only had one add-in registered in the background category, and I had them rename the 3 registry sub-keys above and that caused Windows Media Center to stop trying to launch this add-in when starting up, and ehExtHost stopped crashing.
In some cases, it may be possible that multiple applications are registered in the background category. In that case, I suggest renaming the sets of 3 registry values that correspond to each add-in one at a time to narrow down which add-in is causing the ehExtHost crash.
In general, it would be best to use official unstall mechanisms to unregister the add-in, but I have seen my share of add-ins that either do not create Add/Remove Programs entries or that do not correctly unregister themselves during uninstall. Therefore it is sometimes necessary to directly edit the registry. It is important to note that I always recommend renaming the registry sub-keys as opposed to deleting them because you can rename the sub-keys back in case something goes wrong.
If you are unsure about what add-ins are installed and what the possible cause of this type of crash is, you can use the following command lines to gather the relevant registry information and send them to me so I can try to advise.
Click on the Start menu, choose Run, type cmd and click OK
Run start /wait regedit /e %temp%\hkcu_mce_extensibility.reg "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility"
Run start /wait regedit /e %temp%\hklm_mce_extensibility.reg "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Media Center\Extensibility"
Zip the files named %temp%\hkcu_mce_extensibility.reg and %temp%\hklm_mce_extensibility.reg
|
