visitor (0 QPoints)
  • FR
  • EN
  • NL
  • DE
  • ES
315 experts, 1193 registered users, 1659 questions already answered
European Experts Exchange, the very best site for high-quality IT solutions

New Improved Search!

 


05/10/2011 1h30 : Steve Jobs is dead, the father of Apple ][ is gone, we are all orphaned.

Operating Systems :: Windows :: HowTo : mini dump analysis after crash (IRQ LESS OR EQUAL ... blue screen )


By: VGR France  Date: 03/11/2006 09:41:27  English  Points: 0 Status: Answered
Quality : Excellent
When you get a nice Blue Screen Of Death with the sybilline message "IRQ LESS OR EQUAL" wihout any useful information attached to it (as are all windaube error messages), then it's about time to analyse the minidump "core dump files" produced by the "new" DrWatson added at the time of IE 5.5 (for obvious reasons ;-)

Preliminary remark : it's usually best to first perform a RAM memory check using MemTest, but as this takes place after rebooting your fragile windows (r)(tm)(c) installation, it's not something you'd do first, so let's try the "microsoft way" of things :

the "minidump" files created in %windir%\minidump (most likely c:\WINNT\minidump) are completely useless unless you have a debugger able to decypher them.

Such tools are supposedly offered by Microshaft at this MSDN download page (for Win2K SP4, but others do exist)

Once you downloaded all symbols, retail and debug, the "tools" and such, and ***finally*** open up the *.dmp file in WinDbg, you ***should*** be able do diagnose the faulty driver (probably linked to faulty hardware also)

***if*** all you get is this :

Could not get base of kernel ffffffff8046e8f0 Thread Create: Process=0, Thread=0 Could not get address of KiProcessorBlock DMKD: Unable to get address of debugger data list Could not get address of KiProcessorBlock Finished re-loading kernel modules Kernel Debugger connection established for D:\WINNT\Minidump\Mini110306-01.dmp Kernel Version 2195 Free loaded @ 0000000000000000 Bugcheck 000000d1 : 00000000 00000002 00000000 00000000 Hard coded breakpoint hit >


then the educated guess if that memory (RAM) is the culprit. You installed and downloaded minidump analysis tools (uninstallable and many hundreds of MBs in size) for ***nothing***

Just run Memtest from DOS and pray ;-)
By: VGR Date: 14/11/2006 21:21:45 English  Type : Comment
Now how to analyse stuff if WinDbg runs nominally :

You may either do File | Symbols Path and set it to your symbols location (r:\symbols in my case)
Then do File | Open Crash Dump and wait for completion to analyse the output : Look for the MODULE_NAME and IMAGE_NAME headings

OR

You may use this script :

D:\>type transformdump.bat @echo off echo transforming minidump %1 ... d: cd mini* kd -z D:\WINNT\Minidump\%1.dmp kd> .logopen .\debuglog.txt kd> .sympath srv*r:\symbols*http://msdl.microsoft.com/download/symbols kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q notepad .\debuglog.txt echo Port Mortem : Look for the MODULE_NAME and IMAGE_NAME headings.

By: VGR Date: 22/11/2006 20:08:02 English  Type : Comment
if you still get "blank" BSoDs (no driver indication), like 0x00001D IRQ LESS OR EQUAL and you tested the RAM ok (from true DOS), ***and*** if all your memory dumps appear "broken" as above, ***then*** probaly your hard disk is dying... backup your data while Windaube still boots [especially if you use FAT32 or NTFS partitions, because FAT16 ones will be readable from DOS so you can backup them from DOS, using a parallel ZIP100 for instance], then examine the hard disk from DOS...

Do register to be able to answer

EContact
browser fav
page generated in 332.895040 milliseconds

Why Google AdSense ads ?

compteur
 Ranking-Hits PageRank for this page