depending on how much of a Geek you are ..
here is how to find out what exactly is causing your PC to blowup (80% of
the time it's a bad 3rd party driver)
aka: the dummies guide to troubleshoot all Blue screen errors..
download WinDBG program from MS website.
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
once you have the app installed.. run it... click start.. run.. select
(debugging tools for windows ) windbg.exe
when the application starts ... click on "file" button and select 'symbols
file path" and past in this text below
SRV*C:\symbols*
http://msdl.microsoft.com/download/symbols
(your PC needs to have internet access) - create a folder on your PC call
c:\symbols
click on "file" again and select "open dump file"
select C:\Windows\Minidump\Mini112106-02.dmp
(the folder you specified in your posting below
some weird text will start to fill the screen.... issue the following
command in the text box below
! analyze -v
more text will flash on the screen.... what your looking for is "what
caused my PC to blowup" if you review my example below
you will see (in my case) some weird file called MPFirewall.sys under
module name below... what is MPfirewall.sys ? I have no idea
either .. so you google search.. on mpfirewall.sys.... Oh ... it's Mcaffee
firewall... that seems to blow up my PC on Vista startup... gee maybe if I
uninstall that application..& reboot..
Wow ... no more blue screens.. everything works ok... mission
accomplished...
this is the "cheap and dirty" on how to troubleshoot any type of blue screen
errors... if you would like to watch a Video MSFT has that goes into more
detail on how to do this... visit the link below
http://msevents.microsoft.com/CUI/W...&EventCategory=5&culture=en-US&CountryCode=US
MSFT was so impressed with the presentation this person gave .. that they
literally purchased his company... and now he works for them..
My Example file below... it's ok .. if you don't understand 95% of what is
below.. all your looking for is what file is doing this... in this case
mpfirewall.sys.. who is the guilty party
1: kd> ! analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8bcacbb0, The address that the exception occurred at
Arg3: a2b9ba50, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
FAULTING_MODULE: 81800000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx
referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
MpFirewall+2bb0
8bcacbb0 ?? ???
TRAP_FRAME: a2b9ba50 -- (.trap ffffffffa2b9ba50)
Unable to read trap frame at a2b9ba50
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 00000000 to 8bcacbb0
STACK_TEXT:
a2b9bac0 00000000 86ff4a00 86ff4948 86ff4330 MpFirewall+0x2bb0
STACK_COMMAND: kb
FOLLOWUP_IP:
MpFirewall+2bb0
8bcacbb0 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: MpFirewall+2bb0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MpFirewall
IMAGE_NAME: MpFirewall.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
