How can I find more information regarding why Outlook crashed ? Hotmail Support +1-800-210-6150 We Help you in this trouble
How can I find more information regarding why Outlook crashed?
From the Event Viewer, you may often find out more info concerning why Outlook crashed.
The Event Viewer is a general location in Windows itself where software and Windows will write status events if as an example an agency is started/stopped, an application is launched or shut, if a backup was successful, who logged on into the system, respectively... It also comprises events for when an application suddenly stopped or crashed.
The Event Viewer might be a great assistance to determine the root cause of concern or to discover new leads if regular Tracking of Outlook did not bring any benefits.
Open the Event Viewer
There are a number of number of approaches to open it. Some of them are;
Expand System Tools to see Event Viewer.
Windows-8 and Windows-10
Click the Windows icon at the bottom left and choose Event Viewer.
Windows Key+X-> Event Viewer
Right Click This PC from File Explorer and select Manage. Expand System Tools to view Event Viewer.
Locating the Outlook entrances
Outlook logs its entrances to the Application log. For for the particular log, first enlarge the Event Viewer list and then the Windows Logs list.
The application that created the Occasion is recorded in the"Source" column. Generally, you will have to look for"Outlook" here but sometimes it's written by another process and that means you'll need to look at that time then instead. Scroll till you have found the latest entry or entries that were written during your last Outlook session.
If you're having problems locating the correct event entry (for instance when you wish to see if the same happened a few days ago), then you can also employ a filter into the log to just demonstrating the entrances with the big event Level "Error" along with Event Source being Outlook.
You'll come across the filter command in what pane on the right or by right-clicking on the application form log.
Example of a filtered Event Viewer for Outlook errors. (click image to enlarge)
Looking up the meaning of the entries
Whenever you have discovered the entry, you can find more info about the big event in the Preview Pane. The most important information for troubleshooting purposes can be seen by taking a look at the"Event ID" number and the full-text description.
The complete text description may occasionally already let you know what exactly is going on when it shows the name of the add-in that you have installed. Disable the add-in and find out whether Outlook starts normally now. If it can, reboot, reinstall or upgrade the add-in or get the vendor of the add-in that willhelp you farther troubleshooting their product.
In the event the description field is not clear, then it is also possible to try to find extra information relating to this via the Microsoft Support website. For Example, when you want to find out more about Event ID 27 you can sort the following search phrase;
Outlook malfunction Event ID 27
Event IDs aren't always clear enough. Especially once you receive an error 1000 or 1001 you will get a lot of results since these are useful for more generic crashes. In those cases, it will help to additionally incorporate some keywords from the description field, especially if it contains references to all files.
First troubleshooting steps
It's not always directly needed to start to analyze your (Outlook) problems by launching the Event Viewer and dive into technical descriptions. Many problems allow themselves to be solved by easy deduction.
As an example, if Outlook works in Outlook Safe Mode, it usually suggests that the problem is brought on by an add-in.
Other overall troubleshooting steps can be found here.
When you have issues locating the cause, you could always post in the Outlook forums with all the exact error message. Open the event by double-clicking onto it and then press the copy button to readily paste it from the newsgroup message.
Essential! Whenever you have crashes with references to all files, never manually or disable replace these all files unless you are specifically instructed to do so by a renowned support specialist or directions from a trusted source. , replace all files using all files that you obtained from a number of many all-download sites which are around. These are typically modified, virus-infected or the wrong variant and is going to get your computer more harm than good.
From the Event Viewer, you may often find out more info concerning why Outlook crashed.
The Event Viewer is a general location in Windows itself where software and Windows will write status events if as an example an agency is started/stopped, an application is launched or shut, if a backup was successful, who logged on into the system, respectively... It also comprises events for when an application suddenly stopped or crashed.
The Event Viewer might be a great assistance to determine the root cause of concern or to discover new leads if regular Tracking of Outlook did not bring any benefits.
Open the Event Viewer
There are a number of number of approaches to open it. Some of them are;
Expand System Tools to see Event Viewer.
Windows-8 and Windows-10
Click the Windows icon at the bottom left and choose Event Viewer.
Windows Key+X-> Event Viewer
Right Click This PC from File Explorer and select Manage. Expand System Tools to view Event Viewer.
Locating the Outlook entrances
Outlook logs its entrances to the Application log. For for the particular log, first enlarge the Event Viewer list and then the Windows Logs list.
The application that created the Occasion is recorded in the"Source" column. Generally, you will have to look for"Outlook" here but sometimes it's written by another process and that means you'll need to look at that time then instead. Scroll till you have found the latest entry or entries that were written during your last Outlook session.
If you're having problems locating the correct event entry (for instance when you wish to see if the same happened a few days ago), then you can also employ a filter into the log to just demonstrating the entrances with the big event Level "Error" along with Event Source being Outlook.
You'll come across the filter command in what pane on the right or by right-clicking on the application form log.
Example of a filtered Event Viewer for Outlook errors. (click image to enlarge)Looking up the meaning of the entries
Whenever you have discovered the entry, you can find more info about the big event in the Preview Pane. The most important information for troubleshooting purposes can be seen by taking a look at the"Event ID" number and the full-text description.
The complete text description may occasionally already let you know what exactly is going on when it shows the name of the add-in that you have installed. Disable the add-in and find out whether Outlook starts normally now. If it can, reboot, reinstall or upgrade the add-in or get the vendor of the add-in that willhelp you farther troubleshooting their product.
In the event the description field is not clear, then it is also possible to try to find extra information relating to this via the Microsoft Support website. For Example, when you want to find out more about Event ID 27 you can sort the following search phrase;
Outlook malfunction Event ID 27
Event IDs aren't always clear enough. Especially once you receive an error 1000 or 1001 you will get a lot of results since these are useful for more generic crashes. In those cases, it will help to additionally incorporate some keywords from the description field, especially if it contains references to all files.
First troubleshooting steps
It's not always directly needed to start to analyze your (Outlook) problems by launching the Event Viewer and dive into technical descriptions. Many problems allow themselves to be solved by easy deduction.
As an example, if Outlook works in Outlook Safe Mode, it usually suggests that the problem is brought on by an add-in.
Other overall troubleshooting steps can be found here.
When you have issues locating the cause, you could always post in the Outlook forums with all the exact error message. Open the event by double-clicking onto it and then press the copy button to readily paste it from the newsgroup message.
Essential! Whenever you have crashes with references to all files, never manually or disable replace these all files unless you are specifically instructed to do so by a renowned support specialist or directions from a trusted source. , replace all files using all files that you obtained from a number of many all-download sites which are around. These are typically modified, virus-infected or the wrong variant and is going to get your computer more harm than good.
Comments
Post a Comment