ultimamente ho dei crash, freeze e schermate blu ( rare )
l'ultima mentre giocavo a Dwarf fortess ( e scaricavo degli aggionramenti)
questo il dump
Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`07200000 PsLoadedModuleList = 0xfffff803`076480f0
Debug session time: Wed Sep 2 13:08:22.897 2020 (UTC + 1:00)
System Uptime: 0 days 1:08:19.672
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
.................................................. ..............
...
Loading User Symbols
.................................................. ..............
.............................
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
...................................
.....
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
2: 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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80307773358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
Unable to load image E:\SteamEtoshiba\steamapps\common\F1 2018\F1_2018.exe, Win32 error 0n2
*** WARNING: Unable to verify checksum for F1_2018.exe
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
TRAP_FRAME: ffffc7862ba3ea40 -- (.trap 0xffffc7862ba3ea40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffc7862ba3ec00
rdx=ffffc7862ba3ec20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803077ab3f0 rsp=ffffc7862ba3ebd0 rbp=ffffc7862ba3ed40
r8=ffffc90172715280 r9=0000000000000000 r10=0000fffff803077a
r11=ffffb8fb1dc00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!IopLiveDumpProcessCorralStateChange+0x28:
fffff803`077ab3f0 e8db93a9ff call nt!KeYieldProcessorEx (fffff803`072447d0)
Resetting default scope
Rispondi Citando