SYSTEM_THREAD_EXCEPTION_NOT_HANDLED nach Neuinstallation

Guten Tag,

und ich muss mich entschuldigen wenn das Thema schonmal hier vertreten war.

Erstmal mein Problem:

Ich habe mir diesen Monat ein neues Mainboard(Steht alles unten) und 2 SSD angeschafft. Alle anderen Teile sind von Oktober letzten Jahres, mit Außname der HDD die schon relativ alt ist. habe nun am Samstag das System neu installiert, damit nicht mehr alles nur auf der HDD ist. Vorher hatte ich schon selten mal Bluescreens aber jetzt hab ich seit der Neuinstallation nur noch welche. Die Fehler waren fast immer: "irql not less or equal". Habe gedacht dass es an der HDD liegt weil ich diese vielleicht nicht richtig gelöscht habe oder so und habe mithilfe von Seatools ein Full erase gemacht, und Windows nochmal neu Installiert. Seitdem kommt dieser Bluescreen zwar nicht mehr aber dafür andere(Crashdumps unten). Ich habe mit Seatools ein long test gemacht und kein fehler in der HDD festgestellt. Ich habe das Gefühl das das auch immer nur passiert wenn ich gerade etwas großes auf der HDD Installiere. Diese CrashDumps sind etwas zu hoch für mich und ich hab keine ahnung was ich damit machen soll. Habe sie mit Windbg angeguckt und wurde daraus nicht schlau. BlueScreenView zeigt bei den beiden SYSTEM_THREAD_EXCEPTION_NOT_HANDLED folgendes an:

Spoiler: Chash Dump 2

Spoiler: Crash Dump 1

Achja, hier das memtest ergebniss von heute:

Spoiler: Hier:

Erstmal das System:

Betriebsystemname Microsoft Windows 10 Pro x64
Version 10.0.15063 Build 15063


Mainboard: Asus 970 Pro Gaming
Prozessor: AMD FX-8350
RAM: 2x Crucial Ballistix Sport DDR3-1600 8 GB
GraKa: Geforce 1060 Gigabyte Windforce OC
Kühler: BeQuiet Dark Rock Pro 3
Netzteil: be quiet Pure Power 9 700 Watt
Bios habe ich auf die neuste Version gebracht.

Das waere glaub ich alles. Vielen Dank im vorraus für die Hilfe.


Achja, Die crash Dumps(einer der Dumps zeigt ein fehler mit dem Netztwerkadapter an. das habe ich behoben):

Spoiler: Hier wegen zu langem Text

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 18.04.2017 02:52:01 your computer crashed
crash dump file: C:\Windows\Minidump\041817-6093-01.dmp
This was probably caused by the following module: ndu.sys (Ndu+0x4D23)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF80384854D23, 0xFFFF8280D3D060A8, 0xFFFF8280D3D058E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 18.04.2017 02:52:01 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e1r65x64.sys (e1r65x64+0x1622B)
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF80384854D23, 0xFFFF8280D3D060A8, 0xFFFF8280D3D058E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\e1r65x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1r65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Tue 18.04.2017 01:34:31 your computer crashed
crash dump file: C:\Windows\Minidump\041817-11500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80335827E2F, 0xFFFFC801180A6E00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 17.04.2017 21:43:20 your computer crashed
crash dump file: C:\Windows\Minidump\041717-6578-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x2792B)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF805A651792B, 0xFFFFBE80570C0F28, 0xFFFFBE80570C0760)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

Du kannst mal den S.M.A.R.T. der SSDs und Festplatte überprüfen.
http://www.pcwelt.de/downloads/CrystalDiskInfo-570015.html
SMART-Parameter
http://www.pcwelt.de/ratgeber/Smart...erte-erklaert-Ratgeber-Festplatte-317722.html
Den Screenshot erst machen, wenn die Seriennummer ausgeblendet ist (unter Optionen) und was noch wichtiger ist: die Rohwerte auf 10 [DEC] einstellen (unter Optionen - Erweiterte Optionen - Rohwerte). Dann sind sie direkt als Dezimalwerte ablesbar.

Was mich da vor allem interessiert, sind CRC-Fehler, die häufig durch schlechte SATA-Kabel und Stecker verursacht werden.

 

Okay, ich kannte das Tool nicht. Ich hoffe das ist so wie es sein sollte:

Spoiler: SSD 1

Spoiler: HDD

Spoiler: SSD 2

Edit: ich habe gerade gesehen, dass das tool mir anzeigt das bei den letzten bluescreens wieder was mit den Netzwerkadaptern falsch war. ich habe den Intel Treiber von der offiziellen homepage genommen. Wie kann da ein Fehler kommen?

 

LPM (Link Power Management) kannst du dann mal deaktivieren:
http://www.pc-experience.de/wbb2/thread.php?threadid=31911
siehe Update vom 27.12.2013

 

Ich habe dieses Programm gar nicht und wenn ich es Installieren möchte, sagt er mir der Service wird nicht unterstützt.

Edit: Auch bei dem treiber von Asus wird die Plattform nicht unterstützt

 

Mach mal bitte einen Screenshot von DriveControllerInfo,
https://www.hardwareluxx.de/community/f227/drive-controller-info-ahci-trim-detection-665207.html
wie auf dem Bild:
http://pic.sysprofile.de/images/USE02307.jpg
Das Tool ist zwar alt, funktioniert aber auch bei Win10.

Überprüfe beim Smart der Festplatte, ob der C7-Wert angestiegen ist. So alle paar Stunden und nachdem der PC neu gestartet worden ist.
Der steht bei 746 auf dem Screenshot.

 

Hier der Screenshot:

 

Habe das System neu gestartet und es bleibt bei 746 auf der HDD

 

Der Standard AHCI-Treiber von Windows wird genutzt. Damit gibt es keine Probleme mit LPM, da der Windows Treiber LPM nicht einschaltet.

 

Ich habe seit der Erstellung des Threads kein Bluescreen mehr gehabt. Ich werde jetzt das tun was mir bis jetzt immer ein Bluescreen verpasst hat. Ghost Recon Wildlands auf der HDD installieren. Ich werde gucken was dann passiert.

 

Das ist eine gute Idee.

 

Bluescreen nach 7 min :


On Tue 18.04.2017 17:22:09 your computer crashed
crash dump file: C:\Windows\Minidump\041817-5890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xA (0x0, 0xFF, 0x13, 0xFFFFF802C8A76522)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


CrC fehler sind immernoch wie vorher: 746

 

Habe das ganze mal mit WinDbg ausgewertet:

Spoiler: Inhalt:

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, ff, 13, fffff802c8a76522}

Probably caused by : ntkrnlmp.exe ( nt!PoIdle+3f2 )

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

3: 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: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000013, 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: fffff802c8a76522, address which referenced memory

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


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000000

CURRENT_IRQL: 0

FAULTING_IP:
nt!PoIdle+3f2
fffff802`c8a76522 ff15a06c3800 call qword ptr [nt!_imp_HalRequestIpi (fffff802`c8dfd1c8)]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFF99008113EFB0

TRAP_FRAME: ffff990081137970 -- (.trap 0xffff990081137970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=ffff990081137b70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802c8a76522 rsp=ffff990081137b00 rbp=ffff990081137c00
r8=0000000000000000 r9=ffff990081137b70 r10=0000000000000000
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!PoIdle+0x3f2:
fffff802`c8a76522 ff15a06c3800 call qword ptr [nt!_imp_HalRequestIpi (fffff802`c8dfd1c8)] ds:fffff802`c8dfd1c8=00000000003dfc38
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff802c8b962a9 to fffff802c8b8af70

STACK_TEXT:
ffff9900`81137828 fffff802`c8b962a9 : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`00000013 : nt!KeBugCheckEx
ffff9900`81137830 fffff802`c8b9487d : ffff9900`8111f180 ffffbf87`f332e1f8 00000000`00000000 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69
ffff9900`81137970 fffff802`c8a76522 : 00000000`00000003 00000000`00000002 ffffbf87`00000001 00000000`00000000 : nt!KiPageFault+0x23d
ffff9900`81137b00 fffff802`c8b8dfec : ffffffff`00000000 ffff9900`8111f180 ffff9900`8112bd80 ffffbf87`f57cf080 : nt!PoIdle+0x3f2
ffff9900`81137c60 00000000`00000000 : ffff9900`81138000 ffff9900`81132000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PoIdle+3f2
fffff802`c8a76522 ff15a06c3800 call qword ptr [nt!_imp_HalRequestIpi (fffff802`c8dfd1c8)]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!PoIdle+3f2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 58dee9f6

IMAGE_VERSION: 10.0.15063.138

BUCKET_ID_FUNC_OFFSET: 3f2

FAILURE_BUCKET_ID: AV_nt!PoIdle

BUCKET_ID: AV_nt!PoIdle

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!poidle

FAILURE_ID_HASH: {0f00f4f4-fc66-441c-10bf-8ccc2952f11b}

Followup: MachineOwner

 

Bei DriveControlerlInfo wird angezeigt, dass TRIM nicht unterstützt wird. Das sollte es aber, da alle Voraussetzungen dazu vorhanden sein sollten.
Erstelle dazu bitte einen Screenshot beider SSDs mit AS SSD Benchmark.
http://alex-is.de/PHP/fusion/downloads.php?download_id=9
Der sieht so aus: http://pic.sysprofile.de/images/s8519671.png
Womöglich stimmt etwas mit einer SSD nicht.

 

Spoiler: System SSD

Spoiler: 2. SSD

 

Hab noch ein Bluescreen bekommen:

Spoiler: Bluescreen Viewer

Spoiler: Crash Dump

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 18.04.2017 18:37:11 your computer crashed
crash dump file: C:\Windows\Minidump\041817-5578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x7F (0x8, 0xFFFFB3818911CBF0, 0xC1B30FC1, 0xFFFFF802FE6B8F02)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Spoiler: Windbg

Response Time (ms) Location
Deferred srv*C:\DbgSymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\DbgSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff802`fe613000 PsLoadedModuleList = 0xfffff802`fe95f5a0
Debug session time: Tue Apr 18 18:37:11.578 2017 (UTC + 2:00)
System Uptime: 0 days 1:14:27.278
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, ffffb3818911cbf0, c1b30fc1, fffff802fe6b8f02}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b3 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffb3818911cbf0
Arg3: 00000000c1b30fc1
Arg4: fffff802fe6b8f02

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff802fe78a2a9 to fffff802fe77ef70

STACK_TEXT:
ffffb381`8911caa8 fffff802`fe78a2a9 : 00000000`0000007f 00000000`00000008 ffffb381`8911cbf0 00000000`c1b30fc1 : nt!KeBugCheckEx
ffffb381`8911cab0 fffff802`fe7880f3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb381`8911cbf0 fffff802`fe6b8f02 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb3
00000000`c1b30fc1 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x72


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b3
fffff802`fe7880f3 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 58dee9f6

IMAGE_VERSION: 10.0.15063.138

BUCKET_ID_FUNC_OFFSET: b3

FAILURE_BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort

BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7f_8_nt!kidoublefaultabort

FAILURE_ID_HASH: {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}

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

 

Meine Praxiserfahrung zeigt mir das der IRQL-Fehler zu 99% am Speicher liegt. Der Memtest zeigte hierbei keine Fehler. Auch sollte man alle Platten außer der zu installierenden und Cardreader abstecken

 

Noch eins. Ich mache keine installationen momentan.

Spoiler: WinDbg

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {ffffdd01226c2890, cfb210d73797, ffff304def28c868, 0}

Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: ffffdd01226c2890, Actual security check cookie from the stack
Arg2: 0000cfb210d73797, Expected security check cookie
Arg3: ffff304def28c868, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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


DEFAULT_BUCKET_ID: GS_FALSE_POSITIVE_MISSING_GSFRAME

SECURITY_COOKIE: Expected 0000cfb210d73797 found ffffdd01226c2890

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xF7

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFFDD01226C9FB0

LAST_CONTROL_TRANSFER: from fffff80139fe95c5 to fffff80139f7af70

STACK_TEXT:
ffffdd01`226c2848 fffff801`39fe95c5 : 00000000`000000f7 ffffdd01`226c2890 0000cfb2`10d73797 ffff304d`ef28c868 : nt!KeBugCheckEx
ffffdd01`226c2850 fffff801`39e66ed2 : 00000000`00000001 00000000`003bce41 00000000`00000000 00000000`00000001 : nt!_report_gsfailure+0x25
ffffdd01`226c2890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0x8d2


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_report_gsfailure+25
fffff801`39fe95c5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!_report_gsfailure+25

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 58dee9f6

IMAGE_VERSION: 10.0.15063.138

BUCKET_ID_FUNC_OFFSET: 25

FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!_report_gsfailure

BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!_report_gsfailure

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xf7_missing_gsframe_nt!_report_gsfailure

FAILURE_ID_HASH: {82d2c1b5-b0cb-60a5-9a5d-78c8c4284f84}

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

 

Der Ram Speicher oder der Festplatten speicher? es sah für mich aus als waere die HDD nicht mehr ganz so gesund... sollte ich mir eine neue kaufen?

 

Noch eins. Ich habe aber gemerkt das fast immer alle Einstellungen die ich auf Teamspeak vorgenommen habe nicht mehr da sind. Und laut dem Bericht ist Teamspeak an irgendwas schuld. das war schonmal so vor der neuinstalation.

Spoiler: Dump File

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80317c76827, Address of the instruction which caused the bugcheck
Arg3: ffffbd006096b0d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

FAULTING_IP:
nt!NtDelayExecution+17
fffff803`17c76827 0084c90f84ce5b add byte ptr [rcx+rcx*8+5BCE840Fh],al

CONTEXT: ffffbd006096b0d0 -- (.cxr 0xffffbd006096b0d0;r)
rax=ffffd302dc955086 rbx=ffffd302dc955080 rcx=0000000000000000
rdx=0000002f9436fcd0 rsi=0000000000000064 rdi=0000000000000000
rip=fffff80317c76827 rsp=ffffbd006096bad0 rbp=ffffbd006096bb80
r8=0000002f916f5000 r9=0000000000000000 r10=fffff80317c76810
r11=0000000000136b40 r12=0000000000000000 r13=0000000000000000
r14=0000002f9436fcd0 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!NtDelayExecution+0x17:
fffff803`17c76827 0084c90f84ce5b add byte ptr [rcx+rcx*8+5BCE840Fh],al ds:002b:00000000`5bce840f=??
Last set context:
rax=ffffd302dc955086 rbx=ffffd302dc955080 rcx=0000000000000000
rdx=0000002f9436fcd0 rsi=0000000000000064 rdi=0000000000000000
rip=fffff80317c76827 rsp=ffffbd006096bad0 rbp=ffffbd006096bb80
r8=0000002f916f5000 r9=0000000000000000 r10=fffff80317c76810
r11=0000000000136b40 r12=0000000000000000 r13=0000000000000000
r14=0000002f9436fcd0 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!NtDelayExecution+0x17:
fffff803`17c76827 0084c90f84ce5b add byte ptr [rcx+rcx*8+5BCE840Fh],al ds:002b:00000000`5bce840f=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x3B

PROCESS_NAME: ts3client_win6

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

MISALIGNED_IP:
nt!NtDelayExecution+17
fffff803`17c76827 0084c90f84ce5b add byte ptr [rcx+rcx*8+5BCE840Fh],al

LAST_CONTROL_TRANSFER: from fffff8031797fe13 to fffff80317c76827

STACK_TEXT:
ffffbd00`6096bad0 fffff803`1797fe13 : ffffd302`dc955080 0000002f`9168e000 ffffffff`fff0bdc0 ffffd302`dc4d3c50 : nt!NtDelayExecution+0x17
ffffbd00`6096bb00 00007fff`883b5a34 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000002f`9436fca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`883b5a34


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff803178781b8 - nt!MiResolvePageTablePage+3b8
[ f6:85 ]
fffff803178781d8-fffff803178781dc 5 bytes - nt!MiResolvePageTablePage+3d8 (+0x20)
[ df be 7d fb f6:bf 70 e1 c2 85 ]
6 errors : !nt (fffff803178781b8-fffff803178781dc)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

STACK_COMMAND: .cxr 0xffffbd006096b0d0 ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_large

FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------