TC 7.5 crash at startup

[Haos]

Posting about this bug here, as it began with TC 7.5 PB3. Same bug happens with all the following versions up to 7.50a.

Access violation at address 79497800. Read of address 79497800.
Windows exception 0xc0000005 (Page Fault).
Stack trace:
[got screenshots, but forum doesnt let me post them for now.]
Will provide screenies asap.

This crash happens on our new, experimental rack box, running Windows 2003 R2. Previous versions like 7.04 work flawlessly.

Any pointers on possible cause? This box is running several critical processes, so OS reinstall is out of question:/

[ghisler(Author)]

Can you copy the stack trace with Ctrl+C? This way I don't need to type it all by hand to analyze it...

[Haos]

You're right...

7.50pb3

Code: Select all

Access violation at address 79497800. Read of address 79497800.
Please report this error to the Author,
with a description of what you were doing when this error occured!
Continue execution?

Windows exception: C0000005
Stack trace:
79497800 00414DDC 77E8A590 7C9068CB
77E8AF03 004429ED 00413DDC 77E8AB14
77E8A352 77E8A371 77E8ACB8 77E8AFE2
00419395 004193C0 0041957A 006931C4
7C723F96 7C723FAE 7C723F9A
Press Ctrl+C to copy this report!

7.50a

Code: Select all

Access violation at address 79497800. Read of address 79497800.

Please report this error to the Author, with a description 
of what you were doing when this error occured!

Windows exception: C0000005
Stack trace:
79497800 
5D87D7 5D7BD3 5D9D65 4443BA  
414514 44397B 414514 419B58
419BF0 69F119
Raw:
5D87D7 42259E 69C025 658882 658E14 682FBE
46BCDB 670063 5C0063 42700E 42738E 4273C9
65828F 4213A6 4213EE 66630F 69C025 65FBC1
530047 40208E 402235 69BFDD 69BE38 6586EB
6596E8 4213A6 4023DB 5D7BD3 666B47 407607
666DED 670063 5C0063 530047 401E4D 530047
47005A 40208E 4023DB 40D030 40CCEE 66607B
6660D9 530047 47005A 695F6F 4DD629 47005A
666B47 530047 65828F 4213A6 4213EE 66630F
530047 4075C9 6660A5 6660D9 402235 402235

Press Ctrl+C to copy this report!
Continue execution?

[ghisler(Author)]

It seems to happen when TC tries to update the drive dropdown list.

Can you try with a fresh wincmd.ini? Just start TC like this:
c:\totalcmd\totalcmd.exe /i=c:\totalcmd\test.ini

[Haos]

Different crash, also at startup (TC 7.50a):

Code: Select all

Access violation at address 0D42CF00. Read of address 0D42CF00.

Please report this error to the Author, with a description 
of what you were doing when this error occured!

Windows exception: C0000005
Stack trace:
0D42CF00
5D87D7 5D7BD3 5D9D65  4443BA  >414514 44397B
414514 419B58 419BF0 69F119
Raw:
5D87D7 42259E 69C025 658882 658E14 682FBE
46BCDB 670063 5C0063 42700E 42738E 4273C9
65828F 4213A6 4213EE 66630F 69C025 65FBC1
402235 4033D4 4021B4 69BFDD 69BE38 6586EB
6596E8 4213A6 4023DB 5D7BD3 666B47 407607
666DED 670063 5C0063 40208E 4023DB 40D030
40CCEE 66607B 6660D9 695F6F 4DD629 666B47
65828F 4213A6 4213EE 66630F 4075C9 6660A5
6660D9 402235 402235 4033D4 402209 4212D3
666413 401DAC 402235 4033D4 4021B4 69BFDD

Press Ctrl+C to copy this report!
Continue execution?

[ghisler(Author)]

It's actually in the same location. Do you get this every time, or only occasionally?

[Haos]

It happens everytime, no matter if i use test.ini or start normally.

[ghisler(Author)]

It looks like a conflict between TC and some background tool, like WindowBlinds or other tool which somehow changes the look or operation (e.g. a macro recorder). Do you use any such (non-Microsoft) tools?

[Haos]

Looks like sorted out right now. One of our tools fitted into your description. Could you please share some secret why such conflict started right at pre-beta 3 with all previous versions working fine?

[ghisler(Author)]

Sorry, no idea - some of these tools can cause the order in which Windows messages are sent to a window to change. For example, WindowBlinds causes a window to appear much earlier than without it, so TC gets redraw messages while the necessary data structures haven't even been created! TC then tries to access them, which fails.

Please contact me by e-mail if you would like to get a test version where I catch this error. I may catch this one, but not others caused by your background tool...