IRQ (Interrupt Request) and IRQL (Interrupt Request Level) are similar terms and somewhat related - but you cannot assume that the IRQ is the same thing as the IRQL, because they're not. A read here (if you can stay awake) explains it: http://ext2fsd.sourceforge.net/documents/irql.htm
Basically it states that IRQ is determined by the hardware, while IRQL is determined by Windows.
A memory dump analysis will reveal a lot about what caused a crash, and may be able to lead to a solution faster than normal troubleshooting procedures. The appearance of a filename in the BSOD is a clue. The filename is where the system crashed - NOT what caused the crash. For example, if the BSOD shows nv4disp.dll (an nVidia driver) as the file, then I'd suspect the video drivers. But, if it shows ntoskrnl.exe (an operating system file), then I'd have to suspect another cause (as the OS files are less likely to cause a BSOD than viruses or bad drivers). 2 other things to consider are the actual BSOD error itself, and at what level is the error being generated (with improved communication between Windows, the BIOS and the CPU this is very important)
An example is if your car stops running (that's the computer). If it's because the engine stopped (that's Windows). If the reason for the engine stopping was that the fuel system failed (fuel, air, cooling are the systems as I remember them) - that's where the crash occurred (the filename). Then you've gotta troubleshoot why the fuel system failed (a line was blocked, you ran out of gas, the carburator/fuel injection broke, your gas had water in it, etc).
Now, this being said, if the BSOD occurs at a level that Windows is able to recognize it'll capture the BSOD event in a memory dump file. A memory dump will contain everything that was in memory at the time of the dump and will be roughly equal to the size of your RAM. In a lot of systems tho', the dump file is set for a minidump, which won't contain the entire contents of memory - but will contain enough to do an analysis with the Windows Debugging Tools.
The easiest part of the memory dump analysis is looking for filenames - the harder part (I still can't quite get this part myself) is seeing where the crash occurred in memory and what processes were running just before it occurred.
Locataing files on your system that end in .dmp and .mdmp is the start for analyzing these files. Then, follow this link to analyze them: http://www.bleepingcomputer.com/forums/t/74712/how-to-find-bsod-error-messages/
Post the results here for some of us to have a look at and we can proceed from there.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able. - John
(my website: http://www.carrona.org/
)**If you need a more detailed explanation, please ask for it. I have the Knack
. ** If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.
<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.