BSOD two recent crashes tcpip.sys and e1q62x64

Welcome to SF, EicEDoNUT,

Please do the following:

BSOD Posting Instructions
https://www.sevenforums.com/crashes-d...tructions.html

In addition, please complete your System Specs:

HOW TO FILL OUT YOUR SYSTEM SPECS

In the line at the top of www.SevenForums.com you will see UserCP.
That is an abbreviation for User Control Panel.
Click on UserCP.
In the left-hand column, under Your Profile you will see Edit System Spec.
Click on Edit System Spec
You can copy and paste from the output of Speccy, Speccy - System Information - Free Download to fill out much of the info. Be sure to use the Other Info section of your System Specs for such info as your optical drive, your wireless adapter, your speakers, etc.

Hi and welcome to the forum. I looked at your last three dumps all have the same error code are essentially the same.

To begin your troubleshooting, I suggest your uninstall Norton using this removal tool: Tool. Norton is known to cause BSOD's on some Win 7 system and one of your dumps shows Norton was involved in the crash. Download and install Microsoft Security Essential and make sure Windows Firewall is turned on.

Error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. Usual causes: Device driver.

Code:

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e59e50
Debug session time: Mon Nov  1 14:11:22.164 2010 (GMT-4)
System Uptime: 0 days 0:12:40.068
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {68, 2, 1, fffff88004418e60}

Unable to load image \SystemRoot\system32\DRIVERS\e1q62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1q62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1q62x64.sys
Probably caused by : e1q62x64.sys ( e1q62x64+18e60 )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004418e60, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec40e0
 0000000000000068 

CURRENT_IRQL:  2

FAULTING_IP: 
e1q62x64+18e60
fffff880`04418e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800b6b67e0 -- (.trap 0xfffff8800b6b67e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80070dc4c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004418e60 rsp=fffff8800b6b6970 rbp=0000000000000040
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
e1q62x64+0x18e60:
fffff880`04418e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8bca9 to fffff80002c8c740

STACK_TEXT:  
fffff880`0b6b6698 fffff800`02c8bca9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b6b66a0 fffff800`02c8a920 : fffffa80`09f62010 00000000`00000000 00000000`00000001 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`0b6b67e0 fffff880`04418e60 : fffffa80`08c1ab40 fffffa80`09ec6d88 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0b6b6970 fffffa80`08c1ab40 : fffffa80`09ec6d88 00000000`00000000 00000000`00000000 00000000`00000000 : e1q62x64+0x18e60
fffff880`0b6b6978 fffffa80`09ec6d88 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`04421305 : 0xfffffa80`08c1ab40
fffff880`0b6b6980 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`04421305 fffffa80`00000000 : 0xfffffa80`09ec6d88


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1q62x64+18e60
fffff880`04418e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1q62x64+18e60

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME:  e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4af31807

FAILURE_BUCKET_ID:  X64_0xD1_e1q62x64+18e60

BUCKET_ID:  X64_0xD1_e1q62x64+18e60

Followup: MachineOwner
---------

All three dumps blame e1q62x64.sys, which is part of your Intel based Ethernet Adapter. The dumps also show that Norton was involved in the crash.

I also find the following out of date drivers on your system.. Older drivers can and do cause memory corruption and BSOD's. Update these drivers, especially the 2008 driver.

000.fcl Fri Sep 26 09:11:22 2008 - CyberLink FCL Driverhttp://www.gocyberlink.com

AsIO.sys Mon Apr 06 03:21:08 2009 - Asus PCProbe Utility ASUSTeK Computer Inc.-Support-

Tosrfhid.sys Tue May 19 21:23:51 2009 - Toshiba Bluetooth HID DriverToshiba Support - Homepage

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: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Uninstall Norton, update these drivers and reboot. Let's see how your system does. If you get another BSOD, upload it and we will go from there.

Good job. Let us know how your system does.

You have not changed any hardware and have update Cyberlink. Just zip and upload the dumps for now.