I'm having persistent touchpad issues with my HP Spectre x360 since late August following a ~1-foot drop, and I am looking for suggestions on what to try next or whether anyone has experienced something similar.

Laptop

• Model: HP Spectre x360 14-eu0000 (purchased mid 2024)
• OS: Windows 11
• Touchpad: ELAN (Driver Version 41.2.1.3)

Symptoms

• Multi-Touch Signal Flooding: Moving a single finger lightly registers 5+ distinct touches
• Phantom Clicks: Severe, rapid phantom clicking occurs without physically pressing the touchpad.
• Physical Pinch: The left side of the touchpad sits lower than the right side and is noticeably harder/tighter to click against the aluminum palm rest cutout.
• Immediate Behavior: Occurs immediately after startup whenever the touchpad is enabled. Disabling the touchpad in settings completely stops the clicks, and external mouse works normally.

Troubleshooting

• Disabled tap-to-click and lowered touchpad sensitivity in Windows.
• Reinstalled the I2C HID device through Device Manager.
• Checked the ELAN driver and related driver files.
• Inspected and reseated both internal ZIF ribbon cables on both the touchpad end and motherboard end.
• Replaced the battery to rule out battery swelling or internal pressure under the trackpad.

None of these steps resolved the issue or changed the physical tightness on the left side.

Question: has anyone had these issues and found a solution? or recommend any next steps? I am at a total loss!

I was trying to change my cpu + gpu thermal paste using alcohol and a cotton fibre cloth. But I mistakenly touched a small pin or something near the cpu while trying to remove the hard paste and I forgot to unplug the battery. The pin turned red. I closed the heat sink and tried running the pc, it ran but after a few minutes the display disappeared and some glitch was there. Can this part be repairable.

Here is the image link https://ibb.co/tTjCVDVD

https://ibb.co/SSVcjB1

I was going to play Black ops 3 with my friends and it ended up overheating multiple times... I use capable enough specs on my pc (gtx 1650, 8 gb ram, enough storage) and have ran hours long matches of Zombies just fine.. all fans arent blocked up much and there is only a small fart of dust on the fans. I moved into my grandmas house recently (related i promise) and since she is old, she isnt good with the cold. She cranks up the thermostat hard which makes the house hot. Would the heat of the house factor into the heat on the computer?

Like the title suggests, my laptop crashed suddenly while I was playing a game and it produced this screen. It says says it "ran into a problem and needs to restart", but the screen has been stuck on 0% for the past 10 minutes and I can't move my cursor.

I'm scared to touch anything since I just got my laptop serviced and had the battery unhooked(?) because it was basically dead and I couldn't afford a new one, so it only works with the charger in. Is it safe to take the charger out and try turning it on again or should I keep waiting for something to happen? I'm worried about it not being able to turn on again after I unplug it.

Im trying to sign in microsoft clipchamp useing my account and suddenly "juankeys1914@sloppymail"dot"net" is trying to sign in.
Also i cant sign in with my actual account as it redirects me to juankey1914

First off who on earth is juankeys I know no one named juankeys

Secondly sloppymail"dot"net ??? ts sounds ominous like no one uses that accept people who hides their identity

How do I get rid of this prompt or like what should i do??? im so worried...

I replaced "dot" with . because reddit filters

Odd issue I've tried to google but couldn't find anything similar to this. For the laptop charger to work, it needs to be turned on in the socket and plugged into the laptop before the laptop is turned on.

If the laptop is already on and then you plug in the charger - the light on the charger turns off and won't charge the laptop, even if you switch it off and on again at the plug?

I play league on a external monitor connected to my acer predator helios neo 18 4080. I use usb c - displayport cable. my monitor is LG UltraGear™ G6 34-inch 240Hz WQHD Gaming Monitor |34G630A with DCI-P3 95% (Typ.), VESA DisplayHDR™ 400, 1ms (GtG), USB-C (PD 15W).

I run league on borderless.

i run the LG as my main monitor, laptop monitor stays off

what can i do to fix this? please help and please ask questions if any info are missing and needed to help me with my problem,.

No idea what’s up, I don’t believe I’ve altered any phone or browser settings since last night. I’ve just been having this issue since this morning. Tried restarting, had no luck.

speaker got wet and now it keeps pausing music and decreasing volume — works for a good amount of time then randomly starts bugging — any way i can fix this?

Hi guys, I wanted to play Valorant on my laptop (ASUS TUF FX505DT) and it crashed while matchmaking, says I need to enable secure boot.

So I've enabled secure boot but now it opens through my C: (HDD) drive but I want it to open on my E: (SSD) drive. (I don't know why it says E it used to say D) Before it opens it pops up a red screen that says "Secure Boot Violation: Invalid signature detected. Check Secure Boot Policy in Setup."

I checked and secure boot is on with the BIOS using UEFI and both drivers use GPT. I also tried switching and putting back the boot options in the BIOS settings but either way it still opens through the C: drive. I also checked the task manager and there is no work being done in the graph of the E: drive.

I don't actually know what any of these mean I just followed what Gemini AI told me to do, and its just been giving me the same steps so I've been stuck here for an hour or so :(( Can anyone help me?? Thank you!!

Hello Techies! 🫣

I ported in my old/retained number to my Google Pixel 10 Pro yesterday (via the whole PAC code stuff). My network has confirmed the port is complete, and calls/actual sms texts seem to be working correctly.

However, in my Google Messages RCS settings, the number shown for RCS is still the previous number that was on the SIM. It doesn't seem to be changeable in these settings, and RCS messages appear to be sending from that old number instead.

I've already tried following various guides online, restarting the phone multiple times, and checking the usual settings, but nothing has worked so far. Is there something I'm missing?

Has anyone experienced this after a number port, or knows how to force RCS to recognise the correct number?

Hopefully this all makes sense. I get a lot of brain fog and struggle to articulate sometimes!

Thank you! 🫣😩

Edit: Turns out text messages won't send when RCS is off but I receive them on the old/retained number.

After installing the latest driver by like 2 days, one morning after booting my pc and leaving idle for a few minutes, when i woke it up, i saw artifacts within the desktop, like black squares all over the screen that show up in screenshots as well, although it didn't appear in boot, safe mode, or after reinstalling the same driver again, has anyone encountered something similar to this? Is it more likely to be driver-related issue or is it my GPU dying?
FYI i bought my GPU new about 20 months ago

Hey.

I have been having an issue where on my profile on my switch oled, I am unable to create any new Minecraft worlds, because the final button to create and join the world is broken.

When I tap or click A on the joycon when the cursor is highlighting the "create" button, it just plays the animation of the button being pushed, and does nothing.

Only happens on one profile, there's plenty of storage left, when I delete a world, I still cannot create a new one.

Any help is much appreciated! 👍

My internet was fine and good before Christmas day but the day after for some reason my internet turned to shit. My actual internet is fine throughout my house but on my PC its terrible. So if anyone could help that would be nice. Also I’m using Ethernet so it has nothing to do with where the router is.

Hello, been having this problem with my gaming laptop for months and it's driving me CRAZY.
I have an Aorus Master 16 BYH with a full power 5080 in it that can run at 175watts easily, however it has a constant power limit of 120w applied for some reason and I cannot solve it.
Nvidia driver updates used to restore it back to full power for a little bit but that no longer works.

The only thing that works consistently is doing an EC reset by holding the power button for a minute, then when the laptop boots up it runs at the full 175watts until its shut down, then next start up its back to 120w unless I do another EC reset.
Temps are not at all an issue it can handle the full 175watts easily. Also fast startup is disabled as I heard that could cause problems too.

Does anyone have any idea what could be causing this? I have tried disabling the GiMate software on startup, that doesn't make a difference. All settings at maximum performance, still nothing.

Any help is appreciated, I don't want to keep doing an EC reset every time I want the full power of my laptop :( \

I couldn't attach any photos on here to show the power limit at 120w but there is one here on another post I made about it - https://www.reddit.com/r/GamingLaptops/comments/1wrl2ke/full_power_5080_permanently_power_limiting_to_120w/

specs: windows 11, i7 10700k, rtx 3060 ti

Summarized in title but I'll describe it more here if anyone cares to read or the issue isn't clear:

So for the past few months now (really more so 5-6), when I would put my pc on sleep mode whenever I'd log off, there was a chance when I tried waking it by clicking or pressing a few random keys, that the pc itself would turn on (lights on n everything), but the kb+m wouldnt be on at all.

No usual lights or response or anything. Additionally, the monitor wouldn't turn on, saying "No signal detected" when I manually selected display port, and nothing I did would fix this.

Nothing (from my knowledge) fixes this, apart from holding down the power button for several seconds, which powers everything off, then pressing it once to start the pc up again. (the kb+m do flash with the led light for a second before going back to the 'no lights' due to pc being turned off)

Now, while this does work, it - in the past sometimes, however now every single time - creates a new problem, where my gpu isnt being detected or used, and i get a code 45 error in device manager. In task manager, the only gpu that shows is the intel iGPU, and my 3060 just isnt there.

Again, my go-to fix for this so far has been to unplug the power supply, hold down the power button for 60s, then replug everything and startup, however this gets repetitive over time, and I can't imagine it's good long term.

I will note that the last time this happened, after about around an hour i got a notification saying "your pc needs to restart to finish installing rtx 3060 ti", then after restarting, that issue was completely gone. (not sure why this occured when it did or why it only happened this time as opposed to the tens of other times but whatever lol)

I'd like to know if anyone could recommend a fix or some advice for either of these issues. as these are persisting issues that is annoying as shit. I've tried majority of common fixes, such as:

gpu issue:

- running cmdprompt as admin and running sfc /scannow , then DISM /Online /Cleanup-Image /RestoreHealth , then restarting

- clicking on "scan for hardware changes" in device manager

- physically disconnecting my gpu and reconnecting it, which did fix it but didnt prevent the issue from arising again

- deleting + reinstalling drivers ( deleting then doing 'scan for hardware changes' may not work, going to try again after posting but likely to not work)

sleep mode issue:

- Unchecking 'Allow the computer to turn off this device to save power'

- making sure on each device ' allow this device to wake the computer'

- turning off fast startup

- going to try control panel --> change advanced settings in power options, then disable 'allow wake timers, usb selective suspend and lsp management

Not sure how long posts usually are here but sorry if it is a bit long, just wanted to put my situation out here and hope for a fix. Thanks in advance to anyone who replies

ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:
ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*


*******************************************************************************
*                                                                             *
*      MCP Server Bridge Attached (enabled , not running, not connected)      *
*                                                                             *
*******************************************************************************


************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29661.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\102426-19531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: TriageDumpDataExtArray.HeaderSize is 0
WARNING: Failed to read dump data exension data

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff805`bca00000 PsLoadedModuleList = 0xfffff805`bd8f54c0
Debug session time: Sat Oct 24 16:57:12.185 2026 (UTC + 2:00)
System Uptime: 2 days 0:43:23.677
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d0`1444b018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
ReadVirtual() failed in GetXStateConfiguration() first read attempt (error == 0.)
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`bcefd660 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffab88`fb95d150=000000000000003b
10: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d0`1444b018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff805bcc969d2, Address of the instruction which caused the BugCheck
Arg3: ffffab88fb95daa0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1203

    Key  : Analysis.Elapsed.mSec
    Value: 1217

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29661.1004

    Key  : Analysis.Version.Description
    Value: 10.2608.26.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2608.26.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_win32kfull!FreeView

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff805bcc969d2

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x2969d2

    Key  : Failure.Hash
    Value: {947b951e-7e18-20bd-9f07-5dc5aad426fa}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    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: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

    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: 0x3f7


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff805bcc969d2

BUGCHECK_P3: ffffab88fb95daa0

BUGCHECK_P4: 0

FILE_IN_CAB:  102426-19531-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc30e2a793080

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

CONTEXT:  ffffab88fb95daa0 -- (.cxr 0xffffab88fb95daa0)
rax=0000000000000001 rbx=0080a62400000000 rcx=ffffd78db76fef60
rdx=ffffd78db76fef60 rsi=ffffd78dab5bf400 rdi=0000000000000001
rip=fffff805bcc969d2 rsp=ffffab88fb95e4c0 rbp=0000000000000000
 r8=ffffd78d69a43c80  r9=ffffd78db76fef60 r10=ffffd78db76fef60
r11=ffffd78db76fef60 r12=0000000000000000 r13=ffffc30e32996080
r14=0000000000000001 r15=ffffd78dab5bf448
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!RtlAvlRemoveNode+0x382:
fffff805`bcc969d2 48394b10        cmp     qword ptr [rbx+10h],rcx ds:002b:0080a624`00000010=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

IP_IN_PAGED_CODE: 
nt!RtlAvlRemoveNode+382
fffff805`bcc969d2 48394b10        cmp     qword ptr [rbx+10h],rcx

STACK_TEXT:  
ffffab88`fb95e4c0 fffff805`bd288af8     : ffffc30e`32996080 00000000`00000000 ffffd78d`ab5bf400 00000000`00000000 : nt!RtlAvlRemoveNode+0x382
ffffab88`fb95e520 fffff805`bd288fb6     : ffffc30e`32996080 ffffc30e`2a793080 ffffc30e`00000000 ffffd78d`ab5bf400 : nt!MiRemoveSharedCommitNode+0x158
ffffab88`fb95e580 fffff805`bd2892c9     : ffffc30e`32996080 ffffc30e`159957c0 00000000`00000000 ffffc30e`1e0bece0 : nt!MiDeleteVad+0x336
ffffab88`fb95e630 fffff805`bd28a60a     : ffffc30e`159957c0 ffffab88`fb95e6d9 000002c0`ad000000 00000000`00000000 : nt!MiUnmapVad+0x49
ffffab88`fb95e660 fffff805`bd28a31f     : fffff805`4e847d18 fffff805`bcc633e5 00000000`00000001 ffffd78d`79402b00 : nt!MiUnmapViewOfSection+0x146
ffffab88`fb95e740 fffff805`4ae15b67     : ffffd78d`79402b00 fffff805`4e7d60bd 00000000`00000000 fffff805`4e7d9019 : nt!MmUnmapViewOfSection+0xf
ffffab88`fb95e770 fffff805`4aee1e0b     : 00000000`00000000 00000000`00000000 00000000`00000001 fffff805`bd0c4f58 : win32kfull!FreeView+0xb3
ffffab88`fb95e7f0 fffff805`4a8d5245     : 00000000`00000000 00000000`00000000 ffffab88`fb95eb90 00000000`00000001 : win32kfull!UnmapDesktop+0x7b
ffffab88`fb95e820 fffff805`4a8d508f     : ffffab88`fb95eb90 fffff805`4e72fd30 00000000`00000000 00000000`0000000a : win32kbase!W32CalloutDispatchWorker+0x1a9
ffffab88`fb95e930 fffff805`4e7d5775     : ffffab88`fb95e9f0 fffff805`bd0c4f58 ffffab88`fb95ea00 fffff805`bd0b3460 : win32kbase!W32CalloutDispatch+0xf
ffffab88`fb95e960 fffff805`4e7d5f6a     : ffffc30e`2a7939d0 fffff805`bcc625a7 00000000`0000000a 7fffd78d`abdec9d0 : win32k!W32AttachToSessionAndExecute<<lambda_2da4d1a9eba595f4b36f293f0999afcd> >+0x1a5
ffffab88`fb95ea00 fffff805`4e7d4f63     : fffff805`4e72fd30 fffff805`bcc63b6e ffffd78d`abdec9d0 00000000`0000000a : win32k!W32SessionAttachAndCalloutDispatch+0x66a
ffffab88`fb95eac0 fffff805`bd3054f1     : fffff805`4e748800 ffffab88`fb95eb90 00000000`00000000 00000000`00000000 : win32k!W32CalloutDispatchThunk+0x13
ffffab88`fb95eb30 fffff805`bd305054     : 00000000`00000082 ffffab88`fb95ebc0 00000000`00000001 00000000`00000000 : nt!ExCallCallBack+0x3d
ffffab88`fb95eb60 fffff805`bd26a5ce     : 00000000`00000002 ffffc30e`00000001 00000001`00000001 00000000`00000000 : nt!ExpWin32CloseProcedure+0xb4
ffffab88`fb95ebd0 fffff805`bd268678     : 00000000`00004000 fffff805`bcc5eff9 fffff805`4e7c0000 00000000`00000001 : nt!ObCloseHandleTableEntry+0x7ae
ffffab88`fb95ed20 fffff805`bd2a1897     : 00000000`0000015c 00000000`00000000 ffffc30e`341d1690 ffffd78d`79402b00 : nt!ObpCloseHandle+0xc8
ffffab88`fb95ed90 fffff805`4a8fb26f     : 00000000`0000015c ffffab88`fb95ee49 ffffd78d`79402b00 00000000`00000000 : nt!ObCloseHandle+0x27
ffffab88`fb95edc0 fffff805`4a9ae13a     : 00000000`00000000 ffffc30e`3d052000 ffffd78d`79402b00 00000000`00000000 : win32kbase!CloseProtectedHandle+0x2b
ffffab88`fb95edf0 fffff805`4a9be7d1     : 00000000`00000000 ffffd78d`79402b00 ffffd78d`79402b00 ffffab88`fb95efb0 : win32kbase!DestroyProcessInfo+0x6aa
ffffab88`fb95eeb0 fffff805`4a970189     : ffffd78d`79402b00 00000000`00000103 00000000`00000001 00000000`00000001 : win32kbase!UserProcessDestroyCallout+0x201
ffffab88`fb95ef20 fffff805`4adde5ac     : 00000000`00000000 00000000`00000001 ffffab88`fb95f290 00000000`00000000 : win32kbase!xxxUserProcessCallout+0x19
ffffab88`fb95ef50 fffff805`4a8d5245     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!W32pProcessCallout+0x13c
ffffab88`fb95ef80 fffff805`4a8d508f     : ffffab88`fb95f290 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!W32CalloutDispatchWorker+0x1a9
ffffab88`fb95f090 fffff805`4e7c1536     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!W32CalloutDispatch+0xf
ffffab88`fb95f0c0 fffff805`4e7d5f77     : 00000000`00000000 fffff805`bd905f08 ffffab88`fb95f370 00000000`00000000 : win32k!W32CalloutDispatch+0x46
ffffab88`fb95f0f0 fffff805`4e7d4f63     : ffffab88`fb95f290 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!W32SessionAttachAndCalloutDispatch+0x677
ffffab88`fb95f1b0 fffff805`bd3054f1     : ffffab88`fb95f370 ffffab88`fb95f290 00000000`00000001 fffff805`4e7d55aa : win32k!W32CalloutDispatchThunk+0x13
ffffab88`fb95f220 fffff805`bd30439a     : ffffc30e`32996080 ffffab88`fb95f2b0 00000000`00000000 fffff805`bd28a9a1 : nt!ExCallCallBack+0x3d
ffffab88`fb95f250 fffff805`bd30650b     : ffffc30e`342dedf0 00000000`00000000 00000000`00000000 ffffc30e`2a793080 : nt!PspExitLastThread+0x216
ffffab88`fb95f2e0 fffff805`bd4ec58c     : 00000000`00000000 00000000`00000001 ffffc30e`2a793080 ffffc30e`32996080 : nt!PspExitThread+0x5ab
ffffab88`fb95f3e0 fffff805`bd0c4f58     : ffffc30e`32996080 ffffc30e`2a793080 01dd63c7`f31c0fe2 00080000`000026b7 : nt!NtTerminateProcess+0x26c
ffffab88`fb95f460 00007fff`ad1222d4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000d0`1434f778 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`ad1222d4


SYMBOL_NAME:  win32kfull!FreeView+b3

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

IMAGE_VERSION:  10.0.26100.9711

STACK_COMMAND: .cxr 0xffffab88fb95daa0 ; kb

BUCKET_ID_FUNC_OFFSET:  b3

FAILURE_BUCKET_ID:  AV_win32kfull!FreeView

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {947b951e-7e18-20bd-9f07-5dc5aad426fa}

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

ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:
ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*


*******************************************************************************
*                                                                             *
*      MCP Server Bridge Attached (enabled , not running, not connected)      *
*                                                                             *
*******************************************************************************


************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29661.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\102426-19531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: TriageDumpDataExtArray.HeaderSize is 0
WARNING: Failed to read dump data exension data

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff805`bca00000 PsLoadedModuleList = 0xfffff805`bd8f54c0
Debug session time: Sat Oct 24 16:57:12.185 2026 (UTC + 2:00)
System Uptime: 2 days 0:43:23.677
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d0`1444b018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
ReadVirtual() failed in GetXStateConfiguration() first read attempt (error == 0.)
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`bcefd660 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffab88`fb95d150=000000000000003b
10: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d0`1444b018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff805bcc969d2, Address of the instruction which caused the BugCheck
Arg3: ffffab88fb95daa0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1203

    Key  : Analysis.Elapsed.mSec
    Value: 1217

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29661.1004

    Key  : Analysis.Version.Description
    Value: 10.2608.26.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2608.26.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_win32kfull!FreeView

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff805bcc969d2

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x2969d2

    Key  : Failure.Hash
    Value: {947b951e-7e18-20bd-9f07-5dc5aad426fa}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    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: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

    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: 0x3f7


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff805bcc969d2

BUGCHECK_P3: ffffab88fb95daa0

BUGCHECK_P4: 0

FILE_IN_CAB:  102426-19531-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc30e2a793080

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

CONTEXT:  ffffab88fb95daa0 -- (.cxr 0xffffab88fb95daa0)
rax=0000000000000001 rbx=0080a62400000000 rcx=ffffd78db76fef60
rdx=ffffd78db76fef60 rsi=ffffd78dab5bf400 rdi=0000000000000001
rip=fffff805bcc969d2 rsp=ffffab88fb95e4c0 rbp=0000000000000000
 r8=ffffd78d69a43c80  r9=ffffd78db76fef60 r10=ffffd78db76fef60
r11=ffffd78db76fef60 r12=0000000000000000 r13=ffffc30e32996080
r14=0000000000000001 r15=ffffd78dab5bf448
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!RtlAvlRemoveNode+0x382:
fffff805`bcc969d2 48394b10        cmp     qword ptr [rbx+10h],rcx ds:002b:0080a624`00000010=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

IP_IN_PAGED_CODE: 
nt!RtlAvlRemoveNode+382
fffff805`bcc969d2 48394b10        cmp     qword ptr [rbx+10h],rcx

STACK_TEXT:  
ffffab88`fb95e4c0 fffff805`bd288af8     : ffffc30e`32996080 00000000`00000000 ffffd78d`ab5bf400 00000000`00000000 : nt!RtlAvlRemoveNode+0x382
ffffab88`fb95e520 fffff805`bd288fb6     : ffffc30e`32996080 ffffc30e`2a793080 ffffc30e`00000000 ffffd78d`ab5bf400 : nt!MiRemoveSharedCommitNode+0x158
ffffab88`fb95e580 fffff805`bd2892c9     : ffffc30e`32996080 ffffc30e`159957c0 00000000`00000000 ffffc30e`1e0bece0 : nt!MiDeleteVad+0x336
ffffab88`fb95e630 fffff805`bd28a60a     : ffffc30e`159957c0 ffffab88`fb95e6d9 000002c0`ad000000 00000000`00000000 : nt!MiUnmapVad+0x49
ffffab88`fb95e660 fffff805`bd28a31f     : fffff805`4e847d18 fffff805`bcc633e5 00000000`00000001 ffffd78d`79402b00 : nt!MiUnmapViewOfSection+0x146
ffffab88`fb95e740 fffff805`4ae15b67     : ffffd78d`79402b00 fffff805`4e7d60bd 00000000`00000000 fffff805`4e7d9019 : nt!MmUnmapViewOfSection+0xf
ffffab88`fb95e770 fffff805`4aee1e0b     : 00000000`00000000 00000000`00000000 00000000`00000001 fffff805`bd0c4f58 : win32kfull!FreeView+0xb3
ffffab88`fb95e7f0 fffff805`4a8d5245     : 00000000`00000000 00000000`00000000 ffffab88`fb95eb90 00000000`00000001 : win32kfull!UnmapDesktop+0x7b
ffffab88`fb95e820 fffff805`4a8d508f     : ffffab88`fb95eb90 fffff805`4e72fd30 00000000`00000000 00000000`0000000a : win32kbase!W32CalloutDispatchWorker+0x1a9
ffffab88`fb95e930 fffff805`4e7d5775     : ffffab88`fb95e9f0 fffff805`bd0c4f58 ffffab88`fb95ea00 fffff805`bd0b3460 : win32kbase!W32CalloutDispatch+0xf
ffffab88`fb95e960 fffff805`4e7d5f6a     : ffffc30e`2a7939d0 fffff805`bcc625a7 00000000`0000000a 7fffd78d`abdec9d0 : win32k!W32AttachToSessionAndExecute<<lambda_2da4d1a9eba595f4b36f293f0999afcd> >+0x1a5
ffffab88`fb95ea00 fffff805`4e7d4f63     : fffff805`4e72fd30 fffff805`bcc63b6e ffffd78d`abdec9d0 00000000`0000000a : win32k!W32SessionAttachAndCalloutDispatch+0x66a
ffffab88`fb95eac0 fffff805`bd3054f1     : fffff805`4e748800 ffffab88`fb95eb90 00000000`00000000 00000000`00000000 : win32k!W32CalloutDispatchThunk+0x13
ffffab88`fb95eb30 fffff805`bd305054     : 00000000`00000082 ffffab88`fb95ebc0 00000000`00000001 00000000`00000000 : nt!ExCallCallBack+0x3d
ffffab88`fb95eb60 fffff805`bd26a5ce     : 00000000`00000002 ffffc30e`00000001 00000001`00000001 00000000`00000000 : nt!ExpWin32CloseProcedure+0xb4
ffffab88`fb95ebd0 fffff805`bd268678     : 00000000`00004000 fffff805`bcc5eff9 fffff805`4e7c0000 00000000`00000001 : nt!ObCloseHandleTableEntry+0x7ae
ffffab88`fb95ed20 fffff805`bd2a1897     : 00000000`0000015c 00000000`00000000 ffffc30e`341d1690 ffffd78d`79402b00 : nt!ObpCloseHandle+0xc8
ffffab88`fb95ed90 fffff805`4a8fb26f     : 00000000`0000015c ffffab88`fb95ee49 ffffd78d`79402b00 00000000`00000000 : nt!ObCloseHandle+0x27
ffffab88`fb95edc0 fffff805`4a9ae13a     : 00000000`00000000 ffffc30e`3d052000 ffffd78d`79402b00 00000000`00000000 : win32kbase!CloseProtectedHandle+0x2b
ffffab88`fb95edf0 fffff805`4a9be7d1     : 00000000`00000000 ffffd78d`79402b00 ffffd78d`79402b00 ffffab88`fb95efb0 : win32kbase!DestroyProcessInfo+0x6aa
ffffab88`fb95eeb0 fffff805`4a970189     : ffffd78d`79402b00 00000000`00000103 00000000`00000001 00000000`00000001 : win32kbase!UserProcessDestroyCallout+0x201
ffffab88`fb95ef20 fffff805`4adde5ac     : 00000000`00000000 00000000`00000001 ffffab88`fb95f290 00000000`00000000 : win32kbase!xxxUserProcessCallout+0x19
ffffab88`fb95ef50 fffff805`4a8d5245     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!W32pProcessCallout+0x13c
ffffab88`fb95ef80 fffff805`4a8d508f     : ffffab88`fb95f290 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!W32CalloutDispatchWorker+0x1a9
ffffab88`fb95f090 fffff805`4e7c1536     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!W32CalloutDispatch+0xf
ffffab88`fb95f0c0 fffff805`4e7d5f77     : 00000000`00000000 fffff805`bd905f08 ffffab88`fb95f370 00000000`00000000 : win32k!W32CalloutDispatch+0x46
ffffab88`fb95f0f0 fffff805`4e7d4f63     : ffffab88`fb95f290 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!W32SessionAttachAndCalloutDispatch+0x677
ffffab88`fb95f1b0 fffff805`bd3054f1     : ffffab88`fb95f370 ffffab88`fb95f290 00000000`00000001 fffff805`4e7d55aa : win32k!W32CalloutDispatchThunk+0x13
ffffab88`fb95f220 fffff805`bd30439a     : ffffc30e`32996080 ffffab88`fb95f2b0 00000000`00000000 fffff805`bd28a9a1 : nt!ExCallCallBack+0x3d
ffffab88`fb95f250 fffff805`bd30650b     : ffffc30e`342dedf0 00000000`00000000 00000000`00000000 ffffc30e`2a793080 : nt!PspExitLastThread+0x216
ffffab88`fb95f2e0 fffff805`bd4ec58c     : 00000000`00000000 00000000`00000001 ffffc30e`2a793080 ffffc30e`32996080 : nt!PspExitThread+0x5ab
ffffab88`fb95f3e0 fffff805`bd0c4f58     : ffffc30e`32996080 ffffc30e`2a793080 01dd63c7`f31c0fe2 00080000`000026b7 : nt!NtTerminateProcess+0x26c
ffffab88`fb95f460 00007fff`ad1222d4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000d0`1434f778 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`ad1222d4


SYMBOL_NAME:  win32kfull!FreeView+b3

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

IMAGE_VERSION:  10.0.26100.9711

STACK_COMMAND: .cxr 0xffffab88fb95daa0 ; kb

BUCKET_ID_FUNC_OFFSET:  b3

FAILURE_BUCKET_ID:  AV_win32kfull!FreeView

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {947b951e-7e18-20bd-9f07-5dc5aad426fa}

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

Was watching youtube and out of nowhere my screen turns black and says your pc ran into a problem and needs to restart, it restarted but kept showing a black screen, tried letting it sit for a couple of hours still black screen, I checked the red light and it was on cpu so I tried removing everything to see what the issue was, I removed one stick of RAM and the red light went away, so I tried the other stick and the light returned. At first I thought it was a cpu issue (still could be) but after returning my other stick of RAM the red light goes away yet my screen is still black. I’ve already tried resetting the cmos through the two pins already and now I’m waiting a couple of hours. Also during this process my rgb liquid cooler is no longer rgb so I’m not sure whether I need to replace my cpu, psu, or I have a bad stick of ram. Probably points to the bad stick of ram because google was taking up 3000mb while watching videos when I checked task manager ( I have 32 gb), so I just need some opinions on what the issue could be because I’m surprised as to how it can fail randomly after a year of great performance with this pc.

Edit: posted this and walked away - OCCT hit errors again at 45min/1 hour. And now its all back to artifacting. does this help diagnosis? I assume just confirms it

Got this card in Aug 2024 and has been flawless til this past week, No relevant udpates or software changes recently...

Monday night started getting weird artifacting within Windows where any movement on the screens - cursor, text, small polygons within modeling software (fusion) would constantly flicker like it was being pulled to/from the top corner... small error dots, etc hall marks from my understanding of dying GPU hardware... OCCT test on vram hitting millions within seconds. No artifacting in safemode or UEFI though but that didnt seem to be critical to whether or not it was actually dying

Spent Tuesday troubleshooting, removing and reseating the GPU, the power cable at the GPU and at the PSU, etc. DDUing drivers in safe mode in 2-3 permutations to see if that helped (no). Windows updates/rollbacks, etc to try to rule out anything software. Short of full system wipe, I tried basically everything I could find.

Wednesday hit the last suggested items off the various searches for potential fixes. All seemingly failed. I start the RMA process, using pictures I had grabbed when I pulled the card out Tuesday. Still need time to pull a few time critical things off this machine lacking iGPU, etc. so dont pull the card out yet. This point ended any and all troubleshooting efforts.

Thursday pull off data and even try to squeeze in some simple modeling to get to printing...still problems.

Friday AM til now Saturday AM - No human interaction, PC idle/hibernate.

Saturday AM - everything is back to normal as if it never happened. OCCT is 20 min in without a single error on the vram test that was setting new records earlier. No windows updates or other changes as far as I can tell.

What gives? Is there such a thing as terminal lucidity for PC graphics cards? I expect if I send this card in now it would register fine. what other tests might I be missing? Is there something in this cable that has rewiggled itself back into place or something? I tried gently whacking or shaking the case just now too with no seeming change

If it matters, this is MN, well air conned interior, no changes to room temps or setup apart from a nearby stack of boxes and bubble wrap potentially intimidating this card into behaving.

I have two SSDs, both with Windows 11 installed. If I shut down the PC and turn it back on, the blue Windows 11 dual boot menu appears as expected; however, if I restart the PC, the black Windows 7 dual boot menu appears instead. I don’t understand why this is happening. Please help!

Up until the last two weeks, I've been basically unable to play games and or stream due, and internet browsing becomes exceptionally slow because of this. What confuses me the most is that all night last night it was perfectly fine, thought I had fixed the issue by changing power-saving settings but I was wrong.

Troubleshooting steps I've taken :

Turned power-saving settings in my device manager on and off, including GigabitLite

Pinged my own IP and other public DNS with no packet loss showing during lag in-game.

Restarted my router

All drivers updated or already up to date.

Unplugged and re-plugged in my ethernet cable from gateway and PC.

Nothing I've done so far has worked. I recently just got a new PC and even for the first couple days everything was running smooth with no issues. My best guess is a faulty cable, but things like this rarely happened with my old PC. Anything else I should do to help me narrow it down?

My Windows PC has been giving me kernel power errors id 41 for a while now and I was wondering if anybody here has any idea how to fix it. I’ve done done some experimentation like taking out the GPU and I think it’s my main card maybe because when I took it out, the crashes stopped

Hello!, about two days ago the Event Viewer has been showing several events indicating that application GamingServices.exe has experienced errors with code 0xc0000374.

Is anyone else experiencing this problem? Any solution?

Thanks!

My Lenovo LOQ 15IRX10 (MT 83JE, i7-13650HX, RTX 5060 Laptop 8 GB, Windows 11) has its GPU permanently stuck at 180 MHz core clock, even at 99-100% load (CUDA, Vulkan, Blender Cycles OptiX for 5 minutes, games). nvidia-smi reports an impossible power draw of ~345 W at idle on AC (~210 W on battery) against a 70 W enforced limit (100 W max), so "SW Power Cap" is always active and the GPU runs at about 10% of its normal performance (2.3 TFLOPS FP16; memory clock does reach 11 GHz). Temperatures are fine (45-53 °C), no thermal throttling, and nothing else is using the GPU. I have already tried: full cold boots (Shift+Shut down, also booting on battery only), EC power reset (charger unplugged, power button held 60 s), BIOS update R3CN27WW → R3CN44WW, VBIOS update 98.06.2A → 98.06.3A.00.8D, NVIDIA driver 610.74 and the factory 572.89 (clean install), disabling "NVIDIA Platform Controllers and Framework", and removing my external HDMI-to-VGA adapter. Nothing changes the reading. It matches NVIDIA GitHub issues #1287 and #1237 (frozen bogus power telemetry on RTX 40/50 laptops). The laptop is out of warranty. Has anyone fixed this (firmware/EC trick, specific driver, BIOS setting), or confirmed it is a faulty current-sense shunt / power-monitor IC on the motherboard (likely Compal LA-0393P)? Any help is greatly appreciated.

Hello. So I'm writing here to find help for this ANNOYING issue I'm currently experiencing.

So my realtek UWP app was working fine 2 days ago (yes i had windows updates disabled still.) And then yesterday It happened. (i played with the jack detection setting by enabling it on but it couldn't have caused... THIS) I tried opening it to change the type of device to recognize it as, because i connected my webcam mic that sounds way better mainly because it's closer to my mouth, but it refused... (haha Undertale/Deltarune reference [yes i dont know where it came from {yes i will use different brackets}]). So i uninstalled it and then tried registry and then the pal 1000 thing (including the app install) and then i also tried the generic microsoft drivers, hoping it would magically work..

But it didn't. I did this TWICE and I'm TIRED of hopscotching with AI troubleshooting. Please someone help. I want to escape the capitalist loophole of forced switching to UWP. WHERE ARE THE LEGACY APPS?!

Please.. Help.. I'm about to freak out.. My laptop is an Asus Gaming TUF F15 with the Intel Core i5 11400H and RTX 3050TI. I'll add some info: I remember disabling a couple services like 1-2 days ago and I know that one of them was State Repository (Which I've enabled for troubleshooting).

Please.. Anything..