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/Win7 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).
Reboot into Windows (after the crash) and turn off Driver 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:
Code:
Delete these registry keys (works in XP, Vista, Win7):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
These three drivers need updating
Code:
RecFltr.sys fffff880`042b6000 fffff880`042c1180 0x0000b180 0x45aecbfd 1/17/2007 21:23:09
ps6ah4nc.sys fffff880`00f9e000 fffff880`00fb5000 0x00017000 0x464e040f 5/18/2007 15:52:47
pe3ah4nc.sys fffff880`01949000 fffff880`0195f000 0x00016000 0x464e0427 5/18/2007 15:53:11
Code:
092510-23228-01.dmp 9/25/2010 22:05:54 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`040c8e0b fffff880`074b2bc0 00000000`00000000 atikmpag.sys atikmpag.sys+7e0b x64 C:\Users\K\Desktop\New folder\092510-23228-01.dmp 4 15 7600
092410-23446-01.dmp 9/24/2010 15:35:14 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`03fb4d90 fffff880`061f86a8 fffff880`061f7f10 dxgmms1.sys dxgmms1.sys+1ded3 x64 C:\Users\K\Desktop\New folder\092410-23446-01.dmp 4 15 7600
092610-19827-01.dmp 9/26/2010 17:57:08 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`03e20fd6 fffff880`0212e698 fffff880`0212df00 dxgmms1.sys dxgmms1.sys+20d4b x64 C:\Users\K\Desktop\New folder\092610-19827-01.dmp 4 15 7600
092710-21465-01.dmp 9/27/2010 03:09:20 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`04020d90 fffff880`061f96a8 fffff880`061f8f10 dxgmms1.sys dxgmms1.sys+1ded3 x64 C:\Users\K\Desktop\New folder\092710-21465-01.dmp 4 15 7600
092710-22916-01.dmp 9/27/2010 00:14:40 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`04396983 fffff880`06c8ed60 00000000`00000000 dxgmms1.sys dxgmms1.sys+1983 x64 C:\Users\K\Desktop\New folder\092710-22916-01.dmp 4 15 7600
092710-29515-01.dmp 9/27/2010 16:00:48 NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`02862578 fffff880`02861de0 fffff880`01298288 Ntfs.sys Ntfs.sys+7b288 x64 C:\Users\K\Desktop\New folder\092710-29515-01.dmp 4 15 7600
091610-22885-01.dmp 9/16/2010 23:55:12 MEMORY_MANAGEMENT 0x0000001a 00000000`00061940 00000000`04358000 b2200000`b2f118f6 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+70740 x64 C:\Users\K\Desktop\New folder\091610-22885-01.dmp 4 15 7600
091710-26301-01.dmp 9/17/2010 14:13:50 MEMORY_MANAGEMENT 0x0000001a 00000000`00003452 00000000`07e1d000 fffff700`010fca48 8b800000`9e4bf886 ntoskrnl.exe ntoskrnl.exe+70740 x64 C:\Users\K\Desktop\New folder\091710-26301-01.dmp 4 15 7600
091710-29452-01.dmp 9/17/2010 13:47:36 MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 00000000`0bc0c001 00000000`00000000 fffff700`01080000 ntoskrnl.exe ntoskrnl.exe+70740 x64 C:\Users\K\Desktop\New folder\091710-29452-01.dmp 4 15 7600
092610-20186-01.dmp 9/26/2010 19:33:20 MEMORY_MANAGEMENT 0x0000001a 00000000`00003452 00000000`0073e000 fffff700`01082e20 d3300000`cce61816 ntoskrnl.exe ntoskrnl.exe+70740 x64 C:\Users\K\Desktop\New folder\092610-20186-01.dmp 4 15 7600
092710-25459-01.dmp 9/27/2010 15:49:26 BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001097 00000000`046d6f38 fffffa80`04125b50 ntoskrnl.exe ntoskrnl.exe+70740 x64 C:\Users\K\Desktop\New folder\092710-25459-01.dmp 4 15 7600
