Adsense

Saturday, October 06, 2007

"Windows Live Messenger" or "Windows Media Player" has stopped working - APPCRASH / StackHash Error - Fix

If you are getting either of the following two error messages when staring Windows Live Messenger or Windows Media Player, I might know of a couple of things that could be causing the problems. This may only affect people who are getting the error in conjunction with errors in Fault Module Name StackHash_XXXX.
----- ERROR MESSAGES -----
Windows Live Messenger has stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: msnmsgr.exe
Application Version: 8.1.178.0
Application Timestamp: 45b12d6a
Fault Module Name: StackHash_ed38
ETC...
Windows Media Player has stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: wmplayer.exe
Application Version: 11.0.6000.6336
Application Timestamp: 46a16548
Fault Module Name: StackHash_5255
ETC...
----- /ERRORS MESSAGES -----
Possible Fix 1: nVidia nForce driver components
I have an EVGA i650 Ultra motherboard in my system with the nForce drivers installed. Either of the two following nForce driver components / features might cause this problem in Vista.
  1. nVidia MediaShield
  2. nVidia - ForceWare Network Access Manager
Uninstall them to see if it clears up the issue. I uninstalled both of them and it was fixed, so it could be either.
Possible Cause 2: Vista's DEP Protection
To fix this issue, you might need to disable DEP in Vista. To disable DEP, perform the following (found these steps HERE.)
1. Click Start
2. Click All Programs
3. Click Accessories
4. Right Click on Command Prompt
5. Left click on Run as Administrator
6. Click the Allow button if it asks you for permission
7. Type or copy and paste this into the command prompt window:
bcdedit.exe /set {current} nx AlwaysOff
8. You should see the message "Operation Completed Successfully"
9. Reboot and DEP should be off.
For more information regarding DEP, what it is and how it affects your web-based applications. Checkout this link.
Possible Cause 3: Administrator Mode
You may also want to try running the application as an administrator. You can do this by right clicking on the short-cut, selecting properties and checking the "Run as administrator" box.

19 comments:

Unknown said...

Thank you, thank you. I fixed this by uninstalling ForceWare Network Access Manager.

Anonymous said...

Thank you :-D
I have the asus p5n motherboard n it uses nvidia.
I tried you first sollution n it worked like a charm :-D

Snipervzln said...

Thank you very much for this post, i have a Evga 680i and had the very same problem untill i read this and uninstall the Network Access Manager, now i got my messenger back.

Greetings from Venezuela.

Anonymous said...

I would like to add that I had the exact same problem and it seems to be fix now simply by removing the nvidia network component. Thanks so much. :0 It was a huge pain in the backside to have it shutting down all the time.

Anonymous said...

Cool work on windows server 2008! wirh all programm will be RUNS! thank you

Anonymous said...

Спасибо большое, очень помогли.

Привет из России!

Anonymous said...

никуя не помогло. Начинаю расстраиваться в 7

Артур said...

пожалуйста обьясните это на русском

Nastusha said...

Has made all as it is necessary, but has not helped

Anonymous said...

ТОже не куя не помогло

По-русски said...

Долбаная служба контроля пользователей!
Отключение - пункт 2.
Спасибо!
Fu**ing control service users! Disable - Item 2.
Thanks!

Anonymous said...

КАК БЫЛА ПРОБЛЕМА,ТАК ОНА И ОСТАЛАСЬ!(((

Сигнатура проблемы:
Имя события проблемы: APPCRASH
Имя приложения: kl2.exe
Версия приложения: 1.0.0.1
Штамп времени приложения: 4c372bb3
Имя модуля с ошибкой: kl2.exe
Версия модуля с ошибкой: 1.0.0.1
Штамп времени модуля с ошибкой: 4c372bb3
Код исключения: 80000003
Смещение исключения: 00266276
Версия ОС: 6.0.6001.2.1.0.256.1
Код языка: 1049
Дополнительные сведения 1: fd00
Дополнительные сведения 2: ea6f5fe8924aaa756324d57f87834160
Дополнительные сведения 3: fd00
Дополнительные сведения 4: ea6f5fe8924aaa756324d57f87834160

Anonymous said...

Помогло отключение DEP

Anonymous said...

ну а с виндоус 7 что делать?

dphektive said...

i am having this problem with windows7, however it seems to only occur when i try to change focus window to an msn linked facebook chat... any idea if your proposed fix's for vista will work for me?

Paul Fox said...

Sorry dphektive. I don't know if the issues are related. It might work since the error is the same, but it sounds like it could be something different. I suppose it's worth a try though.

Unknown said...

This is needful information...greatly appreciated...keep sharing more!!! visit more info Windows live mail help also Call +1-800-231-4635 (Toll Free) now for Windows live mail help & Support from Microsoft certified technicians.

Unknown said...

Жмем "ПУСК". В строке поиска набираем cmd. Наводим мышь на появившийся значек cmd, жмем правую кнопку мыши, Запуск от имени Администратора => жмем да, открывается черное окно.
Копируем:

bcdedit.exe /set {current} nx AlwaysOff

Вставляем в черное окно, жмем Enter, перезагружаем комп, радуемся.

Anonymous said...

Сигнатура проблемы:
Имя события проблемы: APPCRASH
Имя приложения: Skype.exe
Версия приложения: 7.17.0.104
Отметка времени приложения: 566e622c
Имя модуля с ошибкой: Skype.exe
Версия модуля с ошибкой: 7.17.0.104
Отметка времени модуля с ошибкой: 566e622c
Код исключения: c0000005
Смещение исключения: 00005dca
Версия ОС: 6.1.7600.2.0.0.256.1
Код языка: 1049
Дополнительные сведения 1: 9435
Дополнительные сведения 2: 9435d7bb62cf6d2a57c73c22609e2092
Дополнительные сведения 3: 6d9d
Дополнительные сведения 4: 6d9d074f487d68ec6a82974afed0795c

Ознакомьтесь с заявлением о конфиденциальности в Интернете:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0419

Если заявление о конфиденциальности в Интернете недоступно, ознакомьтесь с его локальным вариантом:
C:\Windows\system32\ru-RU\erofflps.txt

у меня вот что выбевает и всё перепробывал что здесь написано..после закрывания программы выдаёт runtime error 216 at 000405dca