[SOLVED] W11 (+W10) System Freeze & Unresponsive after screen wake or sleep

[Stubbbbbsy]

Hi and thanks in advanced for taking the time to read this

It's been about two months now with this freezing/crashing issue I have been having with my custom-built desktop

SPECS:
W11 21H2 22000.593
i7-8700K (Stock Clock)
Asus TUF 3080 (Stock Clock)
Asus z370-A Prime MoBo
32GB of Corsair RAM @ 3200
Samsung Pro NVME SSD 960 1TB

PROBLEM:

1. I have done a ton of troubleshooting and have determined that if I allow my "screen to turn off" or "put my device to sleep" and then wait 4-5m after, when waking the PC, it is not responsive
2. The HDD light still flashes and if I am in a Discord call, I can still communicate even though I am unable to interact with the system through any other form of input
3. System has always had four monitors attached to the GPU (3DP, 1 HDMI). The issue cannot be replicated if only 2/3 DP monitors are plugged in, but anytime all 3 DP monitors are plugged in the system freezes 5m after sleep/display off
4. Every time the system freezes the "Reliability Monitor" logs a Hardware Error [LiveKernelEvent 193] with parameters: [815, 2, fffde83097f1080,0] - Google was little help in decoding this information
5. I have tried nearly everything possible, so any other advice or just a friendly "Good luck" would be great as I am losing my sanity

TRIED:

• BIOS Update & Rollback
• Clean W11 & W10 installations
• DDU NVIDIA Driver Rollback & Newest Drivers
• Different 3080, 1080ti
• Memtest (Came back clean) & New Memory sticks in different channel configurations
• New DP cables
• Unplugging all USB devices
• Different PC on the same monitors
• Prime95 CPU Stress Test
• 3DMark Stress Test & Benchmarks
• Checked for new Intel Chipset Drivers
• S.M.A.R.T Check on drives
• Deep breathing and meditation

Thank you for reading and any insight you can provide,
Cheers

 

[Colif]

its probably an old driver that doesn't like sleep or screen wake

Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

can take a screenshot from (and including)Driver name to (and including)Creation date.

upload it to an image sharing website and show link here

I have seen similar recently, but until I see what drivers you have, I am not going to suggest anything

that 193 code might be a bsod

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[Stubbbbbsy]

its probably an old driver that doesn't like sleep or screen wake

Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

can take a screenshot from (and including)Driver name to (and including)Creation date.

upload it to an image sharing website and show link here

I have seen similar recently, but until I see what drivers you have, I am not going to suggest anything

that 193 code might be a bsod

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

Hi Colif,

Thanks for the detailed reply

Here is a link to that information:

https://imgur.com/a/hfTMM0n

View: https://imgur.com/a/hfTMM0n


No minidumps could be found

EDIT: Sorry, I didn't realize I have to configure it. I'll do that now and force a freeze to see what happens. I'll keep you updated.

EDIT 2: No minidumps were produced from the freeze, despite the logs being enabled

 

[Colif]

try updating this - https://www.intel.com/content/www/u...-optane-memory-8th-and-9th-gen-platforms.html

Its possible its your wifi dongle but only as its drivers are from 2017

 

[Stubbbbbsy]

try updating this - https://www.intel.com/content/www/u...-optane-memory-8th-and-9th-gen-platforms.html

Its possible its your wifi dongle but only as its drivers are from 2017

Updating now...

I don't have a WiFi Motherboard or Dongle... should I uninstall that driver (device manager?)?

 

[Colif]

it might not be running, the program find all drivers, not just what is active.
if you don't have anything plugged in for it, its just there.
Can probably just ignore it.
might be for an xbox controller or something.

 

[Stubbbbbsy]

it might not be running, the program find all drivers, not just what is active.
if you don't have anything plugged in for it, its just there.
Can probably just ignore it.
might be for an xbox controller or something.

Ahh, it's probably the Wirelessly Xbox Adapter - smart thinking.

Unfortunately the Intel rapid storage drivers did not fix the issue. Still happening under the same conditions.

 

[Colif]

My easy fix didn't work..

try running this - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
might be newer version of Icue, hard to tell as they use older drivers in their driver packages, newest version is 4.22.203 (getting it right now)
could be new version of Synapse

 

[Stubbbbbsy]

My easy fix didn't work..

try running this - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
might be newer version of Icue, hard to tell as they use older drivers in their driver packages, newest version is 4.22.203 (getting it right now)
could be new version of Synapse

That's alright, appreciate it nonetheless.

I've tried running the support assistant and everything, including software, is up to date.
I don't think it's something driver or software related, as a factory reset still produced the issue.

Let me know if you have any other suggestions, as I really appreciate your insight thus far.

 

[Colif]

what Power supply do you have?

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

its not GPU since you tried 2.

 

[Stubbbbbsy]

what Power supply do you have?

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

its not GPU since you tried 2.

Never even considered it could be the PSU (Corsair RM850X Modular)... Hmm

Ran memtest on all 4 of my sticks at the same time and all 4 passes passed (didn't individually test each stick).

Tried an entirely different set of two sticks and still had the issue.

Thoughts?

 

[Colif]

Never even considered it could be the PSU (Corsair RM850X Modular)... Hmm

I only asked as it wasn't listed. I wouldn't normally suspect that model

not GPU
not ram

• BIOS Update & Rollback
• Clean W11 & W10 installations
• DDU NVIDIA Driver Rollback & Newest Drivers
• Different 3080, 1080ti
• Memtest (Came back clean) & New Memory sticks in different channel configurations
• Prime95 CPU Stress Test
• 3DMark Stress Test & Benchmarks
• Checked for new Intel Chipset Drivers
• S.M.A.R.T Check on drives
• Deep breathing and meditation

those are most of the things I would suggest...

i don't use sleep, I see lots of people right now with sleep problems.

try installing Magician and the nvme drivers from here - https://semiconductor.samsung.com/consumer-storage/support/tools/
maybe test the drive since its only thing you didn't do (SMART is just what drive self reports), Magician has diagnostics.

could run this on CPU - https://www.intel.com/content/www/us/en/download/15951/19792/intel-processor-diagnostic-tool.html?

 

[Stubbbbbsy]

"Fixed" the issue

Installed a fresh install of Windows 10 and disabled Windows Updates. Most current NVIDIA Drivers are installed without issue.

The issue does not seem to occur at all without the most recent Windows Updates. When I do update to the most current build for W10, the issue comes right back without fail.

Let me know if there's anything to take away from this, as I would much rather be up to date and on Windows 11.

Appreciate all the help so far and anything people can add going forward.

Will keep this post updated if any new discoveries are made.

 

[Colif]

We don't know what cause was so knowing if its fixed in a later update is difficult to say.

Win 10 is mainly getting bug fixes now, its been in that state for last year so I don't know what it might have changed.
Windows update also gets driver updates so its possible it was one of those that caused it.

Could wait until Win 11 version 22H2 is released but I can't tell you when that might be... apart from probably after June. Its possible problem (whatever it is) could be fixed in that time.

There are a lot of sleep related problems at the moment but not just on 11.