Liebe Leute,
ich habe ein Problem: Mein PC freezt bei nicht näher bestimmten Tätigkeiten. Manchmal surfe ich einfach nur, manchmal spiele ich League of Legends. Ich habe schon einige Tests gemacht:
- Memtest, 4x durchgelaufen, keine Fehler
- Checkdisk, keine Fehler
- Prime95, etwa 3 Stunden, keine Fehler
- Grafikkartentreiber neu aufgesetzt (mit ddu entfernt)
- directx-Grakaprüfung
- stundenlang das Internet durchforstet
- Temperaturen beobachtet
- Graka FurMark Stresstest 20 Minuten, kein Absturz.
Teilweise spiele ich zwei Tage ohne Zwischenfall die unterschiedlichsten Spiele: Subnautica, LoL, Overwatch, Starcraft, RimWorld und andere und nichts passiert.
Dann wieder mehrere Male hintereinander...
Windbg gibt mir bei einem Dump eines Freezes folgende Analyse, falls das jemand kapiert, ich leider nicht. Ich habe nur noch eine Analyse, die is kürzer, daher als erstes.
Ich danke euch schonmal für eure Geduld!
Liebe Grüße!
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff801b526b348
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.296 (WinBuild.160101.0800)
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P2.50
BIOS_DATE: 08/16/2010
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: X58 Extreme
BASEBOARD_VERSION:
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff801b526b348
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 8
CPU_MHZ: a6b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 1a
CPU_STEPPING: 4
CPU_MICROCODE: 6,1a,4,0 (F,M,S,R) SIG: 12'00000000 (cache) 12'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: PAULS
ANALYSIS_SESSION_TIME: 06-25-2017 18:04:19.0976
ANALYSIS_VERSION: 10.0.14321.1024 x86fre
LAST_CONTROL_TRANSFER: from fffff801b501f6af to fffff801b4ff6310
STACK_TEXT:
fffff801`b80628d8 fffff801`b501f6af : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`b526b348 : nt!KeBugCheckEx
fffff801`b80628e0 fffff801`b4ee0db9 : 0000013f`f7269b85 fffff801`b4290180 00000000`00007b8b 00000000`00000006 : nt!KeAccumulateTicks+0x13cc5f
fffff801`b8062940 fffff801`b4e11676 : 0000013f`f7264266 00000000`ffffffff fffff801`b8062d10 fffff801`b4e61460 : nt!KeClockInterruptNotify+0x599
fffff801`b8062c50 fffff801`b4f27255 : fffff801`b4e613b0 fffff801`b4f27255 fffff801`b4e613b0 ffffbd80`d5ce1501 : hal!HalpTimerClockInterrupt+0x56
fffff801`b8062c80 fffff801`b4ff79aa : fffff801`b8062d90 fffff801`b4e613b0 000000f5`741b4325 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`b8062cc0 fffff801`b4ff7df7 : fffff801`b8062d20 fffff801`b4ff7e04 00000000`00000001 00000000`ffffffff : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`b8062d10 fffff809`0bb98d3a : fffff809`0bba1ad9 fffff801`b8062f40 fffff801`b4edd4f1 fffff801`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`b8062ea8 fffff809`0bba1ad9 : fffff801`b8062f40 fffff801`b4edd4f1 fffff801`00000000 00000000`00000000 : storahci!IsPortStartCapable+0x22
fffff801`b8062eb0 fffff809`0b4fd254 : 000000f5`740ef800 ffff8304`67fc67a0 fffff801`b8062f40 fffff809`0a7c167f : storahci!AhciHwInterrupt+0x99
fffff801`b8062ee0 fffff801`b4f27255 : ffffbd80`d5bff3c0 fffff801`b4ec6abf 00000000`00000000 fffff801`b4290180 : storport!RaidpAdapterInterruptRoutine+0x64
fffff801`b8062f40 fffff801`b4ff75ac : fffff801`b8054880 ffffbd80`d5bff3c0 ffffbd80`d5bff3c0 ffff8304`66277200 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`b8062f80 fffff801`b4ff72a7 : ffff8304`67ff7060 00000000`00000000 fffff801`b4290ba0 fffff801`00000000 : nt!KiScanInterruptObjectList+0x13c
fffff801`b8054800 fffff809`0d383d52 : fffff809`0d381360 00000000`00000000 00000000`00000000 ffff8304`69670010 : nt!KiChainedDispatch+0x37
fffff801`b8054998 fffff809`0d381360 : 00000000`00000000 00000000`00000000 ffff8304`69670010 fffff801`b4290180 : intelppm!C1Halt+0x2
fffff801`b80549a0 fffff801`b4ee1c19 : 00000000`00000000 00000000`00000068 00000000`00000000 00000000`00000228 : intelppm!AcpiCStateIdleExecute+0x20
fffff801`b80549d0 fffff801`b4ee1473 : 00000000`00000000 00000000`00000000 00000000`00000004 01d2dd95`b1f56b0f : nt!PpmIdleExecuteTransition+0x619
fffff801`b8054c40 fffff801`b4ff938c : 00000000`00000000 fffff801`b4290180 fffff801`b5283a40 ffff8304`6a436080 : nt!PoIdle+0x343
fffff801`b8054da0 00000000`00000000 : fffff801`b8055000 fffff801`b804f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff801b4f7a533-fffff801b4f7a534 2 bytes - nt!MiAllocatePoolPages+107
[ fb f6:fd fa ]
fffff801b4f7a560 - nt!MiAllocatePoolPages+134 (+0x2d)
[ f6:fa ]
fffff801b510a374-fffff801b510a375 2 bytes - nt!ExFreePoolWithTag+364
[ fb f6:fd fa ]
5 errors : !nt (fffff801b4f7a533-fffff801b510a375)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
TARGET_TIME: 2017-06-05T00:52:15.000Z
OSBUILD: 15063
OSSERVICEPACK: 296
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-28 01:52:30
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.296
ANALYSIS_SESSION_ELAPSED_TIME: 38c9
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
ich habe ein Problem: Mein PC freezt bei nicht näher bestimmten Tätigkeiten. Manchmal surfe ich einfach nur, manchmal spiele ich League of Legends. Ich habe schon einige Tests gemacht:
- Memtest, 4x durchgelaufen, keine Fehler
- Checkdisk, keine Fehler
- Prime95, etwa 3 Stunden, keine Fehler
- Grafikkartentreiber neu aufgesetzt (mit ddu entfernt)
- directx-Grakaprüfung
- stundenlang das Internet durchforstet
- Temperaturen beobachtet
- Graka FurMark Stresstest 20 Minuten, kein Absturz.
Teilweise spiele ich zwei Tage ohne Zwischenfall die unterschiedlichsten Spiele: Subnautica, LoL, Overwatch, Starcraft, RimWorld und andere und nichts passiert.
Dann wieder mehrere Male hintereinander...
Windbg gibt mir bei einem Dump eines Freezes folgende Analyse, falls das jemand kapiert, ich leider nicht. Ich habe nur noch eine Analyse, die is kürzer, daher als erstes.
Ich danke euch schonmal für eure Geduld!
Liebe Grüße!
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff801b526b348
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.296 (WinBuild.160101.0800)
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P2.50
BIOS_DATE: 08/16/2010
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: X58 Extreme
BASEBOARD_VERSION:
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff801b526b348
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 8
CPU_MHZ: a6b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 1a
CPU_STEPPING: 4
CPU_MICROCODE: 6,1a,4,0 (F,M,S,R) SIG: 12'00000000 (cache) 12'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: PAULS
ANALYSIS_SESSION_TIME: 06-25-2017 18:04:19.0976
ANALYSIS_VERSION: 10.0.14321.1024 x86fre
LAST_CONTROL_TRANSFER: from fffff801b501f6af to fffff801b4ff6310
STACK_TEXT:
fffff801`b80628d8 fffff801`b501f6af : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`b526b348 : nt!KeBugCheckEx
fffff801`b80628e0 fffff801`b4ee0db9 : 0000013f`f7269b85 fffff801`b4290180 00000000`00007b8b 00000000`00000006 : nt!KeAccumulateTicks+0x13cc5f
fffff801`b8062940 fffff801`b4e11676 : 0000013f`f7264266 00000000`ffffffff fffff801`b8062d10 fffff801`b4e61460 : nt!KeClockInterruptNotify+0x599
fffff801`b8062c50 fffff801`b4f27255 : fffff801`b4e613b0 fffff801`b4f27255 fffff801`b4e613b0 ffffbd80`d5ce1501 : hal!HalpTimerClockInterrupt+0x56
fffff801`b8062c80 fffff801`b4ff79aa : fffff801`b8062d90 fffff801`b4e613b0 000000f5`741b4325 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`b8062cc0 fffff801`b4ff7df7 : fffff801`b8062d20 fffff801`b4ff7e04 00000000`00000001 00000000`ffffffff : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`b8062d10 fffff809`0bb98d3a : fffff809`0bba1ad9 fffff801`b8062f40 fffff801`b4edd4f1 fffff801`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`b8062ea8 fffff809`0bba1ad9 : fffff801`b8062f40 fffff801`b4edd4f1 fffff801`00000000 00000000`00000000 : storahci!IsPortStartCapable+0x22
fffff801`b8062eb0 fffff809`0b4fd254 : 000000f5`740ef800 ffff8304`67fc67a0 fffff801`b8062f40 fffff809`0a7c167f : storahci!AhciHwInterrupt+0x99
fffff801`b8062ee0 fffff801`b4f27255 : ffffbd80`d5bff3c0 fffff801`b4ec6abf 00000000`00000000 fffff801`b4290180 : storport!RaidpAdapterInterruptRoutine+0x64
fffff801`b8062f40 fffff801`b4ff75ac : fffff801`b8054880 ffffbd80`d5bff3c0 ffffbd80`d5bff3c0 ffff8304`66277200 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`b8062f80 fffff801`b4ff72a7 : ffff8304`67ff7060 00000000`00000000 fffff801`b4290ba0 fffff801`00000000 : nt!KiScanInterruptObjectList+0x13c
fffff801`b8054800 fffff809`0d383d52 : fffff809`0d381360 00000000`00000000 00000000`00000000 ffff8304`69670010 : nt!KiChainedDispatch+0x37
fffff801`b8054998 fffff809`0d381360 : 00000000`00000000 00000000`00000000 ffff8304`69670010 fffff801`b4290180 : intelppm!C1Halt+0x2
fffff801`b80549a0 fffff801`b4ee1c19 : 00000000`00000000 00000000`00000068 00000000`00000000 00000000`00000228 : intelppm!AcpiCStateIdleExecute+0x20
fffff801`b80549d0 fffff801`b4ee1473 : 00000000`00000000 00000000`00000000 00000000`00000004 01d2dd95`b1f56b0f : nt!PpmIdleExecuteTransition+0x619
fffff801`b8054c40 fffff801`b4ff938c : 00000000`00000000 fffff801`b4290180 fffff801`b5283a40 ffff8304`6a436080 : nt!PoIdle+0x343
fffff801`b8054da0 00000000`00000000 : fffff801`b8055000 fffff801`b804f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff801b4f7a533-fffff801b4f7a534 2 bytes - nt!MiAllocatePoolPages+107
[ fb f6:fd fa ]
fffff801b4f7a560 - nt!MiAllocatePoolPages+134 (+0x2d)
[ f6:fa ]
fffff801b510a374-fffff801b510a375 2 bytes - nt!ExFreePoolWithTag+364
[ fb f6:fd fa ]
5 errors : !nt (fffff801b4f7a533-fffff801b510a375)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
TARGET_TIME: 2017-06-05T00:52:15.000Z
OSBUILD: 15063
OSSERVICEPACK: 296
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-28 01:52:30
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.296
ANALYSIS_SESSION_ELAPSED_TIME: 38c9
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
