Hello boafx and welcome to Seven Forums. I will help you if I can. If at any time you don't understand instructions or have questions, please ask. I don't mind a bit. The first thing I need is a detailed system specs listed in the bottom left corner where it says 'My System Specs'. I need Manufacturer and model # for each component. I have to look up components sometimes, and need the information to do that. I just had to look up your Motherboard. Also by putting them there, they are in every post for anyone who tries to help and we don't have to ask or go hunt for them. I also need to know things like your PSU, your CPU cooler and your Case. You have CPU unknown. If you built the computer, you have to know which CPU you put in, you have no information on the Ram and you don't list the manufacturer of your graphics card and the model. those are all important. These are the instructions I usually give.
Please fill out your System Specs
Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task.
System Info - See Your System Specs
You only have 2 dump files, which are created by a BSOD and what we use to find out your problem. Both give the same error code and list the same cause tcpip which is a network related issue and the driver is usually supplied by Windows Update. here is the readout.
Code:
tcpip
start end module name
fffff880`016ad000 fffff880`018b1000 tcpip (pdb symbols) c:\symcache\tcpip.pdb\ABB23D00EE7E4165B6AFF66F2DF02EB22\tcpip.pdb
Loaded symbol image file: tcpip.sys
Mapped memory image file: c:\symcache\tcpip.sys\4CE79420204000\tcpip.sys
Image path: \SystemRoot\System32\drivers\tcpip.sys
Image name: tcpip.sys
Timestamp: Sat Nov 20 03:25:52 2010 (4CE79420)
CheckSum: 001E58E5
ImageSize: 00204000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: tcpip.sys
OriginalFilename: tcpip.sys
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription: TCP/IP Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
That is the cause listed by both dump files.
What I would like you to do is make sure all of your important and recommended windows updates are run and installed. I would like the settings to say automatically install updates. From the windows update page in the left column is a 'change settings' link. Set it to Automatically install updates.
Next I would like you to go to your Motherboard's web site (
Motherboards - M4A88TD-V EVO/USB3 - ASUS) and install the RealteK Lan driver as well as the Chipset driver. make sure that is your motherboard.
Next, I would like you to open a elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow then press enter. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
After that please let us know the results and if your problem has improved any.