Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD Daily - One from tcpip.sys


  • Please log in to reply

#1
pa.kevin1

pa.kevin1

    New Member

  • Member
  • Pip
  • 2 posts
I get a bsod everyday about 10 minutes after I boot. Usually theres no file stated, and one time I think it was from avg. Heres my Blue Screen View :

==================================================
Dump File : Mini070110-02.dmp
Crash Time : 7/1/2010 9:05:41 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x00000008
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xb6befc6f
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+10c6f
File Description : TCP/IP Protocol Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5625 (xpsp_sp3_gdr.080620-1249)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini070110-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini070110-01.dmp
Crash Time : 7/1/2010 12:10:20 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x804e8481
Parameter 3 : 0xf78eec20
Parameter 4 : 0xf78ee91c
Caused By Driver : hal.dll
Caused By Address : hal.dll+2410
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini070110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini063010-01.dmp
Crash Time : 6/30/2010 11:46:36 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 0x0000000d
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+6156
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini063010-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================
  • 0

Advertisements


#2
Bing7

Bing7

    Member

  • Member
  • PipPip
  • 65 posts
  • MVP
the first one can be cause by bad ram. this is copied from another site.
"0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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."


2nd one
"0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information."


3rd one
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

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.

\\\\\\\\\\\\\\

so for me i would start with checking ram ,i use memtest86 to do so ,it could be bad ram or even good ram just mismatched chips if you have more than one chip on the motherboard.
also be sure to check this ot for more info on errors .
Check Event Viewer (EventVwr.msc) for additional information."


site i got dump info from .
http://aumha.org/a/stop.htm
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP