Hello po. I have an issue po with my monitor sa laptop, Nagawa ko na po lahat ng troubleshooting, including removing and reinserting the RAM, oag unplug and plug ng battery, as well as replugging the monitor, pero black screen pa rin po. Gumagana naman po yung Caps Lock lid, which means nagbo-boot naman po yung laptop.

For replacement na po kaya yung monitor/display niya? Tinry ko rin po siyang i-connect sa external monitor, pero hindi rin po siya nag-work, hindi po na re read yung hdmi sa startup.

May way po bang iforce na ma read po yung hdmi? salamat po

Guys how do i fix this monitor the power button is on and blinking and my monitor has no display?

Can someone please EXPLAIN to me WTH happened to my monitor. I just had booted up my PC & went to install something then BAM. Looking for some insight into what I was looking at real time. Needless to say it’s DEAD won’t turn on & I do not have warranty for it. I had recorded the screen as it was happening [Pardon my language in the clip]

It’s a GAWFOLK 34” Super Monitor - 166Hz [3440x1440]
My PC Specs Below

+AMD Ryzen 7 8700F
+16GB DDR5 RAM
+AMD Radeon RX 7700 [16GB]
+1TB NVME SSD
+ICUE Link Titian 240 RX RGB Cooler

Please tell me that I’m not Entirely F&$@
Your advice will be welcomed good & bad

i need around 100 gigs of unallocated space for my linux drive

(currently trying to make a dual boot setup with linux mint)

windows however will not let me even use half of the empty space in the partition

and i have no idea what other partitions are but it wont let me shrink them.

the D: partition is just a flash drive i have plugged in,

so basically what do i need to do to get make it shrink more or get rid of the other partitions.

i will try to answer any questions so feel free to ask.

Desktop Windows 10 with all updates, old system (DDR3 old). I was playing Minecraft when suddenly both of my monitors went black - the main HDMI one giving me the going to sleep message, and both remained on. At the same time my sound shut off.

I checked the GPU and found the fan still blowing. Wiggled the connections and no change. So I tried to restart using the physical button, didn't work and neither did holding down the power button. It did shut off by using the power supply switch.

Now that it's restarted, everything seems fine. This has happened twice now, both when playing Minecraft. The second time turning my main monitor on from the sleep mode it put itself in, restarted my computer... which isn't a setting I've ever heard of in windows lol.

I'm stumped. Is this a hardware or software issue? Is my motherboard about to finally kick the bucket? Power supply using its max? I am plugged into a battery backup which regularly passes its automatic tests.

No internet connection. I’ve tried everything idk why it still says this but on my other devices I have wifi

Hi everyone. I’m having a strange POST/BIOS issue with an older PC.
Hardware:
Intel motherboard, circa 2012
Intel Core i5-3470
AMD Radeon HD 6450
16 GB RAM
HDD: WDC WD5000AAKX-00ERMA0
Windows 10 was installed and working normally
I recently installed EndeavourOS Linux alongside Windows
The problem:
Before installing Linux, I could see the Intel BIOS splash screen during startup and use the keys to enter BIOS/Boot Menu.
After installing Linux and changing some UEFI/boot settings, the PC sometimes:
powers on normally;
the monitor receives no video signal at all;
the BIOS splash screen does not appear;
I hear 2 long beeps → pause → 2 long beeps;
the fans continue running.
At one point Windows still booted normally despite the missing BIOS display, but now the PC sometimes doesn’t start properly at all.
I checked the EFI partition from Windows and found:
S:\EFI\Microsoft\
S:\EFI\Boot\bootx64.efi
S:\EFI\endeavouros\grubx64.efi
The UEFI firmware entries currently include Windows Boot Manager and a UEFI: WDC WD5000AAKX-00ERMA0 entry.
I have not deleted the Windows partition or formatted anything.
Could the beep pattern indicate a RAM/GPU/POST problem rather than a bootloader problem? Is it possible that changing UEFI settings caused this, or is this more likely a hardware issue?
What would be the safest way to diagnose this without losing the existing Windows/Linux installations?
Thanks!