Suspected BUG: Crashing Windows 10 when indexing and hibernating

I'm on the latest Logos beta 29.0.14 and Windows 10.

I believe if Logos is indexing and I close my laptop lid to hibernate it, next time I turn on the laptop Windows 10 will restart. In other words, I think Logos is causing my Windows to crash.

How can I check whether this is the reason why my Windows crashes every so often when being hibernated?

Find more posts tagged with

Comments

Dave Hooton

Windows Event Viewer > Windows Logs > System. Find an event with the Date/time of the hibernation, double-click it and click Copy. Paste into your forum reply and erase any personal info.

You might look at the Application events (above system).

https://community.logos.com/discussion/comment/1275244#Comment_1275244

Thanks Dave. Found these two events around the time of the hibernation / restart, under System:

And this one under Application:

Dave Hooton

https://community.logos.com/discussion/comment/1275265#Comment_1275265

Your screenshots are blurry and cannot be enlarged. Please do as I requested and double-click the event to open another window and then click Copy. That can be pasted into your forum reply after erasing any personal info.

https://community.logos.com/discussion/comment/1275351#Comment_1275351

Log Name:      System
Source:        EventLog
Date:          10/18/2023 11:00:34 PM
Event ID:      6008
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-GCBRS78
Description:
The previous system shutdown at 10:33:25 PM on ‎10/‎18/‎2023 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2023-10-19T03:00:34.3118268Z" />
    <EventRecordID>201957</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>DESKTOP-GCBRS78</Computer>
    <Security />
</System>
<EventData>
    <Data>10:33:25 PM</Data>
    <Data>‎10/‎18/‎2023</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>646469</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>E7070A00030012001600210019001603E7070A00040013000200210019001603DC0500003C00000001000000DC050000010000001E0000000000000000000000</Binary>
</EventData>
</Event>

============

Log Name:      System
Source:        Application Popup
Date:          10/18/2023 10:59:58 PM
Event ID:      56
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-GCBRS78
Description:
The description for Event ID 56 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ACPI
0

The message resource is present but the message was not found in the message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Popup" Guid="{47bfa2b7-bd54-4fac-b70b-29021084ca8f}" EventSourceName="Application Popup" />
    <EventID Qualifiers="49156">56</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2023-10-19T02:59:58.4930082Z" />
    <EventRecordID>201961</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="144" />
    <Channel>System</Channel>
    <Computer>DESKTOP-GCBRS78</Computer>
    <Security />
</System>
<EventData>
    <Data>
    </Data>
    <Data>ACPI</Data>
    <Data>0</Data>
    <Binary>000000000300280000000000380004C000000000380004C000000000000000000000000000000000</Binary>
</EventData>
</Event>

=========

Log Name:      Application
Source:        SetupARService
Date:          10/18/2023 11:00:36 PM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-GCBRS78
Description:
Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.
   at SetupAfterRebootService.SetupARService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SetupARService" />
    <EventID Qualifiers="0">0</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2023-10-19T03:00:36.3723395Z" />
    <EventRecordID>100868</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-GCBRS78</Computer>
    <Security />
</System>
<EventData>
    <Data>Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.
   at SetupAfterRebootService.SetupARService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)</Data>
</EventData>
</Event>

Dave Hooton

https://community.logos.com/discussion/comment/1275366#Comment_1275366

What is your Hibernate setting and is indexing interrupted when Hibernate comes on?

https://community.logos.com/discussion/comment/1275382#Comment_1275382

My theory is that this unexpected shutdown happens during hibernation because the Logos indexer is running and it got interrupted somehow. I'm 90% sure this was the reason for the recent unexpected shutdowns (happened more than once).

This should allowed and supported, right? To hibernate the machine while the indexer is running, and have the indexing pick back up where it left off when the machine comes back on. I'm 99% sure this was OK before.

I'm not sure what your question means (What is your Hibernate setting)? Where do I look to answer your question?

Dave Hooton

https://community.logos.com/discussion/comment/1275400#Comment_1275400

My theory is that this unexpected shutdown happens during hibernation because the Logos indexer is running and it got interrupted somehow. I'm 90% sure this was the reason for the recent unexpected shutdowns (happened more than once).

This should allowed and supported, right? To hibernate the machine while the indexer is running, and have the indexing pick back up where it left off when the machine comes back on. I'm 99% sure this was OK before.

I'm not sure what your question means (What is your Hibernate setting)? Where do I look to answer your question?

Does it hibernate after a set time (as with Sleep settings)? Or do you Hibernate manually during indexing (have you tried that?)?

https://community.logos.com/discussion/comment/1275562#Comment_1275562

I usually hibernate by closing the laptop lid. Indexing was running and I didn't have time to wait for it to finish. I suspect that was crashing Windows.

Dave Hooton

https://community.logos.com/discussion/comment/1275576#Comment_1275576

I would first Pause indexing (and not necessarily hibernate).

nancy irena

Experiencing a critical issue – suspected bug causing system crashes on Windows 10 during indexing and hibernation. Seeking urgent assistance from the community or Essential Objects support to address this matter promptly. Any insights or potential solutions would be highly appreciated. Thank you for your prompt attention to this concern.