DEP closing messenger
#16
Posted 12 April 2011 - 02:46 PM
Rich
Die with memories, not dreams. – Unknown
Register to Remove
#17
Posted 12 April 2011 - 05:58 PM
#18
Posted 12 April 2011 - 06:13 PM
Good to hear that DEP is off.
How does WLM run now?
----------------------------
Ok,I tried that,and it says "This program must run with DEP enabled. You cannot turn off DEP for this program".
EDIT: I also tried the second thing,DEP closed Messenger as soon as I logged into it.
Here are a few things to read up on that should help with your issue.
DEP - Turn On or Off for Programs
http://www.vistax64....f-programs.html
Data Execution Prevention: frequently asked questions
http://windows.micro...asked-questions
Change Data Execution Prevention settings
http://windows.micro...ention-settings
A possible cause is faulty ram due to the Fault Module Name:
Testing your ram would be something to be prepared for and a good practice also.
We will discuss this if other steps fail.
Problem signature
Problem Event Name: BEX
Application Name: msnmsgr.exe
Application Version: 14.0.8117.416
Application Timestamp: 4bc935af
Fault Module Name: StackHash_1a2d
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 7ff70000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: 1a2d
Additional Information 2: ff8e391411f3599c69e21e36a223412f
Additional Information 3: 8381
Additional Information 4: ec057a7faf9b989159f1f978fe727c0a
Extra information about the problem
Bucket ID: 1431110864
Regards,
Edited by Jkc73, 12 April 2011 - 06:16 PM.
--------------------
Want to help others? Join the ClassRoom and learn how.
How to Prevent Malware: by ©miekiemoes
"I do most of my reading when writing".
Due to real life commitments, I may be unable to respond!
#19
Posted 12 April 2011 - 06:51 PM
#20
Posted 12 April 2011 - 07:21 PM
- Click Start > run
- type msconfig press ENTER
- Click on the Startup tab
- Look for 'Windows Live Messenger' and check the box.
- Click Apply, OK and Restart
Let us know how you go.
--------------------
Want to help others? Join the ClassRoom and learn how.
How to Prevent Malware: by ©miekiemoes
"I do most of my reading when writing".
Due to real life commitments, I may be unable to respond!
#21
Posted 12 April 2011 - 07:23 PM
#22
Posted 12 April 2011 - 07:58 PM
Allow about a full 5 minutes, Then if WLM doesn't start automatically, start it manually.
Next~
Here is a How to use Event Viewer posted by Doug, in our Windows made Easy Forum.[/b]
To discover the type of Errors the machine has encountered recently, use Event Viewer.
- Go to Start - Run, type eventvwr.msc, then Press Enter.
- When the Event Viewer opens, there will be two panes.
The left pane is for event categories (Application, Security, and System).
The right pane is for event messages (Information, Warning, and Error). (We want to find errors.) - Left-click the Application category in the left pane and check for any error messages in the right pane, they will be in RED.
You want to find the one(s) that occurred at the same time your system encountered the problem you have posted about. - Repeat the previous step for each category, or until you find an appropriate error to investigate.
- Double-click the error message to bring up the information.
- Click the third button on the right side of the information window (copies information) [attachment=4701:EventViewerCopy.png]
- Paste the information here
- Additional KB information from Microsoft:
- Additional information to help interpret Error and Warning Event Types: http://www.eventid.net/
This may make it a little easier to follow.
Click on any you find that correspond with the time after you have restarted to the time you manually started WLM.
I am only after Errors from the System Events Logs and Application Events Logs.
If you find more than 30, we will just start with System Events Logs that correspond closest to Start up.
--------------------
Want to help others? Join the ClassRoom and learn how.
How to Prevent Malware: by ©miekiemoes
"I do most of my reading when writing".
Due to real life commitments, I may be unable to respond!
#23
Posted 12 April 2011 - 09:19 PM
#24
Posted 13 April 2011 - 09:40 PM
Event ID: 46
Description: Crash dump initialization failed!
- Go to Control Panel\System and Maintenance\System
- Click on "Advanced System Settings" on the left panel
- Under "Startup and Recovery" select "Settings"
- Make sure you have a check mark beside "Write and event to the system log"
Post back and let us know if that fixes the error from appearing in the Event Viewer.
Below is a Microsoft Knowledge Base Article that applies to the Event ID offered by the Event Viewer, for you to have a read through, I only recommend reading this information at this point. Please advise us if you believe that there is some material in the support based article that applies to your circumstances directly.
"Event ID: 7000" or "Event ID: 7013" Error Message When You Attempt to Start a Service
Best Regards,
--------------------
Want to help others? Join the ClassRoom and learn how.
How to Prevent Malware: by ©miekiemoes
"I do most of my reading when writing".
Due to real life commitments, I may be unable to respond!
#25
Posted 14 April 2011 - 07:39 AM
Edited by Somethingsimple, 17 April 2011 - 03:51 PM.
Register to Remove
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users