reelsn
Herzlich willkommen
Hallo
also ich hab folgendes problem .. und zwar unmengen an bluescreens ^^.
Mein PC ist jetzt 1 Jahr alt und seit dem quäl ich mich mit jedermenge bluescreens rum seit dez 08 bis heute ungefäir 70 stück ^^ ich hab leider total keine ahnung woher die kommen und wie ich herrausfinde was nicht stimmt.
Deshalb dachte ich mir ich poste die bluescreens mal hier ins forum hab einfach mal 3 rausgesucht von den vielen die ich bekomme^^
vielen dank shonmal im vorraus
Hardware infos
------------------------------------
Mainboard : ASUS Maximus Formula (Special Edition)
CPU : Inten core 2 duo Q6800 2x3 Ghz
RAM : Corsair xms2 DHX 2x 1gb
Grafikkarte : MSI 8800 GT
Netzteil : be quiet! Dark power Pro 530W
------------------------------------
--------------------------------------
Ich hoffe die infos reichen aus
also ich hab folgendes problem .. und zwar unmengen an bluescreens ^^.
Mein PC ist jetzt 1 Jahr alt und seit dem quäl ich mich mit jedermenge bluescreens rum seit dez 08 bis heute ungefäir 70 stück ^^ ich hab leider total keine ahnung woher die kommen und wie ich herrausfinde was nicht stimmt.
Deshalb dachte ich mir ich poste die bluescreens mal hier ins forum hab einfach mal 3 rausgesucht von den vielen die ich bekomme^^
vielen dank shonmal im vorraus
Hardware infos
------------------------------------
Mainboard : ASUS Maximus Formula (Special Edition)
CPU : Inten core 2 duo Q6800 2x3 Ghz
RAM : Corsair xms2 DHX 2x 1gb
Grafikkarte : MSI 8800 GT
Netzteil : be quiet! Dark power Pro 530W
------------------------------------
Bluescreen 1
------------------------------------
BugCheck 1E, {ffffffffc000001d, fffff80001aa0e9c, 2ff00, fffff80001aa0e9c}
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME} Ung ltige Anweisung Es wurde versucht, eine ung ltige Anweisung auszuf hren.
FAULTING_IP:
nt!KiSecondaryClockInterrupt+c
fffff800`01aa0e9c 488dac2480000000 lea rbp,[rsp+80h]
EXCEPTION_PARAMETER1: 000000000002ff00
EXCEPTION_PARAMETER2: fffff80001aa0e9c
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001a80e47 to fffff80001aa7350
FAILED_INSTRUCTION_ADDRESS:
nt!KiSecondaryClockInterrupt+c
fffff800`01aa0e9c 488dac2480000000 lea rbp,[rsp+80h]
STACK_TEXT:
fffffa60`0191b1d8 fffff800`01a80e47 : 00000000`0000001e ffffffff`c000001d fffff800`01aa0e9c 00000000`0002ff00 : nt!KeBugCheckEx
fffffa60`0191b1e0 fffff800`01aa71a9 : fffffa60`0191b918 00000000`00000000 fffffa60`0191b9c0 fffffa60`005efa00 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`0191b7e0 fffff800`01aa56c3 : fffffa60`0191b9c0 00000000`00000000 fffffa80`03e3f100 fffffa60`00000000 : nt!KiExceptionDispatch+0xa9
fffffa60`0191b9c0 fffff800`01aa0e9c : 00000000`00000000 00000000`00000002 00000000`00000080 fffff800`01a1a5a0 : nt!KiInvalidOpcodeFault+0xc3
fffffa60`0191bb50 fffffa60`00d777a2 : fffffa60`00d76685 0000001a`9a8037a8 fffffa60`0191bd50 fffffa60`005ec180 : nt!KiSecondaryClockInterrupt+0xc
fffffa60`0191bce8 fffffa60`00d76685 : 0000001a`9a8037a8 fffffa60`0191bd50 fffffa60`005ec180 fffff800`01a88979 : intelppm!C1Halt+0x2
fffffa60`0191bcf0 fffff800`01ac27f8 : fffffa80`050e9710 fffffa60`005f5d40 fffffa60`0191bdb0 fffff800`01aaa9ed : intelppm!C1Idle+0x9
fffffa60`0191bd20 fffff800`01ab1b21 : fffffa60`005ec180 00000000`0002c3e8 00000000`00000000 00000000`00000000 : nt!PoIdle+0x148
fffffa60`0191bd80 fffff800`01c7f5c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x21
fffffa60`0191bdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm!C1Halt+2
fffffa60`00d777a2 c3 ret
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: intelppm!C1Halt+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4791902d
FAILURE_BUCKET_ID: X64_0x1E_BAD_IP_intelppm!C1Halt+2
BUCKET_ID: X64_0x1E_BAD_IP_intelppm!C1Halt+2
Followup: MachineOwner
----------------------------------
Bluescreen 2
----------------------------------
UGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001a6d0ee to fffff80001a6d350
STACK_TEXT:
fffffa60`005f1a68 fffff800`01a6d0ee : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffffa60`005f1a70 fffff800`01a6b938 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`005f1bb0 fffff800`01a6711f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
00000000`0091bcb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSecondaryClockInterrupt+0x28f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b8
fffff800`01a6b938 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8
Followup: MachineOwner
-------------------------------
Bluescreen 3
-------------------------------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80001a16363, 0, ffffffffffffffff}
Unable to load image \SystemRoot\system32\DRIVERS\yk60x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for yk60x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk60x64.sys
Probably caused by : yk60x64.sys ( yk60x64+13f31 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80001a16363, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
hal!HalBuildScatterGatherList+77
fffff800`01a16363 4983620800 and qword ptr [r10+8],0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c81080
ffffffffffffffff
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80001a86e47 to fffff80001aad350
STACK_TEXT:
fffffa60`019196a8 fffff800`01a86e47 : 00000000`0000001e ffffffff`c0000005 fffff800`01a16363 00000000`00000000 : nt!KeBugCheckEx
fffffa60`019196b0 fffff800`01aad1a9 : fffffa60`01919de8 00000000`00000074 fffffa60`01919e90 fffffa80`03eef040 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`01919cb0 fffff800`01aabd8d : 00000000`00000074 fffffa80`03de60f0 00000000`00000074 fffffa60`02f77fa0 : nt!KiExceptionDispatch+0xa9
fffffa60`01919e90 fffff800`01a16363 : fffffa60`0191a41e 00000000`00000000 fffffa60`0191a028 00000000`00000000 : nt!KiGeneralProtectionFault+0xcd
fffffa60`0191a020 fffffa60`00e0f589 : fffffa80`02b4a130 fffffa80`03d421a0 fffffa80`03e7f6f0 fffffa60`01057c01 : hal!HalBuildScatterGatherList+0x77
fffffa60`0191a090 fffffa60`02f77f31 : 00000000`00000000 fffffa80`03d421a0 00000000`00000002 fffffa80`04193010 : ndis!NdisMAllocateNetBufferSGList+0xc9
fffffa60`0191a130 00000000`00000000 : fffffa80`03d421a0 00000000`00000002 fffffa80`04193010 ffe3fa80`03f78bd0 : yk60x64+0x13f31
STACK_COMMAND: kb
FOLLOWUP_IP:
yk60x64+13f31
fffffa60`02f77f31 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: yk60x64+13f31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: yk60x64
IMAGE_NAME: yk60x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46559e5d
FAILURE_BUCKET_ID: X64_0x1E_yk60x64+13f31
BUCKET_ID: X64_0x1E_yk60x64+13f31
Followup: MachineOwner
------------------------------------
BugCheck 1E, {ffffffffc000001d, fffff80001aa0e9c, 2ff00, fffff80001aa0e9c}
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME} Ung ltige Anweisung Es wurde versucht, eine ung ltige Anweisung auszuf hren.
FAULTING_IP:
nt!KiSecondaryClockInterrupt+c
fffff800`01aa0e9c 488dac2480000000 lea rbp,[rsp+80h]
EXCEPTION_PARAMETER1: 000000000002ff00
EXCEPTION_PARAMETER2: fffff80001aa0e9c
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001a80e47 to fffff80001aa7350
FAILED_INSTRUCTION_ADDRESS:
nt!KiSecondaryClockInterrupt+c
fffff800`01aa0e9c 488dac2480000000 lea rbp,[rsp+80h]
STACK_TEXT:
fffffa60`0191b1d8 fffff800`01a80e47 : 00000000`0000001e ffffffff`c000001d fffff800`01aa0e9c 00000000`0002ff00 : nt!KeBugCheckEx
fffffa60`0191b1e0 fffff800`01aa71a9 : fffffa60`0191b918 00000000`00000000 fffffa60`0191b9c0 fffffa60`005efa00 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`0191b7e0 fffff800`01aa56c3 : fffffa60`0191b9c0 00000000`00000000 fffffa80`03e3f100 fffffa60`00000000 : nt!KiExceptionDispatch+0xa9
fffffa60`0191b9c0 fffff800`01aa0e9c : 00000000`00000000 00000000`00000002 00000000`00000080 fffff800`01a1a5a0 : nt!KiInvalidOpcodeFault+0xc3
fffffa60`0191bb50 fffffa60`00d777a2 : fffffa60`00d76685 0000001a`9a8037a8 fffffa60`0191bd50 fffffa60`005ec180 : nt!KiSecondaryClockInterrupt+0xc
fffffa60`0191bce8 fffffa60`00d76685 : 0000001a`9a8037a8 fffffa60`0191bd50 fffffa60`005ec180 fffff800`01a88979 : intelppm!C1Halt+0x2
fffffa60`0191bcf0 fffff800`01ac27f8 : fffffa80`050e9710 fffffa60`005f5d40 fffffa60`0191bdb0 fffff800`01aaa9ed : intelppm!C1Idle+0x9
fffffa60`0191bd20 fffff800`01ab1b21 : fffffa60`005ec180 00000000`0002c3e8 00000000`00000000 00000000`00000000 : nt!PoIdle+0x148
fffffa60`0191bd80 fffff800`01c7f5c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x21
fffffa60`0191bdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm!C1Halt+2
fffffa60`00d777a2 c3 ret
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: intelppm!C1Halt+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4791902d
FAILURE_BUCKET_ID: X64_0x1E_BAD_IP_intelppm!C1Halt+2
BUCKET_ID: X64_0x1E_BAD_IP_intelppm!C1Halt+2
Followup: MachineOwner
----------------------------------
Bluescreen 2
----------------------------------
UGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001a6d0ee to fffff80001a6d350
STACK_TEXT:
fffffa60`005f1a68 fffff800`01a6d0ee : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffffa60`005f1a70 fffff800`01a6b938 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`005f1bb0 fffff800`01a6711f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
00000000`0091bcb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSecondaryClockInterrupt+0x28f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b8
fffff800`01a6b938 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8
Followup: MachineOwner
-------------------------------
Bluescreen 3
-------------------------------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80001a16363, 0, ffffffffffffffff}
Unable to load image \SystemRoot\system32\DRIVERS\yk60x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for yk60x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk60x64.sys
Probably caused by : yk60x64.sys ( yk60x64+13f31 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80001a16363, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
hal!HalBuildScatterGatherList+77
fffff800`01a16363 4983620800 and qword ptr [r10+8],0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c81080
ffffffffffffffff
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80001a86e47 to fffff80001aad350
STACK_TEXT:
fffffa60`019196a8 fffff800`01a86e47 : 00000000`0000001e ffffffff`c0000005 fffff800`01a16363 00000000`00000000 : nt!KeBugCheckEx
fffffa60`019196b0 fffff800`01aad1a9 : fffffa60`01919de8 00000000`00000074 fffffa60`01919e90 fffffa80`03eef040 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`01919cb0 fffff800`01aabd8d : 00000000`00000074 fffffa80`03de60f0 00000000`00000074 fffffa60`02f77fa0 : nt!KiExceptionDispatch+0xa9
fffffa60`01919e90 fffff800`01a16363 : fffffa60`0191a41e 00000000`00000000 fffffa60`0191a028 00000000`00000000 : nt!KiGeneralProtectionFault+0xcd
fffffa60`0191a020 fffffa60`00e0f589 : fffffa80`02b4a130 fffffa80`03d421a0 fffffa80`03e7f6f0 fffffa60`01057c01 : hal!HalBuildScatterGatherList+0x77
fffffa60`0191a090 fffffa60`02f77f31 : 00000000`00000000 fffffa80`03d421a0 00000000`00000002 fffffa80`04193010 : ndis!NdisMAllocateNetBufferSGList+0xc9
fffffa60`0191a130 00000000`00000000 : fffffa80`03d421a0 00000000`00000002 fffffa80`04193010 ffe3fa80`03f78bd0 : yk60x64+0x13f31
STACK_COMMAND: kb
FOLLOWUP_IP:
yk60x64+13f31
fffffa60`02f77f31 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: yk60x64+13f31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: yk60x64
IMAGE_NAME: yk60x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46559e5d
FAILURE_BUCKET_ID: X64_0x1E_yk60x64+13f31
BUCKET_ID: X64_0x1E_yk60x64+13f31
Followup: MachineOwner
Ich hoffe die infos reichen aus
Zuletzt bearbeitet von einem Moderator: