View Single Post
06 Jun 2010  
usasma
Microsoft MVP

 
 

5 memory dumps from the last 4 days (3 to 6 Jun 2010)
3 different STOP errors with 3 different causes:
- 2 STOP 0xA - error info here: BSOD Index
- 1 STOP 0x19 - error info here: BSOD Index
- 2 STOP 0x109 - error info here: BSOD Index

I would suggest running Driver Verifier to see if we can force Windows to give up the name of a faulting driver.
Please follow these instructions to run Driver Verifier:
Quote:
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"
- 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 (verified in Win7 and Vista only):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
Quote:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2008 or earlier:
Code:
ASACPI.sys   Sun Mar 27 22:30:36 2005 - Asus ATK0110 ACPI Utility (a known BSOD maker).  Also a part of the Asus PCProbe and AISuite   Utilities, update IMMEDIATELY - http://www.carrona.org/dvrref.html#ASACPI.sys
ctac32k.sys  Wed Jul 02 04:38:22 2008 - Creative Audio Driver - http://www.carrona.org/dvrref.html#ctac32k.sys
SaiH8000.sys Fri Apr 04 07:26:34 2008 - Saitek Hid driver - http://www.carrona.org/dvrref.html#SaiH8000.sys
wdcsam.sys   Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager - http://www.carrona.org/dvrref.html#wdcsam.sys
Summary of the BSOD's:
[CODE]
Code:
[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 10:05:08.306 2010 (GMT-4)
System Uptime: 0 days 20:44:57.367
BugCheck A, {28, 2, 0, fffff80002d15410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  explorer.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 12:19:58.555 2010 (GMT-4)
System Uptime: 0 days 2:33:13.601
BugCheck A, {28, 2, 0, fffff80002ccb410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchFilterHo
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 09:44:22.498 2010 (GMT-4)
System Uptime: 0 days 4:55:00.934
BugCheck 109, {a3a039d89d531849, 0, 2d12ec06a4d0e0e6, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 04:46:57.866 2010 (GMT-4)
System Uptime: 1 days 13:30:00.610
BugCheck 109, {a3a039d89c66e934, 0, a4f5e9508d6e6f81, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 15:13:49.338 2010 (GMT-4)
System Uptime: 2 days 3:45:22.829
BugCheck 19, {22, 1000000000000, 0, 0}
Probably caused by : Npfs.SYS ( Npfs!NpFsdWrite+76 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  chrome.exe
My System SpecsSystem Spec