Seneste forumindlæg
Køb / Salg
 * Uofficiel Black/White liste V3
Login / opret bruger

Forum \ Software \ Operativsystemer
Denne tråd er over 6 måneder gammel

Er du sikker på, at du har noget relevant at tilføje?

Windows crasher - hjælp til analyse af dump fil

Af Supporter Aspirant goldeneye | 16-01-2024 21:15 | 734 visninger | 3 svar, hop til seneste
Hej Fruens notebook (Lenovo Legion Pro) er helt umotiveret crashet 5 gange her i aften. Har fundet logfil og kørt WinDbg, men fatter intet af rapporten den smider ud. Kan nogle hjælpe? ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\mette\Downloads\michael\011624-13937-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff805`79000000 PsLoadedModuleList = 0xfffff805`79c134a0 Debug session time: Tue Jan 16 20:31:47.067 2024 (UTC + 1:00) System Uptime: 0 days 0:16:36.787 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........... Loading User Symbols PEB is paged out (Peb.Ldr = 0000000f`f52b2018). Type ".hh dbgerr001" for details Loading unloaded module list ................... For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff805`79416b00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff182`6ca1ddd0=000000000000003b 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff805a7bd7218, Address of the instruction which caused the BugCheck Arg3: fffff1826ca1e720, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1812 Key : Analysis.Elapsed.mSec Value: 10356 Key : Analysis.IO.Other.Mb Value: 3 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 31 Key : Analysis.Init.CPU.mSec Value: 218 Key : Analysis.Init.Elapsed.mSec Value: 139941 Key : Analysis.Memory.CommitPeak.Mb Value: 104 Key : Bugcheck.Code.LegacyAPI Value: 0x3b Key : Dump.Attributes.AsUlong Value: 808 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: AV_wmiacpi!WmiAcpiQueryWmiDataBlock Key : Failure.Hash Value: {11ae2119-7072-a9fd-ca6a-8294f5115ef4} Key : Hypervisor.Enlightenments.ValueHex Value: 1497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 4853999 Key : Hypervisor.Flags.ValueHex Value: 4a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 3f7 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff805a7bd7218 BUGCHECK_P3: fffff1826ca1e720 BUGCHECK_P4: 0 FILE_IN_CAB: 011624-13937-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x808 Kernel Generated Triage Dump CONTEXT: fffff1826ca1e720 -- (.cxr 0xfffff1826ca1e720)rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000rdx=000000000000004f rsi=ffffd103ee17dc01 rdi=0000000034415157 rip=fffff805a7bd7218 rsp=fffff1826ca1f140 rbp=ffffd103d9efd4c0 r8=0000000000000000 r9=000000000000001c r10=00000000ffffffff r11=0000000000000000 r12=fffff1826ca1f2f0 r13=ffffd103d9efd370 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246 wmiacpi!WmiAcpiQueryWmiDataBlock+0x108: fffff805`a7bd7218 41890f mov dword ptr [r15],ecx ds:002b:00000000`00000000=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: WmiPrvSE.exe STACK_TEXT: fffff182`6ca1f140 fffff805`789c642e : 00000000`00000000 ffffd103`e4df8010 fffffa2c`b3680002 fffff805`00000000 : wmiacpi!WmiAcpiQueryWmiDataBlock+0x108 fffff182`6ca1f1b0 fffff805`a7bd7a50 : ffffd103`e4df8010 ffffd103`e4df8010 ffffd103`e4df8010 fffff182`6ca1f2f0 : WMILIB!WmiSystemControl+0x41e fffff182`6ca1f2b0 fffff805`792ebef5 : 00000000`00000000 00000000`00000000 ffffd103`e4df8010 ffffd103`d9efd370 : wmiacpi!WmiAcpiSystemControlDispatch+0x80 fffff182`6ca1f2f0 fffff805`79764d3f : 00000000`00000000 ffffd103`e4df8010 ffffd103`d9efd370 fffff805`7979e3e2 : nt!IofCallDriver+0x55 fffff182`6ca1f330 fffff805`7979da69 : 00000000`00000000 fffff182`6ca1f4c0 00000000`00000000 ffffd103`e6581630 : nt!WmipForwardWmiIrp+0x14f fffff182`6ca1f3c0 fffff805`7979c310 : ffffc100`9a60f9b0 00000000`00000001 ffffd103`e4df8010 fffff805`79280284 : nt!WmipQueryAllData+0x1f1 fffff182`6ca1f590 fffff805`792ebef5 : ffffd103`e4df8010 fffff805`79742417 00000000`00000002 ffffd103`d59cbc60 : nt!WmipIoControl+0xc0 fffff182`6ca1f6e0 fffff805`79740060 : ffffd103`e4df8010 00000000`00000002 ffffd103`df18fe20 ffffd103`df18fe20 : nt!IofCallDriver+0x55 fffff182`6ca1f720 fffff805`79741a90 : ffffd103`e4df8010 00000000`00000048 fffff182`6ca1fb05 ffffd103`df18fe20 : nt!IopSynchronousServiceTail+0x1d0 fffff182`6ca1f7d0 fffff805`79741376 : 00000000`00000001 fffff182`6ca1fb20 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x700 fffff182`6ca1f9c0 fffff805`7942bbe8 : ffffd103`e1e9c080 0000000f`f557e188 fffff182`6ca1fa48 00000000`00000000 : nt!NtDeviceIoControlFile+0x56 fffff182`6ca1fa30 00007ffa`33baf454 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 0000000f`f557e1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`33baf454 SYMBOL_NAME: wmiacpi!WmiAcpiQueryWmiDataBlock+108 MODULE_NAME: wmiacpiIMAGE_NAME: wmiacpi.sysIMAGE_VERSION: 10.0.22621.1774 STACK_COMMAND: .cxr 0xfffff1826ca1e720 ; kb BUCKET_ID_FUNC_OFFSET: 108 FAILURE_BUCKET_ID: AV_wmiacpi!WmiAcpiQueryWmiDataBlock OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {11ae2119-7072-a9fd-ca6a-8294f5115ef4} Followup: MachineOwner ---------
--
#1
XPAction
Monsterbruger
16-01-2024 21:22

Rapporter til Admin
det er vel ikke den nye omtalte windows updatering som du har fået problemmer med.
--
#2
goldeneye
Supporter Aspirant
16-01-2024 21:34

Rapporter til Admin
#1 kan se at update KB5034123 blev installeret i går. Er det den du tænker på? Crashene startede her til aften, og kom alle ca. 6 minutter efter opstart kan jeg se i loggen. Jeg kom til efter det 5. crash, og så at der var en fejl på "avast secure browser", så den startede jeg med at afinstallere. Og maskinen er faktisk ikke crashet siden. Ku det være så enkelt?
--
#3
xectia
Juniorbruger
17-01-2024 07:30

Rapporter til Admin
VMI fejler, tag og kør en sfc eller dism i cmd og se om de hjælper. Det kunne også meget vel være en opdatering som #1 skriver. Når det er VMI, så havde jeg ikke fejlsøgt det store, windows er hæsligt at fikse når noget fejler. I de fleste tilfælde er en reinstall hurtigere. :)
--
=)

Opret svar til indlægget: Windows crasher - hjælp til analyse af dump fil

Grundet øget spam aktivitet fra gæstebrugere, er det desværre ikke længere muligt, at oprette svar som gæst.

Hvis du ønsker at deltage i debatten, skal du oprette en brugerprofil.

Opret bruger | Login
NYHEDSBREV
Afstemning