BSOD caused by tcpip.sys
Posted 19 April 2013 - 03:43 PM
Posted 25 April 2013 - 10:07 AM
I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
- Please understand we are all volunteers and we are not here all the time.
- Sometimes it may be a extended amount of time to get back to you. If it has been
more then 3 days please shoot me a PM and I will try to get back to you quickly
- Please do the following and supply the requested information as needed. If you
don't understand my instructions please ask and I will try to explain them
clearer for you.
- Do not attempt any steps unless instructed or ask before to
make sure they will not cause any further issues.
- If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.
Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?
- If a name brand system then what brand, make and model is the system?
- If custom built then what brand, make and model is the motherboard
- Total memory installed
- Total hard drive capacity and free space
- What steps have you taken so far to resolve the issue
Before I begin I would like to have the following. Your zip file may contain the info but as a rule I never open a zip file unless I specifically asked for it.
Please follow the steps below to enter the Event Viewer program in Vista\Win7. This will give me more information into what is causing your issue. You can get to Event viewer two ways and I will post both for you.
" Go to
" In the Search box type in Event Viewer in the search box and press Enter
" From this point you can follow from step four from the below method as they will be the same.
" Go to Start
" Right click on the Computer Icon and select Manage
" Navigate to the Event Viewer, You will be prompted to accept the action you are going to perform. Click continue
" On the left window pane click on Local and then expand the Windows entry. This will allow you to see every error for the past 24 hours as well as the last 7 days in the right window pane.
" Look for the ones that correspond to the times that your issue occurred.
" If any are found please double click and expand the error. This will open and give you more information on the error.
" Please include that in your next reply.
Posted 25 April 2013 - 07:53 PM
computer name: ADAM-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core i3-2120 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8571392000 total
VM: 2147352576, free: 1931264000
steps taken updated my drivers using slim driver
with the log even viewer i don't know how to use this and what i am looking for it there something else i can use i have win 7
Posted 26 April 2013 - 06:30 AM
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
Posted 26 April 2013 - 06:34 AM
One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.
First common issue seen is a memory issue so I will start there.
A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:
8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:
10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.
To change Boot Sequence in your BIOS
Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.
The running program will look something like this depending on the size and number of ram modules installed:
It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.
The following image is the test results area:
The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
Posted 28 April 2013 - 07:42 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users