bluescreen Probably caused by : NETIO.SYS

[kladob]

Witam.

Po raz drugi mam problem z niebieskim ekranem. Nie wiem czy to ten sam problem co ostatnio. Bardzo proszę o pomoc w analizie problemu Bluescreen. Będę bardzo wdzięczny za pomoc. Zamieszczam poniżej odczytany zrzut pliku DMP:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\J&K\Desktop\090814-34866-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'C:\Users\J&K\Desktop\Nowy folder'
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/;C:\Users\J&K\Desktop\Nowy folder
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`03094890
Debug session time: Mon Sep 8 20:06:02.018 2014 (UTC + 2:00)
System Uptime: 5 days 1:11:07.909
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff880011a86fd}

Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
Probably caused by : NETIO.SYS ( NETIO+106fd )

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100
0000000000000028

CURRENT_IRQL: 2

FAULTING_IP:
NETIO+106fd
fffff880`011a86fd 448b5228 mov r10d,dword ptr [rdx+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88003776790 -- (.trap 0xfffff88003776790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880037769b0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011a86fd rsp=fffff88003776920 rbp=fffff88003776a48
r8=00000000ffffffbc r9=0000000000000044 r10=0000000000000000
r11=fffffa8007c0cc20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
NETIO+0x106fd:
fffff880`011a86fd 448b5228 mov r10d,dword ptr [rdx+28h] ds:d0da:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ec6169 to fffff80002ec6bc0

STACK_TEXT:
fffff880`03776648 fffff800`02ec6169 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03776650 fffff800`02ec4de0 : fffffa80`0dbd6690 00000000`00000006 fffffa80`0dbd6690 00000000`00000044 : nt!KiBugCheckDispatch+0x69
fffff880`03776790 fffff880`011a86fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03776920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO+0x106fd


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO+106fd
fffff880`011a86fd 448b5228 mov r10d,dword ptr [rdx+28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: NETIO+106fd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 5294760d

FAILURE_BUCKET_ID: X64_0xD1_NETIO+106fd

BUCKET_ID: X64_0xD1_NETIO+106fd

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

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

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


READ_ADDRESS: 0000000000000028

CURRENT_IRQL: 2

FAULTING_IP:
NETIO+106fd
fffff880`011a86fd 448b5228 mov r10d,dword ptr [rdx+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88003776790 -- (.trap 0xfffff88003776790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880037769b0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011a86fd rsp=fffff88003776920 rbp=fffff88003776a48
r8=00000000ffffffbc r9=0000000000000044 r10=0000000000000000
r11=fffffa8007c0cc20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
NETIO+0x106fd:
fffff880`011a86fd 448b5228 mov r10d,dword ptr [rdx+28h] ds:d0da:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ec6169 to fffff80002ec6bc0

STACK_TEXT:
fffff880`03776648 fffff800`02ec6169 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03776650 fffff800`02ec4de0 : fffffa80`0dbd6690 00000000`00000006 fffffa80`0dbd6690 00000000`00000044 : nt!KiBugCheckDispatch+0x69
fffff880`03776790 fffff880`011a86fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03776920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO+0x106fd


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO+106fd
fffff880`011a86fd 448b5228 mov r10d,dword ptr [rdx+28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: NETIO+106fd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 5294760d

FAILURE_BUCKET_ID: X64_0xD1_NETIO+106fd

BUCKET_ID: X64_0xD1_NETIO+106fd

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

[djkamil09061991]

Przeinstaluj na początek sterownik do sieci.

[robiwielki]

Jak by dalej wystąpił problem to sprawdź:
- sprawdzenie pamięć
Plik do pobrania:
Dostępne tylko dla zarejestrowanych użytkowników
http://www.hotfix.pl/instrukcja-obslugi-programu-memtest86+-sprawdzanie-pamieci-ram-a204.htm
- wykonaj chkdsf /F /R

Ale myślę za to tak piszę djkamil09061991, ze to karta sieciowa.