BSOD Irq not less or equal

No help at all in the diagnosis...

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

OK, thanyou.

Ill have a look at that over the weekend.

Bazzle

Good luck.

Dump zip att to 1st post

Thanks Bazzle

We prefer to have more than one DMP file to work with so we can spot trends, and in case one of them is corrupt. In your case one thing does pop out. This crash may be related to a HD problem

Lets start with running a CHKDSK and a SFC

Disk Check

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

OK
Both complete.
Nothing found.
I guess Ill wait for the next BSOD and post the file again?
It has been happeneing regularly.

Bazzle

Good news indeed.
OK, will wait until you submit any further DMP's.

Sadly it happened again pretty quick, didnt even see what was running.
New dmp file

Bazzle

bazzle said:

Sadly it happened again pretty quick, didnt even see what was running.
New dmp file

Bazzle

Well the active thread during this crash was your MSE. It isnt that. More likely one of these really old drivers

Code:

smwdm.sys    3/28/2005 10:19:36 AM        0x94a3a000    0x94a6ff40    0x00035f40    0x42481278                        
nv4_mini.sys    12/10/2005 7:45:16 AM        0x9583e000    0x95b9d780    0x0035f780    0x439abfcc                        
DNISp50.sys    11/16/2006 2:36:27 AM        0x9f9e6000    0x9f9f0000    0x0000a000    0x455c06eb                        
ckldrv.sys    3/17/2008 12:45:52 PM        0x94864000    0x94868c80    0x00004c80    0x47dea040                        
jswpslwf.sys    5/15/2008 6:28:43 AM        0x8dff8000    0x8dffcfa0    0x00004fa0    0x482c105b

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
http://www.carrona.org/dvrref.php