My dark has been running great for weeks. Within the last week, I’ve noticed, at random, when I am in the bios editing or navigating...all the sudden the screen will go black and the a6 error is shown on the debug led. A reset usually solves the problem and I can navigate the bios until it randomly pops up again. I know a6 is SCSI related. I only have 2 m.2 drives and a 1080ti ftw3. Is it a bad mobo? Graphics card? I really cannot replicate the error with certainty...it seems to happen at random and only in Bios.

I’ve tried clearing the CMOS and reloading my bios settings but it seems to creep up again at some point.

Any thoughts are greatly appreciated.

Yeah, not sure about that since it has been working fine for a month and no issues once in windows.

I talked with support and they mentioned maybe the psu with a fluctuating 12v rail. Going to swap in a spare to see if the error resurfaces.

Yes, essentially the monitor losses signal and the debug led shows a static a6.

https://www.evga.com/support/faq/afmmain.aspx?faqid=59363
"A6" - SCSI Detect | A6 will show while inside BIOS
 
This POST code should be normal. The  loss of display, is not. Does this happen with integrated graphics as well, or is this only with the GPU you have installed?
 
-Jacob B.

I have not touched the stock bios version at all since receiving the board. AFAIK, they are on 1.03 as well but I can check.

Dropped another PSU in. I tested the 12v rail of the PSU I had in the PC with a multi-meter and it was fluctuating quite a bit...while the one i swapped it out with held a constant voltage. We'll see how it holds up over a week and if the error comes again.

onMute
Dropped another PSU in. I tested the 12v rail of the PSU I had in the PC with a multi-meter and it was fluctuating quite a bit...while the one i swapped it out with held a constant voltage. We'll see how it holds up over a week and if the error comes again.

Sounds like that could've potentially been the source of the issue. Any update on this?
 
-Jacob B.

I guess I spoke too soon. It happened again right as my bios screen was loading. The screen lost signal. Before resetting, I hooked up the onboard video to my monitor to see if the signal would come back, no luck. Not sure if the system will automatically switch between the two. Anyways, a simple reset and all works well.

Any ideas?

Depending on the card you have, you may want to try the NVIDIA Graphics Firmware Update Tool for DisplayPort 1.3 and 1.4 and see if this helps your issue at all. I have seen this fix some strange issues with display output.
 
-Jacob B.

Installed, we'll see how it goes.
 
Another oddity presented itself as I booted the machine this morning to install the firmware update. As the machine was booting, the normal POST screen came up. Next, as it was moving into the windows load, the screen went blank (oddly, the display signal didn't drop...it just kept the back-light on with no picture). The debug LED showed the CPU temperature so it appeared something in the boot process was hanging. Simple reset worked fine and then i was able to install the firmware update.

Well the same thing happened again when i went to power on the system.
 
"As the machine was booting, the normal POST screen came up. Next, as it was moving into the windows load, the screen went blank (oddly, the display signal didn't drop...it just kept the back-light on with no picture). The debug LED showed the CPU temperature so it appeared something in the boot process was hanging."
 
This time, I managed to find the corresponding errors in the windows event log.
 
The first error thrown was a "Kernel Boot Error" with the details listed as "Windows failed fast startup with error status 0xC0000001". Followed by, "volmgr" with details listed as "Dump file creation failed due to error during dump creation.". The next item in the log was my forced reset.
 
After some online research, I disabled fast boot...so we'll see if it comes up again. Not sure, but it seems like it might be software related. I still cannot explain the display occasionally dropping while in BIOS....maybe that was taken care of by the firmware update.
 
More updates to come...
 
 

onMute
Installed, we'll see how it goes.
 
Another oddity presented itself as I booted the machine this morning to install the firmware update. As the machine was booting, the normal POST screen came up. Next, as it was moving into the windows load, the screen went blank (oddly, the display signal didn't drop...it just kept the back-light on with no picture). The debug LED showed the CPU temperature so it appeared something in the boot process was hanging. Simple reset worked fine and then i was able to install the firmware update.

Interestingly this has happened to me for the first time this morning, took couple of power offs and ons to get the system booted up.
I never saw a windows  screen, seemed to happen after successful post and was in process of loading windows. Digital readout on board was showing cpu temp.

onMute

GGTV-Jon
onMute when this happens during boot up / in bios if you power cycle the monitor does your display come back?
 
I have 2 Samsung monitors, same era different models - both HDMI. One of them when used as the primary display has a hard time showing the bios when I try to load it. A power cycle of the monitor and it is OK, the other one does not have this issue. I think it is a monitor firmware issue with the one monitor - it does not like whatever the timing delay is during video switching between the boot screen and bios and just goes black - no signal loss warning
 
Of course that happened to be the monitor that I was using when first setting up my new build - freaked me out at first until I realized it was a monitor issue and not motherboard / GPU issue

Thanks! I’ll keep this in mind if it happens again.

d.burnette

onMute
Installed, we'll see how it goes.
 
Another oddity presented itself as I booted the machine this morning to install the firmware update. As the machine was booting, the normal POST screen came up. Next, as it was moving into the windows load, the screen went blank (oddly, the display signal didn't drop...it just kept the back-light on with no picture). The debug LED showed the CPU temperature so it appeared something in the boot process was hanging. Simple reset worked fine and then i was able to install the firmware update.

Interestingly this has happened to me for the first time this morning, took couple of power offs and ons to get the system booted up.
I never saw a windows  screen, seemed to happen after successful post and was in process of loading windows. Digital readout on board was showing cpu temp.

Try disabling fast startup in windows to see if it happens again. Also, go to your event viewer and under administrative try to see what errors were being thrown around boot. Curious if you had the same as me.

No errors specifically like yours, a few random ones but nothing related to what yours were describing.

RNeon
Hello, I’ve build my rig yesterday and have noticed the exact same issue. Sometimes computer starts with 5 beeps and no video. After I restart the computer everything works fine. Or the computer is starting and after the windows boot Sequenz the screen went black. I no this thread is old now but maybe you can share the solution if you had one. Thx

The 5 beeps and no signal happens to me as well - not often at all but on occasion.
Shut down and power up again and all is well.
It is almost like it is not getting a video signal or something.

Ok i solved the issue for me. At the 5 beeps I saw on the postcode also d6. That means that there is no output signal. After reading in this forum several issues with d6 I’ve tried to reproduce it every time. So i unplugged the Display port cable and after that there comes the 5 beeps. So i was thinking why it happened to me every time when my computer was for several hours off. I figured out that my monitor has a display port deep sleep function. This means that if the monitor is a longer time in stand by, it goes to a deep sleep. So the Motherboard is checking on Startup if there is a monitor present and because the monitor is in deepsleep and it needs a longer time to wake up, the motherboard think that there is no output signal present. Long story short, I’ve disabled the deep sleep function in the monitor OSD and it never happened again.