Black Screen Video 10 Hours
Dimple Belousson
My new iPhone 14pro max has a black screen this morning following its regular overnight charge. I have tried the reset and it is now plugged in via a cord hoping this will work. Anyone else had this issue?
I woke up this morning and found out that this had happened to my iPhone 14 pro max. The tip of volume up/down then hold the power button worked after a few tries (thankfully), but what I'm amazed at is that this was first reported 2 months ago and still hasn't been fixed by Apple. It's the first time this has happened to an iPhone of mine (and I've had them all!), but come on Apple, this should be fixed by now.
FYI, 16.0.2 did NOT fix the problem on my 14 Pro as hoped. I put it back on my wireless charger last night for the first time since my overnight BSOD a week ago. When I woke up this morning, it was clear the phone had rebooted (passcode required; different home screen widgets showing). I opened the battery app and found it had been unresponsive for 3 hours overnight, then re-booted itself. My first BSOD occurrence while charging overnight was similar but never rebooted. This is really annoying...
BTW, there's a 300+ post on Reddit discussing the issue. It seems to be highly correlated with charging, especially overnight charging, both wired and wireless. There are a couple of cases where this happened while not charging, but those seem rare. I'm surprised it hasn't appeared in the press yet. The Click Vol Up, Click Vol Down, Hold Sleep button until logo appears (up to a minute or two!) fix seems to revive the phone in all cases I've seen...
The first time this happened on my Iphone 14, the reset worked (volume buttons, then hold power button for a long time). It just happened again this morning when i took it off USB charger. Reset did not work. Tried 3-4 times . Finally, after holding power button for a long long time, a message popped up that showed message to connect phone to computer. When i connected to computer it said I needed update to firmware. Said 9 minutes remaining. We will see if this is a permanent fix.
Today the helpdesk of GameHouse advised me to download Driver Booster. I installed v4.5 and DB found 11 issues to solve. Outdated drivers. First few drivers went well. Just a restart and another restart and 7 problems were fixed. At this moment the 8th driver (don't know which one) makes my HP laptop doesn't start up. All I see is arrow and circles dots going around. No start. Is this a common problem or normal it takes such a long time? I can't use or enter my laptop now. Restart doesn't work either. All I see is HP logo showing up and then the arrow + circles. Should I just be patient and let it run for many hours more? Or is there another thing I can do?
In the meantime, you should boot your pc in Safe Mode, Launch System Restore -(If you have Advanced Systemcare installed you can access system restore in the Rescue Centre)- and restore your pc to a time before you updated the drivers. This should revert the drivers back to the originals.
If you then wish to update your drivers you should so so one at a time and reboot after each update. Then if you hit the same issue you will know which driver is causing the problem and can ignore that update.
Thanks for thinking with me. I had to create new bootfiles (HP trick with button combination). System Restore was gone, all repairfunctions gone too. Safe mode didn't start up either. I'll never use Drive Booster again. It has one goal: destroying your computer, collect personal data. So to me it's malware. Fortunately my laptop was still recognising an USB port. Recovery software on an USB stick. So at this moment I'm trying to recover my laptop this way. Don't use Power Booster people. It's crap!
Exactly! Didn't have any BIOS problems until I downloaded Driver Booster 4.5. So there are two options: DB 4.5 itself is messing up harddisk Bios files or the 'recent driver software' DB 4.5 found for your computer or laptop is malware / virus. Can't use Driver Rollback function because Windows is not starting.
The only thing that was working were some rootfiles last night. The kind of screen you can only enter by pressing Escape key several times or F8, F9, F10 imidiately after start up. No Windows or mouse arrow but only up and down keys and escape button + enter to go to next pages. HP files on USB stick and laptop still recognising USB port made it possible to make new partition and start up laptop back to HP factory settings. I do believe HP was the giant hero last night. So I have Windows 8 running now. Big relieve. With HP factory settings and this old version of Windows running again Im able to download import other software and update everything to 2017. But might take a few days. 111 updates available now lol So glad everything is working again. No Driver Booster more for me in future. Thanks for thinking with me.
Really sorry for the inconvenience. You may please kindly know that the driver update provided by Driver Booster works properly on most of users computers. And it is impossible for our testing team to test every single driver update in every single PC situation because driver updates quantity is colossal and PC situations are various, and even though the updates are from official recourse and tested before being added into our database, they cannot be guaranteed to be error-free. So sometimes the problem happens.
Update 1: Hello it's been a while so I'll give an update. My Ubuntu install is still crashing. For a time it got worse where 90% of the time my main account won't load. I created a second test account and that loads perfectly fine with no delay whereas the main could take hours(seriously I would go play ps4 while I waited)gotten better by removing some extensions as now its 50/50 whether I can sign in. Also a few things of note, my HDD indicator keeps blinking throughout the whole process. I have checked the disk for errors and it came back fine. I will try it again, though as maybe all the forced reboot did something. Sometimes it crashes before logging into an account but this is rare.so maybe on top of my having something messed up there's something also messing up the login globally. I haven't been able to pinpoint exactly what extensions, if it is an extension, crashes my account I have gone one by one enabling the extensions and deleting the seemingly responsible extensions and it will work for a few reboots and then start again IDK why but it seems like the act of disabling or enabling a extensions fixes the problem for the next boot. Sorry, this turned into such a long thing with so many ]posts I just wanted to document all I have tried to do and noticed. I'm at a loss as to what to do other than just using another account or disabling all the extensions before logging out or rebooting and then enabling them after I login. Idk if the last one would work
Update2: After trying Prateek kkY it worked for all of yesterday I tried several reboot and shutdowns and it was fine so I turned it off and today I went to use it and it wouldn't log in to my account again
Make sure no late startup jobs and auto-start applications are loading, sometimes Ubuntu get stuck in while starting some network and gtk applications (dhcpcd, netctl and systemctl)make sure NVIDIA latest or its drivers are loaded normally, do blacklist Nouveau drivers, also do some simple sanity checks.steps to override start/stop jobs:
When they released the new version before this on. 8.1.20 I think. It worked until Last week and started to go black screen after 8 hours. Upgraded to the new version and same issue. The video feed screen that is open will go out to a black screen and stop recording. I thought they fixed it but it started to fail as usual. I believe they have a issue with AMD 3400G CPU's. My PC also runs Plex 24/7 and never has a issue. So this tells me that the 3400G is fine. The old version 7 would crash but it took over 24 hours to crash. A better one where you just had to restart it. Does any one have a AMD 3400G build running the client?
If you read the header it states the version number. You just did a cookie cutter response. Why is there no debug version so a log can be created so we can see if it can catch the failure. If you will not release one then put back the last version 7 on your website. It is more stable then this one.
I've also experienced this, I've got a couple of different machines and it happens mostly on the oldest/slowest machine (Intel Core2 Duo). It tends to happen more in playback mode and seems to happen within a few minutes of opening the first time, sometimes in response to a window event like scrollwheel, mouse click or maximise. Once the video goes blank there doesn't appear to be any way to get it back without closing and reopening the application, it seems to happen less after being opened the second time. Even on this older machine it doesn't seem to happen with the older Reolink Client (v7.2.2.33) which seems to be completely different software.
I haven't noticed it happen on a newer Intel i7 machine, but it could be more to do with the video card of the machine in question.
Hope that helps!
I' m posting the mail that I sent to sup...@helpdesk.eset.com 4 days ago.
"Recently I have migrated my windows 10 to a new m2 ssd drive (Samsung NVMe SSD 980). Old one was a normal SSD. After migration, I noticed a long black screen duration (10 to 30 seconds) time before windows login at nearly each boot. After many tries (changing used sata slots, updating drivers, removing other storage drives from the system, migrating to old ssd by using a recovey image) I have found that If my new SSD is connected, there is no way to get rid of this black screen delay except uninstalling Eset Internet Security. When I unistalled Eset Internet Security, boot time returned to normal.
I want to use both my new ssd and Eset Internet Security. So please fix this problem."
Would it be possible to configure Windows to generate complete memory dumps as per , re-enable Deep Behavioral Inspection (DBI), reproduce the issue and manually trigger a crash to generate a memory dump? When done, please supply it for perusal compressed in an archive. Afterwards you can temporarily disable DBI while the issue will be investigated.
c80f0f1006