BSOD - memory_management, please help

Did you try to boot in the safe mode?

Now wait for it to crash, then upload the new DMP file to us

Gnomicide said:

I did not, I did a system restore and am now booted in. Was that the incorrect thing to do?

No, that was not an incorrect thing to do. It worked and you can use your computer. The restore can negate the information in the uploaded dump files because your system has changed (somewhat); but that is no big deal. It was a good move.

There are 11 dumps just from today. This will take a little while; but I will be back. :)

For now, please turn Driver Verifier off.

I have looked at five of the dumps and I will look at the rest. Four of the five dumps blamed Microsoft drivers as the cause. This is highly unlikely. One blamed CI.dll - ci.dll belongs to the software ci.dll or Alcohol 120% by Alcohol Soft Development Team. Uninstall this program using Revo (free) uninstaller.

I find the following out of date drivers:

GEARAspiWDM.sys Mon May 18 08:17:04 2009 - CDRom Class Filter Driver or Filter Driver for 2k and XP or CD/DVD Class Filter Driver or CD DVD Filter or GEAR ASPI Filter Driver belongs to the software GEAR.wrks or GEAR CDRom Filter or GEARAspi or GEARAspiWDM or Norton Ghost or MixMeister Studio Demo or MixMeister Pro or GEAR 32bit Driver Installer or MixMeister CD-R Drivers or Drive Image or Norton Save and Restore or CD DVD Filter or GearDrvs or iTunes or GEAR ASPI Filter Driver or GEAR driver installer for x by GEAR Software Inc (www.gearsoftware.com). I do not think there is an update for this driver. Let this one ride for the time being. If you know what software in this list you have installed, you can try to update the software.

scmndisp.sys Wed Jan 17 02:48:03 2007 - ® Neutral Wireless Solution, Netgear, Inc. This driver is really obsolete. I am not sure what it does. It appears to be a utility driver associated with a Netgear wireless adapater. I could not find an upgrade for the software; but maybe you can. If not, you can uninstall the utility or rename the driver from scmndisp.sys to scmndisp.bak. This way you can simply rename it back to .sys if necessary.

Take care of the above, reboot, and lets see what happens.