Share via

Restart problem

Anonymous
2022-10-22T16:52:49+00:00

Hi, my computer has been restarting like once or twice a day for no reason but each time i couldn't witness it all i have is this :

Provider

[ Name] Microsoft-Windows-Kernel-Power

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

EventID 41

Version 8

Level 1

Task 63

Opcode 0

Keywords 0x8000400000000002

  • TimeCreated

[ SystemTime] 2022-10-22T14:50:29.4344075Z

EventRecordID 10546

Correlation

  • Execution

[ ProcessID] 4

[ ThreadID] 8

Channel System

Computer DESKTOP-EDR2I9Q

  • Security

[ UserID] S-1-5-18

  • EventData BugcheckCode 78 BugcheckParameter1 0x8d BugcheckParameter2 0x9b80 BugcheckParameter3 0x410001 BugcheckParameter4 0xffffe280080a5170 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 0 CsEntryScenarioInstanceId 0 BugcheckInfoFromEFI false CheckpointStatus 0 CsEntryScenarioInstanceIdV2 0 LongPowerButtonPressDetected false

Forgot to say i changed a graphics card and then went back to the old one cause the new one was overheating so i did touch the cable management so i'm scared it might be powersupply or wire issue and i hope not, but might be driver related, i just hoped someone here could tell me if it's software or hardware

Windows for home | Windows 10 | Performance and system failures

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

6 answers

Sort by: Most helpful
  1. DYARI BARHAM 34,936 Reputation points Independent Advisor
    2022-10-24T07:08:14+00:00

    Sounds great. Please keep me updated if your computer crashed to analyze the newly created minidump files.

    Regards,

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-10-23T22:02:24+00:00

    Hi,

    I haven't encountered any other BSOD since then but they seem to be very random and far appart, i do have another minidump but it's pretty much the same as this one so the problem is consistent.

    Regards.

    Was this answer helpful?

    0 comments No comments
  3. DYARI BARHAM 34,936 Reputation points Independent Advisor
    2022-10-23T21:54:01+00:00

    Hi dorianbaudet,

    Thanks for sharing the minidump analysis.

    The minidump analysis did not name any driver only indicate ntkrnlmp.exe which is a Windows component that means something else drove the system to a fault or it could be a memory corruption that usually happens due to driver incompatibility.

    This is the only minidump file that you have? did your computer encounter any BSOD after performing these steps?

    Regards,

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-10-23T14:25:46+00:00

    Hi couldn't get it into drive cause it says it's unreadable so i installed WinDbg and did the thing here is what i got:

    ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

    PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 000000000000008d, Arg2: 0000000000009b80 Arg3: 0000000000410001 Arg4: ffffe280080a5170

    Debugging Details:

    KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1265
    
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    
    Key  : Analysis.Elapsed.mSec
    Value: 1329
    
    Key  : Analysis.IO.Other.Mb
    Value: 8
    
    Key  : Analysis.IO.Read.Mb
    Value: 0
    
    Key  : Analysis.IO.Write.Mb
    Value: 24
    
    Key  : Analysis.Init.CPU.mSec
    Value: 406
    
    Key  : Analysis.Init.Elapsed.mSec
    Value: 85949
    
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 93
    
    Key  : Bugcheck.Code.DumpHeader
    Value: 0x4e
    
    Key  : Bugcheck.Code.Register
    Value: 0x4e
    
    Key  : Dump.Attributes.AsUlong
    Value: 8
    
    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1
    

    FILE_IN_CAB: 102222-5828-01.dmp

    DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump

    BUGCHECK_CODE: 4e

    BUGCHECK_P1: 8d

    BUGCHECK_P2: 9b80

    BUGCHECK_P3: 410001

    BUGCHECK_P4: ffffe280080a5170

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    STACK_TEXT:
    ffffd80aadfb79a8 fffff8052c6be2cd : 000000000000004e 000000000000008d 0000000000009b80 0000000000410001 : nt!KeBugCheckEx ffffd80aadfb79b0 fffff8052c7ad168 : ffff9785572b9e10 ffffd80a00000003 fffff80500000000 0000000000000008 : nt!MiZeroLargePages+0xddd ffffd80aadfb7aa0 fffff8052c671d25 : 0000000000000000 ffff9785572a2d70 ffffd78000007000 fffff8052d050b40 : nt!MiZeroLargePageThread+0x88 ffffd80aadfb7b50 fffff8052c800778 : ffffad0011f03180 ffff97855729c040 fffff8052c671cd0 0000000000000000 : nt!PspSystemThreadStartup+0x55 ffffd80aadfb7ba0 0000000000000000 : ffffd80aadfb8000 ffffd80aadfb1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

    SYMBOL_NAME: nt!MiZeroLargePages+ddd

    MODULE_NAME: nt

    IMAGE_VERSION: 10.0.19041.2130

    STACK_COMMAND: .cxr; .ecxr ; kb

    IMAGE_NAME: ntkrnlmp.exe

    BUCKET_ID_FUNC_OFFSET: ddd

    FAILURE_BUCKET_ID: 0x4E_8d_nt!MiZeroLargePages

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {41cd1249-9aa7-846e-e42a-376ea0b02183}

    Followup: MachineOwner

    So what i did is a sfc /snannow and i also used DDU to uninstall Nvidia drivers and reinstall them, i hope it's gonna fix it

    Was this answer helpful?

    0 comments No comments
  5. DYARI BARHAM 34,936 Reputation points Independent Advisor
    2022-10-22T19:36:53+00:00

    Hi dorianbaudet,

    I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

    Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

    Regards,

    Was this answer helpful?

    0 comments No comments