Only while plugged in, the Laptop screen(goes black) doesn't respond after idle screen timeout.

all your mini dump files are for today 11/26/2020. That does mean ETD.sys causes BSOD.

Wait a second because I changed the ELAN touchpad drivers to Windows precision touchpad using an unofficial method using this link given here-- https://www.windowscentral.com/how-enable-precision-touchpad-drivers

I did this cause I felt this precision drivers are more responsive and easy to work with Touchpad after I installed I used to get blue screen of death at every startup(What failed on BSOD showed ETD.sys) after installing and I fixed it by stopping elan service and ELAN startup service like this

But the thing is, the issue which I am facing is not after installing this but long before I even knew about this precision driver. So i don't think ETD.sys is causing Black screen. Because this issue was present even after Factory reset.

Ok I found one file that causes a BSOD, it called ETD.sys from your mini dump file. 

To read more about ETD.sys please follow the link don't download anything there, I send to you to just get an information about the file https://www.file.net/process/etd.sys.html

KMODE_EXCEPTION_NOT_HANDLED ETD.sys+4e9d6 (relate to  mouse pad) (is possible your black screen is caused by this ETD.sys) Get an external mouse ready in case your mouse pad refuses to work after the modification we are going to do. Here is what you are going to do.

open command prompt as admin

cd\  (hit enter key on your keyboard)

C:>

C:>cd windows\system32\drivers (hit enter key)

C:\Windows\System32\drivers> ren etd.sys etd.sys.old     (hit enter key) (ren command is to  Renames a file or files)

Then reboot your laptop

Work with your computer as you did and see if the blank screen is still there, we close the laptop lid when we use an external monitor connected to the laptop ports (vga, hdmi,dvi). You can still close it to see if it freezes. Leave a feedback

Application

Bonjour Service : -

1 - Local Hostname LAPTOP-JETP8JQ4.local already in use; will try LAPTOP-JETP8JQ4-2.local instead

2 - mDNSCoreReceiveResponse: ProbeCount 1; will deregister   16 LAPTOP-JETP8JQ4.local. AAAA FE80:0000:0000:0000:4D40:9F9E:F4C5:6FE9

3 - mDNSCoreReceiveResponse: Received from FE80:0000:0000:0000:4D40:9F9E:F4C5:6FE9:5353   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:16FB:BE09:4D40:9F9E:F4C5:6FE9

4 - Local Hostname LAPTOP-JETP8JQ4.local already in use; will try LAPTOP-JETP8JQ4-2.local instead

5 - mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 LAPTOP-JETP8JQ4.local. Addr 192.168.43.189

6 - mDNSCoreReceiveResponse: Received from 192.168.43.189:5353   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:22BB:F03B:C15E:2453:74D2:A7AB

7 - mDNSCoreReceiveResponse: Resetting to Probing:   16 LAPTOP-JETP8JQ4.local. AAAA FE80:0000:0000:0000:4D40:9F9E:F4C5:6FE9

8 - mDNSCoreReceiveResponse: Received from 192.168.43.189:5353   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:22BB:F03B:C15E:2453:74D2:A7AB

9 - mDNSCoreReceiveResponse: Resetting to Probing:   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:22BB:F03B:CD5B:C4D5:B5E2:CC7D

10 - mDNSCoreReceiveResponse: Received from 192.168.43.189:5353   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:22BB:F03B:C15E:2453:74D2:A7AB

11 - mDNSCoreReceiveResponse: Resetting to Probing:   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:22BB:F03B:4D40:9F9E:F4C5:6FE9

12 - mDNSCoreReceiveResponse: Received from 192.168.43.189:5353   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:22BB:F03B:C15E:2453:74D2:A7AB

13 - mDNSCoreReceiveResponse: Resetting to Probing:    4 LAPTOP-JETP8JQ4.local. Addr 192.168.43.189

14 - mDNSCoreReceiveResponse: Received from 192.168.43.189:5353   16 LAPTOP-JETP8JQ4.local. AAAA 2401:4900:22BB:F03B:C15E:2453:74D2:A7AB

15 - Task Scheduling Error: m->NextScheduledSPRetry 17188

16 - Task Scheduling Error: m->NextScheduledEvent 17188

17 - Task Scheduling Error: Continuously busy for more than a second

18 - Task Scheduling Error: m->NextScheduledSPRetry 16828

19 - Task Scheduling Error: m->NextScheduledEvent 16828

20 - Task Scheduling Error: m->NextScheduledSPRetry 83172

21 - Task Scheduling Error: m->NextScheduledEvent 83172

SecurityCenter:-

1 - Security Center failed to validate caller with error DC040780.

PerfNet:-

1 - Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.

SYSTEM

Tcpip:-

1 - The system detected an address conflict for IP address 2401:4900:16fb:be09:a46e:5696:9abc:d46f with the system having network hardware address E4-46-DA-99-00-47. Network operations on this system may be disrupted as a result.

Kernel-Power:-

1 - The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

EventLog:-

1 - The previous system shutdown at 8:21:47 AM on ‎11/‎26/‎2020 was unexpected.

Service control manager:-

1 - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the mfemms service.

2 - The description for Event ID 7023 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

3 - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ModuleCoreService service.

4 - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the mfemms service.

MEIx64:-

1 - Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware.

5 same errors of MEIx64 were present.

And many same errors were there in Event log, Tcpip, SecurityCenter, Kernel-Power, PerfNet and Bonjour Service.

copy and paste just the message (11/25/2020 and now) that is relate to your issue