BSOD's, new build, need help!

well, just got off work and after many restarts, I was able to boot up in safe mode with networking. I just enabled the verifier and I will try running it after this post. Here are the crash dumps from today's mess. I was unable to run the performance monitor and save a report. I'm going to clear all dump files and go ahead and restart to run the verifier. Hopefully my computer will reboot, not holding my breathe

Wow, computer actually re-booted. Here are dump logs post-verifier. Hope these shed some light on the issues I am having. Cheers!

I've been away for a few days but I updated USB drivers and ran the verifier. I am still getting BSOD's. It has been happening when I run a game updater. The downloader will start downloading game files, and bam, BSOD. I have the latest versions of everything for my system installed. Here's the reports.

I just googled my error e1q62x64.sys and found this. And it seems i have the same error than you SDQuattroDriver!
I have already spoken with Alternate and Asus. Asus support suggested to send the mainboard back to Alternate and they were getting the error too even with other hardware. So they send the mainboard to Asus and now i am waiting for an answer of Asus. Alternate sent me a new one, but i have still the same problem.
Yesterday i wrote an email to pcgameshardware and now i am waiting for an answer from them.
Maybe they have a solution for our problem!

Keep me informed, I'd really like to get this annoyance fixed. I can't even use my computer. Keep up the good work Ansker!

SDQuattroDriver said:

I've been away for a few days but I updated USB drivers and ran the verifier. I am still getting BSOD's. It has been happening when I run a game updater. The downloader will start downloading game files, and bam, BSOD. I have the latest versions of everything for my system installed. Here's the reports.

Three of these point to netio.sys/tcpip.sys which usually results from zone alarm. Do you by chance have it installed? If so you should remove it and replace it with Microsoft Security Essentials and the win 7 firewall

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\101610-12012-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (5 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`03094e50
Debug session time: Sat Oct 16 03:43:09.423 2010 (GMT-4)
System Uptime: 0 days 0:00:52.750
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff880016897a0}

*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+f3 )

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

0: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016897a0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff0e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip+897a0
fffff880`016897a0 488b01          mov     rax,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880089108c0 -- (.trap 0xfffff880089108c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80092962e0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8006938000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016897a0 rsp=fffff88008910a50 rbp=0000000000000000
 r8=0000000000006888  r9=00000000000000d0 r10=fffff80002e57000
r11=000000000000029d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
tcpip+0x897a0:
fffff880`016897a0 488b01          mov     rax,qword ptr [rcx] ds:07ff:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec6ca9 to fffff80002ec7740

STACK_TEXT:  
fffff880`08910778 fffff800`02ec6ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`08910780 fffff800`02ec5920 : 00000000`00000009 fffffa80`07f108e0 fffffa80`078b5860 fffffa80`091a6cf0 : nt!KiBugCheckDispatch+0x69
fffff880`089108c0 fffff880`016897a0 : fffffa80`07f09350 00000000`00000001 00000000`206c644d fffffa80`078b5860 : nt!KiPageFault+0x260
fffff880`08910a50 fffff880`01402173 : 00000000`00000000 00000000`00000005 00000000`00000005 00000000`00000000 : tcpip+0x897a0
fffff880`08910aa0 fffff880`0167387f : fffffa80`07f09350 00000000`00000001 00000000`00000000 fffffa80`07f2cf50 : NETIO!NetioDereferenceNetBufferListChain+0xf3
fffff880`08910b20 fffff880`0167b44c : fffffa80`07eaa000 00000000`00000000 00000000`00000000 fffff880`0165e600 : tcpip+0x7387f
fffff880`08910c00 fffff880`0165d6c7 : fffffa80`079f5000 fffffa80`078c46c0 fffffa80`07a05000 00000000`00000004 : tcpip+0x7b44c
fffff880`08910cb0 fffff880`0165d799 : fffff880`08910e30 fffff880`0176b9a0 fffff880`08910e40 fffff880`0176b9a0 : tcpip+0x5d6c7
fffff880`08910d70 fffff880`0165dc90 : fffffa80`07f09350 00000000`00000000 00000000`00000011 fffff880`08910e30 : tcpip+0x5d799
fffff880`08910de0 fffff880`0165cb21 : 00000000`00000000 fffffa80`079f1750 fffff880`0176b9a0 00000000`00610001 : tcpip+0x5dc90
fffff880`08910ec0 fffff880`0167d39c : fffffa80`07f4a660 00000000`00000000 0064006e`00610001 00690072`00000007 : tcpip+0x5cb21
fffff880`089110c0 fffff880`01674e22 : fffffa80`07f48010 fffffa80`07f48010 00490050`00410002 006c006c`00640000 : tcpip+0x7d39c
fffff880`08911220 fffff800`02ed6e5a : 00000000`00000000 fffff880`0890c000 00000000`00004800 00000000`00000000 : tcpip+0x74e22
fffff880`08911270 fffff880`01674882 : fffff880`01674d80 fffff880`08911380 0020006b`00630002 006e0061`00720074 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`08911350 fffff880`0159c0eb : fffffa80`07f49010 00000000`00000000 fffffa80`07d561a0 00000007`01bd01bd : tcpip+0x74882
fffff880`089113c0 fffff880`01565fc6 : 00000010`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`08911430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!NetioDereferenceNetBufferListChain+f3
fffff880`01402173 4c8b742440      mov     r14,qword ptr [rsp+40h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NETIO!NetioDereferenceNetBufferListChain+f3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0xD1_NETIO!NetioDereferenceNetBufferListChain+f3

BUCKET_ID:  X64_0xD1_NETIO!NetioDereferenceNetBufferListChain+f3

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

Nope, I don't have zone alarm. I am using Webroot antivirus, and I was having the problem before installing Webroot.

Hello... I'm having the exact same problem as SDQuattroDriver.

Attached are some minidumps which can be crossed referenced with SDQuattroDriver. I believe we have the exact same Mainboard and Processor.

Here are the things I have done so far:
-Clean install of Windows 7 x64 Ultimate
-Updated Windows.
-Updated System Drivers from Asus 3.00.0765 and direct web sites of the manufactures (e.g. AMD/ATI 3.00.0790 chipset). Also checked for firmware updates and found none (already up2date).
-No NB standoff/temperature issues. NB steady at about 45-48C @ 26.3C ambient. CPU, MB, etc temperatures are all within tolerance as well.
-Ran prime95 for 20+ hours successfully; no errors.
-Used Intel Drivers 15.3.68.0 + 15.5.74.0 same results. Used Asus supplied driver first and then Intel's web site driver.
-Tried enabling and disabling page file and same BSoD occurs after rebooting. (STOP code refers to this as a possible problem). Also replaced SATA6 (supplied) cable with another same result.
-Was able to reproduce the BSoD everytime by transfering large network files from this computer to another and accessing/browsing another network folder at the same time. With nothing else running; except TSR Bluetooth, and Asus Ai Suite. It doesn't however seem to crash when transfering a large network file and doing nothing else.
-Tried auto/manual DRAM voltage settings from 1.5 to 1.6 same result.
-Tried auto/manual DRAM timmings as stated CL9-9-9-24 same result.
-Tried auto/manual DRAM Freq 800Mhz (DDR1600) same result.
-Currently running mem86+ v4.10; 1 pass so far no errors.
-Have done SFV /scannow and found no problems.
-I was successfully able to install another 1GB NIC in a PCI slot. Repeated the steps from eariler and no BSoD. Also watched a couple 1080p youtube videos like someone mentioned in another forum without any problems.
-NOTE: Almost everytime the computer BSOD's I run a quick chkdsk on the system drive to make sure everything is okay.

I hope some of this information can be useful. Thanks!

It seems that we are not alone with this bsod! In the Asustek forum is another post with some people describing exactly the Same error! Just go there and go to the Asus CIVE section in the forum.