Why does opening the Outlook Program cause reboot?

By leet26 ·
This happens occasionally when Outlook is opened on one user in the netwrok. He clicks on Outlook and prior to it loading, his computer reboots over and over.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Try this

by Jacky Howe In reply to Why does opening the Outl ...

How to setup and use WinDBG to read a Memory Dump from a Blue Screen (BSOD)

If you haven't already performed this task, consider it step 1.

1. Press the WinKey + Pause
2. Click Advanced and under Startup and Recovery select Settings.
3. Uncheck Automatically restart.
4. Click on the dropdown arrow under Write debugging information.
5. Select Small memory dump (64 KB) and the output is %SystemRoot%\Minidump.
6. Restart the PC normally as this will allow the System to Blue Screen and create the Minidump.

The location of the Minidump Files can be found here. eg: C:\WINDOWS\Minidump\Mini000000-01.dmp

This article will explain how to read the small memory dump files that Windows creates for debugging

To download and install the Windows debugging tools for your version of Windows, visit the following Microsoft Web site:

Follow the prompts, and when you install, take note of your Symbols location, if you except the default settings. I normally create the folder first and then direct the install to the folder as I use WinDBG for two Operating Systems, XP and Vista.

Instructions for setting up and using WinDBG.

1. Click Start, All Programs, Debugging Tools for Windows, open WinDBG and select file, Symbol file path and modify this to suit your location, then copy & paste it.


or if you are using different Symbols eg:


SRV*c:\XPsymbols*, select OK.

2. Close the workpage and save the Workspace information. This should lock in the Symbol path.

3. Open WinDBG and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.

Click on !analyze -v under Bugcheck Analysis.

Tips! if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v or .lastevent, and press the Enter key, it will show you the exception record and stack trace of the function where the exception occurred.
You can also use the .exr, .cxr and .ecxr commands to display the exception and context records.
When working with Drivers you can use kd> lm tn
Ctrl + a will let you copy the information and paste it into notepad.


Look to the bottom of the page for information like this.

PROCESS_NAME: logon.scr
LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea
STACK_TEXT: f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585
STACK_COMMAN .thread 0xffffffff864f6a98 ; kb
FOLLOWUP_IP: sgiul50!DrvBitBlt+585 bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)
SYMBOL_NAME: sgiul50!DrvBitBlt+585
MODULE_NAME: sgiul50
IMAGE_NAME: sgiul50.dll
FAILURE_BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

Post analysis:

This System was repaired by updating the Graphics Drivers.

Related Discussions

Related Forums