Windows 7 Forums
Join Forum | Login | Today's Posts | Tutorials | Vista Forum | Windows 8 Forum


Windows 7: BSOD tcip.sys , 0x0000000D1 Freshly installed win7 x64

10 Jun 2012   #1

Windows 7 Ultimate x64 Full Retail
9 posts
Stockholm
 
 
BSOD tcip.sys , 0x0000000D1 Freshly installed win7 x64
Hello, i'm having 10 min intervall BDOS's after reinstalling my Windows 7 Ultimate, retailer bought

My hardware is about a year old, the OS installation just under 1-2 hours old.

Hopefully someone will have the time knowledge required to help me sort this out, meanwhile i'll try windows updates and high hopes for a response



Perfmon and jcgriff2 are in the same archive, attached to this post
My System SpecsSystem Spec

10 Jun 2012   #2

Windows 7 Ultimate x64 Full Retail
9 posts
Stockholm
 
 
0x0000000D1 is the stop line code, to clairfy. but that surely shows in the dump-files as well
My System SpecsSystem Spec
10 Jun 2012   #3

Windows 7 Home Premium 64 Bit
11,308 posts
Colorado
 
 
Problem Devices:
Code:
eLicenser	USB\VID_0819&PID_0101\5&3AFD18BD&0&2	The drivers for this device are not installed.
Universal Serial Bus (USB) Controller	PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_03\FFFFFFFFFFFFFFFF00	The drivers for this device are not installed.
Make sure the above drivers are installed. ASUS - Motherboards- ASUS Crosshair IV Extreme is a good place to start.


Security Software: ??? Make sure to install security software. I recommend either of these:
After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.


Code:
--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\SouthPaw\061112-32089-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64

System Uptime: 0 days 0:20:40.075

BugCheck D1, {9, 2, 0, fffff880016ec80f}

*** 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+239e9 )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  TERA-Launcher.

STACK_TEXT:  
fffff880`030b6908 fffff800`02ed1be9 : 00000000`0000000a 00000000`00000009 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff880`030b6908 fffff800`02ed1be9 : 00000000`0000000a 00000000`00000009 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`030b6910 fffff800`02ed0860 : 00000000`00000006 fffffa80`07935f00 fffffa80`07ce1ea8 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffff880`030b6910 fffff800`02ed0860 : 00000000`00000006 fffffa80`07935f00 fffffa80`07ce1ea8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030b6a50 fffff880`016ec80f : fffffa80`0792f910 00000000`00005000 fffffa80`000072c4 00000000`000072c4 : nt!KiPageFault+0x260
fffff880`030b6be0 fffff880`016fba52 : fffffa80`06e70010 fffffa80`06e70010 fffffa80`06e70002 fffff880`030b0000 : tcpip!IpFlcReceivePreValidatedPackets+0xcf
fffff880`030b6d40 fffff800`02edf078 : 00000000`00000000 00000000`00004800 fffffa80`07c55060 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2
fffff880`030b6d90 fffff880`016fc152 : fffff880`016fb9b0 00000000`00000000 fffffa80`08987002 fffffa80`0881a000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`030b6e70 fffff880`015660eb : fffffa80`08aed8d0 00000000`00000000 fffffa80`07c691a0 fffffa80`0792f910 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`030b6ee0 fffff880`0152fad6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`030b6f50 fffff880`014a8cc1 : fffffa80`07c691a0 00000000`00000002 00000000`00000001 fffff880`0156621d : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`030b73d0 fffff880`02c239e9 : fffffa80`07c7b000 fffffa80`0a28d2c0 fffffa80`089bb450 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`030b7420 fffffa80`07c7b000 : fffffa80`0a28d2c0 fffffa80`089bb450 00000000`00000001 00000000`00000801 : e1q62x64+0x239e9
fffff880`030b7428 fffffa80`0a28d2c0 : fffffa80`089bb450 00000000`00000001 00000000`00000801 00000000`00000001 : 0xfffffa80`07c7b000
fffff880`030b7430 fffffa80`089bb450 : 00000000`00000001 00000000`00000801 00000000`00000001 fffffa80`07c7db00 : 0xfffffa80`0a28d2c0
fffff880`030b7438 00000000`00000001 : 00000000`00000801 00000000`00000001 fffffa80`07c7db00 fffff880`02c23b84 : 0xfffffa80`089bb450
fffff880`030b7440 00000000`00000801 : 00000000`00000001 fffffa80`07c7db00 fffff880`02c23b84 00000000`00000001 : 0x1
fffff880`030b7448 00000000`00000001 : fffffa80`07c7db00 fffff880`02c23b84 00000000`00000001 fffffa80`0a28d2c0 : 0x801
fffff880`030b7450 fffffa80`07c7db00 : fffff880`02c23b84 00000000`00000001 fffffa80`0a28d2c0 fffffa80`0a28d2c0 : 0x1
fffff880`030b7458 fffff880`02c23b84 : 00000000`00000001 fffffa80`0a28d2c0 fffffa80`0a28d2c0 00000000`00000001 : 0xfffffa80`07c7db00
fffff880`030b7460 00000000`00000001 : fffffa80`0a28d2c0 fffffa80`0a28d2c0 00000000`00000001 0000000a`00000001 : e1q62x64+0x23b84
fffff880`030b7468 fffffa80`0a28d2c0 : fffffa80`0a28d2c0 00000000`00000001 0000000a`00000001 00000000`00000000 : 0x1
fffff880`030b7470 fffffa80`0a28d2c0 : 00000000`00000001 0000000a`00000001 00000000`00000000 fffff880`02c166d0 : 0xfffffa80`0a28d2c0
fffff880`030b7478 00000000`00000001 : 0000000a`00000001 00000000`00000000 fffff880`02c166d0 fffff880`030b76d8 : 0xfffffa80`0a28d2c0
fffff880`030b7480 0000000a`00000001 : 00000000`00000000 fffff880`02c166d0 fffff880`030b76d8 00000000`00000000 : 0x1
fffff880`030b7488 00000000`00000000 : fffff880`02c166d0 fffff880`030b76d8 00000000`00000000 fffffa80`09b820d0 : 0xa`00000001


FAILURE_BUCKET_ID:  X64_0xD1_e1q62x64+239e9

--------------------------------------------
---------------------END--------------------
--------------------------------------------
The above is the analysis of your .dmp file. It points to e1q62x64.sys, your Intel Ethernet driver as the cause of the crashes. Update the driver from your motherboard support site: ASUS - Motherboards- ASUS Crosshair IV Extreme



To fully re-install a driver, use the following steps. You will find the Ethernet driver under Network adapters in Device Manager.
  1. First, download the latest driver. Then do the next steps.
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Find the device you are trying to uninstall by expanding the appropriate set of devices
  7. Right click the device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer only if Windows asks you to.
  11. Install the latest driver for the device.

Alternatively:
  1. Login as an adminstrative user.
  2. First, download the latest driver. Then do the next steps.
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Find the device you are trying to uninstall by expanding the appropriate set of devices
  8. Right click the device
  9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  11. Restart your computer only if Windows asks you to.
  12. Install the latest driver for the device.
My System SpecsSystem Spec
.


11 Jun 2012   #4

Windows 7 Ultimate x64 Full Retail
9 posts
Stockholm
 
 
did windows updates, downloaded the ethernet driver from Intel directly, and reinstalled it, my computer has been running all night while i was sleeping without any incident.

i will follow your list of advice and report back if i should have more bsod's
My System SpecsSystem Spec
11 Jun 2012   #5

Windows 7 Home Premium 64 Bit
11,308 posts
Colorado
 
 
Sounds good. Also let us know when you are confident the problem is solved. You may also mark the thread solved when you are sure.
My System SpecsSystem Spec
Reply

 BSOD tcip.sys , 0x0000000D1 Freshly installed win7 x64 problems?



« BSOD when S3/reboot resume, DRIVER_POWER_STATE_FAILURE error 0x9f | BSOD while downloading game »
Thread Tools



Similar help and support threads for: BSOD tcip.sys , 0x0000000D1 Freshly installed win7 x64
Thread Forum
Freshly installed OS win7 64bit taking 30 seconds at Welcome screen General Discussion
BSOD on freshly installed Windows 7 BSOD Help and Support
frequent bsod crushes on freshly installed PC BSOD Help and Support
BSOD on freshly installed Windows, error 0x0000007a BSOD Help and Support
BSOD freshly installed system BSOD Help and Support


All times are GMT -5. The time now is 08:58 PM.

Contact Us - Windows 8 Support - Windows Vista Support - Legal - Privacy and cookies - Top

Seven Forums Android App Seven Forums IOS App Follow us on Facebook

Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32