BSOD Windows 7

4803 Views 1 Reply 2 Participants Last post by usasma, Jul 13, 2010

Unknowndady

Discussion Starter · Jul 12, 2010

My computer usually crashes while surfing the internet in Google Chrome. It happens every once in awhile but not all the time. My specs are below. Thankyou for your help:smile:

OS - Windows 7
x86 (32-bit)
Windows XP
full retail version
2 years old at most
Age of OS installation - last summer
CPU - AMD Phenom II X4 925
Video Card Geforce 8600 GT
MotherBoard Biostar MCP6P M2+
Power Supply - OCZ 600 watt

Save

Status: Not open for further replies.

1 - 2 of 2 Posts

13 memory dumps, from 10 Feb to 12 Jul 2010 (6 months)
A single STOP 0x116 (from 09 May 2010)- and the rest are STOP 0xD1

More info on the STOP 0x116 here: http://www.carrona.org/bsodindx.html#0x00000116
Specific troubleshooting steps here: http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

More info on the STOP 0xD1 here: http://www.carrona.org/bsodindx.html#0x000000D1

Interestingly, there's several different network processes present in the stack text:
- vpcnfltr.sys - a component of Windows Virtual PC
- athr.sys - a component of a wireless networking device. This is probably your D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.B)

I'd suggest that you 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:

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: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://www.carrona.org/dvrref.html ).
Please pay particular attention to any dated 2008 or earlier:

Code:

adfs.SYS     Thu Aug 14 10:57:15 2008 - Adobe Filter driver - http://www.carrona.org/dvrref.html#adfs.SYS 
nvm62x32.sys Fri Oct 17 17:00:39 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) - http://www.carrona.org/dvrref.html#nvm62x32.sys

Then, I would suggest running Driver Verifier according to these instructions:

Code:
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: http://support.microsoft.com/?kbid=244617&sd=RMVP

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 18:36:50.882 2010 (UTC - 4:00)
System Uptime: 0 days 8:17:07.412
BugCheck D1, {6, 2, 0, 890a08cb}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!IppChecksumDatagram+be )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 08:38:20.663 2010 (UTC - 4:00)
System Uptime: 0 days 0:19:47.567
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
BugCheck D1, {6, 2, 0, 890828cb}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Tue Jun 22 22:04:59.190 2010 (UTC - 4:00)
System Uptime: 0 days 0:47:16.094
BugCheck D1, {10, 2, 1, 8905c23a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 14:10:57.808 2010 (UTC - 4:00)
System Uptime: 0 days 3:00:02.338
BugCheck D1, {10, 2, 1, 8905d23a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 13:39:54.312 2010 (UTC - 4:00)
System Uptime: 0 days 1:17:04.216
BugCheck D1, {10, 2, 1, 8907d23a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May  9 16:42:20.345 2010 (UTC - 4:00)
System Uptime: 0 days 1:46:54.420
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Apr 25 16:31:13.558 2010 (UTC - 4:00)
System Uptime: 0 days 7:19:30.634
BugCheck D1, {6, 2, 0, 890a18cb}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!IppChecksumDatagram+be )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Wed Apr  7 17:40:07.020 2010 (UTC - 4:00)
System Uptime: 0 days 1:43:30.095
BugCheck D1, {10, 2, 1, 8906823a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sun Mar 28 01:02:09.284 2010 (UTC - 4:00)
System Uptime: 0 days 11:05:35.360
BugCheck D1, {10, 2, 1, 8907b23a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sun Feb 28 01:33:46.391 2010 (UTC - 4:00)
System Uptime: 0 days 13:39:57.466
BugCheck D1, {10, 2, 1, 88e8f23a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sat Feb 13 17:19:14.567 2010 (UTC - 4:00)
System Uptime: 0 days 5:29:51.642
BugCheck D1, {10, 2, 1, 88e6523a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Wed Feb 10 18:04:56.929 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:15.880
BugCheck D1, {10, 2, 1, 88e9923a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Wed Feb 10 18:02:08.600 2010 (UTC - 4:00)
System Uptime: 0 days 1:23:54.675
BugCheck D1, {10, 2, 1, 88e8c23a}
*** WARNING: Unable to verify timestamp for vpcnfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for vpcnfltr.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

See less See more

Save

1 - 2 of 2 Posts

Status: Not open for further replies.

BSOD Windows 7

Unknowndady

Attachments

usasma

Top Contributors this Month