Danielson
Captain
- Registriert
- Nov. 2011
- Beiträge
- 3.890
Heyho, habe seit heute 2x schon eine Bluescreen innerhalb einer Stunde gehabt. Habe ein Youtubevideo geschaut, sonst war nichts weiter gestartet. Meines Wissens nach wurde zumindest "von Hand" keine Änderung am System vorgenommen.
Windows 7 Ultimate 64bit inkl. Service Pack1 + alle verfügbaren Updates
Chrome 35.0.1916.114 m
Hier die Auswertung der Dump:
Vielleicht kann ja jemand von euch darin etwas erkennen, für mich scheint nur ersichtlich, dass es wohl etwas mit einem Treiber zu tun hat.
Vielen Dank & Grüße,
Danielson
Windows 7 Ultimate 64bit inkl. Service Pack1 + alle verfügbaren Updates
Chrome 35.0.1916.114 m
Hier die Auswertung der Dump:
Code:
*******************************************************************************
* *
* 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: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003dd06a0, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c0100
GetUlongFromAddress: unable to read from fffff800032c01c0
0000000000000068 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
e1c62x64+236a0
fffff880`03dd06a0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88005f326a0 -- (.trap 0xfffff88005f326a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009ea63a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003dd06a0 rsp=fffff88005f32830 rbp=00000000000000e7
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
e1c62x64+0x236a0:
fffff880`03dd06a0 f00fc14168 lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003088169 to fffff80003088bc0
STACK_TEXT:
fffff880`05f32558 fffff800`03088169 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`05f32560 fffff800`03086de0 : 00000000`00000000 fffff880`0171664e fffffa80`098b2000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`05f326a0 fffff880`03dd06a0 : 00000000`00000000 fffffa80`083aebd0 00000000`00000000 fffff880`03dd2c03 : nt!KiPageFault+0x260
fffff880`05f32830 00000000`00000000 : fffffa80`083aebd0 00000000`00000000 fffff880`03dd2c03 00000000`00000000 : e1c62x64+0x236a0
STACK_COMMAND: kb
FOLLOWUP_IP:
e1c62x64+236a0
fffff880`03dd06a0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: e1c62x64+236a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: e1c62x64
IMAGE_NAME: e1c62x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c9924d7
FAILURE_BUCKET_ID: X64_0xD1_e1c62x64+236a0
BUCKET_ID: X64_0xD1_e1c62x64+236a0
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* 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: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003dd06a0, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c0100
GetUlongFromAddress: unable to read from fffff800032c01c0
0000000000000068 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
e1c62x64+236a0
fffff880`03dd06a0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88005f326a0 -- (.trap 0xfffff88005f326a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009ea63a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003dd06a0 rsp=fffff88005f32830 rbp=00000000000000e7
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
e1c62x64+0x236a0:
fffff880`03dd06a0 f00fc14168 lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003088169 to fffff80003088bc0
STACK_TEXT:
fffff880`05f32558 fffff800`03088169 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`05f32560 fffff800`03086de0 : 00000000`00000000 fffff880`0171664e fffffa80`098b2000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`05f326a0 fffff880`03dd06a0 : 00000000`00000000 fffffa80`083aebd0 00000000`00000000 fffff880`03dd2c03 : nt!KiPageFault+0x260
fffff880`05f32830 00000000`00000000 : fffffa80`083aebd0 00000000`00000000 fffff880`03dd2c03 00000000`00000000 : e1c62x64+0x236a0
STACK_COMMAND: kb
FOLLOWUP_IP:
e1c62x64+236a0
fffff880`03dd06a0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: e1c62x64+236a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: e1c62x64
IMAGE_NAME: e1c62x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c9924d7
FAILURE_BUCKET_ID: X64_0xD1_e1c62x64+236a0
BUCKET_ID: X64_0xD1_e1c62x64+236a0
Followup: MachineOwner
---------
Vielleicht kann ja jemand von euch darin etwas erkennen, für mich scheint nur ersichtlich, dass es wohl etwas mit einem Treiber zu tun hat.
Vielen Dank & Grüße,
Danielson
Zuletzt bearbeitet: