My PC keeps black screening and blue screening, even after full wiping last month its not fixed anything and everything i've done has not helped.

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

EXCEPTION_ON_INVALID_STACK (1aa)
This BugCheck indicates that exception dispatch crossed over into an invalid
kernel stack. This might indicate that the kernel stack pointer has become
corrupted during exception dispatch or unwind (e.g. due to stack corruption of
a frame pointer), or that a driver is executing off of a stack that is not a
legal kernel stack.
Arguments:
Arg1: 00000000494ff4f8, A pointer to the current stack.
Arg2: 0000000000000003, A normal kernel thread stack
Arg3: ffff9e01459f7900, A pointer to the context record representing the context that was
being unwound (or dispatched for an exception) when the invalid stack
was encountered.
Arg4: ffff9b83152368a8, ExceptionRecord - Supplies an exception record representing the active
exception that was being dispatched.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2281

Key : Analysis.Elapsed.mSec
Value: 6855

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x1aa

Key : Bugcheck.Code.TargetModel
Value: 0x1aa

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: 0x1AA_nt!RtlpGetStackLimitsEx

Key : Failure.Hash
Value: {a75f195a-d08e-20f7-b020-0d8ede2085b8}

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

Key : Stack.Pointer
Value: PRCBException


BUGCHECK_CODE: 1aa

BUGCHECK_P1: 494ff4f8

BUGCHECK_P2: 3

BUGCHECK_P3: ffff9e01459f7900

BUGCHECK_P4: ffff9b83152368a8

FILE_IN_CAB: 102324-16343-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffd108769f8080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: GTA5.exe

STACK_TEXT:
ffff9e01`459f7108 fffff800`1e4c7d2c : 00000000`000001aa 00000000`494ff4f8 00000000`00000003 ffff9e01`459f7900 : nt!KeBugCheckEx
ffff9e01`459f7110 fffff800`1e46f44d : ffff9b83`15236ae0 ffff9b83`152368a8 fffff800`1e425ff8 fffff800`1e0ee178 : nt!RtlpGetStackLimitsEx+0x18112c
ffff9e01`459f7160 fffff800`1e31813e : ffffffff`ffffffff ffff9b83`15236950 ffff9b83`15236950 ffff9e01`459f7900 : nt!RtlDispatchException+0x240c7d
ffff9e01`459f78d0 fffff800`1e416012 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1ae
ffff9e01`459f7fb0 fffff800`1e415fe0 : fffff800`1e42ae75 ffffd108`7cb8c390 ffffd108`7cb8c390 ffff9b83`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffff9b83`15236768 fffff800`1e42ae75 : ffffd108`7cb8c390 ffffd108`7cb8c390 ffff9b83`00000000 00000000`00012024 : nt!KiExceptionDispatchOnExceptionStackContinue
ffff9b83`15236770 fffff800`1e424042 : ffffd108`769f8080 00000000`00000000 ffffbb8e`e52d91f7 fffff800`1e6be8de : nt!KiExceptionDispatch+0x135
ffff9b83`15236950 fffff800`1e425ff8 : ffffd108`769f8080 00000000`00000000 000002af`f679e980 ffffd108`00000000 : nt!KiInvalidOpcodeFault+0x342
ffff9b83`15236ae0 00007ff7`b60dae66 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x2f8
00000000`494ff4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`b60dae66


SYMBOL_NAME: nt!RtlpGetStackLimitsEx+18112c

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.4317

STACK_COMMAND: .process /r /p 0xffffd1086ae210c0; .thread 0xffffd108769f8080 ; kb

BUCKET_ID_FUNC_OFFSET: 18112c

FAILURE_BUCKET_ID: 0x1AA_nt!RtlpGetStackLimitsEx

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a75f195a-d08e-20f7-b020-0d8ede2085b8}

Followup: MachineOwner
---------

My guess is there's hardware issues, maybe heating. lSome of the things I've ran into, might check the RAM modules contacts for corrosion, the heat transfer compound between the CPU and cooling fan [I've used Arctic Silver for years], dust in the fan/s, etc.

I got a Lenovo Notebook on the 16th with a Ryzen 5 7520U CPU, not expensive at $349 in WalMart, works quite well.

Hi, welcome to the forum

Someone will come along and help you do a BSOD analysis. This is probably what will be asked of you:




Not good that this happened to you, always most inconvenient.
In the mean time, some things for your reading (dis)pleasure.

Hello @Casstiel and welcome to ElevenForum.


First, you get ten cookies, just for filling out your computer specs.

2nd, how many sticks of RAM in your 32GB of RAM?

Try powering off the computer and re-seating the RAM.
Then power ON and see if you black screen.

If you're still seeing the black and blue screens...
Power off, and take all the RAM out of the computer.
Then try one stick at a time, in the 2nd slot, counting away from the CPU, to the right.

You're looking for one or more RAM sticks that do NOT cause the black and blue screening.
If you find some that do NOT cause the problem, then you know the RAM was the problem.
And you also know, which sticks of RAM are... good.



That's how you check the RAM. It's one of the easiest things to check.


And is this... your motherboard?

MSI PRO B550M-VC WIFI (with the M in there?)

I would have to ask if the issue began occurring after a forced upgrade to 24h2. Do you have WD m.2 drive or run easy anti-cheat? If so, roll back.

Ghot said:

Hello @Casstiel and welcome to ElevenForum.


First, you get ten cookies, just for filling out your computer specs.

2nd, how many sticks of RAM in your 32GB of RAM?

Try powering off the computer and re-seating the RAM.
Then power ON and see if you black screen.

If you're still seeing the black and blue screens...
Power off, and take all the RAM out of the computer.
Then try one stick at a time, in the 2nd slot, counting away from the CPU, to the right.

You're looking for one or more RAM sticks that do NOT cause the black and blue screening.
If you find some that do NOT cause the problem, then you know the RAM was the problem.
And you also know, which sticks of RAM are... good.



That's how you check the RAM. It's one of the easiest things to check.


And is this... your motherboard?

MSI PRO B550M-VC WIFI (with the M in there?)

Click to expand...

Hello, i will absolutely give this a try and yes that was be the exact motherboard model!

glasskuter said:

I would have to ask if the issue began occurring after a forced upgrade to 24h2. Do you have WD m.2 drive or run easy anti-cheat? If so, roll back.

Beware of Windows 11 24H2 Update: Here’s a List of Issues Users Are Facing After the Update

Microsoft's latest Windows 11 24H2 update hasn't been received well by users, as they're facing numerous issues, including BSOD.

techreport.com

Click to expand...

I can't pinpoint the exact date this started but yes i do actually think this started around the 24h2 update, and no i have a WD 2tb HDD but my boot drive is a crucial p3 plus m.2 drive. I do not think i run easy anti cheat.

That's too much of a coincidence IMO. Before I chased my tail trying to find hardware problems that may not exist, I would roll back to 23h2 if you're within the 10 day rollback period , to see if the issues stop. If not, you can restore an image made before the upgrade if you have one.
(Please tell me you make images to protect yourself)

1. Press Windows+I to open Settings.
2. Click Update & security.
3. Click Recovery on the left-hand side.
4. Under Go back to the previous version of Windows, click Get started. You won't have that option if your upgraded more than 10 days ago.

Attention: Casstiel
Before posting a BSOD thread, please read the instructions here: Blue/Black Screen of Death (BSOD) Posting Instructions
If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 11 Blue/Black Screen Of Death problems in this section.

your RAM is bad.

lunatk said:

your RAM is bad.

Click to expand...

Don't jump the gun. Of course, that's a possibility, but there is no way at this point in his troubleshooting that anyone can say definitively that the ram is the issue. This far, he hasn't reported back what happened when he stick-tested his ram, nor stated if the ram is on the OVL. If neither of those points to the ram being the problem, the next step would be memtest86.

First I need to know his type of RAM in order to figure out if it has firmware issues or the ram isn't that good when bought (dies quickly)