Big Folder - Unable Open Windows Explorer - DEBUG LOG

Found a bug in "Everything"? report it here
Post Reply
Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Wed Jul 08, 2020 4:05 pm

The folder cannot be opened if it is huge. I click open open no reaction.
How can I solve this problem? The problem only occurs with the largest folder with 14k files inside.~
~ 71GB !!! size
The problem also occurs in applications/tool based on "MFT" (Master Seeker or UltraSearch) or Java Explorer.
In Windows Explorer and Total Commander this problem does not occur

Vers. 1.4.1.969 (x64)
Windows 7 64-b
Last edited by Debugger on Thu Jul 09, 2020 7:13 pm, edited 2 times in total.

tuska
Posts: 251
Joined: Thu Jul 13, 2017 9:14 am

Re: Big Folder - Unable Open

Post by tuska » Wed Jul 08, 2020 6:12 pm

Debugger wrote:How can I solve this problem?
With these settings you can double click on the folder in 'Everything' and
it will then be opened automatically in Total Commander in the active window.

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open

Post by Debugger » Wed Jul 08, 2020 7:11 pm

However, I prefer the standard Win Explorer...
And TC was just an example ...
I'm most interested in why Everything has restrictions on opening such large folders ...

horst.epp
Posts: 318
Joined: Fri Apr 04, 2014 3:24 pm

Re: Big Folder - Unable Open

Post by horst.epp » Wed Jul 08, 2020 7:57 pm

Debugger wrote:
Wed Jul 08, 2020 7:11 pm
However, I prefer the standard Win Explorer...
And TC was just an example ...
I'm most interested in why Everything has restrictions on opening such large folders ...
What do you mean with Open a folder in Everything ?
Everything doesn't open any folder by itself, it just shows a list of files and folders.
Any Open happens with Windows Explorer by default or any other configured file manager.

tuska
Posts: 251
Joined: Thu Jul 13, 2017 9:14 am

Re: Big Folder - Unable Open

Post by tuska » Wed Jul 08, 2020 8:21 pm

2Debugger
What are your settings in 'Everything' under:

Code: Select all

Menu "Tools" - "Options..." - "General: Context Menu" - "Open (Folders)" --> Command:
when trying to open large folders?

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open

Post by Debugger » Wed Jul 08, 2020 10:28 pm

$exec("%1")

tuska
Posts: 251
Joined: Thu Jul 13, 2017 9:14 am

Re: Big Folder - Unable Open

Post by tuska » Thu Jul 09, 2020 9:56 am

Debugger wrote:
Wed Jul 08, 2020 10:28 pm
$exec("%1")
Well, this is the default setting ... for opening folders in Windows Explorer.
So a double click on a folder in 'Everything' should open that folder in Windows Explorer.

If that doesn't happen, you can try to open the folder in Total Commander, with this setting in Everything:

Code: Select all

$exec("Path\To\TOTALCMD64.EXE" /O /A /S "%1")
You have to change the path to the file TOTALCMD64.EXE.

If that does not work either, then we need an expert...

PS:
I have no problem with a folder with 175 GB after double clicking on the folder in 'Everything'
to open it immediately in Windows Explorer or Total Commander.

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open

Post by Debugger » Thu Jul 09, 2020 11:29 am

Try to understand. Actually, it's not about the size of the folder, but what's in one folder.
Please do not confuse with subfolders in the folder.
Put 20,000 files, e.g. mp3 in only one folder larger than 70 GB.
And try to open it.
Oh then you will be surprised.

tuska
Posts: 251
Joined: Thu Jul 13, 2017 9:14 am

Re: Big Folder - Unable Open

Post by tuska » Thu Jul 09, 2020 11:52 am

Sorry, I cannot create such a test scenario due to a lack of sufficient files.

I understand your information as follows:
1. You can open the 71 GB folder directly in Windows Explorer and Total Commander
2. You double click on this folder in 'Everything' and it will NOT open in Windows Explorer [and in Total Commander?]
Is this correct?

For testing purposes please use the latest 'Everything' Beta Nightly Build Version 1.4.1.984 (x64)
and report whether the problem persists.

________________________________________________
Windows 10 Pro (x64) Version 2004 (OS build 19041.329)
Intel(R) Core(TM) i7-4770 CPU @ 3.4OGHz, 16 GB RAM
TC 9.51 x64/x86 | 'Everything'-Version 1.4.1.984 (x64)

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open

Post by Debugger » Thu Jul 09, 2020 2:25 pm

Version 1.4.1.984 (x64)

This folder cannot be opened ...
I click "Open" and nothing happens, no reaction whatsoever!

Code: Select all

2020-07-09 16:32:01.295: selection: 1/1: E:\test
2020-07-09 16:32:01.299: exec: first expr
2020-07-09 16:32:01.301: exec: command $exec("%1")
2020-07-09 16:32:01.303: exec: fullfilename E:\test
2020-07-09 16:32:01.305: exec: depth 0 
2020-07-09 16:32:01.307: exec: exec "%1")
2020-07-09 16:32:01.308: exec: depth 1 
2020-07-09 16:32:01.310: exec: got "E:\test"
2020-07-09 16:32:01.312: exec: shellexecute (idlist) file:E:\test param:
2020-07-09 16:32:01.317: WM_ACTIVATE 0000000000000000 00000000009b0f4e, lastfocus 00000000001817d0, current focus 00000000001817d0
2020-07-09 16:32:01.319: Enter ShellExecuteExW
2020-07-09 16:32:01.321: E:
2020-07-09 16:32:01.327: Leave ShellExecuteExW
2020-07-09 16:32:01.330: WM_ACTIVATE 0000000000000001 00000000009b0f4e, lastfocus 00000000001817d0, current focus 00000000009b0f4e
2020-07-09 16:32:01.332: sub buf killed
2020-07-09 16:32:01.335: set 1 run history in 0.000024 seconds
2020-07-09 16:32:01.336: exec: main thread regained focus
2020-07-09 16:32:01.338: new results 69
2020-07-09 16:32:02.229: WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 00000000001817d0, current focus 00000000001817d0

Code: Select all

selection: 1/1: E:\test
exec: first expr
exec: command $exec("%1")
exec: fullfilename E:\test
exec: depth 0
exec: exec "%1")
exec: depth 1
exec: got "E:\test"
exec: shellexecute (idlist) file:E:\test param:
WM_ACTIVATE 0000000000000000 0000000000481de6, lastfocus 00000000001f1a72, current focus 0
0000000001f1a72
Enter ShellExecuteExW
E:
Leave ShellExecuteExW
WM_ACTIVATE 0000000000000001 0000000000481de6, lastfocus 00000000001f1a72, current focus 0
000000000481de6
sub buf killed
set 1 run history in 0.000030 seconds
exec: main thread regained focus
MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
MSG: 0000000000530e4c 1401 0000000000000000 0000000000000000
EVENT: 000000013f713d80 00000000004d8c80
new results 69
MSG: 00000000001f1a72 0200 0000000000000001 0000000001de000e
MSG: 00000000001f1a72 000f 0000000000000000 0000000000000000
MSG: 0000000000141568 0113 0000000000000006 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0202 0000000000000001 0000000001de000e
MSG: 0000000000141568 0113 0000000000000006 0000000000000000
MSG: 0000000000141568 0113 0000000000000006 0000000000000000
MSG: 00000000001f1a72 0201 0000000000000000 0000000001de000e
MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
MSG: 00000000001f1a72 0200 0000000000000000 0000000001de000e
MSG: 00000000001f1a72 000f 0000000000000000 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 0000000000141568 0113 0000000000000006 0000000000000000
MSG: 00000000003c1d18 0113 0000000000000001 0000000000000000
MSG: 0000000000141568 0113 0000000000000006 0000000000000000
MSG: 00000000001f1a72 0200 0000000000000000 0000000001df000e
MSG: 00000000001f1a72 0200 0000000000000000 0000000001e0000e
MSG: 00000000001f1a72 0200 0000000000000000 0000000001e1000e
MSG: 00000000001f1a72 0200 0000000000000000 0000000001e40011
MSG: 00000000001f1a72 0200 0000000000000000 0000000001f00026
MSG: 00000000001f1a72 0200 0000000000000000 000000000208006a
MSG: 00000000001f1a72 0200 0000000000000000 00000000022400dc
MSG: 00000000001f1a72 0200 0000000000000000 00000000023d0171
MSG: 00000000001f1a72 0200 0000000000000000 00000000025e0213
MSG: 00000000001f1a72 0200 0000000000000000 00000000028402d4
MSG: 00000000001f1a72 0200 0000000000000000 0000000002ae038d
MSG: 00000000001f1a72 0200 0000000000000000 0000000002d70438
MSG: 00000000001f1a72 0200 0000000000000000 0000000002fa04b4
MSG: 00000000001f1a72 0200 0000000000000000 00000000031e0501
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0200 0000000000000000 0000000003310519
MSG: 00000000001f1a72 0200 0000000000000000 000000000339051c
MSG: 00000000001f1a72 0200 0000000000000000 00000000033c051c
MSG: 00000000001f1a72 0200 0000000000000000 000000000343051c
MSG: 00000000001f1a72 0200 0000000000000000 000000000345051a
MSG: 00000000001f1a72 0200 0000000000000000 00000000034b0516
MSG: 00000000001f1a72 0200 0000000000000000 000000000354050f
MSG: 00000000001f1a72 0200 0000000000000000 00000000035a0509
MSG: 00000000001f1a72 0200 0000000000000000 0000000003600503
MSG: 00000000001f1a72 0200 0000000000000000 0000000003660500
MSG: 00000000001f1a72 0200 0000000000000000 00000000036904ff
MSG: 00000000001f1a72 0200 0000000000000000 00000000036e04ff
MSG: 00000000001f1a72 0200 0000000000000000 00000000037204ff
MSG: 00000000001f1a72 0200 0000000000000000 00000000037404ff
MSG: 00000000001f1a72 0200 0000000000000000 00000000037604fe
MSG: 00000000001f1a72 0200 0000000000000000 00000000037704fe
MSG: 00000000001f1a72 0200 0000000000000000 00000000037804fe
MSG: 00000000001f1a72 0200 0000000000000000 00000000037a04fd
MSG: 00000000001f1a72 0200 0000000000000000 00000000037c04fd
MSG: 00000000001f1a72 0200 0000000000000000 00000000038004fc
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0200 0000000000000000 00000000038304fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000038704fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000038904fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000038c04fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000039004fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000039504fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000039804fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000039c04fc
MSG: 00000000001f1a72 0200 0000000000000000 00000000039f04fd
MSG: 00000000001f1a72 0200 0000000000000000 0000000003a60502
MSG: 00000000001f1a72 0200 0000000000000000 0000000003ac0506
MSG: 0000000000172192 0200 0000000000000000 000000000000050c
MSG: 0000000000172192 0200 0000000000000000 000000000000050c
MSG: 0000000000172192 0200 0000000000000000 000000000004050f
MSG: 0000000000141568 0113 0000000000000006 0000000000000000
MSG: 0000000000172192 0200 0000000000000000 00000000000b0513
MSG: 0000000000172192 0200 0000000000000000 00000000000d0515
MSG: 0000000000172192 0200 0000000000000000 0000000000110518
MSG: 0000000000172192 0200 0000000000000000 0000000000140519
MSG: 0000000000172192 0200 0000000000000000 000000000016051a
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 00000000001f1a72, current focus 0
0000000001f1a72
MSG: 00000000001f1a72 000f 0000000000000000 0000000000000000
MSG: 0000000000dd1f0c 0113 0000000000000006 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 0000000000172192 0200 0000000000000000 00000000000a04ed
MSG: 00000000001f1a72 0200 0000000000000000 0000000003b204d5
MSG: 00000000001f1a72 0200 0000000000000000 0000000003a304bb
MSG: 00000000001f1a72 0200 0000000000000000 00000000038f0498
MSG: 00000000001f1a72 0200 0000000000000000 00000000037b0471
MSG: 00000000001f1a72 0200 0000000000000000 00000000035e0441
MSG: 00000000001f1a72 0200 0000000000000000 00000000033a0404
MSG: 00000000001f1a72 0200 0000000000000000 00000000030f03b6
MSG: 00000000003c1d18 0113 0000000000000001 0000000000000000
MSG: 00000000001f1a72 0200 0000000000000000 0000000002e10363
MSG: 00000000001f1a72 0200 0000000000000000 0000000002aa0302
MSG: 00000000001f1a72 02a3 0000000000000000 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000
MSG: 00000000001f1a72 0113 000000000000002d 0000000000000000

tuska
Posts: 251
Joined: Thu Jul 13, 2017 9:14 am

Re: Big Folder - Unable Open - DEBUG LOG

Post by tuska » Thu Jul 09, 2020 5:25 pm

I cannot help you with this problem, but it would be very interesting,
whether a double click on the folder will open it in Total Commander Version 9.51.

Could you please still try this in version 1.4.1.984 (x64) with this parameter:

Code: Select all

$exec("Path\To\TOTALCMD64.EXE" /O /A /S "%1")
Thank you!

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open - DEBUG LOG

Post by Debugger » Thu Jul 09, 2020 6:49 pm

$exec("C:\totalcmd\TOTALCMD64.EXE" /O /A /S "%1")

Work

tuska
Posts: 251
Joined: Thu Jul 13, 2017 9:14 am

Re: Big Folder - Unable Open - DEBUG LOG

Post by tuska » Fri Jul 10, 2020 10:47 am

Debugger wrote:
Thu Jul 09, 2020 6:49 pm
$exec("C:\totalcmd\TOTALCMD64.EXE" /O /A /S "%1")

Work
I am glad to hear that with Total Commander it works.
Thanks again!

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Sun Jul 12, 2020 5:27 am

tuska - This error/bug is caused by the folder name

If the FOLDER Name contains a name

Code: Select all

E:\poky
or

Code: Select all

E:\POKY
unable to open folder in Explorer



For tests I changed the name to

Code: Select all

E:\1
and it opens here correctly
this confirms that the name causes this opening problem



Of course, this only applies when there are many elements (9800) with this specific folder name "POKY" OR "ROKY" etc.!!!

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Mon Jul 13, 2020 10:03 am

No response from developers?
Why the file name causes problems with opening, I say it once and it is not Unicode, only the English foldername. [A-Z]
https://dictionary.cambridge.org/pl/dic ... glish/poky

NotNull
Posts: 2421
Joined: Wed May 24, 2017 9:22 pm

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by NotNull » Mon Jul 13, 2020 8:21 pm

EDIT: POXY should be POKY. Too much work to replace it all ...

I tried to reproduce the issue, so I:
- created 10.000 folders (POXY_1_POXY ... POXY_10000_POXY) and filled POXY_5000_POXY with 15.000 files. [1]
- Started Everything
- Searched for POXY_5000
- Double-clicked the folder POXY_5000_POXY

Result:
File Explorer opened normally, albeit a little slower than usual.


I guess there are more factors in play here, other than the POXY foldername or the amount of folders/files. Maybe a virus-/malware scanner?

There is a difference between Explorer the filemanager and Explorer the shell/desktop.
Opening a folder from Everything has more similarities with opening it through Explorer the shell.
What happens if you open the Run-box (Win + R), type your POXY foldername and press ENTER? Does it open the folder in Explorer (the file manager)?


You can also try to open File Explorer in different way:
Enter the following Open (Folder) command: $exec(c:\windows\explorer.exe "%1")


And another question:
Are you running Everything as administrator or as a restricted user + Everything Service (see Menu:Tools > Options > General)



[1] Created using these 2 CMD commands:

Code: Select all

for /l %x in (1,1,10000) do @md manyfiles\POXY_%x_POXY
for /l %x in (1,1,15000) do @echo.> manyfiles\POXY_5000_POXY\file_%x.txt

( TEsted with Everything 1.4.1.976 x64 @ Win10 1909 )

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Tue Jul 14, 2020 8:59 am

NotNull
General
[x] Run as administrator
[ ] Everything Service

You can also try to open File Explorer in different way:
Enter the following Open (Folder) command: $exec(c:\windows\explorer.exe "%1")

With this command it opens correctly :)

NotNull
Posts: 2421
Joined: Wed May 24, 2017 9:22 pm

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by NotNull » Tue Jul 14, 2020 1:39 pm

Debugger wrote:
Tue Jul 14, 2020 8:59 am
With this command it opens correctly :)
Good.

What about this?
What happens if you open the Run-box (Win + R), type your POXY foldername and press ENTER? Does it open the folder in Explorer (the file manager)?
If that didn't open it is an issue outside Everything.

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Tue Jul 14, 2020 2:09 pm

Win+R
Here it opens without a problem...

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Tue Jul 14, 2020 5:08 pm

I would like to solve the same problem in MasterSeeker, except that there is no option to type this command.
Unfortunately, the author does not respond to my messages.
Can anyone help?

NotNull
Posts: 2421
Joined: Wed May 24, 2017 9:22 pm

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by NotNull » Tue Jul 14, 2020 7:12 pm

Debugger wrote:
Tue Jul 14, 2020 2:09 pm
Win+R
Here it opens without a problem...
Then it is still unsure if it is Everything related or not. Probably not, as you have the same issue in other programs.
(but at least you now have a workaround..)

Debugger wrote:
Tue Jul 14, 2020 5:08 pm
I would like to solve the same problem in MasterSeeker, except that there is no option to type this command.
Unfortunately, the author does not respond to my messages.
Can anyone help?
Can't help you.
I am not surprised the author doesn't respond as it looks like MasterSeeker is abandoned (most recent version is from 2014).

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Wed Jul 15, 2020 6:06 am

My computer went into "Button Windows Start -> Close -> Sleep" mode all the time to start the computer faster.
I just made a clean start of the computer (Normal start) and I see that this error was immediately resolved in the applications.

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Wed Jul 15, 2020 6:13 am

And now I remember that a Exlporer shell failure occurred two or three times when I opened the Everything folder on the system
E:\Downloads\Everything.exe

This behavior is caused when the explorer shell temporarily crashes. Of course, on all computers, sometimes the shell can behave this way. Because every system is not completely free of temporary errors and such exceptions occur in the system.

therube
Posts: 2768
Joined: Thu Sep 03, 2009 6:48 pm

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by therube » Mon Jul 20, 2020 7:56 pm

Am I understanding correctly, that after a computer reboot, all is now working correctly?

Debugger
Posts: 559
Joined: Thu Jan 26, 2017 11:56 am

Re: Big Folder - Unable Open Windows Explorer - DEBUG LOG

Post by Debugger » Thu Jul 23, 2020 10:51 pm

Could not open folder in Everything has caused an access violation exception (0xC0000005) when trying to execute instructions from a non-executable address at memory location 0x0ff40fd8 on thread 2

Code: Select all

All functions in this operation      (includes system functions, excludes boiler-plate functions)
 
0x0ff40fd8 
kernel32!WerpReportFaultInternal 
kernel32!WerpReportFault 
kernel32!BasepReportFault 
kernel32!UnhandledExceptionFilter 
ntdll! ?? ::FNODOBFM::`string' 
ntdll!_C_specific_handler 
ntdll!RtlpExecuteHandlerForException 
ntdll!RtlDispatchException 
ntdll!KiUserExceptionDispatcher 
EXPLORERFRAME!CExplorerFrame::FrameMessagePump 
EXPLORERFRAME!BrowserThreadProc 
EXPLORERFRAME!BrowserNewThreadProc 
EXPLORERFRAME!CExplorerTask::InternalResumeRT 
EXPLORERFRAME!CRunnableTask::Run 
shell32!CShellTask::TT_Run 
shell32!CShellTaskThread::ThreadProc 
shell32!CShellTaskThread::s_ThreadProc 
shlwapi!WrapperThreadProc 
kernel32!BaseThreadInitThunk 
ntdll!RtlUserThreadStart

Post Reply