NathanThe three newest were related to something called a memory exception. Usually caused by a driver (but can be the ram itself). My experience tells me it is probably your Kaspersky. Since that is the easiest to check I would remove and replace it with MSE.
Kaspersky is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.
http://support.kaspersky.com/downloads/utils/kavremover10.zip
http://www.microsoft.com/security\_essentials/
If that doesnt stop the crashes run these tests to find the mis-behaving driver.
These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.
*Dont forget to upload any further DMP files (especially those when verifier is running)
*If you are overclocking anything reset to default before running these tests.
In other words STOP!!! If you dont know what this means you probably arent
1-Memtest.
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org
*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.
2-Driver verifier
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.
*But sometimes it'll crash and won't tell you the driver.
*Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable 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.
*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.
*Further Reading
"http://support.microsoft.com/kb/244617"
Drivers needing updating
nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
hamachi.sys Thu Feb 19 05:36:41 2009 (499D3639)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
http://www.carrona.org/drivers/driver.php?id=nvm62x64.sys
http://www.carrona.org/drivers/driver.php?id=hamachi.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys