Skip to main content
Participating Frequently
October 25, 2024

Generative Expand/Fill causes (high-end) PC to freeze in hard power off

  • October 25, 2024
  • 20 replies
  • 2245 views

Recently upgraded my PC to perform optimally for graphic design work and 3D.


While using Photoshop the last few weeks I'm facing  the following issue:

It first happened as I was trying to transform an image from vertical to horizontal with Generative Expand turned on. Second time happened as I was simply brushing with symmetry turned on.

Third and forth time, which I was crash testing happened as I was using Generative AI features. 


The displays instantly shut off, PC appears to be on, but does not respond even to hard power off(continuous button press). To fix this and actually reboot the computer I have to manually cut the power supply off and on again, then the PC responds to manual power off (button press). Then I turn it on again manually. 

 

I have tried sfc scans, uninstall Adobe CC and reinstall everything manually, checked for faulty RAM or PSU. 

WINDOWS RELIABILITY ERROR REPORT:
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\SearchHost.exe

Source
Microsoft® Windows® Operating System

Summary
Stopped responding and was closed

Date
‎10/‎25/‎2024 6:32 PM

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\SearchHost.exe

Problem signature
Problem Event Name: MoAppHang
Package Full Name: MicrosoftWindows.Client.CBS_1000.22700.1047.0_x64__cw5n1h2txyewy
Application Name: praid:CortanaUI
Application Version: 2124.25508.20.0
Application Timestamp: 67101d1b
Hang Signature: 8397
Hang Type: 2097152
OS Version: 10.0.22631.2.0.0.256.121
Locale ID: 1033
Additional Hang Signature 1: 8397039bfc56edbcf4c78a242517c53d
Additional Hang Signature 2: 6c77
Additional Hang Signature 3: 6c77b77e6416aebf4f5b401a1d1aa884
Additional Hang Signature 4: 8397
Additional Hang Signature 5: 8397039bfc56edbcf4c78a242517c53d
Additional Hang Signature 6: 6c77
Additional Hang Signature 7: 6c77b77e6416aebf4f5b401a1d1aa884

Extra information about the problem
Bucket ID: 0479d073f14437cfc3d968a13b308c34 (1430289398358903860)

[Moderator removed System Specs and attacked as RTF]

20 replies

diosimosAuthor
Participating Frequently
November 18, 2024

Update:
In this situation the problem was essentialy the mobo's VRM and the power hungry nature of the more recent processor I installed.
Despite the manufacturer's approval and apparent compatibility, Adobe's software create this interaction where a certain, sudden amount of power is asked from the motherboard which it can not provide, so the power to the CPU gets cut ,whenever there's a CPU intensive action or task.
This happens quite rapidly in comparison to stress-testing software that create a virual load. Therefore why I couldn't recreate the problem with Prime, OCCT, FurMark or anyother software or task. 

I fixed this issue and have been experiencing improved stability and no issues for 3 days of intensive work by disabling Core Boost setting in BIOS.
That is a bandaid solution though, as you're leaving out CPU performance, and the motherboard still can not satisfy the compartment's needs.

So I just bought a new, more powerful motherboard that can handle my CPU, which I'll be installing soon. That *should* be the end of that. 

Just documenting this for anyone having similar issues.

Happy to say I'm finally back to business as usual. God is good.

Dio
diosimosAuthor
Participating Frequently
November 16, 2024

Update: I was using the healing brush tool on the Web Application a few minutes ago, and after a few adjustments, the issue occured again. This was the first time it has happened with the Web App. So this is not limited to the desktop applications. 

I require assistance. @CMass @Sameer K  

Dio
diosimosAuthor
Participating Frequently
November 15, 2024

I took some time to clean everything, stress test a bunch of times with OCCT, Prime95 and FurMark, all of which found no issue whatsoever. I also rewired everything on my build, checked all compartments cleanliness and stability, removed all unnecessary software. 

Everything was going smoothly for a while after going into BIOS and resetting overclocking settings, and installing the new NVIDIA Studio Drivers. The problem seemed to have dissipatated for a day or two, no occurences. 

However today, as I was working on an illustration, after 4 hours of steady and reliable usage with no issue, I trying playing with blending modes. Instant crash.
The first time this happened I just opened my PC back up the manual way and my file opened normally. I was able to go back into my work. 
Second time, I had a suspicion that playing with the blending mode was what caused it this time. However the issue did not occur like it did in the past with Liquify or AI expand. I hovered over layer blending modes, this made the problem occur again, and corrupted my file, leaving no trace or room for a recovery file.

Just lost 4 hours and an artwork to the same annoying problem. And still have no idea as to what may be causing it.

Send help x_x

Dio
D Fosse
Community Expert
Community Expert
November 9, 2024

These things are always hardware based.

 

The problem with AMD is that they're all targeted at gaming. That's their market. In this market segment all kinds of overclocking and modifying and pushing specs are par for the course, even encouraged. Sub-vendors follow suit.

 

Go into the BIOS and check clock speeds and general settings for all major components. Compare to the manufacturer's specs.

 

Then a physical check-up for broken fans, clogged up air vents etc.

 

Reinstall drivers, especially the GPU driver. Use the Studio driver, not the Game Ready driver. I'd consider reinstalling Windows, but maybe not immediately.

 

Go over your list of installed software. Remove everything you don't need. Clean house.

 

 

diosimosAuthor
Participating Frequently
November 9, 2024

@Sameer K 
Today, while operating on Lightroom it suddenly happened again. I had File Explorer, Spotify and Photoshop Web open simultaneously in the background. 
So it's not only constrained within Photoshop bounds.

This issue literally blows my mind. Appreciate any and all assistance.

Dio
diosimosAuthor
Participating Frequently
November 8, 2024

Despite changing it to a standalone singular power socket and unplugging the TV, the problem persists beyond the amount of displays connected. I am at wit's end. 

Dio
diosimosAuthor
Participating Frequently
November 8, 2024

I now switched PC power cable from a multisocket where I have another 11 outlets connected, to a solo outlet. Will see whether that impacts performance aswell. 

Dio
diosimosAuthor
Participating Frequently
November 8, 2024

After some usage with all the displays connected, during a small adjustment in Hue+Saturation of an image, there was another crash.
This time the WRER is this: 

 

I'll try disconnecting the TV screen and seeing how that goes. If I don't get a crash after a day of use that should be pretty helpful in determining the origin of the problem. 

 


Booted into safe mode and opened the software. I wasnt able to do any adjustments and play around, but this time the software opened properly without displaying a crash report. Just the usual "are your online" window

Dio
diosimosAuthor
Participating Frequently
November 8, 2024

I updated the software to latest version.
Then tested it with every screen and the TV back on. It never exhbited the issue after every attempt at serious stress test. Which is very weird to me. Booting into safe mode to check if I'll get a crash report like last time. 

Dio
diosimosAuthor
Participating Frequently
November 8, 2024

 

@Sameer K 
Breakthrough!

I just disconnected the peripheral monitors (left and right) and the TV above. I stress tested everything on a big file, and so far it hasn't caused a crash. This however is unsustainable but at least it gets us closer to a solution as to what may be causing the issue. I'll go ahead and test it with incrementally more displays and finally add the big TV above. 

Dio