Page MenuHome
Create Task
Maniphest T94932

Blender 3.0 fails to load, stuck on reading from the user prefs
Closed, ResolvedPublic
Actions

Description

System Information
Operating system: Windows-10-10.0.19041 64 Bits
Graphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25

Blender Version
Broken: version: 3.0.0
Worked: Blender 2.93

Short description of error
Different daily builds of Blender 3.0 fail to load most times without any errors recorded when launched from cmd and sometimes load only after system restart. Other versions of Blender load without issues.

Exact steps for others to reproduce the error
Open downloaded folder for Blender 3.0 and launch the blender.exe file, it would run but Blender won't load. Running blender_debug_gpu_glitchworkaround.cmd nor blender_factory_startup.cmd made any difference.

Related Objects

Event Timeline

Ayodele Arigbabu (DADA_universe) created this task.Jan 15 2022, 12:23 PM
Garek (Garek) changed the subtype of this task from "Design" to "Report".Jan 15 2022, 1:01 PM
Garek (Garek) added a project: BF Blender.
Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Jan 18 2022, 5:49 PM
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).

Never heared about this particular issue, however Since your GPU has M suffix, I assume you are using notebook and perhaps you use docking station and/or external monitor. Please check if this happens when there are no external peripherals connected to your machine.

Ayodele Arigbabu (DADA_universe) added a comment.Jan 18 2022, 6:26 PM
In T94932#1290384, @Richard Antalik (ISS) wrote:

Never heared about this particular issue, however Since your GPU has M suffix, I assume you are using notebook and perhaps you use docking station and/or external monitor. Please check if this happens when there are no external peripherals connected to your machine.

Thanks for the feedback. I do not use an external monitor, docking station or any other peripheral with the laptop.

Richard Antalik (ISS) added a comment.Jan 19 2022, 5:47 PM

Thanks for info. What I should have noticed though is your GPU driver version - it's very old. Latest is 511.23. Please update driver and check if this helps.

Ayodele Arigbabu (DADA_universe) added a comment.Jan 24 2022, 6:55 AM
In T94932#1291169, @Richard Antalik (ISS) wrote:

Thanks for info. What I should have noticed though is your GPU driver version - it's very old. Latest is 511.23. Please update driver and check if this helps.

Thank you. I didn't think it was the graphics card driver. I was avoiding upgrades to prevent conflicts with other OEM drivers. Upgraded the GPU driver to 511.23 anyway, but it has made no difference.

Richard Antalik (ISS) added a comment.Jan 26 2022, 12:22 AM

Thanks for checking. Not sure what could be the issue. There are other quite fresh reports with same GPU, so this is not common problem. Have you ever tried leaving Blender to load for quite long time? like 30 minutes? also in description you say, that it does actually sometimes load, can you say whas success rate is there? does it crash after some time randomly?

Only other thing I can think of now is if you have some network drive mapped and it is not present, this could potentially cause some delay.

Richard Antalik (ISS) added a comment.Feb 1 2022, 2:59 AM

Did you manage to resolve this?

Ayodele Arigbabu (DADA_universe) added a comment.Feb 1 2022, 7:55 AM

It's not been resolved. It's the weirdest thing ever. I've been leaving it for longer than 30 minutes, even overnight just yesterday. Success rate is quite poor and it is totally random. I can't put a finger on anything that informs successful loading when it happens. Yes sometimes it crashes and with that too, I can't say what leads to it. I kept trying to work with 3.0 hoping a stable version would fix things so I now have some project files in 3.0 which I've been locked out from finishing off.

Ayodele Arigbabu (DADA_universe) added a comment.EditedFeb 1 2022, 9:46 AM

I've downloaded and tried Blender 3.1.0 Beta and it's even worse, it does not even get as far as reading the User Prefs before getting stuck.

Ayodele Arigbabu (DADA_universe) added a comment.Feb 1 2022, 10:36 AM

Also tried installing Blender with the installer rather than running it from the portable folder in case that would clear anything thing. It made no difference, Blender 3.0 just isn't running.

Richard Antalik (ISS) added a comment.Feb 2 2022, 12:06 AM

I have idea what to check, perhaps this will allow you to use Blender at least.

Download mesa3d-21.3.5-release-msvc.7z from https://github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe.
This will enable opengl emulation, which will be slow, but if it will work, this means that issue is within GPU driver. Can you check this?

Ayodele Arigbabu (DADA_universe) added a comment.Feb 2 2022, 9:08 AM
In T94932#1299640, @Richard Antalik (ISS) wrote:

I have idea what to check, perhaps this will allow you to use Blender at least.

Download mesa3d-21.3.5-release-msvc.7z from https://github.com/pal1000/mesa-dist-win/releases/tag/21.3.5, extract files opengl32.dll, libglapi.dll and libgallium_wgl.dll to folder next to blender.exe.
This will enable opengl emulation, which will be slow, but if it will work, this means that issue is within GPU driver. Can you check this?

Thanks. This has not worked. I didn't think it was GPU a issue because running blender_debug_gpu_glitchworkaround.cmd didn't fix it. Perhaps this confirms that it's not a GPU issue? Wondering what has changed fundamentally between Blender 2.93 and Blender 3.0 that could cause this.

Richard Antalik (ISS) added a comment.Feb 3 2022, 2:57 AM

Yes, I think this confirms that this isn't GPU issue. Sometimes code may be changed internally that suddenly causes issues on specific GPUs because of driver bugs, so that's why this is always possiblility for me.

Perhaps can you run Blender from console with argument --debug-all and upload console output? You can also try adding -t 1 argument which should force Blender to use only one thread. I can only imagine code being stuck on hardware device (GPU, sound card, storage device), thread lock or OS/library call. First 2 options would be most likely I would say.

Ayodele Arigbabu (DADA_universe) added a comment.Feb 4 2022, 8:40 AM

Hello Richard, I ran Blender with the suggested argument, it still remained stuck not responding. Here's the console output:

C:\Users\ATTITA\Downloads\blender-3.0.0-07012022>blender --debug-all -t 1
Switching to fully guarded memory allocator.
Read prefs: C:\Users\ATTITA\AppData\Roaming\Blender Foundation\Blender\3.0\config\userpref.blend
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRScene Collection flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
DEG_relations_tag_update: Tagging relations for update.
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
DEG_relations_tag_update: Tagging relations for update.

Richard Antalik (ISS) added a subscriber: Harley Acheson (harley).Feb 5 2022, 3:31 AM

When it is stuck, do you still see console screen that pops up briefly, or do you see white/gray window with nothing in it?

According to debug output it seems to me that this is likely stuck in wm_window_ghostwindows_ensure(). This function does bunch of OS calls to initialize window. Recently some error messages have been added in rBfd1078e1055e, please check if you tested 3.1 build that is older than this commit, if not please re-check again perhaps these errors may appear. Don't quite see where this could be stuck.

Can you check what happens when you run Blender from command line with arguments -b -f 1 It should render image to C:\tmp unless you use custom startup file. This still creates window for drawing, but it is hidden, so I guess it does skip some steps.

At this point my advice would be to reinstall OS. @Harley Acheson (harley) I think you know this area much better, do you have any idea what to check?

Ayodele Arigbabu (DADA_universe) added a comment.Feb 5 2022, 8:50 AM
In T94932#1302029, @Richard Antalik (ISS) wrote:

When it is stuck, do you still see console screen that pops up briefly, or do you see white/gray window with nothing in it?

I've been getting a blank console screen with Blender 3.1 while with Blender 3.0 the console would have just one line saying reading user prefs and then stay stuck there.

According to debug output it seems to me that this is likely stuck in wm_window_ghostwindows_ensure(). This function does bunch of OS calls to initialize window. Recently some error messages have been added in rBfd1078e1055e, please check if you tested 3.1 build that is older than this commit, if not please re-check again perhaps these errors may appear. Don't quite see where this could be stuck.

I downloaded the latest Blender 3.1 Beta to be sure and those errors don't come up, console output when runnung blender --debug-all -t 1 is same as before

Can you check what happens when you run Blender from command line with arguments -b -f 1 It should render image to C:\tmp unless you use custom startup file. This still creates window for drawing, but it is hidden, so I guess it does skip some steps.

Console output when running with command line arguments: b -f 1 of which 0001.png does render as expected and gets saved to C:\tmp:
C:\Users\ATTITA\Documents\BlenderBuilds\daily\blender-3.1.0-beta+daily.0b4cf2984f82>blender -b -f 1
Blender 3.1.0 Beta (hash 0b4cf2984f82 built 2022-02-05 01:00:44)
Fra:1 Mem:42.01M (Peak 42.65M) | Time:00:02.39 | Syncing Cube
Fra:1 Mem:42.39M (Peak 42.75M) | Time:00:04.29 | Syncing Light
Fra:1 Mem:42.39M (Peak 42.75M) | Time:00:04.29 | Syncing Camera
Fra:1 Mem:42.39M (Peak 42.75M) | Time:00:04.29 | Rendering 1 / 64 samples
Fra:1 Mem:42.40M (Peak 42.75M) | Time:00:05.29 | Rendering 26 / 64 samples
Fra:1 Mem:42.40M (Peak 42.75M) | Time:00:05.40 | Rendering 51 / 64 samples
Fra:1 Mem:42.40M (Peak 42.75M) | Time:00:05.45 | Rendering 64 / 64 samples
Saved: 'C:\tmp\0001.png'
Time: 00:06.19 (Saving: 00:00.68)

At this point my advice would be to reinstall OS. @Harley Acheson (harley) I think you know this area much better, do you have any idea what to check?

Thanks, reinstalling OS would be so much stress. I hope we come up with a gentler fix.

Ray Molenkamp (LazyDodo) added a subscriber: Ray Molenkamp (LazyDodo).Feb 14 2022, 8:06 PM

It's grasping at straws here, but when blender is in this hung state can you open up the task manager, right click blender and select this option

you'll get a dialog like this for a bit:

followed by

This file will be HUGE , so please zip or 7z it up before attaching it here.

also be sure to mention the exact version of blender you made this dump from (inc buildhash if this was a daily)

Ayodele Arigbabu (DADA_universe) added a comment.Feb 17 2022, 12:01 PM
In T94932#1307752, @Ray Molenkamp (LazyDodo) wrote:

It's grasping at straws here, but when blender is in this hung state can you open up the task manager, right click blender and select this option

This file will be HUGE , so please zip or 7z it up before attaching it here.

also be sure to mention the exact version of blender you made this dump from (inc buildhash if this was a daily)

I've uploaded here the dump file as requested. The Blender version is Blender 3.1.0-beta+daily.0b4cf2984f82

Ray Molenkamp (LazyDodo) added a comment.Feb 17 2022, 3:10 PM

I'm not seeing it, where did you put it?

Ayodele Arigbabu (DADA_universe) added a comment.Feb 17 2022, 5:52 PM

blender.zip198 MBDownload
> I've uploaded here the dump file as requested. The Blender version is Blender 3.1.0-beta+daily.0b4cf2984f82

Ayodele Arigbabu (DADA_universe) added a comment.Feb 17 2022, 5:53 PM
In T94932#1309277, @Ray Molenkamp (LazyDodo) wrote:

I'm not seeing it, where did you put it?

Sorry it didn't attach. Done it right in last comment.

Ray Molenkamp (LazyDodo) added a subscriber: Nicholas Rishel (nicholas_rishel).Feb 17 2022, 7:39 PM

got a stack trace, looks like it gets stuck here trying to load C:\WINDOWS\system32\explorerframe.dll but seemingly gets stuck waiting for a lock which i suspect tread 23 is holding

0:023> ~0kb
 # RetAddr               : Args to Child                                                           : Call Site
00 00007ffd`d9df9205     : 002d0069`00000000 00007ffd`7d9600f8 0063002d`006e0069 002d0065`0072006f : ntdll!NtWaitForAlertByThreadId+0x14
01 00007ffd`d9e17cf5     : 00007ffd`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlAcquireSRWLockExclusive+0x165
02 00007ffd`d9e17bcd     : 00000236`837db020 00000000`00000000 00000000`00000000 00000236`837db020 : ntdll!LdrpHandleTlsData+0xe1
03 00007ffd`d9e0288a     : 00000236`00000004 00000236`86c06380 00000000`00000000 00000075`f25fb4e8 : ntdll!LdrpDoPostSnapWork+0x6d
04 00007ffd`d9de7bc4     : 00000236`837db020 00007ffd`00000000 00000236`0000ee0c 00000000`00000a91 : ntdll!LdrpSnapModule+0x49a
05 00007ffd`d9de4c14     : 00000236`837db020 00000236`8cb2e9f0 00000000`00000000 00000236`86c06380 : ntdll!LdrpMapAndSnapDependency+0x234
06 00007ffd`d9e2fc73     : 00000000`00000000 00000075`f25fb649 00000000`00000000 00220000`00d83fbe : ntdll!LdrpMapDllWithSectionHandle+0x184
07 00007ffd`d9e2f9a0     : 00000000`00000000 00000000`00000000 00000236`86c063d8 00000236`837db020 : ntdll!LdrpMapDllNtFileName+0x19f
08 00007ffd`d9e2ec3f     : 00000075`f25fb8e8 00000236`837db020 00000075`f25fb901 00000075`f25fb8e8 : ntdll!LdrpMapDllFullPath+0xe0
09 00007ffd`d9defb53     : 00000236`837db020 00000075`f25fba01 00000075`00000000 00000075`f25fb970 : ntdll!LdrpProcessWork+0x123
0a 00007ffd`d9de73e4     : 00000075`f25fb970 00000075`f25fbb10 00000075`f25fbc00 00000075`f25fbb00 : ntdll!LdrpLoadDllInternal+0x13f
0b 00007ffd`d9de6af4     : 00000000`00000000 00000000`00002009 00000236`8caf7428 00000075`f25fbf80 : ntdll!LdrpLoadDll+0xa8
0c 00007ffd`d7adade2     : 00000000`00000c06 00000000`00002008 00000000`00000040 00000000`00000000 : ntdll!LdrLoadDll+0xe4
0d 00007ffd`d977d475     : 00000000`00000000 00000075`f25fbd18 00000000`00000001 00000000`00000000 : KERNELBASE!LoadLibraryExW+0x162
0e 00007ffd`d977d3be     : 00000236`8caf73f0 00000075`f25fbd50 00000075`f25fbd18 00000075`f25fbdd0 : combase!LoadLibraryWithLogging+0x2d [onecore\com\combase\common\internal\loadfree.cxx @ 160] 
0f 00007ffd`d977d190     : 00000075`f25fbd50 00000075`f25fbdd0 00000075`f25fc0c0 00300039`00300041 : combase!CClassCache::CDllPathEntry::LoadDll+0x56 [onecore\com\combase\objact\dllcache.cxx @ 2294] 
10 00007ffd`d977cdca     : 00000236`8caf73f0 00000075`f25fc2d0 00000075`f25fc0c0 00000075`f25fc0c0 : combase!CClassCache::CDllPathEntry::Create+0x58 [onecore\com\combase\objact\dllcache.cxx @ 2123] 
11 00007ffd`d972b0d0     : 00000000`00000000 00000075`f25fc150 00000000`00000000 00000000`00000000 : combase!CClassCache::CClassEntry::CreateDllClassEntry+0xf6 [onecore\com\combase\objact\dllcache.cxx @ 1056] 
12 00007ffd`d97bb88d     : 00000236`86a937c0 00000000`00000c06 00000075`f25fc228 00007ffd`d9e0e25f : combase!CClassCache::GetClassObjectActivator+0x620 [onecore\com\combase\objact\dllcache.cxx @ 5353] 
13 00007ffd`d97bb206     : 00000236`86a937c0 00000075`f25fcce8 00000000`00000000 00000000`00000000 : combase!CClassCache::GetClassObject+0x45 [onecore\com\combase\objact\dllcache.cxx @ 5108] 
14 00007ffd`d971c0f0     : 00000075`f25fcce8 00000236`86a937c0 00000236`86a937c0 00007ffd`d9779b0e : combase!CServerContextActivator::CreateInstance+0x156 [onecore\com\combase\objact\actvator.cxx @ 856] 
15 00007ffd`d974d11c     : 00000236`00008664 00000000`00000000 00000000`00000000 00000000`00000000 : combase!ActivationPropertiesIn::DelegateCreateInstance+0x90 [onecore\com\combase\actprops\actprops.cxx @ 1983] 
16 00007ffd`d97d2ad8     : 00000000`00000000 00000075`f25fcab0 00000000`00000000 00007ffd`d9a02f00 : combase!CApartmentActivator::CreateInstance+0x9c [onecore\com\combase\objact\actvator.cxx @ 2189] 
17 00007ffd`d97d6b10     : 00000000`00000008 00000000`00000000 00000075`f25fd5a8 00000000`00000000 : combase!CProcessActivator::CCICallback+0x58 [onecore\com\combase\objact\actvator.cxx @ 1640] 
18 00007ffd`d97ce8a1     : 00007ffd`d9a02f00 00000075`f25fd5a8 00000000`00000000 00000000`00004048 : combase!CProcessActivator::AttemptActivation+0x40 [onecore\com\combase\objact\actvator.cxx @ 1527] 
19 00007ffd`d97d2e90     : 00007ffd`d9a02f00 00000075`d998c418 00000000`00000000 00000075`00000001 : combase!CProcessActivator::ActivateByContext+0x91 [onecore\com\combase\objact\actvator.cxx @ 1371] 
1a 00007ffd`d971c0f0     : 00000075`f25fcce8 00000075`f25fc6f0 00000075`f25fcab0 ffffff8a`0da03550 : combase!CProcessActivator::CreateInstance+0x80 [onecore\com\combase\objact\actvator.cxx @ 1271] 
1b 00007ffd`d9761a4f     : 00000075`f25fcce8 00000075`f25fcce8 00000075`f25fc750 00000075`f25fcce8 : combase!ActivationPropertiesIn::DelegateCreateInstance+0x90 [onecore\com\combase\actprops\actprops.cxx @ 1983] 
1c 00007ffd`d971c0f0     : 00000075`f25fcce8 ffffff8a`0da03550 00000000`00000000 00000000`80004005 : combase!CClientContextActivator::CreateInstance+0x17f [onecore\com\combase\objact\actvator.cxx @ 570] 
1d 00007ffd`d972d83a     : 00000000`00000000 00000075`f25fd530 00000000`00000001 00000000`00000000 : combase!ActivationPropertiesIn::DelegateCreateInstance+0x90 [onecore\com\combase\actprops\actprops.cxx @ 1983] 
1e 00007ffd`d972c309     : 00007ffd`9f6758d0 00007ff7`c5e838f1 00007ffd`9f670000 00000000`00000000 : combase!ICoCreateInstanceEx+0x90a [onecore\com\combase\objact\objact.cxx @ 2031] 
1f 00007ffd`d972c13c     : 00000000`ffffffff 00000000`00000000 00007530`0000c350 00000000`00000000 : combase!CComActivator::DoCreateInstance+0x169 [onecore\com\combase\objact\immact.hxx @ 386] 
20 (Inline Function)     : --------`-------- --------`-------- --------`-------- --------`-------- : combase!CoCreateInstanceEx+0xd1 [onecore\com\combase\objact\actapi.cxx @ 177] 
21 00007ff7`c5e85773     : 00000000`00000001 00000000`00000001 00000075`f25fdc50 00000236`824c3fb0 : combase!CoCreateInstance+0x10c [onecore\com\combase\objact\actapi.cxx @ 121] 
22 00007ff7`c5e37865     : 00000075`f25fde40 00007ffd`d9de6777 00000075`f25fdd10 00000236`833dc108 : blender!GHOST_WindowWin32::GHOST_WindowWin32+0x523
23 00007ff7`c5e2f131     : 00007ff7`cb33a838 00000000`00000000 00000236`833dc108 00000000`00000000 : blender!GHOST_SystemWin32::createWindow+0xc5
24 00007ff7`c52d0181     : 00000236`833d3588 00000000`00000000 00000000`00000000 00000000`00000000 : blender!GHOST_CreateWindow+0x71
25 00007ff7`c52d0389     : 00000000`00000870 00000236`833d3588 00000000`00000f00 00000236`833dc808 : blender!wm_window_ghostwindow_add+0xf1
26 00007ff7`c52d05ae     : 00000236`833dc108 00007ff7`cb35f858 00000000`00000000 00000000`00000000 : blender!wm_window_ghostwindow_ensure+0xe9
27 00007ff7`c52c621e     : 00000236`00000f00 00000236`00000870 00000236`833dc108 00000236`833dc108 : blender!wm_window_ghostwindows_ensure+0x6e
28 00007ff7`c52cb859     : 00000236`8216b388 00000236`833dc808 00000075`f25fe430 00000075`f25fe430 : blender!WM_check+0x1be
29 00007ff7`c52c73c0     : 00000236`8216b388 00000000`00000001 00000236`8216b388 00000236`82e8be08 : blender!wm_homefile_read_ex+0x6e9
2a 00007ff7`c4f10758     : 00000236`8216b388 00000000`00000000 00000000`00000000 00000000`00000000 : blender!WM_init+0x140
2b 00007ff7`ca5eb310     : 00007ff7`00000001 00000000`00000000 00000000`61fd8a38 00000236`fe0bb690 : blender!main+0x378
2c 00007ffd`d9b77034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : blender!__scrt_common_main_seh+0x10c
2d 00007ffd`d9e22651     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
2e 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
0:023> ~23kb
 # RetAddr               : Args to Child                                                           : Call Site
00 00007ffd`d9df18b3     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtWaitForAlertByThreadId+0x14
01 00007ffd`d9e18191     : 00000000`00000000 00000000`00000000 00000000`00000000 00000075`f237c000 : ntdll!RtlAcquireSRWLockShared+0x153
02 00007ffd`d9de77a7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrpAllocateTls+0x41
03 00007ffd`d9e44f84     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : ntdll!LdrpInitializeThread+0x6f
04 00007ffd`d9e44b63     : 00000000`00000000 00007ffd`d9dd0000 00000000`00000000 00000075`f23bb000 : ntdll!LdrpInitialize+0x408
05 00007ffd`d9e44b0e     : 00000075`f27ff3d0 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrpInitialize+0x3b
06 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe
`

@Harley Acheson (harley) / @Nicholas Rishel (nicholas_rishel) any of this rings a bell for either of you two? have we messed with the CoInitialize(ex?) call in recent versions?

Harley Acheson (harley) added a comment.Feb 17 2022, 9:13 PM

@Ray Molenkamp (LazyDodo) - have we messed with the CoInitialize(ex?) call in recent versions?

I don't think so. Still as weird as ever,

Calling OleInitialize(0) and OleUninitialize in system, (single-thread apartment) apparently for GHOST_DropTargetWin32? Then a couple more calls to CoInitializeEx / CoUninitialize (COINIT_APARTMENTTHREADED). Although one call to CoInitializeEx includes COINIT_DISABLE_OLE1DDE while other doesn't - both probably should.

No bells going off and looks as I remember it all, so I doubt any recent changes.

Nicholas Rishel (nicholas_rishel) added a comment.Feb 18 2022, 1:44 AM

Nothing stands out to me.

Ayodele Arigbabu (DADA_universe) added a comment.Feb 18 2022, 7:34 AM

In case it helps, I ran a Windows update some days ago, after which Blender 3.X was loading normally as if nothing ever happened, for a couple of days. Then it went back to hanging at Start Up for no clear reason.

Richard Antalik (ISS) added a comment.Apr 12 2022, 9:26 PM

@Ayodele Arigbabu (DADA_universe) I want to check on status here - does this issue still happen? Did you check latest 3.1/3.2 builds?

Ayodele Arigbabu (DADA_universe) added a comment.Apr 13 2022, 9:36 AM
In T94932#1340067, @Richard Antalik (ISS) wrote:

@Ayodele Arigbabu (DADA_universe) I want to check on status here - does this issue still happen? Did you check latest 3.1/3.2 builds?

Thanks for checking back in. I've downloaded the latest 3.2 built and I will test over a couple of days and report back.

Ayodele Arigbabu (DADA_universe) closed this task as Resolved.Apr 28 2022, 1:24 AM
Ayodele Arigbabu (DADA_universe) claimed this task.

Happy to report that I've been running Blender 3.1.2 build #cc661020c3b for two weeks now and it's been loading normally without getting stuck on my PC while loading. I am thus encouraged to believe the issue has been resolved in this build and hopefully that would remain accurate for subsequent builds after this one. Thank you to all who chimed in to help look into the matter!