hoschi2010
Schraubenverwechsler(in)
Löle
Habe seit kurzem ständig BlueScreen mit der Fehlermeldung IRQL NOT LESS OR EQUAL. Passiert meist beim hochfahren. Wenn der Rechner dann mal läuft taucht das Problem nicht mehr auf. Hab schon den Speicher getestet. Der scheint es nicht zu sein. Hab dann mal den Debugger von Microsoft laufen lassen und folgendes dabei bekommen.
Loading Dump File [C:\Windows\Minidump\091110-15272-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows Longhorn Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Kernel base = 0xfffff800`0341c000 PsLoadedModuleList = 0xfffff800`03659e50
Debug session time: Sat Sep 11 08:32:13.470 2010 (GMT+2)
System Uptime: 0 days 0:00:10.389
Loading Kernel Symbols
.................................................................................................................
Loading unloaded module list
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff8800d208000, 2, 0, fffff800034834e0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> .reload
Loading Kernel Symbols
.................................................................................................................
Loading unloaded module list
.
Loading User Symbols
0: 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: fffff8800d208000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800034834e0, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: discache
READ_ADDRESS: unable to get MiSystemVaType - probably bad symbols
fffff8800d208000
CURRENT_IRQL: 2
FAULTING_IP:
nt!memmove+b0
fffff800`034834e0 488b040a mov rax,[rdx+rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from fffff8000348bca9 to fffff8000348c740
STACK_TEXT:
fffff800`00b9c1b8 fffff800`0348bca9 : 00000000`0000000a fffff880`0d208000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1c0 fffff800`0348a920 : 0000000e`00000028 fffff880`0d205018 fffff880`019abbb4 00000000`0007c0c8 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c300 fffff800`034834e0 : fffff800`0393a419 fffffa80`049e7820 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c498 fffff800`0393a419 : fffffa80`049e7820 00000000`00000000 00000000`00000000 fffff880`0167dcca : nt!memmove+0xb0
fffff800`00b9c4a0 fffff800`0393d178 : 00000000`00000000 00000000`00000001 fffffa80`039f77a0 fffffa80`039f77a4 : nt!GxpWriteFrameBufferPixels+0xb9
fffff800`00b9c4f0 fffff800`0393e757 : 00000000`00000000 00000000`00033189 00000000`00000001 00000000`00000000 : nt!BgpGxDrawRectangle+0x48
fffff800`00b9c520 fffff800`0349829e : fffff800`00b9c600 00000000`00000000 00000000`00000000 00000000`00000000 : nt!AnFwpProgressIndicatorTimer+0x107
fffff800`00b9c570 fffff800`03497dd6 : fffff800`0361ca80 00000000`00000299 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`034984be : 00000000`06315475 fffff800`00b9cc58 00000000`00000299 fffff800`0360a5a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`03497cb7 : 00000000`01feb9c1 00000000`00000299 00000000`01feb9a4 00000000`00000099 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03494eea : fffff800`03606e80 fffff800`03614c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`0348a920 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiPageFault+260
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0xA_nt!KiPageFault+260
BUCKET_ID: X64_0xA_nt!KiPageFault+260
Followup: MachineOwner
---------
Infos zu meiner Kiste:
Windows 7 Pro 64bit
AMD X6 1090T
Gigabyte GA-870A-UD3
ADATA DIMM 4 GB DDR3-1333
Sapphire HD5870
Western Digital WD1002FAEX 1 TB
Netzteil Seasonic M12 500Watt
Das BIOS ist auf dem neuesten Stand. Habe keine Übertaktungen eingestellt. Nur die ser. und par. Schnittstellen sind aus.
Kann da jemand was mit anfangen. Wäre echt nett.
Habe seit kurzem ständig BlueScreen mit der Fehlermeldung IRQL NOT LESS OR EQUAL. Passiert meist beim hochfahren. Wenn der Rechner dann mal läuft taucht das Problem nicht mehr auf. Hab schon den Speicher getestet. Der scheint es nicht zu sein. Hab dann mal den Debugger von Microsoft laufen lassen und folgendes dabei bekommen.
Loading Dump File [C:\Windows\Minidump\091110-15272-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows Longhorn Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Kernel base = 0xfffff800`0341c000 PsLoadedModuleList = 0xfffff800`03659e50
Debug session time: Sat Sep 11 08:32:13.470 2010 (GMT+2)
System Uptime: 0 days 0:00:10.389
Loading Kernel Symbols
.................................................................................................................
Loading unloaded module list
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff8800d208000, 2, 0, fffff800034834e0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> .reload
Loading Kernel Symbols
.................................................................................................................
Loading unloaded module list
.
Loading User Symbols
0: 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: fffff8800d208000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800034834e0, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: discache
READ_ADDRESS: unable to get MiSystemVaType - probably bad symbols
fffff8800d208000
CURRENT_IRQL: 2
FAULTING_IP:
nt!memmove+b0
fffff800`034834e0 488b040a mov rax,[rdx+rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from fffff8000348bca9 to fffff8000348c740
STACK_TEXT:
fffff800`00b9c1b8 fffff800`0348bca9 : 00000000`0000000a fffff880`0d208000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1c0 fffff800`0348a920 : 0000000e`00000028 fffff880`0d205018 fffff880`019abbb4 00000000`0007c0c8 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c300 fffff800`034834e0 : fffff800`0393a419 fffffa80`049e7820 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c498 fffff800`0393a419 : fffffa80`049e7820 00000000`00000000 00000000`00000000 fffff880`0167dcca : nt!memmove+0xb0
fffff800`00b9c4a0 fffff800`0393d178 : 00000000`00000000 00000000`00000001 fffffa80`039f77a0 fffffa80`039f77a4 : nt!GxpWriteFrameBufferPixels+0xb9
fffff800`00b9c4f0 fffff800`0393e757 : 00000000`00000000 00000000`00033189 00000000`00000001 00000000`00000000 : nt!BgpGxDrawRectangle+0x48
fffff800`00b9c520 fffff800`0349829e : fffff800`00b9c600 00000000`00000000 00000000`00000000 00000000`00000000 : nt!AnFwpProgressIndicatorTimer+0x107
fffff800`00b9c570 fffff800`03497dd6 : fffff800`0361ca80 00000000`00000299 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`034984be : 00000000`06315475 fffff800`00b9cc58 00000000`00000299 fffff800`0360a5a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`03497cb7 : 00000000`01feb9c1 00000000`00000299 00000000`01feb9a4 00000000`00000099 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03494eea : fffff800`03606e80 fffff800`03614c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`0348a920 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiPageFault+260
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0xA_nt!KiPageFault+260
BUCKET_ID: X64_0xA_nt!KiPageFault+260
Followup: MachineOwner
---------
Infos zu meiner Kiste:
Windows 7 Pro 64bit
AMD X6 1090T
Gigabyte GA-870A-UD3
ADATA DIMM 4 GB DDR3-1333
Sapphire HD5870
Western Digital WD1002FAEX 1 TB
Netzteil Seasonic M12 500Watt
Das BIOS ist auf dem neuesten Stand. Habe keine Übertaktungen eingestellt. Nur die ser. und par. Schnittstellen sind aus.
Kann da jemand was mit anfangen. Wäre echt nett.
