Share via

Windows 11 BSOD Bugcheck 0x00000050 and other Bugchecks

Anonymous
2024-09-25T01:58:03+00:00

I have Asus Vivobook 17 with Windows 11 Pro.

I have been getting random BSOD bugchecks, about 1 per day or two and they seem to be different every time.

I have ran 24 hour diagnostic bios memory tests as well as Windows memory test without error so I feel memory is not an issue.

Here is the latest bug check and memory.dmp:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffffffffffffd4, 0x0000000000000002, 0xfffff80227112126, 0x0000000000000002). 

Here is a link to the memory.dmp (zipped) if someone could assist in reading it.

MEMORY.zip

Also here are the 4 previous bugchecks (no memory.dmp), but wanted you to see what else was showing up:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007a (0x0000000000000001, 0xffffffffc0000005, 0xffff800f94c75080, 0xfffff0120e136000). 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x000000000006194a, 0x0000000000000000, 0x0000000000000001, 0x0000000000000000). 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000041792, 0xffffa73ffe0b2930, 0x0000200000000000, 0x0000000000000000). 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8052611d340, 0x0000000000000000). 

Several of the above seem unrelated so very confusing as to what is causing this.

Thank you in advance for your help. If I have another / different bugcheck I will send link to the dmp file.

I have ran the SFC and DISM commands and all is verified as good.

Thanks in advance!

Windows for home | Windows 11 | 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

12 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-09-27T20:47:54+00:00

    Here is contents of Report.wer from file in WER\ReportArchive named NonCritical_0_f2bf2faebb16863c52b8bf3e67385e4c693ebbb_00000000_5da6d6ca-a35b-4c50-ae84-60c6c735dcea

    Version=1

    EventType=MemDiagV1

    EventTime=133719432503864408

    Consent=1

    UploadTime=133719433973447581

    ReportStatus=268435558

    ReportIdentifier=5da6d6ca-a35b-4c50-ae84-60c6c735dcea

    Wow64Host=34404

    OriginalFilename=RelPost.exe

    AppSessionGuid=00002b54-0000-0031-515a-e2891d11db01

    TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!00008896cee32fac064190f0085cf2fe1afc10340f1e!RelPost.exe

    TargetAppVer=2051//07//01:18:02:40!3f727!RelPost.exe

    BootId=4294967295

    TargetAsId=233

    IsFatal=4294967295

    Response.BucketId=f2b1f4144fb481920f5523f3c08a1dd7

    Response.BucketTable=5

    Response.LegacyBucketId=5014495

    Response.type=4

    Sig[0].Name=Range of memory size

    Sig[0].Value=0

    Sig[1].Name=Launch type

    Sig[1].Value=Manual

    Sig[2].Name=Schedule type

    Sig[2].Value=Immediate

    Sig[3].Name=Completion type

    Sig[3].Value=MemTestError

    Sig[4].Name=Test type

    Sig[4].Value=Unknown

    Sig[5].Name=Failed tests

    Sig[5].Value=0

    Sig[6].Name=Number of bad pages

    Sig[6].Value=0

    Sig[7].Name=Test duration in seconds

    Sig[7].Value=0

    DynamicSig[1].Name=OS Version

    DynamicSig[1].Value=10.0.22631.2.0.0.256.48

    DynamicSig[2].Name=Locale ID

    DynamicSig[2].Value=1033

    State[0].Key=Transport.DoneStage1

    State[0].Value=1

    OsInfo[0].Key=vermaj

    OsInfo[0].Value=10

    OsInfo[1].Key=vermin

    OsInfo[1].Value=0

    OsInfo[2].Key=verbld

    OsInfo[2].Value=22631

    OsInfo[3].Key=ubr

    OsInfo[3].Value=4169

    OsInfo[4].Key=versp

    OsInfo[4].Value=0

    OsInfo[5].Key=arch

    OsInfo[5].Value=9

    OsInfo[6].Key=lcid

    OsInfo[6].Value=1033

    OsInfo[7].Key=geoid

    OsInfo[7].Value=244

    OsInfo[8].Key=sku

    OsInfo[8].Value=48

    OsInfo[9].Key=domain

    OsInfo[9].Value=0

    OsInfo[10].Key=prodsuite

    OsInfo[10].Value=256

    OsInfo[11].Key=ntprodtype

    OsInfo[11].Value=1

    OsInfo[12].Key=platid

    OsInfo[12].Value=10

    OsInfo[13].Key=sr

    OsInfo[13].Value=0

    OsInfo[14].Key=tmsi

    OsInfo[14].Value=222862844

    OsInfo[15].Key=osinsty

    OsInfo[15].Value=2

    OsInfo[16].Key=iever

    OsInfo[16].Value=11.1.22621.0-11.0.1000

    OsInfo[17].Key=portos

    OsInfo[17].Value=0

    OsInfo[18].Key=ram

    OsInfo[18].Value=40645

    OsInfo[19].Key=svolsz

    OsInfo[19].Value=3724

    OsInfo[20].Key=wimbt

    OsInfo[20].Value=0

    OsInfo[21].Key=blddt

    OsInfo[21].Value=220506

    OsInfo[22].Key=bldtm

    OsInfo[22].Value=1250

    OsInfo[23].Key=bldbrch

    OsInfo[23].Value=ni_release

    OsInfo[24].Key=bldchk

    OsInfo[24].Value=0

    OsInfo[25].Key=wpvermaj

    OsInfo[25].Value=0

    OsInfo[26].Key=wpvermin

    OsInfo[26].Value=0

    OsInfo[27].Key=wpbuildmaj

    OsInfo[27].Value=0

    OsInfo[28].Key=wpbuildmin

    OsInfo[28].Value=0

    OsInfo[29].Key=osver

    OsInfo[29].Value=10.0.22621.4169.amd64fre.ni_release.220506-1250

    OsInfo[30].Key=buildflightid

    OsInfo[31].Key=edition

    OsInfo[31].Value=Professional

    OsInfo[32].Key=ring

    OsInfo[32].Value=Retail

    OsInfo[33].Key=expid

    OsInfo[33].Value=MD:283BAEF,ME:2E30985,ME:2E30A2A,ME:3036FD6,MD:3037091

    OsInfo[34].Key=fconid

    OsInfo[34].Value=18299130,0,2,0;19194309,0,2,0;19638787,0,2,0;26742989,0,1,0;35681102,0,1,0;36803287,0,2,1;36803295,0,2,0;38142198,0,2,0;38277973,0,1,0;39145991,0,2,0;39263329,1,2,0;39281392,0,2,0;40025975,0,1,0;40616880,0,1,0;40883769,0,1,0;40981503,0,1,0;41135193,0,1,1;41137130,0,1,0;41267076,0,2,1;41342175,0,1,0;41655236,0,2,0;42105254,0,2,0;43133808,1,2,1;43169616,0,1,0;43203978,0,2,1;43772553,0,1,0;43844371,0,1,0;43978769,0,1,1;43995105,0,2,0;43995122,0,2,0;44325080,0,1,1;44521793,0,1,0;44552141,0,1,0;44776738,0,2,0;45009259,0,1,0;45185354,0,2,0;45286373,0,1,0;45732051,0,2,0;45796396,0,2,0;45825686,0,1,0;45991456,0,1,1;46457961,0,1,0;46541070,0,2,0;46551074,0,1,0;46557400,0,1,0;47115450,0,1,0;47134595,0,1,0;47205155,0,2,0;47268464,2,2,1;47402621,0,2,0;47681899,0,1,0;47916854,0,1,0;47924308,0,1,0;47973375,0,1,0;48057519,0,2,0;48126879,0,2,0;48296377,0,1,0;48433541,0,2,0;48433706,0,2,0;48433719,0,1,0;48468527,0,2,0;48468541,0,2,0;48503047,0,2,0;48531596,0,2,0;48540091,0,2,1;48635704,0,2,1;48780814,0,2,0;49006888,0,1,1;49084341,0,1,1;49106743,0,2,0;49175271,0,2,0;49199869,0,2,0;49204591,0,1,1;49239926,0,1,0;49309588,0,1,0;49408394,0,1,1;49577493,0,1,0;49615603,0,1,0;49689210,0,1,0;49822061,0,1,0;50039410,0,2,0;50174338,0,1,1;50288426,0,1,1;50480279,0,1,0;50556886,0,2,0;50557073,0,1,0;50564196,0,1,0;50564332,0,1,0;50565209,0,1,0;50565295,0,1,0;50762615,0,1,0;51578581,0,1,0;51944598,0,1,0;52087985,0,1,0

    OsInfo[35].Key=containerid

    OsInfo[36].Key=containertype

    OsInfo[37].Key=edu

    OsInfo[37].Value=0

    OsInfo[38].Key=servicinginprogress

    OsInfo[38].Value=0

    OsInfo[39].Key=featureupdatependingreboot

    OsInfo[39].Value=0

    FriendlyEventName=Memory test results reported

    ConsentKey=MemDiagV1

    AppName=Windows Memory Diagnostic

    AppPath=C:\Windows\System32\RelPost.exe

    ReportDescription=The results of running the Windows Memory Diagnostic were submitted to Microsoft for analysis and product improvement

    ApplicationIdentity=00000000000000000000000000000000

    MetadataHash=1083636721

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-27T19:40:31+00:00

    I ran the Windows Memory test... just a single pass and I see the following in the event log. Does the below indicate there was an error?

    Fault bucket , type 0

    Event Name: MemDiagV1

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: 0

    P2: Manual

    P3: Immediate

    P4: MemTestError

    P5: Unknown

    P6: 0

    P7: 0

    P8: 0

    P9:

    P10:

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4af237b4-c523-455e-b39c-6887e028d0c5.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_0_f2bf2faebb16863c52b8bf3e67385e4c693ebbb_00000000_cab_587417ba-d57c-40f1-a682-6875efc0243d\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240808_1_EC_0_inject.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ba37966e-0eaa-473e-a4c2-50d7a3beb832.tmp.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_0_f2bf2faebb16863c52b8bf3e67385e4c693ebbb_00000000_cab_587417ba-d57c-40f1-a682-6875efc0243d\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.748a95d4-ab2f-47e8-9071-2ebe48727584.tmp.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.55e7fe5e-e0eb-436e-b3cb-6b0c3d56e91a.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.731f150a-42a1-4610-8f1f-356e27dd396c.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e9db9fd4-30e8-40b3-a103-21f8401d99b6.tmp.xml

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_0_f2bf2faebb16863c52b8bf3e67385e4c693ebbb_00000000_cab_587417ba-d57c-40f1-a682-6875efc0243d

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 587417ba-d57c-40f1-a682-6875efc0243d

    Report Status: 6

    Hashed bucket:

    Cab Guid: 0

    Fault bucket 5014495, type 5

    Event Name: MemDiagV1

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: 0

    P2: Manual

    P3: Immediate

    P4: MemTestError

    P5: Unknown

    P6: 0

    P7: 0

    P8: 0

    P9:

    P10:

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4af237b4-c523-455e-b39c-6887e028d0c5.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_0_f2bf2faebb16863c52b8bf3e67385e4c693ebbb_00000000_cab_587417ba-d57c-40f1-a682-6875efc0243d\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240808_1_EC_0_inject.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ba37966e-0eaa-473e-a4c2-50d7a3beb832.tmp.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_0_f2bf2faebb16863c52b8bf3e67385e4c693ebbb_00000000_cab_587417ba-d57c-40f1-a682-6875efc0243d\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.748a95d4-ab2f-47e8-9071-2ebe48727584.tmp.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.55e7fe5e-e0eb-436e-b3cb-6b0c3d56e91a.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.731f150a-42a1-4610-8f1f-356e27dd396c.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e9db9fd4-30e8-40b3-a103-21f8401d99b6.tmp.xml

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_0_f2bf2faebb16863c52b8bf3e67385e4c693ebbb_00000000_587417ba-d57c-40f1-a682-6875efc0243d

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 587417ba-d57c-40f1-a682-6875efc0243d

    Report Status: 268435458

    Hashed bucket: f2b1f4144fb481920f5523f3c08a1dd7

    Cab Guid: 0

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-09-27T18:34:45+00:00

    Here are the mini-dump files I found:

    MiniDump.zip

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-09-27T18:30:34+00:00

    Here is the link to the event logs (Application and System):

    Events.zip

    Was this answer helpful?

    0 comments
  5. Lester Bernard Reyes 82,005 Reputation points Independent Advisor
    2024-09-26T14:50:14+00:00

    Sure thanks, kindly update and provide the shareable link once you have it, so that we can further check what is causing the issue.

    Was this answer helpful?

    0 comments