Solved When closing the lid and trying to wake from sleep all I see is blank

So the problem i am having is when i wake it from sleep the display doesent go on and then i hve to restart by holding the home button

I know the facility to close the lid is provided by Microsoft but I never close the lid to turn off or put to sleep. Why, you ask? Because I prefer to look at the screen as I select 'Sleep' or 'Shutdown' or press the power button to turn off. I do this because there may be an alert message showing to tell you that something is not right. I look at the screen until the screen shows black to ensure there has been no messages. These messages could be something like "There is another user logged-on...." or "Process xxxxx is stopping windows from shutting down..." or "Updates are in progress....". You will not see these if you simply close the lid and you may introduce corruptions to the OS.

I suggest you open a command window and run sfc /scannow (Note the space between c and /) command to check for and (hopefully) fix your OS. There are other command strings but this one is the easiest to do first.

After fixing your issue never close the lid to turn off or put to sleep.

yes but when i do than it does the same as when i shut the lid and i need to shut it

jasonhook244 said:

it does the same as when i shut the lid and i need to shut it

Click to expand...

Jason,

Just try it for test purposes to see if there are any error messages.

If it is not clear whether it is reaching sleep or not, you could add an Event viewer, Custom view definition that will show you all power state transitions & when each one happened.
This link contains the view definition as well as instructions for setting it up [importing it into your Event viewer].
Import Event viewer, Custom views - Power state transitions - my post #4 - TenForums
It applies to both Windows 10 & Windows 11.

And, for now, please would you post the results of this command [Windows Terminal, it doesn't matter if it's the PS or Cmd part]
PowerCfg -a
so we can see what power states you have available.
Open Windows Terminal - ElevenForumTutorials


If you run the command
systeminfo.exe
then the lines beginning
System Manufacturer:
System Model:
will allow you to add those parameters to your system specs [which currently say, "I don't know"]


All the best,
Denis

so why it says idk is becase i really dont know who makes tis thing


what sysinfo says

Jason,

OK, at least we are not dealing with S0 Low power idle.

1 I think that clarifying what does & does not happen by using that Event viewer, Custom view will help.

2 I think it would also be worth reinstalling the display driver just to make sure that we are not facing some aberrant behaviour caused by display driver corruption.
I'd normally advise people to go to their computer maker's support site to get the driver but you can't do that so go straight to Intel instead.
List of Drivers for Intel Graphics
This is just to avoid wasting time & effort looking elsewhere. There is no diagnostic test for display driver corruption so reinstalling it just eliminates it as a possible cause.

3 How long has this problem been happening? And what is the history of this laptop?

4 I notice that your Windows 11 is 22621.188. The latest Cumulative update takes us to 22621.1992. Why haven't you been updating?

5 Do you have any means of finding out if your Bios is up-to-date? Some Bioses can place constraints on, for example, choosing lid close actions.
That systeminfo.exe command should also reveal your Bios version and the entry might include the name of the Bios maker so you could use that in searching for Bios version-update info.

6 Is your laptop a conventional laptop? Is there anything unusual about it? I ask because I have a 'laptop' that is actually a tablet with an integrated keyboard that it slots into so it looks like a laptop but remains, in essence, a tablet.


Best of luck,
Denis

so i tried to reinstall the graphics driver and that did not help

it is solved. it was something in the bios and my cousin who works in it fixed it