Windows 10: Periodic reboot with code 41 event 98 - Периодическая перезагрузка с кодом 41 событие 98

Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64

Copyright c Microsoft Corporation. All rights reserved.



Loading Dump File [C:\Users\user\Desktop\Синийєкран\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:

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

WARNING: .reload failed, module list may be incomplete

Debugger can not determine kernel base address

Windows 10 Kernel Version 18362 MP 2 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff801`4c000000 PsLoadedModuleList = 0xfffff801`4c448190

Debug session time: Wed Feb 26 13:33:15.314 2020 UTC + 2:00

System Uptime: 0 days 0:31:29.080

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

WARNING: .reload failed, module list may be incomplete

Debugger can not determine kernel base address

Loading Kernel Symbols

Missing image name, possible paged-out or corrupt data.

.*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - HRESULT 0x80004002


Loading unloaded module list

...Image path too long, possible corrupt data.

...Image path too long, possible corrupt data.

.Image path too long, possible corrupt data.

........

WARNING: .reload failed, module list may be incomplete

For analysis of this file, run !analyze -v

fffff801`4c1c1510 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff281`5f664b20=????????????????


Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\user\Desktop\Синий єкран\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:

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

WARNING: .reload failed, module list may be incomplete

Debugger can not determine kernel base address

Windows 10 Kernel Version 18362 MP 2 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff801`4c000000 PsLoadedModuleList = 0xfffff801`4c448190

Debug session time: Wed Feb 26 13:33:15.314 2020 UTC + 2:00

System Uptime: 0 days 0:31:29.080

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

WARNING: .reload failed, module list may be incomplete

Debugger can not determine kernel base address

Loading Kernel Symbols

Missing image name, possible paged-out or corrupt data.

.*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - HRESULT 0x80004002



Loading unloaded module list

...Image path too long, possible corrupt data.

...Image path too long, possible corrupt data.

.Image path too long, possible corrupt data.

........

WARNING: .reload failed, module list may be incomplete

For analysis of this file, run !analyze -v

fffff801`4c1c1510 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff281`5f664b20=????????????????

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



REFERENCE_BY_POINTER 18

Arguments:

Arg1: 0000000000000000, Object type of the object whose reference count is being lowered

Arg2: ffff83032cac3890, Object whose reference count is being lowered

Arg3: 0000000000000006, Reserved

Arg4: ffffffffffffffff, Reserved

The reference count of an object is illegal for the current state of the object.

Each time a driver uses a pointer to an object the driver calls a kernel routine

to increment the reference count of the object. When the driver is done with the

pointer the driver calls another kernel routine to decrement the reference count.

Drivers must match calls to the increment and decrement routines. This bugcheck

can occur because an object's reference count goes to zero while there are still

open handles to the object, in which case the fourth parameter indicates the number

of opened handles. It may also occur when the object's reference count drops below zero

whether or not there are open handles to the object, and in that case the fourth parameter

contains the actual value of the pointer references count.



Debugging Details:

------------------



***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 0



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on WIN-96S7BHPN3K4



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 0



Key : Analysis.Memory.CommitPeak.Mb

Value: 43



Key : Analysis.System

Value: CreateObject



Key : WER.CorruptModuleList

Value: 1





ADDITIONAL_XML: 1



BUGCHECK_CODE: 18



BUGCHECK_P1: 0



BUGCHECK_P2: ffff83032cac3890



BUGCHECK_P3: 6



BUGCHECK_P4: ffffffffffffffff



STACK_TEXT:

fffff281`5f664b18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff801`4c1c1510





SYMBOL_NAME: ANALYSIS_INCONCLUSIVE



MODULE_NAME: Unknown_Module



IMAGE_NAME: Unknown_Image



STACK_COMMAND: .thread ; .cxr ; kb



FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x18



OS_VERSION: 10.0.18362.1



BUILDLAB_STR: 19h1_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {e36791bb-b6fb-3b26-8593-b7183312f316}



Followup: MachineOwner

---------

:)

 

event 41

Hello,

The kernel power event ID 41 error occurs when the computer is shut down, or it restarts unexpectedly. Having said that, we highly suggest performing the troubleshooting steps in this article:

Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows.

If you have any other questions or concerns, feel free to share them with us here. Your input is very much welcome in our Community.

 

Event 41, Karnel - Power

Hello,

The Event 41 is used to report the unexpected shutting down of a device. For better assistance, we'd like to ask the following:

• What troubleshooting steps have you tried so far?
• Did you make any changes to your computer? If yes, can you tell us the changes?
  

Meanwhile, we recommend following the workaround on this link. The article
is about Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows.

We are looking forward to your reply.

 

Event 41, Karnel - Power

Sorry for very late response.

I tried Windows Memory diagnostic but Ram is okay, and i didn't make any changes to my computer.