Aurora r13, second machine, blackscreen again, and multiple.dll errors after
the machine being initialized
Hello All,
Due to the black screen and power on problem of the previous machine. The tech department requested a replacement for me. I just received the new machine, however, for the first time I powered on the replacement, went into windows, it has multiple .dll errors, which include sqlite3.dll, WebView2Loader.dll, VCRUNTIME140.dll, VCRUNTIME140_1.dll, I know it's obviously a returned machine from someone else, I don't care about that part. I just wonder
1. Why a newly received machine have multiple dll errors?
2. The first time I enter the windows, I immediately set the power performance setting on both ACC and battery to high
performance.
The computer runs fine for the first 2-3 hrs. Then black screen problem just occurred again.
Thanks for the suggestion. Just update the bios, the same error codes showed up again. Before the update, the error codes showed up right after log in. Now the error codes show up on the log in page.
Try turning off microsoft teams at startup. Go to your search bar, type "startup apps" and open that up. Scroll through it and turn off Microsoft Teams. See if that helps. A clean install of Windows would probably fix it, but try the other suggestion first.
If the black screen problem is during post, prior to windows, it will not be related to Windows.
In that case I would contact support again, since this is a system straight out of a box.
The DLL errors should not happen out of the box either, but that you likely can fix with a clean Windows installation from USB media, or the OS recovery mode from the recovery partition.
For the first machine that has the black screen problem, I found a temporary solution is to let the computer keep playing web streaming video (then the computer will always be running, and never turns to sleep. In contrast, if I set the power plan to never to sleep and let the computer be there without any operation, the blackscreen problem will occur). But I don't think that's a feasible solution, any idea about what's the problem behind this issue?
F34R
2 Intern
•
436 Posts
462
0
Posted January 18th, 2022 17:00
If you haven't already, download and install the 1.08 bios. See if that fixed your problems.