BSOD randomly (1st time)

Welcome

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

From the dump file it looks as if it's a network crash.
You should update this driver from here: Driver Reference Table

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002e92e9f}

*** WARNING: Unable to verify timestamp for pneteth.sys
*** ERROR: Module load completed but symbols could not be loaded for pneteth.sys
Probably caused by : pneteth.sys ( pneteth+19a4 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e92e9f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cd100
GetUlongFromAddress: unable to read from fffff800030cd1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExInterlockedInsertTailList+2f
fffff800`02e92e9f 48890a          mov     qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff880096e3e10 -- (.trap 0xfffff880096e3e10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80093d09f0 rbx=0000000000000000 rcx=fffff88005dfb260
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e92e9f rsp=fffff880096e3fa0 rbp=0000000000000000
 r8=fffff88005dfb228  r9=000000000000000a r10=0000000000000000
r11=fffff880096e4110 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
nt!ExInterlockedInsertTailList+0x2f:
fffff800`02e92e9f 48890a          mov     qword ptr [rdx],rcx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e9a1e9 to fffff80002e9ac40

STACK_TEXT:  
fffff880`096e3cc8 fffff800`02e9a1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`096e3cd0 fffff800`02e98e60 : fffffa80`05a0e830 fffff880`019483c0 fffff880`009b3180 fffff880`05dfb260 : nt!KiBugCheckDispatch+0x69
fffff880`096e3e10 fffff800`02e92e9f : 00000000`00000282 fffff880`05df89a4 fffffa80`05a0e960 fffff880`096e40e0 : nt!KiPageFault+0x260
fffff880`096e3fa0 fffff880`05df89a4 : fffffa80`05a0e960 fffff880`096e40e0 fffff880`096e4110 00000000`00000000 : nt!ExInterlockedInsertTailList+0x2f
fffff880`096e3fb0 fffffa80`05a0e960 : fffff880`096e40e0 fffff880`096e4110 00000000`00000000 00000000`00000000 : pneteth+0x19a4
fffff880`096e3fb8 fffff880`096e40e0 : fffff880`096e4110 00000000`00000000 00000000`00000000 fffffa80`05a0e830 : 0xfffffa80`05a0e960
fffff880`096e3fc0 fffff880`096e4110 : 00000000`00000000 00000000`00000000 fffffa80`05a0e830 fffff880`016ab110 : 0xfffff880`096e40e0
fffff880`096e3fc8 00000000`00000000 : 00000000`00000000 fffffa80`05a0e830 fffff880`016ab110 fffff880`096e4110 : 0xfffff880`096e4110


STACK_COMMAND:  kb

FOLLOWUP_IP: 
pneteth+19a4
fffff880`05df89a4 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  pneteth+19a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: pneteth

IMAGE_NAME:  pneteth.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c801bf9

FAILURE_BUCKET_ID:  X64_0xA_pneteth+19a4

BUCKET_ID:  X64_0xA_pneteth+19a4

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

2: kd> lmvm pneteth
start             end                 module name
fffff880`05df7000 fffff880`05e00000   pneteth  T (no symbols)           
    Loaded symbol image file: pneteth.sys
    Image path: \SystemRoot\system32\DRIVERS\pneteth.sys
    Image name: pneteth.sys
    Timestamp:        Fri Sep 03 03:49:45 2010 (4C801BF9)
    CheckSum:         00008093
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
---
fffff880`096e4a78  fffff880`0194145e tcpip!IpNlpFastSendDatagram+0xd5e
fffff880`096e4a80  fffffa80`093c7ab0
fffff880`096e4a88  fffffa80`0a747190
fffff880`096e4a90  fffff880`01a599a0 tcpip!Ipv4Global
fffff880`096e4a98  fffff880`0193b447 tcpip!IppDispatchSendPacketHelper+0x87
fffff880`096e4aa0  fffff880`01a599a0 tcpip!Ipv4Global
fffff880`096e4ae8  fffff880`01745028 NETIO!FilterMatchEnum+0x199
fffff880`096e4af0  00000000`00000000
fffff880`096e4af8  00000000`00000000
fffff880`096e4b00  fffffa80`05a00002
fffff880`096e4b08  fffff880`0194145e tcpip!IpNlpFastSendDatagram+0xd5e
fffff880`096e4b10  fffff880`01a599a0 tcpip!Ipv4Global
fffff880`096e4ba8  fffff880`01943bb0 tcpip!TcpBeginTcbSend+0x670

Await the Nfo file.

Thanks. Go to this link: Intel® Driver Update Utility and check the system for latest updates. Download and install all it finds.

Run the System File Checker. It allows the user to scan for and restore corruptions in Windows system files.

• 1. Click on the
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Free up the start-up, nothing except the antivirus is usually needed.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Good luck :)

Hi - Happy new year :)

   Tip

• If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner