Windows 10 October UPDATE 1809 - Your thoughts/feedback

[RetroBlast]

Is anyone willing to test the new re-released 1809 update and see if they’re still having issues with sleep/wake? I just recently reinstalled 1803 and don’t wanna go through the whole rigmarole again if it’s not fixed, I rely on having my PC being able wake reliably from sleep.*

Okay - I just spent the whole day working on this. I'm getting the Internal Power Error blue screen every time I wake from sleep with 1809 on my Asus ROG Z370-E motherboard. Latest BIOS (1601, 10/23), latest Nvidia drivers (416.94), latest everything in fact.

I tried updating first, then tried doing a clean install of Windows 10 1809 - both times going to sleep and waking results in a blue screen.

I've seen some reports that the Samsung NVME drivers might cause this, so I uninstalled them (I have a 960 EVO). I also have an Intel Optane 900p as my boot disk, so I removed those as drivers as well. No dice.

Hoping someone finds what driver or setting is borking things...this is weird stuff.

[Mr. Fox]

I installed Windows 10 Enterprise 1809 without issues today, but it seems like a pretty pointless endeavor. No benefit identified thus far. Still not as good as 1607. Performance is not better than 1803, but it's not worse than 1803 either. So, at least that is good.


Time Spy scores are within a tiny margin of error in favor of 1803 and 1607. Nothing really to see here... overall an unremarkable waste of time.

[MrAgapiGC]

Okay - I just spent the whole day working on this. I'm getting the Internal Power Error blue screen every time I wake from sleep with 1809 on my Asus ROG Z370-E motherboard. Latest BIOS (1601, 10/23), latest Nvidia drivers (416.94), latest everything in fact.

I tried updating first, then tried doing a clean install of Windows 10 1809 - both times going to sleep and waking results in a blue screen.

I've seen some reports that the Samsung NVME drivers might cause this, so I uninstalled them (I have a 960 EVO). I also have an Intel Optane 900p as my boot disk, so I removed those as drivers as well. No dice.

Hoping someone finds what driver or setting is borking things...this is weird stuff.

Disable sleep and wake on windows. those are not working since 1802. i did test again that function and in the end i just take those out. i just leave the screen will go off in like 1h. BUT still mess with the drivers. I read that issue with the nvmes. There is trade off. You coul install the drivers, but CSM OFF. i have to try that and see. BUT.... i test the 960evo without drives and runs better. Do not ask. sleep are mix with s3 and s4. i start using those wit my OC again. in my 7700k is just 100point of cinebench and i fell better.

1809 is missing and there is are issues. Just disable the wake sleep from windows in settings and you will be ok

[geneo]

Okay - I just spent the whole day working on this. I'm getting the Internal Power Error blue screen every time I wake from sleep with 1809 on my Asus ROG Z370-E motherboard. Latest BIOS (1601, 10/23), latest Nvidia drivers (416.94), latest everything in fact.

I tried updating first, then tried doing a clean install of Windows 10 1809 - both times going to sleep and waking results in a blue screen.

I've seen some reports that the Samsung NVME drivers might cause this, so I uninstalled them (I have a 960 EVO). I also have an Intel Optane 900p as my boot disk, so I removed those as drivers as well. No dice.

Hoping someone finds what driver or setting is borking things...this is weird stuff.

It is the Samsung driver. Same thing happened to me. I just posted this a few posts back.
Uninstall it and boot to safe mode so it will pick up the microsoft nvme driver. What have you got to loose?

EDIT: Sorry to see you had tried it. Next I would try your video driver. Roll it back. I have had crashes with my Nvidia driver.

[ImpulsePie]

Okay - I just spent the whole day working on this. I'm getting the Internal Power Error blue screen every time I wake from sleep with 1809 on my Asus ROG Z370-E motherboard. Latest BIOS (1601, 10/23), latest Nvidia drivers (416.94), latest everything in fact.

I tried updating first, then tried doing a clean install of Windows 10 1809 - both times going to sleep and waking results in a blue screen.

I've seen some reports that the Samsung NVME drivers might cause this, so I uninstalled them (I have a 960 EVO). I also have an Intel Optane 900p as my boot disk, so I removed those as drivers as well. No dice.

Hoping someone finds what driver or setting is borking things...this is weird stuff.

Thanks for your testing! Guess my main rig is going to have to stick with 1803 for now until we can be sure if it’s just the Samsung NVME driver causing the sleep/wake issues, and not a combination of other things. I have a 960 Evo boot drive with the Samsung NVME driver on 1803 that’s working flawlessly. The only thing I really wanted 1809 for is the dark mode file explorer. It’s not worth giving up the energy savings of sleep and the ability to wake my PC remotely just to get that.*

[geneo]

Thanks for your testing! Guess my main rig is going to have to stick with 1803 for now until we can be sure if it’s just the Samsung NVME driver causing the sleep/wake issues, and not a combination of other things. I have a 960 Evo boot drive with the Samsung NVME driver on 1803 that’s working flawlessly. The only thing I really wanted 1809 for is the dark mode file explorer. It’s not worth giving up the energy savings of sleep and the ability to wake my PC remotely just to get that.*

It is really simple to try removing the Samsung driver. You can always reinstall it. Also if you have Nvidia graphics try going back a few releases.

[geneo]

Thanks for your testing! Guess my main rig is going to have to stick with 1803 for now until we can be sure if it’s just the Samsung NVME driver causing the sleep/wake issues, and not a combination of other things. I have a 960 Evo boot drive with the Samsung NVME driver on 1803 that’s working flawlessly. The only thing I really wanted 1809 for is the dark mode file explorer. It’s not worth giving up the energy savings of sleep and the ability to wake my PC remotely just to get that.*

The Samsung driver worked fine for me prior to 1809 too. It is really simple to try removing the Samsung driver. You can always reinstall it. Also if you have Nvidia graphics try going back a few releases.

[ImpulsePie]

It is really simple to try removing the Samsung driver. You can always reinstall it. Also if you have Nvidia graphics try going back a few releases.

To be honest, if I have to muck around so much just for a Windows update, then it can wait until there is better compatibility. I want the latest Nvidia driver for optimisations to Battlefield V, and the driver works fine on 1803 with no issues. I’d be happy to try after removing the Samsung NVME driver, but the abode user said it didn’t work for him and he still had issues. Not worth the risk right now until I can guarantee it’s just that causing it and not something else.*

[geneo]

To be honest, if I have to muck around so much just for a Windows update, then it can wait until there is better compatibility. I want the latest Nvidia driver for optimisations to Battlefield V, and the driver works fine on 1803 with no issues. I’d be happy to try after removing the Samsung NVME driver, but the abode user said it didn’t work for him and he still had issues. Not worth the risk right now until I can guarantee it’s just that causing it and not something else.*

Well it worked for me an others. Yeah, there are no guarantees but it takes 5-10 minutes off your time - less time than you probably pent in this thread asking advice.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffffa4849fcf51f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\110318-19890-01.dmp. Report Id: ec70db2b-1adf-48cb-ae03-8c43bed6d333.

stack trace right to the Samsung nvme driver

[ImpulsePie]

Well it worked for me an others. Yeah, there are no guarantees but it takes 5-10 minutes off your time - less time than you probably pent in this thread asking advice.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000a0 (0x0000000000000608, 0xffffa4849fcf51f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\110318-19890-01.dmp. Report Id: ec70db2b-1adf-48cb-ae03-8c43bed6d333.

stack trace right to the Samsung nvme driver

No, it could possibly take a lot longer than 5-10 minutes, because if it’s not the only issue it’ll take me hours to reinstall Windows back to 1803 again and set it all back up the way I had it. Or try to do a rollback to before the 1809 update, but that’s not a guarantee to work either.*

I’ll probably just wait until Samsung have a newer NVME driver to bother trying again. By then maybe Microsoft will have another cumulative update out and will have figured out most of the issues. This rollout has been a huge stinking mess. They just don’t test things properly, and they don’t even listen to Insider feedback/bug reports that are telling them the issues.*