Sporadic BSOD IRQL Not Less or Equal, as well as Memory Management BSO

ScrumpyDorito said:

New dump file

The most recent two WERE driver verified and Related to mcdbus.sys MagicISO SCSI Host Controller from MagicISO, Inc.. I would remove it at least to test.

Yours is almost 3 years old.

ok i have uninstalled magic disc. is there anything else?

ScrumpyDorito said:

ok i have uninstalled magic disc. is there anything else?

Wait and see if it crashes.


If you want to do an additional test you can run a system file check. Fairly easy to do.


Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before sucessful

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Im going to leave the computer on for 48 hours, Ill know if it blue screened by the windows check for solution window being open. Ill get back to you as soon as.

ScrumpyDorito said:

Im going to leave the computer on for 48 hours, Ill know if it blue screened by the windows check for solution window being open. Ill get back to you as soon as.

Good luck

I was mid game when MEMORY_MANAGEMENT BSOD came up this time. DUmp files attached.

ScrumpyDorito said:

I was mid game when MEMORY_MANAGEMENT BSOD came up this time. DUmp files attached.

All of the crashes up to 11/20 were verified and caused by magicIso. The more recent ones are memory management, either ram, or a driver.

Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

I had a blue screen that said " A device driver attempting to corrupt the system has been caught. The faulty driver currently on the kernel stack must be replaced"

I had a look at a bluescreen viewer as well and it says:


"ntoskrnl.exe ntoskrnl.exe+5063dc fffff800`02c67000 fffff800`03250000 0x005e9000 0x4e02aaa3 23/06/2011 02:53:23 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe"

This is what its saying is causing the BSODS

New dump file for the most recent blue screen after being verified attached as well.

ScrumpyDorito said:

I had a blue screen that said " A device driver attempting to corrupt the system has been caught. The faulty driver currently on the kernel stack must be replaced"

I had a look at a bluescreen viewer as well and it says:


"ntoskrnl.exe ntoskrnl.exe+5063dc fffff800`02c67000 fffff800`03250000 0x005e9000 0x4e02aaa3 23/06/2011 02:53:23 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe"

This is what its saying is causing the BSODS

New dump file for the most recent blue screen after being verified attached as well.

Any ideas?