BSOD, 5 Beeps, Help Needed

Question

BSOD, 5 Beeps, Help Needed

Rocky 20

I recently been having no display with my 3060 ti. Would just go black and do nothing after that, my keyboard would still work, i would have audio (discord ppl talking). i would try to reset gpu but that would just give a beep. 2 things would happen, restart after a couple seconds or not restart and would have to force shut down. i have ask around, i tried what i could but i have to no avail. you guys are my last hope. Sometimes on boot it would 5 beep and not display at all, or it would boot normal and go into desktop. Hope im posting this in the right place/tags

I have tried
-Reseating ram/gpu
-I ran HWinfo for my temps/etc and those never go past 70s for gpu, mb is never over 55, cpu never over 70
-Fresh install of windows, completely removed my drive
-My bios update to latest
-Csm enabled
-Pcie link to gen4
-I tried my 1050 ti (that never had any bsod, only a couple of 5 beeps on start up, but usually always displayed)
-OCCT stress test, cpu went to 100 c, was scared of that so i stopped it after a 3 mins
-Furmark test instantly blacked screen
-Windows memory diagnostics would instant black as well and restart into 5 beeps

Im trying to remember what more i did cause i been on this for a whole week with not much sleep, i know i done more.

Things i havent done
-A different psu
-Different motherboard
-Reseat cpu (no paste, maybe in a couple days, i wanna pinpoint the problem first before messing with other hardware and cause more issues)

I have recently been checking my event viewer and i got Whea Logger-Pcie root port, windows error reporting, application crash that usually shows up at crash before or after. Im willing to run more test and more in depth test, to help out more. Because im no technician so i cant really go in depth for coding or what not, i cant see what you all see. If there's specific or info that would show better whats happening, dont be afraid to ask. I dont want to send so much info and it all means nothing and waste someone's time by having them read nothing important to my problem but looks important to me. im sorry for the grammer as well.

Specs
Windows 11 64 bit
b560 ds3h ac-y1
intel i5-11400F
32 gbs of ram
NIVIDA 3060 ti
EVGA SuperNOVA 750 GT, 80 Plus Gold 750W

if any other specs needed i will edit them back in, let me know

Here's my most recent event viewer of whea logger, i removed the secruity id, not sure if thats personal.

I have minidump file and also a hwinfo for sensory but the site wont let me upload those file types

-	System
-	System


-	Provider
--------	--------
-	Provider

			[ Name]	Microsoft-Windows-WHEA-Logger
			[ Name]	Microsoft-Windows-WHEA-Logger

			[ Guid]	{c26c4f3c-3f66-4e99-8f8a-39405cfed220}
			[ Guid]	{c26c4f3c-3f66-4e99-8f8a-39405cfed220}

-	Provider				[ Name]	Microsoft-Windows-WHEA-Logger				[ Guid]	{c26c4f3c-3f66-4e99-8f8a-39405cfed220}

-	Provider
-	Provider

			[ Name]	Microsoft-Windows-WHEA-Logger
			[ Name]	Microsoft-Windows-WHEA-Logger

			[ Guid]	{c26c4f3c-3f66-4e99-8f8a-39405cfed220}
			[ Guid]	{c26c4f3c-3f66-4e99-8f8a-39405cfed220}


	EventID	17
--------	--------	--------
	EventID	17

	EventID	17

	EventID	17
	EventID	17


	Version	1
--------	--------	--------
	Version	1

	Version	1

	Version	1
	Version	1


	Level	3
--------	--------	--------
	Level	3

	Level	3

	Level	3
	Level	3


	Task	0
--------	--------	--------
	Task	0

	Task	0

	Task	0
	Task	0


	Opcode	0
--------	--------	--------
	Opcode	0

	Opcode	0

	Opcode	0
	Opcode	0


	Keywords	0x8000000000000000
--------	--------	--------
	Keywords	0x8000000000000000

	Keywords	0x8000000000000000

	Keywords	0x8000000000000000
	Keywords	0x8000000000000000


-	TimeCreated
--------	--------
-	TimeCreated

			[ SystemTime]	2025-12-14T16:54:34.8540132Z
			[ SystemTime]	2025-12-14T16:54:34.8540132Z

-	TimeCreated				[ SystemTime]	2025-12-14T16:54:34.8540132Z

-	TimeCreated
-	TimeCreated

			[ SystemTime]	2025-12-14T16:54:34.8540132Z
			[ SystemTime]	2025-12-14T16:54:34.8540132Z


	EventRecordID	12226
--------	--------	--------
	EventRecordID	12226

	EventRecordID	12226

	EventRecordID	12226
	EventRecordID	12226


-	Correlation
--------	--------
-	Correlation

			[ ActivityID]	{5a3d13e8-64bc-48e2-a268-efae6a813ba5}
			[ ActivityID]	{5a3d13e8-64bc-48e2-a268-efae6a813ba5}

-	Correlation				[ ActivityID]	{5a3d13e8-64bc-48e2-a268-efae6a813ba5}

-	Correlation
-	Correlation

			[ ActivityID]	{5a3d13e8-64bc-48e2-a268-efae6a813ba5}
			[ ActivityID]	{5a3d13e8-64bc-48e2-a268-efae6a813ba5}


-	Execution
--------	--------
-	Execution

			[ ProcessID]	4012
			[ ProcessID]	4012

			[ ThreadID]	4548
			[ ThreadID]	4548

-	Execution				[ ProcessID]	4012				[ ThreadID]	4548

-	Execution
-	Execution

			[ ProcessID]	4012
			[ ProcessID]	4012

			[ ThreadID]	4548
			[ ThreadID]	4548


	Channel	System
--------	--------	--------
	Channel	System

	Channel	System

	Channel	System
	Channel	System


	Computer	ROB
--------	--------	--------
	Computer	ROB

	Computer	ROB

	Computer	ROB
	Computer	ROB


-	Security
--------	--------
-	Security

			[ UserID]
			[ UserID]

-	Security				[ UserID]

-	Security
-	Security

			[ UserID]
			[ UserID]

-	EventData
-	EventData

		ErrorSource	4
		ErrorSource	4

		FRUId	{00000000-0000-0000-0000-000000000000}
		FRUId	{00000000-0000-0000-0000-000000000000}

		FRUText
		FRUText

		ValidBits	0xdf
		ValidBits	0xdf

		PortType	4
		PortType	4

		Version	0x101
		Version	0x101

		Command	0x407
		Command	0x407

		Status	0x10
		Status	0x10

		Bus	0x0
		Bus	0x0

		Device	0x1
		Device	0x1

		Function	0x0
		Function	0x0

		Segment	0x0
		Segment	0x0

		SecondaryBus	0x0
		SecondaryBus	0x0

		SecondaryDevice	0x0
		SecondaryDevice	0x0

		SecondaryFunction	0x0
		SecondaryFunction	0x0

		VendorID	0x8086
		VendorID	0x8086

		DeviceID	0x4c01
		DeviceID	0x4c01

		ClassCode	0x30400
		ClassCode	0x30400

		DeviceSerialNumber	0x0
		DeviceSerialNumber	0x0

		BridgeControl	0x0
		BridgeControl	0x0

		BridgeStatus	0x0
		BridgeStatus	0x0

		UncorrectableErrorStatus	0x0
		UncorrectableErrorStatus	0x0

		CorrectableErrorStatus	0x1
		CorrectableErrorStatus	0x1

		HeaderLog	00000000000000000000000000000000
		HeaderLog	00000000000000000000000000000000

		PrimaryDeviceName	PCI\VEN_8086&DEV_4C01&SUBSYS_50001458&REV_01
		PrimaryDeviceName	PCI\VEN_8086&DEV_4C01&SUBSYS_50001458&REV_01

		SecondaryDeviceName
		SecondaryDeviceName

Thank you for your time, I really appreciate it!

0 comments

Answer accepted by question author

2 additional answers

Your answer

Answer 1

Lucus-V 6,570 Microsoft External Staff Moderator

Hi Rocky,
Welcome to Microsoft Q&A forum. I'm happy to help.

On modern Gigabyte motherboard with RTX GPU, 5 beeps code means your GPU cannot detect signal from monitor. If you already have turned your monitor on, then the problem should be GPU connector, cable, or monitor connector.

You should try swapping to another port on GPU, changing signal cable, swapping another port on monitor to see if the problem is gone. You should also make sure that you have turned on your monitor before turning on your machine.

I hope that above information is helpful to you.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Rocky 20 Reputation points

2025-12-17T02:33:09.3233333+00:00

I did a couple things, first I swapped power cable for my gpu. When I did I realized my 6+2 pin wasn't connected and it was a flat 8 pin connected. I had those for 3-4 years like that so it's weird till now it's detecting that. I also changed my power settings to high performance. And never to turn off my display, also my pcie express link state power to off. I'm not sure which of all those I did fixed my problem. But I'm very happy it did. I'm not sure what to turn off and see what was really the issue.
Lucus-V 6,570 Reputation points Microsoft External Staff Moderator

2025-12-17T02:47:18.17+00:00

Hi Rocky,
Sometimes issues can arise from a combination of different factors rather than just one specific cause, so it's great to hear that you were able to resolve the problem!

If you run into any other challenges or have more questions, please don't hesitate to reach out anytime, I'm always happy to support.

Answer 2

EmilyS726 227K Independent Advisor

Hello

So, it looks like your computer is already giving you the hardware error beep code. The 5 beeps has meaning. Typically 5 beeps indicates CPU error, but different brands could also mean different thing. You should reach out to OEM support in this case to troubleshoot on the hardware side. This is very unlikely to be a Windows issue.

0 comments

Answer 3

It sounds like you're experiencing a complex issue with your system, particularly related to your GPU and possibly other hardware components. Here are some troubleshooting steps and considerations based on your description:

5 Beeps on Startup: The 5 beeps typically indicate a hardware issue, often related to the GPU or memory. Since you've reseated the RAM and GPU, consider testing the RAM sticks one at a time in different slots to rule out faulty RAM or motherboard slots.
Event Viewer Logs: The WHEA Logger errors you're seeing in the Event Viewer could indicate hardware issues, particularly with the PCIe root port. This might suggest a problem with the motherboard or the GPU. Ensure that the GPU is properly seated and that the PCIe slot is functioning correctly.
Testing with Different Hardware: Since you mentioned trying a different GPU (the 1050 Ti), if possible, also try using a different PSU, as power supply issues can lead to instability. If you have access to another motherboard, testing your components on that could help isolate the issue further.
BIOS Settings: You mentioned having the latest BIOS update and that CSM is enabled. Double-check the BIOS settings to ensure that the PCIe settings are configured correctly for your GPU. Sometimes, resetting the BIOS to default settings can help resolve conflicts.
Thermal Issues: Although your temperatures seem fine, ensure that your cooling solutions are adequate and that thermal paste is applied correctly if you decide to reseat the CPU.
Memory Diagnostics: Since running the Windows Memory Diagnostics tool resulted in a black screen, this could indicate a deeper issue with either the RAM or the motherboard. Consider testing the RAM in another system if possible.
Further Testing: If you can, run stress tests on individual components (CPU, GPU, RAM) separately to see if one of them fails under load. Tools like Prime95 for CPU and MemTest86 for RAM can be useful.
Seek Professional Help: If you've exhausted these options and the problem persists, it might be worth consulting with a professional technician who can perform more in-depth diagnostics.

Remember to document any changes you make and their effects, as this can help in troubleshooting further.

References:

Share via

BSOD, 5 Beeps, Help Needed

2 additional answers

Your answer