Bluescreen nach Ruhemodus

MarryHT

MarryHT

Komplett-PC-Käufer(in)
Hallo
mein System ist noch nicht sehr alt aber ich hab jetzt seit aufsetzten Anfang/Mitte Januar 6Bluescreens gehabt.
Aufgetreten wenn ich den Rechner aus dem Ruhemodus aufzuwecken versuche

Hier die Auswertungen der letzten 3dmp dateien von windows debugger (nach der Anleitung im How-to)

25.02.2015
*******************************************************************************
* *
* 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: fffffffffffffff8, 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: fffff80003a53ac8, address which referenced memory

Debugging Details:
------------------
*******************************************************************************
* *
* 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: 0000000000000001, 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: fffff8000369d476, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038cb100
0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiInsertTimerTable+c6
fffff800`0369d476 4c894008 mov qword ptr [rax+8],r8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: sidebar.exe

TRAP_FRAME: fffff88008ed8640 -- (.trap 0xfffff88008ed8640)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000001760a40d89
rdx=fffffa800bb2b5d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000369d476 rsp=fffff88008ed87d0 rbp=fffffa800bb2b5d8
r8=fffffa800adc91c0 r9=0000000000000025 r10=fffff8000380ee80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KiInsertTimerTable+0xc6:
fffff800`0369d476 4c894008 mov qword ptr [rax+8],r8 ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003691469 to fffff80003691ec0

STACK_TEXT:
fffff880`08ed84f8 fffff800`03691469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08ed8500 fffff800`036900e0 : fffffa80`0b4c5600 00000000`00000001 fffffa80`0a37da90 fffffa80`0adc91a0 : nt!KiBugCheckDispatch+0x69
fffff880`08ed8640 fffff800`0369d476 : fffffa80`0b4c5760 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`08ed87d0 fffff800`0369d1b0 : ffffffff`fff0c1db fffff800`0380ee80 fffffa80`0adc91a0 00000000`00000000 : nt!KiInsertTimerTable+0xc6
fffff880`08ed8830 fffff800`036a12d2 : 00000000`00000001 ffffffff`fff0c1db 00000000`00000000 00000000`00000002 : nt!KiSetTimerEx+0xf0
fffff880`08ed88c0 fffff800`0367ebff : 00000000`00000001 ffffffff`fff0c1db fffff880`08ed8b60 00000000`00000001 : nt!KeSetCoalescableTimer+0xb2
fffff880`08ed8910 fffff800`0367ea33 : 00000000`00000001 00000000`77a44601 fffff880`08ed8a30 00000000`00000000 : nt!ExpSetTimer+0x18f
fffff880`08ed89e0 fffff800`03691153 : fffffa80`0b4c56a0 00000000`0802f658 fffff880`08ed8a88 00000000`0000ffff : nt!NtSetTimer+0xaf
fffff880`08ed8a70 00000000`779918da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0802f638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779918da


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiInsertTimerTable+c6
fffff800`0369d476 4c894008 mov qword ptr [rax+8],r8

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiInsertTimerTable+c6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff

FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+c6

BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+c6

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


READ_ADDRESS: fffffffffffffff8

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiInitialPCR+3dc8
fffff800`03a53ac8 c8ce320a enter 32CEh,0Ah

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8000400d9e0 -- (.trap 0xfffff8000400d9e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a32cee0 rbx=0000000000000000 rcx=fffffa8009183a40
rdx=fffffa800a32cc60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a53ac8 rsp=fffff8000400db78 rbp=0000000000000000
r8=fffffa8009183b90 r9=000000000000000c r10=fffffa8006a23290
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiInitialPCR+0x3dc8:
fffff800`03a53ac8 c8ce320a enter 32CEh,0Ah
Resetting default scope

MISALIGNED_IP:
nt!KiInitialPCR+3dc8
fffff800`03a53ac8 c8ce320a enter 32CEh,0Ah

LAST_CONTROL_TRANSFER: from fffff800038d2469 to fffff800038d2ec0

STACK_TEXT:
fffff800`0400d898 fffff800`038d2469 : 00000000`0000000a ffffffff`fffffff8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`0400d8a0 fffff800`038d10e0 : fffffa80`0c926910 fffff880`012c04de fffff880`041ef3f0 fffffa80`0a32ce9b : nt!KiBugCheckDispatch+0x69
fffff800`0400d9e0 fffff800`03a53ac8 : fffff800`038d61e1 fffffa80`0a32ce0b fffffa80`091799d0 fffffa80`0a32cc60 : nt!KiPageFault+0x260
fffff800`0400db78 fffff800`038d61e1 : fffffa80`0a32ce0b fffffa80`091799d0 fffffa80`0a32cc60 fffffa80`0a32cc60 : nt!KiInitialPCR+0x3dc8
fffff800`0400db80 fffff880`01c01bce : fffffa80`0c933010 00000000`00000001 fffffa80`06a231b0 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`0400dc70 fffff800`038d61e1 : 00000000`00000000 fffffa80`06a23060 00000000`00000000 fffff880`041ef0b8 : CLASSPNP!TransferPktComplete+0x1ce
fffff800`0400dcf0 fffff880`014ff6c8 : fffff880`041d8010 fffffa80`06a2c301 fffffa80`0c926f80 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`0400dde0 fffff880`014ff443 : 00000000`00000000 fffffa80`000000eb 00000000`ffffff02 fffffa80`06a23060 : storport!RaidUnitCompleteRequest+0x208
fffff800`0400dec0 fffff800`038de7ac : fffff800`03a4fe80 fffff880`00000000 fffffa80`06a23128 00000000`0000fffe : storport!RaidpAdapterDpcRoutine+0x53
fffff800`0400df00 fffff800`038d5925 : 00000000`00000000 fffffa80`066c7040 00000000`00000000 fffff880`014ff3f0 : nt!KiRetireDpcList+0x1bc
fffff800`0400dfb0 fffff800`038d573c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`035f4c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!TransferPktComplete+1ce
fffff880`01c01bce 837c243002 cmp dword ptr [rsp+30h],2

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: CLASSPNP!TransferPktComplete+1ce

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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


23.02.2015 19:24
*******************************************************************************
* *
* 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: fffffffffffffff8, 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: fffff80003a53ac8, address which referenced memory

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


READ_ADDRESS: fffffffffffffff8

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiInitialPCR+3dc8
fffff800`03a53ac8 c8ce320a enter 32CEh,0Ah

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8000400d9e0 -- (.trap 0xfffff8000400d9e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a32cee0 rbx=0000000000000000 rcx=fffffa8009183a40
rdx=fffffa800a32cc60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a53ac8 rsp=fffff8000400db78 rbp=0000000000000000
r8=fffffa8009183b90 r9=000000000000000c r10=fffffa8006a23290
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiInitialPCR+0x3dc8:
fffff800`03a53ac8 c8ce320a enter 32CEh,0Ah
Resetting default scope

MISALIGNED_IP:
nt!KiInitialPCR+3dc8
fffff800`03a53ac8 c8ce320a enter 32CEh,0Ah

LAST_CONTROL_TRANSFER: from fffff800038d2469 to fffff800038d2ec0

STACK_TEXT:
fffff800`0400d898 fffff800`038d2469 : 00000000`0000000a ffffffff`fffffff8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`0400d8a0 fffff800`038d10e0 : fffffa80`0c926910 fffff880`012c04de fffff880`041ef3f0 fffffa80`0a32ce9b : nt!KiBugCheckDispatch+0x69
fffff800`0400d9e0 fffff800`03a53ac8 : fffff800`038d61e1 fffffa80`0a32ce0b fffffa80`091799d0 fffffa80`0a32cc60 : nt!KiPageFault+0x260
fffff800`0400db78 fffff800`038d61e1 : fffffa80`0a32ce0b fffffa80`091799d0 fffffa80`0a32cc60 fffffa80`0a32cc60 : nt!KiInitialPCR+0x3dc8
fffff800`0400db80 fffff880`01c01bce : fffffa80`0c933010 00000000`00000001 fffffa80`06a231b0 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`0400dc70 fffff800`038d61e1 : 00000000`00000000 fffffa80`06a23060 00000000`00000000 fffff880`041ef0b8 : CLASSPNP!TransferPktComplete+0x1ce
fffff800`0400dcf0 fffff880`014ff6c8 : fffff880`041d8010 fffffa80`06a2c301 fffffa80`0c926f80 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`0400dde0 fffff880`014ff443 : 00000000`00000000 fffffa80`000000eb 00000000`ffffff02 fffffa80`06a23060 : storport!RaidUnitCompleteRequest+0x208
fffff800`0400dec0 fffff800`038de7ac : fffff800`03a4fe80 fffff880`00000000 fffffa80`06a23128 00000000`0000fffe : storport!RaidpAdapterDpcRoutine+0x53
fffff800`0400df00 fffff800`038d5925 : 00000000`00000000 fffffa80`066c7040 00000000`00000000 fffff880`014ff3f0 : nt!KiRetireDpcList+0x1bc
fffff800`0400dfb0 fffff800`038d573c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`035f4c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!TransferPktComplete+1ce
fffff880`01c01bce 837c243002 cmp dword ptr [rsp+30h],2

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: CLASSPNP!TransferPktComplete+1ce

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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


23.02.2015 16:37
*******************************************************************************
* *
* 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: fffff8800a7a4008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800036d1476, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038ff100
fffff8800a7a4008

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiInsertTimerTable+c6
fffff800`036d1476 4c894008 mov qword ptr [rax+8],r8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

TRAP_FRAME: fffff88007fe7680 -- (.trap 0xfffff88007fe7680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800a7a4000 rbx=0000000000000000 rcx=0000001ab6d23824
rdx=fffffa8006960488 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800036d1476 rsp=fffff88007fe7810 rbp=fffffa8006960488
r8=fffffa800b2f8af0 r9=00000000000000fc r10=fffff80003842e80
r11=fffff80003842e00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiInsertTimerTable+0xc6:
fffff800`036d1476 4c894008 mov qword ptr [rax+8],r8 ds:bf01:fffff880`0a7a4008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800036c5469 to fffff800036c5ec0

STACK_TEXT:
fffff880`07fe7538 fffff800`036c5469 : 00000000`0000000a fffff880`0a7a4008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`07fe7540 fffff800`036c40e0 : fffff880`07fe7698 00000000`00000000 00000000`00000000 fffffa80`0b2f8ad0 : nt!KiBugCheckDispatch+0x69
fffff880`07fe7680 fffff800`036d1476 : 00000000`00000000 fffff800`039bec56 00000000`00000001 fffff800`0360fb7f : nt!KiPageFault+0x260
fffff880`07fe7810 fffff800`036cb252 : fffffa80`0b2f8a10 00000000`0000066c 00000002`00000400 00000000`00000000 : nt!KiInsertTimerTable+0xc6
fffff880`07fe7870 fffff800`036cd90f : 00000001`00000000 00000000`00000001 00000000`000000fc fffffa80`0b2f8a10 : nt!KiCommitThreadWait+0x332
fffff880`07fe7900 fffff800`036a6b46 : fffffa80`0a41a800 00000000`0000001b 00000000`03204600 fffff800`03842e00 : nt!KeWaitForSingleObject+0x19f
fffff880`07fe79a0 fffff800`036cbd2c : ffffffff`ffb3b4c0 fffffa80`0a504820 fffffa80`0a41a8d0 00000000`00000000 : nt!ExpWaitForResource+0xae
fffff880`07fe7a10 fffff800`036d02bb : 00000000`00000001 fffffa80`0b2f8a10 fffff880`07fe7b60 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`07fe7a80 fffff960`000f6999 : fffffa80`746c6644 fffff880`07fe7ae8 00000000`00000000 00000000`00000000 : nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x23
fffff880`07fe7ab0 fffffa80`746c6644 : fffff880`07fe7ae8 00000000`00000000 00000000`00000000 00000000`00000020 : win32k+0xd6999
fffff880`07fe7ab8 fffff880`07fe7ae8 : 00000000`00000000 00000000`00000000 00000000`00000020 fffff800`036c5153 : 0xfffffa80`746c6644
fffff880`07fe7ac0 00000000`00000000 : 00000000`00000000 00000000`00000020 fffff800`036c5153 fffffa80`0b2f8a10 : 0xfffff880`07fe7ae8


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+d6999
fffff960`000f6999 ?? ???

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: win32k+d6999

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0xA_win32k+d6999

BUCKET_ID: X64_0xA_win32k+d6999

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

=/
und nun?
 
Zuletzt bearbeitet:
Sieht ziemlich eindeutig nach einem RAM-Defekt aus. Probier die Riegel mal einzeln durch (Also alle bis auf 1 ausbauen, Ruhezustand - aufwecken, was passiert? / Und das mit jedem Riegel)
Einer müsste dann ja wohl einen Bluescreen verursachen. Evtl auch mal alle 4 (gleichzeitig) mit Memtest testen. Aber am besten über nacht laufen lassen.
 
es passiert ja nur alle 50male, trotztdem so testen?

edit: system screenshot im anhang
ah jetzt check ichs sry, ok wird morgen gemacht
 

Anhänge

  • sys.jpg
    sys.jpg
    959,2 KB · Aufrufe: 47
  • 1.gif
    1.gif
    26,9 KB · Aufrufe: 33
  • 2.gif
    2.gif
    21 KB · Aufrufe: 33
Zuletzt bearbeitet:
Hier noch die letzten 2 DMP im Anhang (das sind die ältesten)
Die andren 3 aktuelleren sind im ersten post.
 

Anhänge

MarryHT schrieb:
Die andren 3 aktuelleren sind im ersten post.
Zum Vergrößern anklicken....

Da sind nur die Auswertungstexte, nicht aber die Dumps.

Ein primäres Treiberproblem ist den beiden älteren Dumps nicht zu entnehmen (denkbar, dass die aktuelleren Dumps auch keine weiteren Hinweise bringen).
Es fallen jedoch ein paar veraltete Treiber auf, die zu Gigabyte Tools (z.B. EasyTune) gehören. Diese könnten durchaus mit dem Problem in Verbindung stehen.
- etdrv.sys (März 2009)
- gdrv.sys (März 2009)
- GVTDrv64.sys (Sept. 2006)
Ich würde daher empfehlen die (alle) Gigabyte Tools zu deinstallieren.

Sollten danach erneut Bluescreens auftreten, lade bitte die aktuellsten Dumps (nicht nur den Auswertungstext) hier hoch.
 
Ah achso sry, ich dachte da sieht man alles.
Okay also das ganze Gigabyte App Center?
Da müsste dann ja alles weg sein oder?
 
Dann sollte alles weg sein.
In der Systemsteuerung -> Programme anschließend noch mal nachsehen, ob dort noch etwas von Gigabyte vorhanden ist.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen

M
Neustarts und Bluescreens, USB Overcurrent
Antworten
16
Aufrufe
2K
mauersegler
M
A
Monitor verliert Signal - Sound kurz weiter - PC Neustart
Antworten
16
Aufrufe
775
Sesambrötchen
Sesambrötchen
H
Leistungsprobleme mit Lightroom und Windows 11
Antworten
15
Aufrufe
567
Hiper86
H
A
CachyOS nach Systemupdate halbierte FPS
Antworten
8
Aufrufe
4K
_Oskar_
_Oskar_
Mao_Zedong
DDR4 Probleme ... Defekte RMA und CO.
Antworten
6
Aufrufe
862
eXquisite
eXquisite
Oben Unten
Zurück