F5F Stay Refreshed Software Operating Systems : Long windows 11 shutdown times Answer: Long shutdown durations in Windows 11 can occur due to various factors.

: Long windows 11 shutdown times Answer: Long shutdown durations in Windows 11 can occur due to various factors.

: Long windows 11 shutdown times Answer: Long shutdown durations in Windows 11 can occur due to various factors.

A
Alpha_dagger13
Junior Member
7
02-10-2021, 02:11 PM
#1
Hey guys,
My main rig looks like this: a Ryzen 5 2600X, Gigabyte DS3H 450M, 32GB DDR4 3000 memory, and a 512GB SATA SSD. It usually shuts down in about 1 to 1.5 minutes. I’d say it’s not a big issue.
Lately I noticed a Ryzen 7 5800X on sale, so I upgraded my CPU and added 32GB DDR4 3200 memory. The process was quick—just remove and install—but my computer still takes around 5 minutes to shut down sometimes.
Could there be a reason for this delay? How can I fix it?
TIA.
A
Alpha_dagger13
02-10-2021, 02:11 PM #1

Hey guys,
My main rig looks like this: a Ryzen 5 2600X, Gigabyte DS3H 450M, 32GB DDR4 3000 memory, and a 512GB SATA SSD. It usually shuts down in about 1 to 1.5 minutes. I’d say it’s not a big issue.
Lately I noticed a Ryzen 7 5800X on sale, so I upgraded my CPU and added 32GB DDR4 3200 memory. The process was quick—just remove and install—but my computer still takes around 5 minutes to shut down sometimes.
Could there be a reason for this delay? How can I fix it?
TIA.

C
Cupcake_Rose
Posting Freak
844
02-12-2021, 02:55 AM
#2
Did you refresh the BIOS before adding the Ryzen 7 5800x? What version are you currently running? Also, please share details about the 32GB DDR4-3200 memory installation. I saw your specifications in the signature area; it’s best to add them to the discussion thread so changes don’t affect future advice. Your current specs are noted, but the power supply information is missing—could you provide the model and age of your PSU?
C
Cupcake_Rose
02-12-2021, 02:55 AM #2

Did you refresh the BIOS before adding the Ryzen 7 5800x? What version are you currently running? Also, please share details about the 32GB DDR4-3200 memory installation. I saw your specifications in the signature area; it’s best to add them to the discussion thread so changes don’t affect future advice. Your current specs are noted, but the power supply information is missing—could you provide the model and age of your PSU?

B
BlackSlayer
Junior Member
25
02-26-2021, 09:13 PM
#3
The bios version is gigabyte ds3h 450m f62d, compatible with 5800x and 2600x. It's not the newest bios, but upgrading the bios seems like a good next step.
B
BlackSlayer
02-26-2021, 09:13 PM #3

The bios version is gigabyte ds3h 450m f62d, compatible with 5800x and 2600x. It's not the newest bios, but upgrading the bios seems like a good next step.

K
Kamikaze_007
Senior Member
625
02-28-2021, 05:03 AM
#4
if you didn't reinstall windows, there will be a list showing the hardware from the old CPU and the new one. The old CPU list won't respond and might slow down startup or shutdown. Once the new CPU is installed, reset the BIOS to defaults so it can rebuild the database that sends data to Windows. You could also open the Windows Control Panel or Device Manager, go to the view menu, enable hidden devices, and remove any greyed-out hardware entries from the tree.
K
Kamikaze_007
02-28-2021, 05:03 AM #4

if you didn't reinstall windows, there will be a list showing the hardware from the old CPU and the new one. The old CPU list won't respond and might slow down startup or shutdown. Once the new CPU is installed, reset the BIOS to defaults so it can rebuild the database that sends data to Windows. You could also open the Windows Control Panel or Device Manager, go to the view menu, enable hidden devices, and remove any greyed-out hardware entries from the tree.

H
heyjudge100
Member
186
02-28-2021, 07:05 AM
#5
The BIOS version gigabyte ds3h 450m is f62d
https://www.gigabyte.com/Motherboard/B45...rt-dl-bios
If you check here, the F62d entry isn't present. They likely removed it because of problems or they uploaded a more stable version. I recommend updating to the newest BIOS and then reset the CMOS by unplugging from power, turning off the display, removing the battery, holding the power button for 30 seconds to drain any remaining charge, and after 30 minutes replace the battery again.
H
heyjudge100
02-28-2021, 07:05 AM #5

The BIOS version gigabyte ds3h 450m is f62d
https://www.gigabyte.com/Motherboard/B45...rt-dl-bios
If you check here, the F62d entry isn't present. They likely removed it because of problems or they uploaded a more stable version. I recommend updating to the newest BIOS and then reset the CMOS by unplugging from power, turning off the display, removing the battery, holding the power button for 30 seconds to drain any remaining charge, and after 30 minutes replace the battery again.

B
220
03-07-2021, 07:04 PM
#6
That's typical for Gigabyte—the BIOS they offer isn't listed on their site anymore. It's possible it was a beta version, as they often test before finalizing a release. They might still have it in place just in case, since I wouldn't have installed it if I knew it would disappear again.

It looks like F62d caused issues during image flashing, which likely led to its removal or replacement.

I should update it, but it still functions.
B
BlueSkyHorizon
03-07-2021, 07:04 PM #6

That's typical for Gigabyte—the BIOS they offer isn't listed on their site anymore. It's possible it was a beta version, as they often test before finalizing a release. They might still have it in place just in case, since I wouldn't have installed it if I knew it would disappear again.

It looks like F62d caused issues during image flashing, which likely led to its removal or replacement.

I should update it, but it still functions.

J
jshi40700
Member
67
03-08-2021, 09:43 AM
#7
The reason I didn't flash initially was my concern about compatibility with my existing Ryzen 5 2600x. After flashing the latest BIOS F67d, the problem persisted. I plan to try the workaround about removing the CMOS battery later. If that fails, I'll consider reinstalling Windows at a later time.
J
jshi40700
03-08-2021, 09:43 AM #7

The reason I didn't flash initially was my concern about compatibility with my existing Ryzen 5 2600x. After flashing the latest BIOS F67d, the problem persisted. I plan to try the workaround about removing the CMOS battery later. If that fails, I'll consider reinstalling Windows at a later time.

D
Daboss132
Member
161
03-08-2021, 11:14 AM
#8
Gigabyte BIOS usually keeps CPU support intact, providing sufficient memory for future use. Asrock, however, tends to eliminate support altogether.
D
Daboss132
03-08-2021, 11:14 AM #8

Gigabyte BIOS usually keeps CPU support intact, providing sufficient memory for future use. Asrock, however, tends to eliminate support altogether.

S
SlimesDoMC
Member
65
03-28-2021, 12:06 PM
#9
It's good to hear. I've tried removing the battery and resetting the BIOS, but it didn't solve the problem. I plan to reinstall Windows 11 later.
S
SlimesDoMC
03-28-2021, 12:06 PM #9

It's good to hear. I've tried removing the battery and resetting the BIOS, but it didn't solve the problem. I plan to reinstall Windows 11 later.

A
Assou23
Member
121
04-04-2021, 06:27 PM
#10
Try a clean boot and observe if it alters the outcome—follow the guidelines carefully. Ensure no Microsoft services are disabled or Windows won’t load properly. It doesn’t remove files, just halts non-Microsoft programs during startup. Simple to undo. If this resolves the issue, it likely points to a startup program. Over several restarts, restart the stopped applications to pinpoint the culprit. Worth a shot.
Did you check for chipset driver updates?
A
Assou23
04-04-2021, 06:27 PM #10

Try a clean boot and observe if it alters the outcome—follow the guidelines carefully. Ensure no Microsoft services are disabled or Windows won’t load properly. It doesn’t remove files, just halts non-Microsoft programs during startup. Simple to undo. If this resolves the issue, it likely points to a startup program. Over several restarts, restart the stopped applications to pinpoint the culprit. Worth a shot.
Did you check for chipset driver updates?