Share via

Event IDs 41 and 1001 issue

Anonymous
2025-01-02T18:16:55+00:00

My computer has started rebooting when I place it in sleep or lock mode, but not all the time. It doesn't reboot while I'm working. Below is the error Event log (ID 1001):

Log Name: System

Source: Microsoft-Windows-WER-SystemErrorReporting

Date: 1/2/2025 7:50:29 AM

Event ID: 1001

Task Category: None

Level: Error

Keywords:

User: SYSTEM

Computer: XPS-720

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffa20135817580, 0x0000000000000011, 0xffffa20135817580, 0x0000000000000002). A dump was saved in: C:\Windows\Minidump\010225-17296-01.dmp. Report Id: 034a6f64-be22-4d2b-aa89-db2bd24a2533.

Event Xml:

1001

1

2

0

0

0x8000000000000000

62202

System

XPS-720

0x00000050 (0xffffa20135817580, 0x0000000000000011, 0xffffa20135817580, 0x0000000000000002)

C:\Windows\Minidump\010225-17296-01.dmp

034a6f64-be22-4d2b-aa89-db2bd24a2533

Below is the Critical log (ID 41):

System

  • Provider

[ Name] Microsoft-Windows-Kernel-Power

[ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID 41

Version 9

Level 1

Task 63

Opcode 0

Keywords 0x8000400000000002

  • TimeCreated

[ SystemTime] 2025-01-02T13:50:19.6411963Z

EventRecordID 62122

Correlation

  • Execution

[ ProcessID] 4

[ ThreadID] 8

Channel System

Computer XPS-720

  • Security

[ UserID] S-1-5-18

  • EventData BugcheckCode 80 BugcheckParameter1 0xffffa20135817580 BugcheckParameter2 0x0 BugcheckParameter3 0x0 BugcheckParameter4 0x0 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress true SystemSleepTransitionsToOn 0 CsEntryScenarioInstanceId 1 BugcheckInfoFromEFI true CheckpointStatus 0 CsEntryScenarioInstanceIdV2 1 LongPowerButtonPressDetected false LidReliability false InputSuppressionState 0 PowerButtonSuppressionState 0 LidState 3

I've run a few tests on my memory which show no issues. Also, this started happening when I installed Windows 11 update KB5046732.

Any guidance will be appreciated,

sms1295

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

22 answers

Sort by: Most helpful
  1. DaveM121 870.6K Reputation points Independent Advisor
    2025-01-03T08:02:25+00:00

    All your minidump files jsut indicate generic RAM corruption errors, nothing specific.

    However, I do note that in every minidump file, it is the iCloud app that is running when your PC crashes, it is possible that app is corrupt and may be a contributory factor to the crashes.

    0 comments No comments
  2. Anonymous
    2025-01-02T20:30:44+00:00

    There were four more files. I've uploaded them to the same google folder and the link is below:

    https://drive.google.com/drive/folders/1_P1J9KRVGW16KyOeZu5YxyDGYgTyb36I?usp=sharing

    Thanks for your help,

    sms1295

    0 comments No comments
  3. DaveM121 870.6K Reputation points Independent Advisor
    2025-01-02T19:40:12+00:00

    That one minidump file just indicated generic errors, nothing specific, if this is an on-going problem, do you have any more minidump files available that you can upload for analysis.

    0 comments No comments
  4. Anonymous
    2025-01-02T19:33:40+00:00
    0 comments No comments
  5. DaveM121 870.6K Reputation points Independent Advisor
    2025-01-02T18:49:44+00:00

    Hi, I am Dave, I will help you with this.

    Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    0 comments No comments