Ok, now I want you to open event viewer (winlogo+X>event viewer) >expand windows logs>click on application and system >take a look all the error relate to black screen or freeze, or video card> in the general tab select the error message >on your keyboard press ctrl+C (to copy) > click in this post >ctrl+v (to paste the error message). See if this folder exist c:\windows\minidump , if yes upload all the file on your onedrive or goodle drive and copy paste the link here without password.
Only while plugged in, the Laptop screen(goes black) doesn't respond after idle screen timeout.
Hello there,
I've been facing this issue since 2 years now, seems like a simple problem but mine is really weird, I didn't get any query regarding my issue hence I decided to post it myself. Please read my post completely and please help me resolve this issue.
When I leave the laptop (HP Pavilion 15-cc1xx, win 10 64 bit, Intel core i5-8250U) idle, the screen turns off to save power & doesn't respond to any inputs even external connected USB mouse light turns off (I saw that when this happens the HDD LED turns off I suppose the HDD is not waking). After screen turn off it is suppose to go to sleep but the power LED and fans are continuously on until I hard reboot using power button.
Here is the weird part--- This only happens if my laptop is plugged in and doesn't occur while on battery. The power options screen is shared below
I've tried doing almost all troubleshooting like updating drivers, BIOS, and sfc scan and also reset but all in vain.
Sometimes, this also happens when I put it to sleep, but this sleep issue occurs very rarely cannot predict when it happens I've to hold my breath when I press sleep and wait until the power LED starts blinking for confirmation or else I've to again hard reboot only to loose unsaved data. Although this sleep issue happens very very rarely.
I think the issue is only with HDD since the HDD LED stops blinking when this happens ***.***When it is blinking then I'm sure that the screen will turn on as I've seen it for myself many times.
Here is the picture of power and HDD LED I was talking about,
Windows for home | Windows 10 | Settings
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
88 answers
Sort by: Oldest
-
Anonymous
2020-11-26T15:08:19+00:00 -
Anonymous
2020-11-26T15:25:36+00:00 Tell me did you plug another monitor to your laptop? If yes, which port are you using?
-
Anonymous
2020-11-26T15:38:17+00:00 I see there is mini dump folder in windows folder here is the one drive link for that folder
LINK -https://1drv.ms/u/s!AtuSyEHlaqZvjFHEYDCZXgjnXGGJ?e=cBvoEM
Do I still need to upload the error messages cause the it's showing 34000 and 11000 events in application and system and in between few error msgs which I've to search and paste, which is time consuming.
-
Anonymous
2020-11-26T15:46:01+00:00 copy and paste just the message (11/25/2020 and now) that is relate to your issue
-
Anonymous
2020-11-26T16:19:42+00:00 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.