Bluecreen 1031

[wegberger94]

Hallo zusammen,

ich habe seitdem ich meinen Rechner zuhause abgebaut, und bei nem Kumpel wieder aufgebaut habe Bluescreens, wenn ich mehrere Programme gleichzeitig starte, was bei meinem Rechner eigentlich kein Problem sein dürfte.
Ich habe eine XFX 6870 Black Edition, AMD Phenom X2 1090T, 750 Watt Netzteil von GX, Prozessorüfter von Thermaltake, Asus Crosshair 4 Extreme, AM3, ATX.
Habe mir schon vieles über den Fehler durchgelesen, und habe mir mit dem Windows Debugging Tool die Fehlermeldung geben lassen.
Ich hoffe ihr könnt damit etwas anfangen.


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


Loading Dump File [C:\Windows\Minidump\101511-20248-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50
Debug session time: Sat Oct 15 21:36:12.821 2011 (UTC + 2:00)
System Uptime: 0 days 0:03:41.772
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80002c0976c}

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+18dd7 )

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

4: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
4: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002c0976c, address which referenced memory

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

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef60e0
0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalPutScatterGatherList+1c
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8800c79e740 -- (.trap 0xfffff8800c79e740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002c2ce00 rbx=0000000000000000 rcx=fffffa80084f0040
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c0976c rsp=fffff8800c79e8d0 rbp=00000000000000c6
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=00000000000001ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!HalPutScatterGatherList+0x1c:
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8] ds:eca8:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cbf469 to fffff80002cbff00

STACK_TEXT:
fffff880`0c79e5f8 fffff800`02cbf469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c79e600 fffff800`02cbe0e0 : 00000000`00000000 fffffa80`072eda60 fffffa80`07a20080 fffffa80`07a20700 : nt!KiBugCheckDispatch+0x69
fffff880`0c79e740 fffff800`02c0976c : fffffa80`082b0820 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x260
fffff880`0c79e8d0 fffff880`0144b8a1 : fffffa80`072eda60 00000000`000000c6 fffffa80`08585c58 fffffa80`08590000 : hal!HalPutScatterGatherList+0x1c
fffff880`0c79e930 fffff880`07acbdd7 : fffffa80`082b0820 fffffa80`08585c58 00000000`00000000 00000000`00000000 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`0c79e970 fffffa80`082b0820 : fffffa80`08585c58 00000000`00000000 00000000`00000000 00000000`00000000 : e1q62x64+0x18dd7
fffff880`0c79e978 fffffa80`08585c58 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07ad4305 : 0xfffffa80`082b0820
fffff880`0c79e980 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`07ad4305 fffffa80`00000000 : 0xfffffa80`08585c58


STACK_COMMAND: kb

FOLLOWUP_IP:
e1q62x64+18dd7
fffff880`07acbdd7 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: e1q62x64+18dd7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME: e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4af31807

FAILURE_BUCKET_ID: X64_0xA_e1q62x64+18dd7

BUCKET_ID: X64_0xA_e1q62x64+18dd7

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

4: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002c0976c, address which referenced memory

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


READ_ADDRESS: 0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalPutScatterGatherList+1c
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8800c79e740 -- (.trap 0xfffff8800c79e740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002c2ce00 rbx=0000000000000000 rcx=fffffa80084f0040
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c0976c rsp=fffff8800c79e8d0 rbp=00000000000000c6
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=00000000000001ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!HalPutScatterGatherList+0x1c:
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8] ds:eca8:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cbf469 to fffff80002cbff00

STACK_TEXT:
fffff880`0c79e5f8 fffff800`02cbf469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c79e600 fffff800`02cbe0e0 : 00000000`00000000 fffffa80`072eda60 fffffa80`07a20080 fffffa80`07a20700 : nt!KiBugCheckDispatch+0x69
fffff880`0c79e740 fffff800`02c0976c : fffffa80`082b0820 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x260
fffff880`0c79e8d0 fffff880`0144b8a1 : fffffa80`072eda60 00000000`000000c6 fffffa80`08585c58 fffffa80`08590000 : hal!HalPutScatterGatherList+0x1c
fffff880`0c79e930 fffff880`07acbdd7 : fffffa80`082b0820 fffffa80`08585c58 00000000`00000000 00000000`00000000 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`0c79e970 fffffa80`082b0820 : fffffa80`08585c58 00000000`00000000 00000000`00000000 00000000`00000000 : e1q62x64+0x18dd7
fffff880`0c79e978 fffffa80`08585c58 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07ad4305 : 0xfffffa80`082b0820
fffff880`0c79e980 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`07ad4305 fffffa80`00000000 : 0xfffffa80`08585c58


STACK_COMMAND: kb

FOLLOWUP_IP:
e1q62x64+18dd7
fffff880`07acbdd7 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: e1q62x64+18dd7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME: e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4af31807

FAILURE_BUCKET_ID: X64_0xA_e1q62x64+18dd7

BUCKET_ID: X64_0xA_e1q62x64+18dd7

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

4: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002c0976c, address which referenced memory

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


READ_ADDRESS: 0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalPutScatterGatherList+1c
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8800c79e740 -- (.trap 0xfffff8800c79e740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002c2ce00 rbx=0000000000000000 rcx=fffffa80084f0040
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c0976c rsp=fffff8800c79e8d0 rbp=00000000000000c6
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=00000000000001ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!HalPutScatterGatherList+0x1c:
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8] ds:eca8:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cbf469 to fffff80002cbff00

STACK_TEXT:
fffff880`0c79e5f8 fffff800`02cbf469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c79e600 fffff800`02cbe0e0 : 00000000`00000000 fffffa80`072eda60 fffffa80`07a20080 fffffa80`07a20700 : nt!KiBugCheckDispatch+0x69
fffff880`0c79e740 fffff800`02c0976c : fffffa80`082b0820 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x260
fffff880`0c79e8d0 fffff880`0144b8a1 : fffffa80`072eda60 00000000`000000c6 fffffa80`08585c58 fffffa80`08590000 : hal!HalPutScatterGatherList+0x1c
fffff880`0c79e930 fffff880`07acbdd7 : fffffa80`082b0820 fffffa80`08585c58 00000000`00000000 00000000`00000000 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`0c79e970 fffffa80`082b0820 : fffffa80`08585c58 00000000`00000000 00000000`00000000 00000000`00000000 : e1q62x64+0x18dd7
fffff880`0c79e978 fffffa80`08585c58 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07ad4305 : 0xfffffa80`082b0820
fffff880`0c79e980 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`07ad4305 fffffa80`00000000 : 0xfffffa80`08585c58


STACK_COMMAND: kb

FOLLOWUP_IP:
e1q62x64+18dd7
fffff880`07acbdd7 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: e1q62x64+18dd7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME: e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4af31807

FAILURE_BUCKET_ID: X64_0xA_e1q62x64+18dd7

BUCKET_ID: X64_0xA_e1q62x64+18dd7

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

4: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002c0976c, address which referenced memory

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


READ_ADDRESS: 0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalPutScatterGatherList+1c
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8800c79e740 -- (.trap 0xfffff8800c79e740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002c2ce00 rbx=0000000000000000 rcx=fffffa80084f0040
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c0976c rsp=fffff8800c79e8d0 rbp=00000000000000c6
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=00000000000001ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!HalPutScatterGatherList+0x1c:
fffff800`02c0976c 488b5a08 mov rbx,qword ptr [rdx+8] ds:eca8:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cbf469 to fffff80002cbff00

STACK_TEXT:
fffff880`0c79e5f8 fffff800`02cbf469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c79e600 fffff800`02cbe0e0 : 00000000`00000000 fffffa80`072eda60 fffffa80`07a20080 fffffa80`07a20700 : nt!KiBugCheckDispatch+0x69
fffff880`0c79e740 fffff800`02c0976c : fffffa80`082b0820 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x260
fffff880`0c79e8d0 fffff880`0144b8a1 : fffffa80`072eda60 00000000`000000c6 fffffa80`08585c58 fffffa80`08590000 : hal!HalPutScatterGatherList+0x1c
fffff880`0c79e930 fffff880`07acbdd7 : fffffa80`082b0820 fffffa80`08585c58 00000000`00000000 00000000`00000000 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`0c79e970 fffffa80`082b0820 : fffffa80`08585c58 00000000`00000000 00000000`00000000 00000000`00000000 : e1q62x64+0x18dd7
fffff880`0c79e978 fffffa80`08585c58 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07ad4305 : 0xfffffa80`082b0820
fffff880`0c79e980 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`07ad4305 fffffa80`00000000 : 0xfffffa80`08585c58


STACK_COMMAND: kb

FOLLOWUP_IP:
e1q62x64+18dd7
fffff880`07acbdd7 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: e1q62x64+18dd7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME: e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4af31807

FAILURE_BUCKET_ID: X64_0xA_e1q62x64+18dd7

BUCKET_ID: X64_0xA_e1q62x64+18dd7

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


Bedanke mich schonmal für eure Hilfe

wegberger

 

[simpel1970]

Der Absturz (der geposteten Bluescreenauswertung) wurde durch den Intel Ethernet (Gigabit LAN) Treiber ausgelöst (e1q62x64.sys).

Installiere den aktuellsten Treiber. Tausche das LAN Kabel aus.

Ist es immer der gleiche Stopfehlercode, der beim Bluescreen auftritt? Ist es, wenn du die Bluescreens auswertest immer der e1q62x64.sys Treiber, der als Absturzursache (IMAGE_NAME: e1q62x64.sys) angegeben wird?