Share via

BSOD Error

Anonymous
2023-07-25T02:16:33+00:00

Hello,

I have been consistently getting BSODs while playing LOL or HSR, and sometimes even when my computer is at rest. I've been looking at this minidump and don't really understand it, and would like help interpreting what the issue is:

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the BugCheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff80593896530, Virtual address for the attempted write. Arg2: 090000012d459121, PTE contents. Arg3: ffffa50fb5d16940, (reserved) Arg4: 000000000000000a, (reserved)

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2186

Key  : Analysis.Elapsed.mSec
Value: 3381

Key  : Analysis.IO.Other.Mb
Value: 7

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 31

Key  : Analysis.Init.CPU.mSec
Value: 280

Key  : Analysis.Init.Elapsed.mSec
Value: 13526

Key  : Analysis.Memory.CommitPeak.Mb
Value: 100

Key  : Bugcheck.Code.LegacyAPI
Value: 0xbe

Key  : Dump.Attributes.AsUlong
Value: 1808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 0

Key  : Failure.Bucket
Value: IP\_MISALIGNED\_AuthenticAMD.sys

Key  : Failure.Hash
Value: {716d112a-8330-4bbb-160c-ec98297019d2}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key  : Hypervisor.Flags.Phase0InitDone
Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 1

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 4853999

Key  : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key  : Hypervisor.Flags.VpAssistPage
Value: 1

Key  : Hypervisor.Flags.VsmAvailable
Value: 1

Key  : Hypervisor.RootFlags.AccessStats
Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key  : Hypervisor.RootFlags.Value
Value: 1015

Key  : Hypervisor.RootFlags.ValueHex
Value: 3f7

BUGCHECK_CODE: be

BUGCHECK_P1: fffff80593896530

BUGCHECK_P2: 90000012d459121

BUGCHECK_P3: ffffa50fb5d16940

BUGCHECK_P4: a

FILE_IN_CAB: 072323-14062-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: NVDisplay.Cont

TRAP_FRAME: ffffa50fb5d16940 -- (.trap 0xffffa50fb5d16940) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff80593896530 rbx=0000000000000000 rcx=0000000000000000 rdx=ffffcc8bfb4680c0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80553039a5e rsp=ffffa50fb5d16ad8 rbp=000000002080a068 r8=000000000000000c r9=ffffa50fb5d16c60 r10=0000fffff8059389 r11=ffff977f5ae00000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!guard_dispatch_icall+0xe: fffff80553039a5e 0000 add byte ptr [rax],al ds:fffff80593896530=48 Resetting default scope

MISALIGNED_IP: nt!guard_dispatch_icall+e fffff805`53039a5e 0000 add byte ptr [rax],al

STACK_TEXT:
ffffa50fb5d167c8 fffff80553090868 : 00000000000000be fffff80593896530 090000012d459121 ffffa50fb5d16940 : nt!KeBugCheckEx ffffa50fb5d167d0 fffff80552e7f82f : 090000012d459121 0000000000000003 ffffa50fb5d168d9 0000000000000000 : nt!MiRaisedIrqlFault+0x258268 ffffa50fb5d16820 fffff8055303f829 : ffffa50fb5d16ad0 ffff850ceea76d20 0000000000000000 ffffa50fb5d16b10 : nt!MmAccessFault+0x3af ffffa50fb5d16940 fffff80553039a5e : fffff8059393edba ffffcc8bfb4680c0 00000000b2000000 0000000000000000 : nt!KiPageFault+0x369 ffffa50fb5d16ad8 fffff8059393edba : ffffcc8bfb4680c0 00000000b2000000 0000000000000000 0000000000000000 : nt!guard_dispatch_icall+0xe ffffa50fb5d16ae0 ffffcc8bfb4680c0 : 00000000b2000000 0000000000000000 0000000000000000 0000000000000003 : nvlddmkm+0xaedba ffffa50fb5d16ae8 00000000b2000000 : 0000000000000000 0000000000000000 0000000000000003 fffff8059393ede7 : 0xffffcc8bfb4680c0 ffffa50fb5d16af0 0000000000000000 : 0000000000000000 0000000000000003 fffff8059393ede7 ffffa50f`b5d16a01 : 0xb2000000

SYMBOL_NAME: nvlddmkm+aedba

MODULE_NAME: AuthenticAMD

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: AuthenticAMD.sys

FAILURE_BUCKET_ID: IP_MISALIGNED_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {716d112a-8330-4bbb-160c-ec98297019d2}

Followup: MachineOwner

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 No comments

7 answers

Sort by: Most helpful
  1. Jan J.23 13,665 Reputation points Independent Advisor
    2023-07-26T09:02:49+00:00

    Please share the latest dmp files. Thank you.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-07-26T03:03:52+00:00

    Hello Jan,

    I followed every one of your steps, and after gaming for a few hours my laptop has experienced a BSOD again. The error code was driver irql_less_or_not_equal

    Was this answer helpful?

    0 comments No comments
  3. Jan J.23 13,665 Reputation points Independent Advisor
    2023-07-25T06:47:34+00:00

    The dmp files indicate the AMD processor and the Nvidia driver. Here are some things you can try.

    1. Clean and Install the Nvidia graphics drivers.

    Download the latest driver from the Manufacturer's support website

    Run the driver installer

    Select Custom install

    And perform a clean installation.

    once done with the installation restart your computer.

    If that didn't work, try the older stable version of the graphics driver.

    1. Clean and install the graphics drivers using DDU.

    Display Driver Uninstaller

    https://www.guru3d.com/files-details/display-dr...

    Run the application from Safe mode.

    https://support.microsoft.com//windows/start-yo...

    Select Clean and restart

    Once the drivers are uninstall

    Install the latest Graphics Card driver

    Try the older driver version if the latest driver is crashing.

    1. Update the chipset drivers. Download the latest chipset drivers from the manufacturer's support website. Then restart your computer.

    Then disable any overclocking and set the BIOS settings to its optimal default.

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before downloading and installing it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-07-25T06:05:31+00:00

    Hi Jan!

    Thank you for your timely response. Here is the link you requested: Minidump.zip

    Was this answer helpful?

    0 comments No comments
  5. Jan J.23 13,665 Reputation points Independent Advisor
    2023-07-25T04:13:59+00:00

    Hi, I'm Jan and I'm happy to help you today. I'm sorry you're having this problem. Please share the latest dmp files for us to diagnose the cause of the computer crash/BSOD. Thank you

    Please find this folder.

    C:\Windows\Minidump

    Put the files in a zip

    upload files to OneDrive

    Share the link here.

    Thank you

    Was this answer helpful?

    0 comments No comments