View Single Post
06 Feb 2011  
usasma
Microsoft MVP

 
 

Primarily STOP 0xA errors blaming the kernel of the operating system (not likely IMO).

Many older drivers on the system, please visit the manufacturer's support website and update ALL 0f your drivers (don't use Windows Update or the Update drivers function of Device Manager). Here's a list of the drivers that were found in the memory dumps:
Code:


nvstor32.sys Mon Jun 22 18:19:03 2009 (4A400357)
nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9)
amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
vmnetbridge.sys Mon Aug 10 08:05:29 2009 (4A800D09)
snp2uvc.sys  Mon Jun 22 21:37:07 2009 (4A4031C3)
STREAM.SYS   Mon Jul 13 19:50:57 2009 (4A5BC861)
sncduvc.SYS  Mon Dec 29 04:13:29 2008 (495894B9)
VMkbd.sys    Thu Oct 22 06:50:57 2009 (4AE03911)
SCDEmu.SYS   Sun Jul 26 22:43:19 2009 (4A6D1447)
MpFilter.sys Tue Sep 14 17:23:59 2010 (4C8FE7EF)
ws2ifsl.sys  Mon Jul 13 19:55:01 2009 (4A5BC955)
nvmf6232.sys Thu Jul 30 19:47:55 2009 (4A72312B)
GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5)
atikmpag.sys Wed Mar 10 17:33:47 2010 (4B981E4B)
VMNET.SYS    Mon Aug 10 08:03:57 2009 (4A800CAD)
atipmdag.sys Wed Mar 10 18:12:09 2010 (4B982749)
vmnetadapter.sys Mon Aug 10 08:04:00 2009 (4A800CB0)
hcmon.sys    Thu Oct 22 06:00:39 2009 (4AE02D47)
netr73.sys   Wed May 20 04:47:39 2009 (4A13C3AB)
vmci.sys     Thu Oct 22 05:25:26 2009 (4AE02506)
vwifimp.sys  Mon Jul 13 19:52:09 2009 (4A5BC8A9)
RTKVHDA.sys  Tue Aug 04 05:48:13 2009 (4A7803DD)
dump_nvstor32.sys Mon Jun 22 18:19:03 2009 (4A400357)
vmx86.sys    Thu Oct 22 07:36:25 2009 (4AE043B9)
vmnetuserif.sys Thu Oct 22 06:16:06 2009 (4AE030E6)
vstor2-ws60.sys Mon Oct 12 17:06:25 2009 (4AD39A51)
MpNWMon.sys  Tue Sep 14 17:23:50 2010 (4C8FE7E6)
NisDrvWFP.sys Tue Sep 14 17:24:12 2010 (4C8FE7FC)
FsUsbExDisk.SYS Thu Sep 11 02:42:10 2008 (48C8BDC2)
MpFilter.sys Fri Nov 20 19:22:10 2009 (4B0732B2)
atikmdag.sys Wed Sep 09 00:21:01 2009 (4AA72D2D)
MpNWMon.sys  Fri Nov 20 19:22:01 2009 (4B0732A9)
MpKsl8a419406.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)
MpKsl01ad55f7.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)
MpKsl29289454.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)
MpKsl3351c49a.sys Tue Mar 30 22:06:14 2010 (4BB2AE16)

If that doesn't stop the BSOD's, then try running Driver Verifier according to these directions:
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"
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
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 08:15:50.652 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:18.603
Probably caused by : ntkrpamp.exe ( nt!EtwpFindGuidEntryByGuid+4d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x8E_nt!EtwpFindGuidEntryByGuid+4d
Bugcheck code 1000008E
Arguments c0000005 82ed56da 9d18fbb4 00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 08:11:38.048 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:34.999
BUGCHECK_STR:  0x1a_41289
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iTunes.exe
FAILURE_BUCKET_ID:  0x1a_41289_nt!MiLocateWsle+c1
Bugcheck code 0000001A
Arguments 00041289 6a3ee001 0000293d 06a8e009
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Fri Jan 28 07:19:06.663 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:47.614
Probably caused by : ntkrpamp.exe ( nt!ExpScanGeneralLookasideList+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  SYSTEM
FAILURE_BUCKET_ID:  0xA_nt!ExpScanGeneralLookasideList+22
Bugcheck code 0000000A
Arguments ffffffe0 00000002 00000000 82cdc1dc
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Sat Jan 15 09:03:45.451 2011 (UTC - 5:00)
System Uptime: 0 days 0:11:10.262
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
BUGCHECK_STR:  0x7f_d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x7f_d_nt!KiSystemFatalException+f
Bugcheck code 0000007F
Arguments 0000000d 00000000 00000000 00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Wed May  5 09:36:03.910 2010 (UTC - 5:00)
System Uptime: 0 days 0:09:47.861
Probably caused by : ntkrpamp.exe ( nt!KiTryUnwaitThread+46 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  iTunes.exe
FAILURE_BUCKET_ID:  0xA_nt!KiTryUnwaitThread+46
Bugcheck code 0000000A
Arguments 00000034 00000002 00000001 82a74028
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec