Please remove this program/driver as it's older and may not be compatible: ATITool.sys Fri Nov 10 08:08:51 2006

The memory dumps involve pool corruption and issues with memory accesses - as such I'd suggest:
- a memory test: Memory Diagnostics
- running Driver Verifier. Please follow these instructions exactly:
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.


So, I'd suggest that you first backup your stuff 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 Startup Repair feature).


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 "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then 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 waitfor 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.


Reboot into Windows (after the crash) and turn offDriver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Here's a summary of the memory dump analysis':
Code:
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Nov 23 00:53:46.799 2009 (GMT-5)
System Uptime: 0 days 0:00:09.625
BugCheck C5, {56e8, 2, 0, 82b32795}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+135 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Nov 24 15:28:49.532 2009 (GMT-5)
System Uptime: 0 days 0:00:10.140
BugCheck C5, {9b00, 2, 0, 82b2c795}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+135 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Thu Nov 26 00:47:00.237 2009 (GMT-5)
System Uptime: 0 days 0:00:08.845
BugCheck 1000007E, {c0000005, 82c6708f, 80786890, 80786470}
Probably caused by : ntkrpamp.exe ( nt!ObpLookupDirectoryEntry+2b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Nov 30 06:02:14.286 2009 (GMT-5)
System Uptime: 0 days 0:00:07.893
BugCheck 1000007E, {c0000005, 82c7708f, 80786890, 80786470}
Probably caused by : ntkrpamp.exe ( nt!ObpLookupDirectoryEntry+2b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System