szyzk
Member
I had a sporadic problem in Win 10 Pro 21h2 with explorer hanging & crashing when accessing a specific NVMe designated as a download/catchall repository drive and it happened again today, a few days after doing an iso-based upgrade to Win 11 Pro 22h2.
It typically only begins after I've downloaded something -- but not always -- and Event Viewer offers no clues as to what's happening other than telling me that explorer was hanging.
The drive is healthy.
When this problem pops up and I attempt to view the download folder/drive through Firefox, explorer will hang and crash. If I open File Explorer and try to open the drive from the rightmost panel within File Explorer, explorer will hang and crash. But if I open File Explorer and try to open the drive from the leftmost panel explorer will only hang and crash about 50% of the time; the other 50% of the time it will properly list all the files & folders within the drive in the rightmost panel as it always does.
And of course this issue typically resolves itself after a few minutes of it starting. That leads me to think it has something to do with explorer's indexing of the drive, but... I don't know.
I've done a few searches but haven't come up with anything; hopefully I didn't miss an obvious fix somewhere. Does anyone have a suggestion for what might be happening?
It typically only begins after I've downloaded something -- but not always -- and Event Viewer offers no clues as to what's happening other than telling me that explorer was hanging.
The drive is healthy.
When this problem pops up and I attempt to view the download folder/drive through Firefox, explorer will hang and crash. If I open File Explorer and try to open the drive from the rightmost panel within File Explorer, explorer will hang and crash. But if I open File Explorer and try to open the drive from the leftmost panel explorer will only hang and crash about 50% of the time; the other 50% of the time it will properly list all the files & folders within the drive in the rightmost panel as it always does.
And of course this issue typically resolves itself after a few minutes of it starting. That leads me to think it has something to do with explorer's indexing of the drive, but... I don't know.
I've done a few searches but haven't come up with anything; hopefully I didn't miss an obvious fix somewhere. Does anyone have a suggestion for what might be happening?
My Computers
System One System Two
-
- OS
- Windows 11 Pro 22h2
- Computer type
- PC/Desktop
- CPU
- i5-12600k (P:50x 1-2c, 48x 3-4c, 47x 5-8c; E:38x 1-8c)
- Motherboard
- Asus Tuf Z690-Plus Wifi D4
- Memory
- Predator Apollo 32GB DDR4 3600Mhz (15-15-15-35)
- Graphics Card(s)
- Asus Dual RTX 3070 v2 OC
- Hard Drives
- 1TB T-Force Cardea Z44L Gen4 NVMe
MSI Spatium M470 Gen 4 NVMe
1TB Intel 670p Gen3 NVMe
- PSU
- EVGA Supernova G+ 750w
- Case
- Antec DP503
- Cooling
- CPU: Arctic Liquid Freezer II 360 w/ 3 x 120mm Iceberg Thermal Icegale Xtra; Case: 3 x 140mm Scythe Kaze Flex 1800
-
- Operating System
- Windows 11 Pro 22h2
- Computer type
- PC/Desktop
- CPU
- i3-10105
- Motherboard
- Asus Prime B560M-A
- Memory
- OLOy Blade 32GB 3200MHz (16-16-16-35)
- Hard Drives
- 512GB Toshiba Gen3 NVMe; 6TB WD Red Plus HDD; 2TB WD Red Plus HDD; 2TB Seagate Barracuda HDD
- PSU
- EVGA BQ 600w
- Case
- Thermaltake Versa H15
- Cooling
- CPU: Stock Intel boxed cooler; Case: 4 x 120mm Scythe Kaze Flex Slim 1800; HDDs: 1 x 92mm Kaze Flex Slim 2500
- Other Info
- this low-powered machine wears many hats: it gets to be a generic home server/nas, pi-hole dns, streaming plex server, dayz lan server, and torrent box, among other things