Mehrere Blue Screens nach Neuinstallation

Diskutiere Mehrere Blue Screens nach Neuinstallation im Windows 10 Forum im Bereich Microsoft Community; Hallo Zusammen, ich habe mir neulich einen neuen Rechner zusammengebaut. Verbaut ist: AMD Ryzen 5 2600 6x 3.40GHz So.AM4 BOX 16GB (2x...

MS-User

Threadstarter
Dabei seit
20.09.2016
Beiträge
94.184
Hallo Zusammen,


ich habe mir neulich einen neuen Rechner zusammengebaut.

Verbaut ist:

AMD Ryzen 5 2600 6x 3.40GHz So.AM4 BOX

16GB (2x 8192MB) G.Skill Aegis DDR4-3200 DIMM CL16-18-18-38 Dual Kit

120GB Crucial BX500 2.5" (6.4cm) SATA 6Gb/s 3D-NAND TLC (CT120BX500SSD1)

8GB ASRock Radeon RX 5700 Challenger D 8G OC Aktiv PCIe 4.0 x16 1xHDMI / 3xDisplayPort (Retail)550 Watt Corsair CX Series CX550M Modular 80+ Bronze

GIGABYTE AORUS B450 Elite


Nach der Neuinstallation von Windows10 kamen einfach mehrere Blue Screens immer mit verschiedenen Meldungen.

Die Hardwarekomponenten habe ich alle einem Stresstest unterzogen, dort sind keine Fehler gemeldet.

Auch die Windows Diagnose ist ohne Fehler durchgelaufen.

Die neusten Updates von Windows sind auch auf dem Rechner installiert.

Auch die BIOS Version ist die aktuelle von Aorus Gigabyte.

Hier die OneDrive Links zu den Minidumps:

051020-5718-01.dmp

051020-6218-01.dmp

051120-8984-01.dmp

051120-9156-01.dmp


Hier mal eine der Minidumps:

Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`62200000 PsLoadedModuleList = 0xfffff803`62648150
Debug session time: Mon May 11 16:25:05.841 2020 (UTC + 2:00)
System Uptime: 0 days 0:43:26.562
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000065`3895b018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff803`623c2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe481`c3ad8b10=0000000000000133
10: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

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: fffff80362773358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
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 *
* *
*

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-S70IU0B

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 28

Key : Analysis.Memory.CommitPeak.Mb
Value: 61

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80362773358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (
!blackboxbsd)


BLACKBOXNTFS: 1 (
!blackboxntfs)


BLACKBOXPNP: 1 (
!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: msedge.exe

TRAP_FRAME: ffffbf8615822190 --
(.trap 0xffffbf8615822190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000aa4b0005 rbx=0000000000000000 rcx=0000000000000080
rdx=0000000000000080 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803623ca277 rsp=ffffbf8615822320 rbp=0000000000000002
r8=0000000000000080 r9=0000000000000000 r10=ffffa78000005570
r11=0000000000000057 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!ExpInterlockedPopEntrySListFault:
fffff803`623ca277 498b08 mov rcx,qword ptr [r8] ds:00000000`00000080=????????????????
Resetting default scope

STACK_TEXT:
ffffe481`c3ad8b08 fffff803`6243d8b1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`62773358 : nt!KeBugCheckEx
ffffe481`c3ad8b10 fffff803`622b90a7 : 000005f1`2b68aaaf ffffe481`c3a80180 00000000`00000286 ffffbf86`15821e20 : nt!KeAccumulateTicks+0x181641
ffffe481`c3ad8b70 fffff803`6215f291 : 00000000`00000000 ffff9408`1e2d0700 ffffbf86`15821ea0 ffff9408`1e2d07b0 : nt!KeClockInterruptNotify+0xc07
ffffe481`c3ad8f30 fffff803`6222cc75 : ffff9408`1e2d0700 fffff803`62269347 00000000`00000000 00000000`00000000 : hal!HalRequestSoftwareInterrupt+0x171
ffffe481`c3ad8f60 fffff803`623c3e1a : ffffbf86`15821ea0 ffff9408`1e2d0700 fffff803`6257a250 ffff9408`1e2d0700 : nt!KiCallInterruptServiceRoutine+0xa5
ffffe481`c3ad8fb0 fffff803`623c4387 : 00000000`aa490005 ffffbf86`15821ea0 ffff9408`1e2d0700 00000000`00000003 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffbf86`15821e20 fffff803`623d42c3 : ffffffff`ffffffd2 fffff803`6239d2b2 ffff0c87`0c55e770 00000000`00000003 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffbf86`15821fb0 fffff803`623d0503 : 00000000`aa490005 ffffbf86`15822210 ffff9408`1e2d0700 ffffbf86`15822288 : nt!KiExceptionDispatch+0xc3
ffffbf86`15822190 fffff803`623ca277 : 00000000`00000000 fffff803`622ce5e1 1a000001`71af1867 000058f7`08103000 : nt!KiPageFault+0x443
ffffbf86`15822320 fffff803`622ce5e1 : 1a000001`71af1867 000058f7`08103000 1a000001`71af1867 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
ffffbf86`15822330 fffff803`622cdf31 : fffff803`6266a400 00000000`00000057 00000000`00000057 00000000`00000000 : nt!MiGetPage+0xf1
ffffbf86`15822410 fffff803`622cbc5a : ffffbf86`15822780 00000000`00000000 00000000`00000001 ffffe481`c3879111 : nt!MiGetPageChain+0x181
ffffbf86`15822600 fffff803`622cb738 : 00000000`00000000 0000407b`00000000 00000000`00000004 00000000`00000001 : nt!MiResolvePrivateZeroFault+0x14a
ffffbf86`15822720 fffff803`622cb002 : fffff5fa`d01eee58 00000000`00000000 00000000`00000000 00000000`00000002 : nt!MiResolveDemandZeroFault+0x218
ffffbf86`15822810 fffff803`622c8fc9 : 00000000`00000111 00000000`00000004 00000000`c0000016 0000407b`b9661000 : nt!MiDispatchFault+0x982
ffffbf86`15822960 fffff803`623d041e : 00000000`00000002 ffffbf86`15822b80 00007ffd`e39439a0 ffffffff`ffdac4c0 : nt!MmAccessFault+0x169
ffffbf86`15822b00 00007ffd`dc98ba1b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000065`391fd4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`dc98ba1b


SYMBOL_NAME: nt!KeAccumulateTicks+181641

MODULE_NAME:
nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 181641

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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

10: kd> stack trace
Couldn't resolve error at 'tack trace'
10: kd> !blackboxbsd
Stream size mismatch (expected = 176, read = 168)
10: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 132336791117373201
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : SWD\DAFUPnPProvider\uuid:fa095ecc-e13e-40e7-8e6c-dc396fb7f080
VetoString :

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2001.2001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'



Über eine schnelle Beantwortung auf meine Fragen würde ich mich freuen.


Mit freundlichen Grüßen


Tim König
 
Thema:

Mehrere Blue Screens nach Neuinstallation

Mehrere Blue Screens nach Neuinstallation - Ähnliche Themen

Blackscreen beim zocken: Hallo, wie oben schon erwähnt wird beim zocken mein monitor schwarz und der pc startet neu. Bei WinDbg kam das raus: Microsoft (R) Windows...
BSOD KMODE_EXCEPTION_NOT_HANDLED in PpmPerfSelectProcessorState: Hi everyone! I was asked to investigate a KMODE_EXCEPTION_NOT_HANDLED BSOD on a Windows 10 system. Its current (minimal) configuration is...
Pc stürzt bei spielen ab: Guten Tag, Ich habe ungefähr vor 2 Wochen meinen Pc neu uns sauber aufgesetzt. Allerdings stürzt mein Pc bei Spielen mit mehr Leistung immer...
Nach Crash die Minidump File ausgelesen; was ist das Problem?: Ich hatte vor kurzen einen System Service Exeption Bluescreen, dabei habe ich die Crash File versucht auszulesen, aber selbst komme ich nicht...
BSOD bei vermeintlichem Treiberfehler (seit Jan 2020) verursacht durch ndis.sys+79ccb: Seit Jan 2020 bekomme ich häufig eine BSOD zu sehen. Neuere Netzwerktreiber lassen sich nicht installieren. Windows 10 sagt der aktuelle Treiber...

Sucheingaben

how to make money playing poker

,

casino action

,

poker dice

,
pooker dice
, indian casinos, pokCer straight, live cRasino online, black chip poker, black chip poketr, ellis island casino, pok$er usa, taj mahal casiCno, bravo poker, can you play 7poker with two players, can you play poker with two players, world series poker, world series pokeur, spa casino, casino in north carolina, c9asino in north carolina, strip popker sex, golden tiger casino, golden tiger cashino, stripper pokjer, mansion casino
Oben