Question After installing a new NVMe SSD in my laptop, it suddenly shuts down if it's in sleep mode for too long ?

[jmiles301]

I posted some threads last week when I had issues initializing a drive to replace my older SSD. Well, I got that taken care of (I thought) by buying a different SSD (SN850x instead of SN700) and a slightly different enclosure. Runs fine now, EXCEPT..... when it goes to sleep, it will eventually just shut down if it sleeps for "too long."

This is obviously a major problem and I'm not sure what I can do about it. I already tried error checking the disk and doing some basic google searches, one of which told me to reset the power and battery saving options, which I did but without any effect.

Any ideas out there as to how I could resolve this?

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

List all attached peripherals.

= = = =

Look in Reliability History/Monitor for any error codes, warnings, or even informational events just before or at the times the system goes to sleep and/or shuts down. (There are other places to look - just start with Reliabiity History/Monitor for now.)

Run "powerfg /list" (without quotes) via the Command Prompt (as Admin).

Copy and paste the full results in a post.

FYI:

https://learn.microsoft.com/en-us/w...ice-experiences/powercfg-command-line-options

Objective being to learn more about what all is or is not happening.

 

[evermorex76]

Any ideas out there as to how I could resolve this?

Don't let the system go to sleep? Use hibernation? Doesn't fix the underlying problem but would eliminate the impact it has on you. Hibernation takes a few extra seconds to wake up but it's not full boot time.

Does the Windows Event Viewer show that the system is shutting down by command from SYSTEM or the like, or does it give a "this system shut down unexpectedly" event after turning back on? Is it the same amount of time every time?

I don't remember the details of the previous posts. Did you clone a previous SSD to this one? If so then none of the software settings should be any different. I can't imagine you got another "dud" drive but it's technically possible. What are all your settings for sleeping the screen, the system, all the "advanced" sleep settings, the hard drive sleep, etc? Maybe allowing the hard drive itself to sleep at a different timing from the OS/system is causing a system fault?

 

[jmiles301]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

List all attached peripherals.

= = = =

Look in Reliability History/Monitor for any error codes, warnings, or even informational events just before or at the times the system goes to sleep and/or shuts down. (There are other places to look - just start with Reliabiity History/Monitor for now.)

Run "powerfg /list" (without quotes) via the Command Prompt (as Admin).

Copy and paste the full results in a post.

FYI:

https://learn.microsoft.com/en-us/w...ice-experiences/powercfg-command-line-options

Objective being to learn more about what all is or is not happening.

OK, so let's see..

It's an ASUS A17 FA707RM Laptop, 2022 I think (was new when purchased I believe).
OS: Windows 11 Home - - build 26100.3775

It is in fine working condition, the only reason I was upgrading the SSD is because I wanted something faster than the stock component.
New drive is a WD SN850x 1TB, with only 152gb used out of the allotted 932gb total.
Brand new RAM - G.SKILL Ripjaws DDR5 SO-DIMM Series DDR5 RAM 32GB (2x16GB) 4800MT/s CL34
Ryzen 7 6800H

I tried to run powerfg /list but I keep getting the 'powerfg' is not recognized as an internal or external command, operable program or batch file error.

Thanks for your time!

 

[jmiles301]

OK, so let's see..

ASUS A17 FA707RM 2022 I think (was new when purchased I believe). Win11 Home OS build 26100.3775
It is in fine working condition, the only reason I was upgrading the SSD is because I wanted something faster than the stock component.
New drive is a WD SN850x 1TB, with only 152gb used out of the allotted 932gb total.
Brand new RAM - G.SKILL Ripjaws DDR5 SO-DIMM Series DDR5 RAM 32GB (2x16GB) 4800MT/s CL34
Ryzen 7 6800H

I tried to run powerfg /list but I keep getting the 'powerfg' is not recognized as an internal or external command, operable program or batch file error.

Thanks for your time!

So the error code I am receiving is a little different actually, it just says "Windows cannot find powerfg, make sure it is typed in correctly.

Here is a screenshot of my reliability monitor...

 

[jmiles301]

Don't let the system go to sleep? Use hibernation? Doesn't fix the underlying problem but would eliminate the impact it has on you. Hibernation takes a few extra seconds to wake up but it's not full boot time.

Does the Windows Event Viewer show that the system is shutting down by command from SYSTEM or the like, or does it give a "this system shut down unexpectedly" event after turning back on? Is it the same amount of time every time?

I don't remember the details of the previous posts. Did you clone a previous SSD to this one? If so then none of the software settings should be any different. I can't imagine you got another "dud" drive but it's technically possible. What are all your settings for sleeping the screen, the system, all the "advanced" sleep settings, the hard drive sleep, etc? Maybe allowing the hard drive itself to sleep at a different timing from the OS/system is causing a system fault?

I think I have tried hibernation already but with the same results, I can try it again.

There is no error given about an unexpected shutdown. I basically think I am waking my computer back up, but instead of it waking back up it is essentially booting from scratch. No error given after windows loads successfully.

All of my sleep settings have been factory reset because that was one of the suggestions I came across via googling. That didn't seem to help either.

Thanks for your time!

 

[evermorex76]

So the error code I am receiving is a little different actually, it just says "Windows cannot find powerfg, make sure it is typed in correctly.

@Ralston18 typoed. It's "powercfg /list".

"Sleep" mode saves the system state to RAM so it can quickly be reloaded when you "wake up" the machine. But if power is lost or anything else disrupts the state, it's just like your computer unexpectedly lost power and a full reboot is needed. Hibernation saves the state to the hard drive and then completely powers off the computer. The only way to disrupt coming out of hibernation and cause a "crash" is if it tried to turn on and failed to reload the system state, so it had to do a full reboot. These issues can also happen if there is a problem with the motherboard, as the "hibernation" or "sleep" status is stored by the BIOS so that it knows it needs to "wake up" rather than trying to do a full reboot. If that flag is lost, then it just does a full reboot and the saved system state is ignored (if it's on the hard drive the hibernation file is just left in place and not used; if it's in RAM then the saved state gets erased).

It's possible that a faulty SSD is glitching the BIOS when it tries to wake up, causing it to lose the "flag" and forcing a full reboot, but I've never specifically heard of it happening. There should be something in the Event Viewer indicating that sleep/hibernation failed, or the system booted up without shutting down cleanly first, something like that. There won't be a "system is crashing, saving logs" or anything like that of course since the system is asleep when it happens. (Windows won't pro-actively give you an error. You have to go into event viewer and look through the MANY uninformative messages that happen on startup, including many pointless warnings and errors. Check both Application and System logs for anything that might be related.)

You didn't mention if it happens only after a specific amount of time, although that may be hard to track since you only know it happened when you try to turn it back on.

Reset the BIOS to defaults (make note of any customizations you'd made first of course so you can manually recreate them), and make sure the BIOS is current.

Your screenshot isn't working as ibb.co just gives an "imgbb.com service unavailable" graphic, at least for me. Most users here seem to use imgur.com as their preferred site for images.

 

[Bob.B]

OK, so let's see..

ASUS A17 fa707RM 2022 I think (was new when purchased I believe). Win11 Home OS build 26100.3775
It is in fine working condition, the only reason I was upgrading the SSD is because I wanted something faster than the stock component.
New drive is a WD SN850x 1TB, with only 152gb used out of the allotted 932gb total.
Brand new RAM - G.SKILL Ripjaws DDR5 SO-DIMM Series DDR5 RAM 32GB (2x16GB) 4800MT/s CL34
Ryzen 7 6800H

I tried to run powerfg /list but I keep getting the 'powerfg' is not recognized as an internal or external command, operable program or batch file error.

Thanks for your time!

Try 'powercfg'

 

[jmiles301]

Thanks for all

@Ralston18 typoed. It's "powercfg /list".

"Sleep" mode saves the system state to RAM so it can quickly be reloaded when you "wake up" the machine. But if power is lost or anything else disrupts the state, it's just like your computer unexpectedly lost power and a full reboot is needed. Hibernation saves the state to the hard drive and then completely powers off the computer. The only way to disrupt coming out of hibernation and cause a "crash" is if it tried to turn on and failed to reload the system state, so it had to do a full reboot. These issues can also happen if there is a problem with the motherboard, as the "hibernation" or "sleep" status is stored by the BIOS so that it knows it needs to "wake up" rather than trying to do a full reboot. If that flag is lost, then it just does a full reboot and the saved system state is ignored (if it's on the hard drive the hibernation file is just left in place and not used; if it's in RAM then the saved state gets erased).

It's possible that a faulty SSD is glitching the BIOS when it tries to wake up, causing it to lose the "flag" and forcing a full reboot, but I've never specifically heard of it happening. There should be something in the Event Viewer indicating that sleep/hibernation failed, or the system booted up without shutting down cleanly first, something like that. There won't be a "system is crashing, saving logs" or anything like that of course since the system is asleep when it happens. (Windows won't pro-actively give you an error. You have to go into event viewer and look through the MANY uninformative messages that happen on startup, including many pointless warnings and errors. Check both Application and System logs for anything that might be related.)

You didn't mention if it happens only after a specific amount of time, although that may be hard to track since you only know it happened when you try to turn it back on.

Reset the BIOS to defaults (make note of any customizations you'd made first of course so you can manually recreate them), and make sure the BIOS is current.

Your screenshot isn't working as ibb.co just gives an "imgbb.com service unavailable" graphic, at least for me. Most users here seem to use imgur.com as their preferred site for images.

Thanks for all of that additional information, it's much appreciated!

I haven't had a chance to reset BIOS or look into the Event Viewer yet but I wanted to do a quick upload of the reliability monitor since the last one didn't work - click here.

 

[Ralston18]

Typo - yes. My error - apologies.

Thank you to those who noted and corrected it.

= = = =

In Reliability Monitor, click those red circle errors. Start with the errors in Applications.

Then look at the other errors.

List and post any named applications. Include any error codes.

 

[jmiles301]

Typo - yes. My error - apologies.

Thank you to those who noted and corrected it.

= = = =

In Reliability Monitor, click those red circle errors. Start with the errors in Applications.

Then look at the other errors.

List and post any named applications. Include any error codes.

So I tried to run powercfg /list but for some reason it doesn't do anything. Well, it acts as though it starts to do something, there is a split second flash like it's trying open something but then it goes away (you can see the outer boundaries of whatever box was trying to come up on screen and then it goes away just as fast as it showed up).

Here are some error codes over the past few days.... See here and here and here and here and here.

 

[jmiles301]

OK, so the computer just did this but as far as I know I don't think it was even in sleep mode (screen was off, but don't think it was sleeping). So that is a bit unusual compared to all of the other times in that it happened so quickly. There is nothing new that has been added to the Reliability Monitor for that event (not sure when they update that). As far as the Event Viewer goes, where would I go to check out the details of that most recent unexpected shutdown that just happened within the last hour?

 

[jmiles301]

OK, so I went back through Event Viewer and looked through it with non tech savvy eyes, and here is a gallery of screenshots of errors or warnings that recently came up around the time it unexpectedly shut down.

Click here for gallery of images.

 

[evermorex76]

So I tried to run powercfg /list but for some reason it doesn't do anything.

You need to open the command prompt first, then run the command. If you just run it from the Start menu or Run dialog it will just run it in a command prompt that immediately closes. You should get something like this:

C:\windows\system32>powercfg /list

Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e  (Balanced)
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance) *
Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a  (Power saver)

Click here for gallery of images.

I think you showed us all except the ones that matter. The ones from source Event Log and Kernel should indicate something regarding the startup. You may also find something from source "BugCheck" which is when there is a bluescreen crash. Most of the rest are normal and irrelevant. You may also see useful information in "Informational" type messages, not just errors and warnings. There is one from today shown in one of those images at 12:42 which may be when you had an issue today (don't know your timezone). Also please expand the column for Source before screenshotting, just to make it easier to tell the full source name. Just go through the error events one by one and glance at the descriptions to find ones that say anything about shutting down, hard drive errors, anything like that. (They should show up in the reliability report anyway.)

Here are some error codes over the past few days.... See here and here and here and here and here.

You can see there are errors for Windows shutting down unexpectedly. Click the "view technical details" option for some of those. Were those times that you think this problem occurred? The reports in reliability monitor should be realtime, as it's generated every time you open the app.

Edit: I just saw one of those details, hadn't looked at all the images. It shows a network adapter dump file but I'm not sure if that's normal on every crash or an indication that the network driver was part of the cause.

As far as the Event Viewer goes, where would I go to check out the details of that most recent unexpected shutdown that just happened within the last hour?

Aside from the System events that you've shown, you an also glance at the Application events. There shouldn't be an application causing this, BUT, Windows could possibly be waking itself up from sleep to run some task and then crashing, rather than actually being asleep when it happens.

Look for events that happened at the same time as one of the shutdown events in reliability monitor.

Have you tried disabling sleep completely and letting it just sit for a long time (usually still letting the screens sleep would be okay). What's your pattern of usage, do you let it sleep very quickly even if you're coming back within the hour, or does it only sleep after like 4 hours? Are you only finding that it has crashed if you haven't touched it for a whole night or does it sometimes happen even if it's only been asleep for 20 minutes?

 

[jmiles301]

You need to open the command prompt first, then run the command. If you just run it from the Start menu or Run dialog it will just run it in a command prompt that immediately closes. You should get something like this:

C:\windows\system32>powercfg /list

Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e  (Balanced)
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance) *
Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a  (Power saver)

I think you showed us all except the ones that matter. The ones from source Event Log and Kernel should indicate something regarding the startup. You may also find something from source "BugCheck" which is when there is a bluescreen crash. Most of the rest are normal and irrelevant. You may also see useful information in "Informational" type messages, not just errors and warnings. There is one from today shown in one of those images at 12:42 which may be when you had an issue today (don't know your timezone). Also please expand the column for Source before screenshotting, just to make it easier to tell the full source name. Just go through the error events one by one and glance at the descriptions to find ones that say anything about shutting down, hard drive errors, anything like that. (They should show up in the reliability report anyway.)


You can see there are errors for Windows shutting down unexpectedly. Click the "view technical details" option for some of those. Were those times that you think this problem occurred? The reports in reliability monitor should be realtime, as it's generated every time you open the app.

Edit: I just saw one of those details, hadn't looked at all the images. It shows a network adapter dump file but I'm not sure if that's normal on every crash or an indication that the network driver was part of the cause.


Aside from the System events that you've shown, you an also glance at the Application events. There shouldn't be an application causing this, BUT, Windows could possibly be waking itself up from sleep to run some task and then crashing, rather than actually being asleep when it happens.

Look for events that happened at the same time as one of the shutdown events in reliability monitor.

Have you tried disabling sleep completely and letting it just sit for a long time (usually still letting the screens sleep would be okay). What's your pattern of usage, do you let it sleep very quickly even if you're coming back within the hour, or does it only sleep after like 4 hours? Are you only finding that it has crashed if you haven't touched it for a whole night or does it sometimes happen even if it's only been asleep for 20 minutes?

Tons of great info there, thank you!

So, as of now my sleep settings have been reset to default. Given that this last occurrence appeared to be the only one that I can somewhat "confirm" happened when it was NOT sleeping, because I had just had to restart it within the previous hour. It had never crashed faster than that before. When I'm using it, it runs fine, very smooth, though. I will see if I can adjust settings so it never attempts to sleep (although I don't think it could have been asleep the most recent time this happened).

Central timezone here FWIW.

Yes, it is possible that the file dump you recognized later on, it's possible that occurred during the most recent crash, it was within that time window.

Here is my powercfg

Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced)
Power Scheme GUID: 64a64f24-65b9-4b56-befd-5ec1eaced9b3 (Silent)
Power Scheme GUID: 6fecc5ae-f350-48a5-b669-b472cb895ccf (Turbo) *

I will go back through Event Viewer and Reliability Monitor to see what else I can dig up.

 

[jmiles301]

Here is a screenshot of all problem reports generated by the Reliability Monitor, the only ones that really matter would be ones within the last 5-6 days or so (which is when I had the SSD installed).

The BOLD hardware issue that you see 3 times, when I click on the technical details it shows that livekernel image from before (not sure if it's the same one, but looks similar - it's the last image in the gallery above).

EDIT - Here is a gallery of more error/warning screenshots. There are a **** -ton [Moderator edit to remove profanity. Remember this is a family friendly forum.] of DistributedCOM showing up in there.

 

[evermorex76]

DistributedCOM events are meaningless, just Windows attempting to do things that don't matter. Most of those others are irrelevant too, BUT I see what might be an issue. Those reliability monitor reports are showing that NetAdapterCx dump file, which doesn't seem to be included in other events of the LiveKernelEvent 19e type when I searched for them; 19e is likely indicating a generic hardware event. In image xx4, you see rt68cx21 (cx, like the dump file, hmmm) indicating a hardware IO error. Upload shots of the other events from that source.

Even when asleep, most machine's NICs are actually still live, because ATX sleep isn't a complete disconnection of power, and it's possible for network signals to do things like waking the PC from sleep. It's physically impossible to completely turn it off if the power cord or battery are connected, even if you don't have anything like Wake-On-Lan enabled or any of the other BIOS sleep options set to respond to LAN signals. So if the NIC glitches, it could crash the BIOS and force a reboot which would lose the the system state from sleep mode. I also found this:

https://www.reddit.com/r/techsupport/comments/13qilwb/ethernet_and_usb_disconnecting_during_heavy_load/

That sounds very similar. I think you actually have a hardware problem with the network controller on your motherboard, but it could be a BIOS bug. Most laptops don't let you disable individual components like that, but since it's an ASUS, they may have a more comprehensive BIOS so that you could disable the built-in LAN and see if that resolves the problem. If not, you could try just disabling it in Device Manager (although that Redditor saw the same issue in Linux and Windows). Obviously you'd need to depend on Wi-Fi for a little while. If that does fix it, and the BIOS is up to date and all chipset and network drivers are up to date, then you'd need to RMA the laptop if possible, or just leave it disabled and use a USB Ethernet adapter. Even if it doesn't fix it, it looks like there is a hardware issue and it may still cause problems even if you've disabled it via the BIOS. Also note that the OP in the Reddit post indicated that when they updated their BIOS, it did resolve the issue. Another person couldn't update to the same specific one, though so they couldn't resolve it.

You also clearly have an issue with updates and System Restore. You may need to disable and re-enable System Restore to clear out all previous restore points, and make sure the allocated space is large enough to be useful (presumably you still have a lot of free space on the new drive; remember to always ensure at least 20% free space), and make sure that the Volume Shadow Copy service is able to run.

 

[jmiles301]

DistributedCOM events are meaningless, just Windows attempting to do things that don't matter. Most of those others are irrelevant too, BUT I see what might be an issue. Those reliability monitor reports are showing that NetAdapterCx dump file, which doesn't seem to be included in other events of the LiveKernelEvent 19e type when I searched for them; 19e is likely indicating a generic hardware event. In image xx4, you see rt68cx21 (cx, like the dump file, hmmm) indicating a hardware IO error. Upload shots of the other events from that source.

Even when asleep, most machine's NICs are actually still live, because ATX sleep isn't a complete disconnection of power, and it's possible for network signals to do things like waking the PC from sleep. It's physically impossible to completely turn it off if the power cord or battery are connected, even if you don't have anything like Wake-On-Lan enabled or any of the other BIOS sleep options set to respond to LAN signals. So if the NIC glitches, it could crash the BIOS and force a reboot which would lose the the system state from sleep mode. I also found this:

https://www.reddit.com/r/techsupport/comments/13qilwb/ethernet_and_usb_disconnecting_during_heavy_load/

That sounds very similar. I think you actually have a hardware problem with the network controller on your motherboard, but it could be a BIOS bug. Most laptops don't let you disable individual components like that, but since it's an ASUS, they may have a more comprehensive BIOS so that you could disable the built-in LAN and see if that resolves the problem. If not, you could try just disabling it in Device Manager (although that Redditor saw the same issue in Linux and Windows). Obviously you'd need to depend on Wi-Fi for a little while. If that does fix it, and the BIOS is up to date and all chipset and network drivers are up to date, then you'd need to RMA the laptop if possible, or just leave it disabled and use a USB Ethernet adapter. Even if it doesn't fix it, it looks like there is a hardware issue and it may still cause problems even if you've disabled it via the BIOS. Also note that the OP in the Reddit post indicated that when they updated their BIOS, it did resolve the issue. Another person couldn't update to the same specific one, though so they couldn't resolve it.

You also clearly have an issue with updates and System Restore. You may need to disable and re-enable System Restore to clear out all previous restore points, and make sure the allocated space is large enough to be useful (presumably you still have a lot of free space on the new drive; remember to always ensure at least 20% free space), and make sure that the Volume Shadow Copy service is able to run.

Appreciate all the help!

I think you may have been onto something with rt68cx21 - https://answers.microsoft.com/en-us...dware-io/d6156383-dfca-4915-bcee-da4e55a29ebb

I went to the MyAsus app and just downloaded the latest version. We will see if this does it.

 

[jmiles301]

Oh, and with regard to System Restore, there was an issue there. The system protection was not on for the new SSD but it was still on for the old one (which is now missing). I fixed all of that too.

 

[evermorex76]

I went to the MyAsus app and just downloaded the latest version. We will see if this does it.

If that doesn't, you can try the drivers directly from Realtek which may be a newer version. Of course if the system is asleep, drivers aren't DOING anything so they can't correct an actual hardware fault, and the only way they could come into play is if the system is for some reason attempting to "wake up" by itself and Windows loads the driver and then it crashes.

https://www.realtek.com/Download/List?cate_id=584

Win11 Auto Installation Program (NetAdapterCx) looks like it would be the one for your machine. NetAdapterCx is apparently a newer driver model and it does function a little differently from the previous NDIS model, offloading some functions, so you could also try the NDIS driver. (I doubt the "not support power-saving" versions would make any difference. That refers to allowing the Ethernet link to go into power saving mode, and has nothing to do with the computer sleeping. On the other hand, dropping into power saving mode does sometimes cause some problems, so removing the function in the driver might fix your problem, even though the driver shouldn't be doing anything.)

 

[jmiles301]

If that doesn't, you can try the drivers directly from Realtek which may be a newer version. Of course if the system is asleep, drivers aren't DOING anything so they can't correct an actual hardware fault, and the only way they could come into play is if the system is for some reason attempting to "wake up" by itself and Windows loads the driver and then it crashes.

https://www.realtek.com/Download/List?cate_id=584

Win11 Auto Installation Program (NetAdapterCx) looks like it would be the one for your machine. NetAdapterCx is apparently a newer driver model and it does function a little differently from the previous NDIS model, offloading some functions, so you could also try the NDIS driver. (I doubt the "not support power-saving" versions would make any difference. That refers to allowing the Ethernet link to go into power saving mode, and has nothing to do with the computer sleeping. On the other hand, dropping into power saving mode does sometimes cause some problems, so removing the function in the driver might fix your problem, even though the driver shouldn't be doing anything.)

Awesome, appreciate the link! You think I should just wait and see if the MyAsus download does it or just download that one as well, regardless?

 

[evermorex76]

Awesome, appreciate the link! You think I should just wait and see if the MyAsus download does it or just download that one as well, regardless?

The packages from the computer OEM are rarely the latest version and hardly ever actually contain anything other than the same driver installer with the brand name modified, except there is more often some customization with GPU drivers. In rare instances they may customize the actual firmware of a particular component. But using the OEM package ensures that you're using the "supported" drivers in case you need to contact the vendor for support or a potential RMA.

The Realtek driver package is 2 years newer than the one on the Asus website, and only 2 months old right now, although that doesn't mean there have been major changes in that time. Unfortunately nobody ever provides lists of changes and fixes for a lot of component drivers like this so there's no way to know if they specifically fixed this issue in one of them. Personally I never download driver packages from anywhere but the component manufacturer unless the OEM has built some sort of software around it that includes the driver, and even then you can usually still install the newer driver afterward.

There's a good chance that Windows itself has already updated your driver version during normal updates. The properties of it in Device Manager will show you the version. Asus is supplying 1168.011.1206.2022 while Realtek is on 1168.022.

I'd definitely also check for AMD chipset driver updates from AMD directly, too. The drivers from Asus are also 2.5 years old., plus get drivers from Nvidia and AMD for the graphics (since it has integrated graphics as well as the added Nvidia). You may also want to update the stupid Asus Armoury Crate software if it's not current. Normally I'd say remove it because it's bloatware but with an Asus-brand OEM laptop they may make the hardware more tightly tied to the software.

 

[jmiles301]

The packages from the computer OEM are rarely the latest version and hardly ever actually contain anything other than the same driver installer with the brand name modified, except there is more often some customization with GPU drivers. In rare instances they may customize the actual firmware of a particular component. But using the OEM package ensures that you're using the "supported" drivers in case you need to contact the vendor for support or a potential RMA.

The Realtek driver package is 2 years newer than the one on the Asus website, and only 2 months old right now, although that doesn't mean there have been major changes in that time. Unfortunately nobody ever provides lists of changes and fixes for a lot of component drivers like this so there's no way to know if they specifically fixed this issue in one of them. Personally I never download driver packages from anywhere but the component manufacturer unless the OEM has built some sort of software around it that includes the driver, and even then you can usually still install the newer driver afterward.

There's a good chance that Windows itself has already updated your driver version during normal updates. The properties of it in Device Manager will show you the version. Asus is supplying 1168.011.1206.2022 while Realtek is on 1168.022.

I'd definitely also check for AMD chipset driver updates from AMD directly, too. The drivers from Asus are also 2.5 years old., plus get drivers from Nvidia and AMD for the graphics (since it has integrated graphics as well as the added Nvidia). You may also want to update the stupid Asus Armoury Crate software if it's not current. Normally I'd say remove it because it's bloatware but with an Asus-brand OEM laptop they may make the hardware more tightly tied to the software.

Well, you were right about the chipset drivers from AMD being out of date, I am just now downloading what appears to be a whole new "adrenaline package."

I also did the most recent RealTek update as well.

I will say this (no jinx, lol), I installed everything except the two mentioned above, restarted my computer then purposefully put it in sleep mode, woke up 8 hours later and viola, the system woke back up just fine!

Thanks for all of your help, I owe you big time!

 

[jmiles301]

I posted some threads last week when I had issues initializing a drive to replace my older SSD. Well, I got that taken care of (I thought) by buying a different SSD (SN850x instead of SN700) and a slightly different enclosure. Runs fine now, EXCEPT..... when it goes to sleep, it will eventually just shut down if it sleeps for "too long."

This is obviously a major problem and I'm not sure what I can do about it. I already tried error checking the disc and doing some basic google searches, one of which told me to reset the power and battery saving options, which I did but without any effect.

Any ideas out there as to how I could resolve this?

Can we move this back to unsolved? It is still shutting down randomly.

 

[jmiles301]

@evermorex76 - it's still shutting down randomly unfortunately. I've gone through reliability monitor and Event Viewer and there isn't much there that looks like much to me. It's not like it's been the past few days, with a lot of errors and warnings, most of it is just informational stuff (in white, not red or yellow).