Blank screen & Bluescreen error

M

MarkJohnson

Member
Hi

Got a pc from pcspecialist last year and today had a issue where just got a blank screen when booting nothing would come on the screen

When I finally managed to get into windows i had issues shutting down involving a bluescreen error it's created a minidump which I can attach but not sure how

Specs:

AMD Ryzen 7 7800X3D Eight Core CPU (4.2GHz-5.0GHz/104MB w/3D V-CACHE/AM5)


GIGABYTE B650 AORUS ELITE AX V2 (AM5, DDR5, PCIe 4.0, Wi-Fi 6E)
Motherboard wifi aerials

32GB Corsair VENGEANCE RGB DDR5 6000MHz (2 x 16GB)

12GB ASUS TUF GEFORCE RTX 4070 Ti - HDMI, DP

512GB SOLIDIGM P44 PRO GEN 4 M.2 NVMe PCIe SSD (up to 7000MB/sR, 4700MB/sW)

1TB SOLIDIGM P41+ GEN 4 M.2 NVMe PCIe SSD (up to 4125MB/sR, 2950MB/sW)

CORSAIR 1000W RMx SERIES™ - MODULAR 80 PLUS GOLD, ULTRA QUIET

1 x 1.5 Metre UK Power Cable (Kettle Lead, 1.0mm Core)
CORSAIR iCUE H150i ELITE CAPELLIX XT RGB High Performance CPU Cooler

Hope I've posted it all correctly any help would be amazing
 
F

FigmentOfYourImagination

Gold Level Poster
@ubuysa is the resident diagnostician and will hopefully be able to analyse any files to determine the source. I will quote their reply from another post on what is needed:

"download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe. I'd be happy to take a look at the output and let you know of anything that might account for this behaviour
You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here."
 
F

FigmentOfYourImagination

Gold Level Poster
MarkJohnson said:

Had to upload the zip file to mediafire I hope that's right

Do you want the minidump file aswell ?

Thanks for the help
Click to expand...

I'd probably recommend uploading with GoogleDrive, OneDrive or similar. Whilst I have no issues downloading things from sites like Mediafire, some people don't like doing it as they aren't always the most secure websites.

As to the minidump, I just looked and the Sysnative upload has a .dmp file in it so I wouldn't think you'd need to upload the minidump
 
M

MarkJohnson

Member
FigmentOfYourImagination said:
I am not a diagnostic person so my knowledge is limited. I had a look at the .dmp file and it mentions HDaudbus.sys which is an audio component. I would try the following first to see if they manage to do anything:

Open a command prompt (administrator): Click the Windows icon on the taskbar, type in cmd, right-click the result and "run as administrator". Cope/paste the following in:

dism /online /cleanup-image /restorehealth

and press enter

Once that's run, do the same with:

sfc /scannow

Those check the system for any errors and attempt repairs

Edit: This is assuming you can stay in Windows long enough to run those commands
Click to expand...
Yeah I ran those when it happend and it all came back fine the error happend as the pc was shutting down

Before that I could not get it to post nothing on screen or any beeps and I think a red light stayed on the motherboard when it did finally get into windows
 
F

FigmentOfYourImagination

Gold Level Poster
MarkJohnson said:
Before that I could not get it to post nothing on screen or any beeps and I think a red light stayed on the motherboard when it did finally get into windows
Click to expand...

I forgot to come back to this before. Where was the red light? Was it to the right of the RAM sticks? Did it stay lluminated or just light up briefly? I ask as the LEDs will cycle through as the system checks each bit of hardware..if the LED stays on then it points to the potential fault. If so, it may be indicative of a hardware error. I don't know the LED colours Gigabyte use...you will need to work out which of the 4 LEDs it is:

QLEDs.jpg
 
M

MarkJohnson

Member
I have attached the image of the red light which was on even after the system booted

Seems to be the cpu light

Before this the system would not post at all as I mentioned and there was no error beep codes
 

Attachments

  • 20241026_175319-min.jpg
    20241026_175319-min.jpg
    862.6 KB · Views: 29
ubuysa

ubuysa

The BSOD Doctor
I have the Sysnative download, thank you.

From the one dump in there the problem is related to your audio card or its driver. The BSOD happened because a device (or its driver) did not complete a power transition in time (from low power idle state to full power running state). In the dump we can see both the address of the IRP that managed the power transition and the address of the device object that manages the device.

If we list the IRP we can see the drivers involved in the power transition...,
Rich (BB code): 
0: kd> !irp ffffd6095a225820
Irp is active with 10 stacks 7 is current (= 0xffffd6095a225aa0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffd6095d4bc060 00000000 fffff806a58cbe50-ffffd6095d7d81a0 Success Error Cancel pending
           \Driver\HDAudBus    portcls!PowerIrpCompletionRoutine
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 ffffd6095d7d8050 00000000 00000000-00000000    pending
          Unable to load image RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
 \Driver\IntcAzAudAddService
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffd6095d7cfb30 00000000 fffff8065be060f0-ffffd60968c76818 Success Error Cancel pending
           \Driver\ksthunk    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffd60968c76818

            Args: 00000000 00000000 00000000 00000000
The drivers that I've highlighted there are the ones failing the power transition (the ksthunk.sys driver is a Windows driver involved during the BSOD). The failing drivers are for your Realtek audio device; the main Realtek audio driver RTKVHD64.sys and what looks like an Intel audio driver IntcAzAudAddService.sys. I suspect that this is an Intel on-board audio device that uses a Realtek chipset.

The device object allows us to obtain the address of the device node which describes the actual device...
Rich (BB code): 
0: kd> !devnode ffffd6095d5f4c40
DevNode 0xffffd6095d5f4c40 for PDO 0xffffd6095d4bc060
  Parent 0xffffd6095526ea20   Sibling 0000000000   Child 0xffffd6095dc6e810
  InstancePath is "HDAUDIO\FUNC_01&VEN_10EC&DEV_0897&SUBSYS_1458A194&REV_1005\5&22057c6f&0&0001"
  ServiceName is "IntcAzAudAddService"
  State = DeviceNodeStarted (0x30a) @ 2024 Oct 26 16:50:01.308
  Previous State = DeviceNodeEnumerateCompletion (0x30f) @ 2024 Oct 26 16:50:01.308
  StateHistory[07] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[06] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[05] = DeviceNodeStarted (0x30a)
  StateHistory[04] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[03] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[02] = DeviceNodeStarted (0x30a)
  StateHistory[01] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[00] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[19] = DeviceNodeStarted (0x30a)
  StateHistory[18] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[17] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[16] = DeviceNodeStarted (0x30a)
  StateHistory[15] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[14] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[13] = DeviceNodeStarted (0x30a)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[10] = DeviceNodeStarted (0x30a)
  StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[08] = DeviceNodeEnumeratePending (0x30e)
  Flags (0x2c000130)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_NO_RESOURCE_REQUIRED, DNF_NO_LOWER_DEVICE_FILTERS,
                      DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS
I've highlighted the hardware IDs of the actual device (HDAUDIO\FUNC_01&VEN_10EC&DEV_0897) and they are for your Intel/Realtek Audio device and the associated Intel driver that we saw in the IRP.

BUT

From the symptoms that you describe I'm not 100% convinced that this is the cause of your blank screens. It seems more likely to be a symptom of your issues shutting down. It is worth checking that the chipset drivers form the motherboard are up to date and that the audio driver for the board is up to date. I see from the website for your motherboard that there are recent driver updates for both the chipset driver and the audio driver - and other devices too. I would get all those drivers up to date.

There have also been three BIOS updates since the version you have installed, all with AGESA microcode updates - with AMD systems the AGESA code needs to be kept updated. YOU MUST talk to PCS before updating the BIOS however if you want to keep your warranty. I would ask PCS about these BIOS updates and whether they might relate to your blank screen problems. I would want to be on the latest BIOS there.

I also notice in your System log that there are regular and frequent failures for what looks looks a Gigabyte utility GBTECService...
Code: 
Log Name:      System
Source:        Service Control Manager
Date:          27/10/2024 10:00:16
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Matthew
Description:
The GBTECService service failed to start due to the following error:
The system cannot find the file specified.
This is probably a component of the Gigabyte Control Center and it's not impossible that this failing utility may be involved. I'm not a fan of these motherboard tools in any case and unless you really need it I would uninstall it. Whatever tool it is it's clearly not happy.
 
Last edited:
M

MarkJohnson

Member
The blank screen was when the pc would not POST and when it did finally do it more than one of the red led lights came on at once

PCS have taken it back under a RMA to have a look and I've also had other issues so will see what happens
 
M

MarkJohnson

Member
Getting a refund they can't replicate the issue but evidence I gave them showed there was issues so getting a partial refund

Getting a new system elsewhere as had lots of problems with this one so want a clean slate

Thank you for the help
 
You must log in or register to reply here.
Top