Random Crashes to a Black Screen. No Errors.

zbook · Sep 1, 2025

ZeroC00l said:
I'm dont know what "\device\harddisk5\dr8" is. I dont have a hard drive with that name. I have Local C: | "Main Drive" D: | "Secondary" E: | "Work" F: drives. Nothing named "harddisk5 or DR8.

It's symbolic nomenclature and is unlikely to be any of the drives that remained attached from 08/13 - 08/31.

Plan to monitor the second RAM pair.

JLArranz · Sep 1, 2025

According to this source How to identify drive device from event log (Harddisk#\DR#)? (I've found many matching sources for "HardDisk#", not for "DR#", although I trust this page more than others I've seen):

- HardDisk5 means the disk (not partition or "volume") named as "Disk 5" by Disk Management and similarly by DiskPart and other parts of Windows, in the moment the log report or whatever is generated. As disks are counted from "0", this means a 6th disk, but you might have had or not 6 disks (including pendrives) in such moment, as a disconnected disk leaves a gap in the numeration if it isn't the last one, that will be reused by other disk(s) (any new connected disk gets the lowest number available).

- DR8 means the 8th disk (or pendrive) connected during the Windows session. DR numbers also start by "0" but they aren't reused. New connected disks get the DR number of the just previously connected unit plus one. The same disk will get different and increasing DR numbers if it's disconnected and connected again.

ZeroC00l · Sep 1, 2025

zbook said:
3) Run HD Tune (all drives) (old version) > post

zbook said:
images or share links

Plan to monitor the second RAM pair.

Second RAM pair gave me two black screens in the past two days

Error scans for all drives.

WesternDigital_NVMe_Error Scan_083125.webp

Here's a .zip of the Health .txt documents. The NVMe drive didn't have anything under the health tab.

zbook said:
4) Run Sea Tools Long generic test (all drives) > post images or share links

All drives passed the long generic test.

JLArranz said:
DR8 means the 8th disk (or pendrive) connected during the Windows session. DR numbers also start by "0" but they aren't reused. New connected disks get the DR number of the just previously connected unit plus one. The same disk will get different and increasing DR numbers if it's disconnected and connected again.

It was probably from one of the usb drives I have. I'm thinking nothings wrong with any of my SSD's.

I do wonder if its a voltage thing? My PSU is from around 2015 and the 3000 series I know recommended a higher wattage than what I actually have, but its also never been a problem before and I've had the 3080 since early 2021. Is there a way I can get a history of voltage usage that will survive a reboot or some sort of overlay so I can look at the voltage up until the black screen appears? Right now if I reboot I lose the numbers I was monitoring and everything is back to normal.

I'm also going to try rolling back video drivers to a version before all these problems started, updating BIOS and uninstalling Vanguard anti-cheat as I've read some games recently have been having conflicting issues with that.

zbook · Sep 1, 2025

Please post a new V2 share link for the second pair of RAM.

DJNelson · Sep 1, 2025

I've seen this kind of problem before. Solved it by doing a clean install of graphics drivers and turning off notifications when gaming. Can't hurt to try.

JLArranz · Sep 1, 2025

The build should consume about 500 W when gaming (you add between 50 and 100W to the sum of the processor 105W and gfx 320W TDPs, this math doesn't require a lot of precision). The PSU recommended is a bit arbitrary and leaned upwards if at all, imo 750W suffices if the PSU has high quality, what it looks like. Wear... it's lower at lower temps, but I'd suspect about the gfx card before the PSU b/c you don't have bad PSU symptoms (POST and bootup difficulties). Idk if monitoring voltages has any value, I've also seen many broken sensors (in this system, +3.3 V -> 2,46 V and DRAM -> 2.23 V lol -DDR3 works at 1.5 V-).

PSUs deteriorate and die pretty fast in my experience. Deterioration of 200-300W cheap PSUs used in very old times was instant: you had a totally normal session, normal shut down too, and next power on attempt the rig wouldn't respond at all, you knew you had to replace the PSU. The only modern PSU I've had broken (a 550W one after 13 years of use) had increasing bootup difficulties during some few sessions that I was attibuting to instability, until finally the computer turned on but did not boot (I cannot remember if it did the POST).

I've read that some monitoring tools can save a history of data (that Idk if it would survive a hang), although I've never used it. The overlay you say, also called OSD, isn't very easy to get but it can be got, see post #33, I've recently read from a user that you'd only need HwInfo and MSI Afterburner, not RTSS.

PenPusher · Sep 2, 2025

Do you have a second monitor to connect to the internal graphics port?
May be useful if it survives black screen on main graphics?

ZeroC00l · Sep 2, 2025

zbook said:
Please post a new V2 share link for the second pair of RAM.

Attached is a .zip

DJNelson said:
I've seen this kind of problem before. Solved it by doing a clean install of graphics drivers and turning off notifications when gaming. Can't hurt to try.

I read about a similar issue though not exactly the same and using DDU to uninstall graphics drivers fixed it. So I used DDU to uinstall graphics drivers and reverted to a driver from December 2024 thats known to be stable yesterday. So far no black screen. I'll keep my fingers crossed but I'm hoping thats it. Probably wont be certain it worked until I can go a week without black screens.

JLArranz said:
I've read that some monitoring tools can save a history of data (that Idk if it would survive a hang), although I've never used it. The overlay you say, also called OSD, isn't very easy to get but it can be got, see post #33, I've recently read from a user that you'd only need HwInfo and MSI Afterburner, not RTSS.

I was wanting to see a history of voltage because this video talks about power spikes in the 30 series of cards, and the shutdown seen at :23 seconds. I thought if could see if a power spike is happening it might give a clue as to source of the problem.

PenPusher said:
Do you have a second monitor to connect to the internal graphics port?
May be useful if it survives black screen on main graphics?

I actually do, I completely forgot I had it. Its buried somewhere though so I'll have to dig it out. If I get another black screen i'll try this.

JLArranz · Sep 2, 2025

I don't think you can catch a voltage spike with an OSD (although I'd consider it to see the temps). It happens too fast. It's like trying to measure the speed of something that destroys an anemometer (like a stone) reading the file of measured speeds. Thanks for the video, although I'm not good with spoken English.

ZeroC00l · Sep 2, 2025

PenPusher said:
Do you have a second monitor to connect to the internal graphics port?
May be useful if it survives black screen on main graphics?

I think I jinxed myself, I got another black screen crash today. Before rebooting I tried an HDMI cable plugged in to my main monitor and I tried plugging in the spare monitor with an HDMI. Nothing. Still a black screen.

@zbook Not sure if the attachment actually went through. Here's a link

zbook · Sep 3, 2025

ZeroC00l said:
I think I jinxed myself, I got another black screen crash today. Before rebooting I tried an HDMI cable plugged in to my main monitor and I tried plugging in the spare monitor with an HDMI. Nothing. Still a black screen.

@zbook Not sure if the attachment actually went through. Here's a link

The last recorded was on 08/31.

ZeroC00l · Sep 3, 2025

zbook said:
The last recorded was on 08/31.

What was last recorded on the 31st?

zbook · Sep 5, 2025

ZeroC00l said:
What was last recorded on the 31st?

Black screen

ZeroC00l · Sep 5, 2025

zbook said:
Black screen

I see, well it did crash to a black screen on the 2nd. Do you have any other ideas what the source of this issue could be?

zbook · Sep 5, 2025

Please try the steps in this link:

Troubleshooting blank screens in Windows - Microsoft Support

If your computer is showing a black or blank screen in Windows, these troubleshooting tips could help get your system back up and running.

support.microsoft.com

Report the results for each.

ZeroC00l · Sep 9, 2025

zbook said:
Please try the steps in this link:

Troubleshooting blank screens in Windows - Microsoft Support

If your computer is showing a black or blank screen in Windows, these troubleshooting tips could help get your system back up and running.

support.microsoft.com

Report the results for each.

I've been talking to nVidia customer support the past few days and today they asked that I update to their newest driver from ver566.36. Not sure if it was a coincidence since I've gotten black screen on the older driver as well but a couple hours after updating I got a black screen.

I tried these steps in that link you provided. None of them worked. I also tried turning the monitor off and then on again, that didn't work.

Before this black screen today I went down to using 1 stick of RAM (16GB) to see if just one of the RAM sticks is causing a problem. Things were stable for about 3 and half days until today. I'm going to swap to a different stick and see if I get another crash.

zbook · Sep 9, 2025

Please post a new V2 share link into the newest post.

ZeroC00l · Sep 12, 2025

zbook said:
Please post a new V2 share link into the newest post.

Here is a link to a V2 log. What are you hoping to find, i've done 2 of these in the past? Would it really show anything different?

Ghot · Sep 12, 2025

ZeroC00l said:
Would it really show anything different?

If it only shows one thing different, we can use that information.
If it shows no differences, we can use that information.

Cromax · Sep 12, 2025

black screen is gpu driver + stupid mpo overlay disable mpo overlay and its fixed just dont forget to restart after disable to apply had same issue

Random Crashes to a Black Screen. No Errors.

Well-known member

My Computer

Active member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computer

Member

My Computer

Active member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Similar threads