User Guides solving mysteries of crashing windows.

I have seen many times people asking about windows crashes and others shooting in the dark about hardware problems, heat problems, cleaning ram, cleaning dust etc... etc... etc...:rofl:

Lets analyze and find out whats exactly wrong. and try to fix it instead of replacing the ram.

step 1: setup the mini dumps.
21vdrl.jpg


Step 2: Analyze the dump.
Install the "debugging tools for windows" from msdn and open windbg.
From here:
Install Debugging Tools for Windows 32-bit Version
Install Debugging Tools for Windows 64-bit Version
30bi5ci.jpg


now, in the command window, type "!analyze -v"
357j61c.jpg


xspjt.jpg


Now you have found which driver is rogue.
1zzol88.jpg


now, uninstall the bugger and get a stable new version. or remove the service from registry. (brute way of cleaning)

And please don't blame windows for rogue third party drivers.

Disclaimer: Although 90% the crashes are similar, some times windows crashes due to some faulty windows drivers and some strange cases the minidumps dont provide enough info. but at least you wont have to panic that your ram modules are burnt.
 
rahulyo said:
Is it work with VISTA ??
yeah... but you need to run windbg as administrator
2d7vgnl.jpg

=CrAzYG33K= said:
^ It would also help if you the location of the Dump file was aslo mentioned..
The location is usually defaulted to %systemroot%/minidumps => "c:\windows\minidump\" but you can configure that from screen.
s2fyxj.jpg
 
THANKS a lot.

I found out that a file called nltdi.sys (For Netlimiter) was causing the crashes.

I've uninstalled it, hope it solves the problem.
 
Back
Top