Step by step guide to troubleshooting Blue Screen crashes (Server 2003, XP)
Hey guys, new to the site and it's my 1st question so please be patient!
I've run into the dreaded BSOD many times over the years. Usually it was after a driver change or was pretty obviously faulty hardware. However once and awhile I spend way too much time with trial and error troubleshooting when I know I should be looking at logs or dumps or those cryptic 00000000x44 type numbers that it displays.
My question to the Experts:
Can you please provide a Step by Step Guide to diagnosing and resolving BSOD crashes? I realize this is a bit vague. If the answer is OS specific I'm interested in Windows Server 2003 primarily but also XP Pro. I'm looking for something like:
Step 1 - make sure XYZ is turned on for future crashes
Step 2 - go to this folder to find the dump file and .....
Step 3 - start with the error codes. This block means it's a driver...
or
Step 3 - look at the 000000x44 numbers and plug them into website located at...
I know a lot of this information is a Google click or 3 away but for me, the benefit of this service is I really don't have time to chase down and compile the info myself (hence paying to have access to Experts with the knowledge in their heads).
I do have a specific crash in mind (Windows 2003 Server reboots itself once a week) and I can post more info about that but since I know BSODs will happen in my future I'd like to be armed with a clear procedure for resolving them.
If that procedure ends up being "post your log here and we'll have a look" that's Ok but I suspect there should be clues I can find myself if I know where/when/what to look at.
I've run into the dreaded BSOD many times over the years. Usually it was after a driver change or was pretty obviously faulty hardware. However once and awhile I spend way too much time with trial and error troubleshooting when I know I should be looking at logs or dumps or those cryptic 00000000x44 type numbers that it displays.
My question to the Experts:
Can you please provide a Step by Step Guide to diagnosing and resolving BSOD crashes? I realize this is a bit vague. If the answer is OS specific I'm interested in Windows Server 2003 primarily but also XP Pro. I'm looking for something like:
Step 1 - make sure XYZ is turned on for future crashes
Step 2 - go to this folder to find the dump file and .....
Step 3 - start with the error codes. This block means it's a driver...
or
Step 3 - look at the 000000x44 numbers and plug them into website located at...
I know a lot of this information is a Google click or 3 away but for me, the benefit of this service is I really don't have time to chase down and compile the info myself (hence paying to have access to Experts with the knowledge in their heads).
I do have a specific crash in mind (Windows 2003 Server reboots itself once a week) and I can post more info about that but since I know BSODs will happen in my future I'd like to be armed with a clear procedure for resolving them.
If that procedure ends up being "post your log here and we'll have a look" that's Ok but I suspect there should be clues I can find myself if I know where/when/what to look at.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
1. Make sure memory dumps are turned on
2. Check Event Log
3. Analyze the dump files
4. (this one I'm adding myself) Scan for bad memory
What if the dump files don't help? I've read that 50% of the time it just points to Windows components that aren't really the problem (some 3rd party code is asking the Windows code to do something invalid).
Then what? Is there a place that will tell me what the BSOD codes mean? For example 0000000x44 means a Stop code which typically means..... etc. etc. ??
5. Is my final step to call Microsoft? Is that a useful, worthwhile solution? Will they analyze BSOD messages and give detailed information? What cost is typically associated with this?
Building the above step by step process is really what I'm after here.