Constant Crashes

Things you’d like to miss in the future...
DeadSerious
Posts: 18
Joined: 05 Jan 2010 07:17

Re: Constant Crashes

Post by DeadSerious »

admin wrote:
DeadSerious wrote:
admin wrote:Please find DisableSHChangeNotifyRegister in the INI and set it to 1:

Code: Select all

DisableSHChangeNotifyRegister=1
Still crashes?
Is this one for me? (Sorry, got confused. :) )
Yep, for you (and anybody else with "constant crashes"). :)

But note that certain things (e.g. Undo) will not work anymore with this setting.
Okay, I did it. We'll see how that works. I haven't used the undo setting yet, so maybe I won't miss it.

ogroeger
Posts: 92
Joined: 03 Jul 2007 07:39

Re: Constant Crashes

Post by ogroeger »

admin wrote:Please find DisableSHChangeNotifyRegister in the INI and set it to 1:

Code: Select all

DisableSHChangeNotifyRegister=1
Still crashes?
Yes (and no). Still crashes, but the stack text had changed. But i don't know if these changes are relevant:

Code: Select all

STACK_TEXT:  
0018e420 72a10dcf c000008f 00000001 00000002 KERNELBASE!RaiseException+0x58
WARNING: Stack unwind information not available. Following frames may be wrong.
0018e440 72a0e228 0018e48c 800a01ae 0018e490 msvbvm60!EbGetHandleOfExecutingProject+0x22b3
0018e454 72a1939e 0018e46c 00000000 02c219b8 msvbvm60!rtcDoEvents+0x131
0018e490 72a1a2b6 80004002 02c219b8 004723d0 msvbvm60!TipInvokeMethod+0x4a8
0018e504 006eded4 03ce1450 0018e570 72a1a274 msvbvm60!_vbaHresultCheckObj+0x42
0018e5c0 00612646 03ce1450 0018e7b8 007c90a8 XYplorer+0x2eded4
0018e6b4 00612205 009beff8 0018e7b8 0018e6dc XYplorer+0x212646
0018e714 0060413b 009beff8 0018e7b8 0018e76c XYplorer+0x212205
0018e7d0 005ed73e 009beff8 03cdc5dc 0018e84c XYplorer+0x20413b
0018e894 0057279f 009beff8 03cd598c 0018f518 XYplorer+0x1ed73e
0018e8d8 00575353 009beff8 0018f4b8 0018f518 XYplorer+0x17279f
0018e920 76843ec3 009beff8 0018f4b8 0018f518 XYplorer+0x175353
0018e948 72a16ef5 009bfa1c 0000003c 00000004 oleaut32!DispCallFunc+0x165
0018f2a4 72a09a7b 009bfa1c 0042b290 6003010f msvbvm60!_vbaAptOffset+0x68b
0018f2e4 72a09c2c 009bfa1c 0000000a 00000008 msvbvm60!BASIC_DISPINTERFACE_GetTypeInfo+0x2aa
0018f314 72a11723 009bfa1c 0000000a 7295aea8 msvbvm60!EVENT_SINK_Invoke+0x50
0018f37c 72a48ba5 03c85408 0000000a 00000000 msvbvm60!EbGetHandleOfExecutingProject+0x2c07
0018f500 0067e8a7 03c85408 03c855e0 00000000 msvbvm60!_vbaRaiseEvent+0x16
0018f5f0 72991d33 03c85408 0018f7b4 0018f7bc XYplorer+0x27e8a7
0018f61c 72992034 004279c6 0018f6d8 0000000a msvbvm60!IID_IVbaHost+0x236f3
0018f634 72992159 03c858d8 0018f718 0018f6d8 msvbvm60!IID_IVbaHost+0x239f4
0018f73c 72992667 03b02dc4 02ace5b4 02ab2b88 msvbvm60!IID_IVbaHost+0x23b19
0018f760 729a04d7 03b02dc4 0000000d 0018f780 msvbvm60!IID_IVbaHost+0x24027
0018f7c0 7299d6b7 03b02dc4 0000000d 00000001 msvbvm60!IID_IVbaHost+0x31e97
0018f828 729f3941 02ab2b88 001a04d8 00000201 msvbvm60!IID_IVbaHost+0x2f077
0018f868 7299ce49 03b02dc4 001a04d8 00000201 msvbvm60!DllCanUnloadNow+0x13c8f
0018f890 7299f97d 00000000 001a04d8 00000201 msvbvm60!IID_IVbaHost+0x2e809
0018f8ec 76c46238 001a04d8 00000201 00000001 msvbvm60!IID_IVbaHost+0x3133d
0018f918 76c468ea 7299f74e 001a04d8 00000201 user32!InternalCallWinProc+0x23
0018f990 76c50ab0 00000000 7299f74e 001a04d8 user32!UserCallWinProcCheckWow+0x109
0018f9c8 76c50ad6 ffff09fd 001a04d8 00000201 user32!CallWindowProcAorW+0xab
0018f9e8 7305450e ffff09fd 001a04d8 00000201 user32!CallWindowProcW+0x1b
0018fa04 7305463d 001a04d8 00000201 00000001 comctl32!CallOriginalWndProc+0x1a
0018fa68 730545f1 03c99e00 001a04d8 00000201 comctl32!CallNextSubclassProc+0x3d
0018fa8c 7304fa37 001a04d8 00000201 00000001 comctl32!DefSubclassProc+0x46
0018faa8 7305463d 001a04d8 00000201 00000001 comctl32!TTSubclassProc+0x59
0018fb0c 730545f1 03c99e00 001a04d8 00000201 comctl32!CallNextSubclassProc+0x3d
0018fb30 7304fa37 001a04d8 00000201 00000001 comctl32!DefSubclassProc+0x46
0018fb4c 7305463d 001a04d8 00000201 00000001 comctl32!TTSubclassProc+0x59
0018fbb0 730546e1 03c99e00 001a04d8 00000201 comctl32!CallNextSubclassProc+0x3d
0018fc10 76c46238 001a04d8 00000201 00000001 comctl32!MasterSubclassProc+0x54
0018fc3c 76c468ea 7305469d 001a04d8 00000201 user32!InternalCallWinProc+0x23
0018fcb4 76c50ab0 00000000 7305469d 001a04d8 user32!UserCallWinProcCheckWow+0x109
0018fcec 76c57b0f ffff05b7 001a04d8 00000201 user32!CallWindowProcAorW+0xab
0018fd0c 006dd4ec ffff05b7 001a04d8 00000201 user32!CallWindowProcA+0x1b
0018fd58 76c468ea 006dd4c0 001a04d8 00000201 XYplorer+0x2dd4ec
0018fdd0 76c47d31 00000000 006dd4c0 001a04d8 user32!UserCallWinProcCheckWow+0x109
0018fe30 76c48112 006dd4c0 00000001 0018fe80 user32!DispatchMessageWorker+0x3bc
0018fe40 7294a6c8 0018fe58 ffffffff 02ab207c user32!DispatchMessageA+0xf
0018fe80 7294a63f ffffffff 02ab20a4 02ab0000 msvbvm60!_vbaStrToAnsi+0x2f1
0018fec4 7294a51d 02ab2174 ffffffff 00000c5c msvbvm60!_vbaStrToAnsi+0x268
0018fee0 7294a4e8 02ab20a0 02ab2174 ffffffff msvbvm60!_vbaStrToAnsi+0x146
0018ff04 72943644 ffffffff 00000000 00000000 msvbvm60!_vbaStrToAnsi+0x111
0018ff80 0040f2da 004102d4 76d43677 7efde000 msvbvm60!ThunRTMain+0xa0
0018ff94 77349d72 7efde000 75a7622a 00000000 XYplorer+0xf2da
0018ffd4 77349d45 0040f2d0 7efde000 00000000 ntdll!__RtlUserThreadStart+0x70
0018ffec 00000000 0040f2d0 7efde000 00000000 ntdll!_RtlUserThreadStart+0x1b
One now to something complete different: The version of my msvbvm6.dll is 6.0.98.15 from 2009-07-14. Is this the same version as you use?

admin
Site Admin
Posts: 49999
Joined: 22 May 2004 16:48
Location: Cologne, Win 8.1, Win 10
Contact:

Re: Constant Crashes

Post by admin »

ogroeger wrote:
admin wrote:Please find DisableSHChangeNotifyRegister in the INI and set it to 1:

Code: Select all

DisableSHChangeNotifyRegister=1
Still crashes?
Yes (and no). Still crashes, but the stack text had changed. But i don't know if these changes are relevant:

Code: Select all

STACK_TEXT:  
0018e420 72a10dcf c000008f 00000001 00000002 KERNELBASE!RaiseException+0x58
WARNING: Stack unwind information not available. Following frames may be wrong.
0018e440 72a0e228 0018e48c 800a01ae 0018e490 msvbvm60!EbGetHandleOfExecutingProject+0x22b3
0018e454 72a1939e 0018e46c 00000000 02c219b8 msvbvm60!rtcDoEvents+0x131
0018e490 72a1a2b6 80004002 02c219b8 004723d0 msvbvm60!TipInvokeMethod+0x4a8
0018e504 006eded4 03ce1450 0018e570 72a1a274 msvbvm60!_vbaHresultCheckObj+0x42
0018e5c0 00612646 03ce1450 0018e7b8 007c90a8 XYplorer+0x2eded4
0018e6b4 00612205 009beff8 0018e7b8 0018e6dc XYplorer+0x212646
0018e714 0060413b 009beff8 0018e7b8 0018e76c XYplorer+0x212205
0018e7d0 005ed73e 009beff8 03cdc5dc 0018e84c XYplorer+0x20413b
0018e894 0057279f 009beff8 03cd598c 0018f518 XYplorer+0x1ed73e
0018e8d8 00575353 009beff8 0018f4b8 0018f518 XYplorer+0x17279f
0018e920 76843ec3 009beff8 0018f4b8 0018f518 XYplorer+0x175353
0018e948 72a16ef5 009bfa1c 0000003c 00000004 oleaut32!DispCallFunc+0x165
0018f2a4 72a09a7b 009bfa1c 0042b290 6003010f msvbvm60!_vbaAptOffset+0x68b
0018f2e4 72a09c2c 009bfa1c 0000000a 00000008 msvbvm60!BASIC_DISPINTERFACE_GetTypeInfo+0x2aa
0018f314 72a11723 009bfa1c 0000000a 7295aea8 msvbvm60!EVENT_SINK_Invoke+0x50
0018f37c 72a48ba5 03c85408 0000000a 00000000 msvbvm60!EbGetHandleOfExecutingProject+0x2c07
0018f500 0067e8a7 03c85408 03c855e0 00000000 msvbvm60!_vbaRaiseEvent+0x16
0018f5f0 72991d33 03c85408 0018f7b4 0018f7bc XYplorer+0x27e8a7
0018f61c 72992034 004279c6 0018f6d8 0000000a msvbvm60!IID_IVbaHost+0x236f3
0018f634 72992159 03c858d8 0018f718 0018f6d8 msvbvm60!IID_IVbaHost+0x239f4
0018f73c 72992667 03b02dc4 02ace5b4 02ab2b88 msvbvm60!IID_IVbaHost+0x23b19
0018f760 729a04d7 03b02dc4 0000000d 0018f780 msvbvm60!IID_IVbaHost+0x24027
0018f7c0 7299d6b7 03b02dc4 0000000d 00000001 msvbvm60!IID_IVbaHost+0x31e97
0018f828 729f3941 02ab2b88 001a04d8 00000201 msvbvm60!IID_IVbaHost+0x2f077
0018f868 7299ce49 03b02dc4 001a04d8 00000201 msvbvm60!DllCanUnloadNow+0x13c8f
0018f890 7299f97d 00000000 001a04d8 00000201 msvbvm60!IID_IVbaHost+0x2e809
0018f8ec 76c46238 001a04d8 00000201 00000001 msvbvm60!IID_IVbaHost+0x3133d
0018f918 76c468ea 7299f74e 001a04d8 00000201 user32!InternalCallWinProc+0x23
0018f990 76c50ab0 00000000 7299f74e 001a04d8 user32!UserCallWinProcCheckWow+0x109
0018f9c8 76c50ad6 ffff09fd 001a04d8 00000201 user32!CallWindowProcAorW+0xab
0018f9e8 7305450e ffff09fd 001a04d8 00000201 user32!CallWindowProcW+0x1b
0018fa04 7305463d 001a04d8 00000201 00000001 comctl32!CallOriginalWndProc+0x1a
0018fa68 730545f1 03c99e00 001a04d8 00000201 comctl32!CallNextSubclassProc+0x3d
0018fa8c 7304fa37 001a04d8 00000201 00000001 comctl32!DefSubclassProc+0x46
0018faa8 7305463d 001a04d8 00000201 00000001 comctl32!TTSubclassProc+0x59
0018fb0c 730545f1 03c99e00 001a04d8 00000201 comctl32!CallNextSubclassProc+0x3d
0018fb30 7304fa37 001a04d8 00000201 00000001 comctl32!DefSubclassProc+0x46
0018fb4c 7305463d 001a04d8 00000201 00000001 comctl32!TTSubclassProc+0x59
0018fbb0 730546e1 03c99e00 001a04d8 00000201 comctl32!CallNextSubclassProc+0x3d
0018fc10 76c46238 001a04d8 00000201 00000001 comctl32!MasterSubclassProc+0x54
0018fc3c 76c468ea 7305469d 001a04d8 00000201 user32!InternalCallWinProc+0x23
0018fcb4 76c50ab0 00000000 7305469d 001a04d8 user32!UserCallWinProcCheckWow+0x109
0018fcec 76c57b0f ffff05b7 001a04d8 00000201 user32!CallWindowProcAorW+0xab
0018fd0c 006dd4ec ffff05b7 001a04d8 00000201 user32!CallWindowProcA+0x1b
0018fd58 76c468ea 006dd4c0 001a04d8 00000201 XYplorer+0x2dd4ec
0018fdd0 76c47d31 00000000 006dd4c0 001a04d8 user32!UserCallWinProcCheckWow+0x109
0018fe30 76c48112 006dd4c0 00000001 0018fe80 user32!DispatchMessageWorker+0x3bc
0018fe40 7294a6c8 0018fe58 ffffffff 02ab207c user32!DispatchMessageA+0xf
0018fe80 7294a63f ffffffff 02ab20a4 02ab0000 msvbvm60!_vbaStrToAnsi+0x2f1
0018fec4 7294a51d 02ab2174 ffffffff 00000c5c msvbvm60!_vbaStrToAnsi+0x268
0018fee0 7294a4e8 02ab20a0 02ab2174 ffffffff msvbvm60!_vbaStrToAnsi+0x146
0018ff04 72943644 ffffffff 00000000 00000000 msvbvm60!_vbaStrToAnsi+0x111
0018ff80 0040f2da 004102d4 76d43677 7efde000 msvbvm60!ThunRTMain+0xa0
0018ff94 77349d72 7efde000 75a7622a 00000000 XYplorer+0xf2da
0018ffd4 77349d45 0040f2d0 7efde000 00000000 ntdll!__RtlUserThreadStart+0x70
0018ffec 00000000 0040f2d0 7efde000 00000000 ntdll!_RtlUserThreadStart+0x1b
One now to something complete different: The version of my msvbvm6.dll is 6.0.98.15 from 2009-07-14. Is this the same version as you use?
Almost, I have 6.0.98.2.

The stack text does not tell me anything. :(
FAQ | XY News RSS | XY Twitter | Stay home! 🎸 Or wear a mask! 😷

xman
Posts: 133
Joined: 28 Nov 2009 22:57

Re: Constant Crashes

Post by xman »

I suggest you use OllyDbg and run XY in it. Then when XYplorer crashes, you can easily find where it crashes and from where was that crashed function called.

DeadSerious
Posts: 18
Joined: 05 Jan 2010 07:17

Re: Constant Crashes

Post by DeadSerious »

Well, I thought you had it licked, but it crashed once last night. Again, while I was using my photo cataloging software. I had turned off the previews, but apparently XY was still previewing through the shell. Still, only one crash in two days is better than what I experienced before.

I tried using Ollydbg, as suggested, but it made no sense to me...sorry.

admin
Site Admin
Posts: 49999
Joined: 22 May 2004 16:48
Location: Cologne, Win 8.1, Win 10
Contact:

Re: Constant Crashes

Post by admin »

DeadSerious wrote:Well, I thought you had it licked, but it crashed once last night. Again, while I was using my photo cataloging software. I had turned off the previews, but apparently XY was still previewing through the shell. Still, only one crash in two days is better than what I experienced before.

I tried using Ollydbg, as suggested, but it made no sense to me...sorry.
When you say "apparently XY was still previewing through the shell" you mean XY with AutoRefresh ON was looking at a folder where your photo cataloging software was active?
FAQ | XY News RSS | XY Twitter | Stay home! 🎸 Or wear a mask! 😷

DeadSerious
Posts: 18
Joined: 05 Jan 2010 07:17

Re: Constant Crashes

Post by DeadSerious »

admin wrote:
DeadSerious wrote:Well, I thought you had it licked, but it crashed once last night. Again, while I was using my photo cataloging software. I had turned off the previews, but apparently XY was still previewing through the shell. Still, only one crash in two days is better than what I experienced before.

I tried using Ollydbg, as suggested, but it made no sense to me...sorry.
When you say "apparently XY was still previewing through the shell" you mean XY with AutoRefresh ON was looking at a folder where your photo cataloging software was active?
I meant that I had de-selected all formats under options, but was still getting previews on the preview tab. I de-selected the "automatically show non-previewed..." boxes after that (assuming that now that they were not selected formats, the shell would now handle them). auto-refresh has been on the last couple of days.

On another note, I also removed some programs I hadn't been using, removed my video drivers and re-installed them, and did some other routine maintenance. So far, no more crashes (although I haven't been using it as much the last couple of days). I'm keeping my fingers crossed.

admin
Site Admin
Posts: 49999
Joined: 22 May 2004 16:48
Location: Cologne, Win 8.1, Win 10
Contact:

Re: Constant Crashes

Post by admin »

DeadSerious wrote:
admin wrote:
DeadSerious wrote:Well, I thought you had it licked, but it crashed once last night. Again, while I was using my photo cataloging software. I had turned off the previews, but apparently XY was still previewing through the shell. Still, only one crash in two days is better than what I experienced before.

I tried using Ollydbg, as suggested, but it made no sense to me...sorry.
When you say "apparently XY was still previewing through the shell" you mean XY with AutoRefresh ON was looking at a folder where your photo cataloging software was active?
I meant that I had de-selected all formats under options, but was still getting previews on the preview tab. I de-selected the "automatically show non-previewed..." boxes after that (assuming that now that they were not selected formats, the shell would now handle them). auto-refresh has been on the last couple of days.

On another note, I also removed some programs I hadn't been using, removed my video drivers and re-installed them, and did some other routine maintenance. So far, no more crashes (although I haven't been using it as much the last couple of days). I'm keeping my fingers crossed.
So you suspect the preview to be causing the crashes? Then you should be able to generate a crash by previewing certain file (whatever they are). Independently of auto-refresh or being in the background. Or is it the combination of preview + background?
Just some thoughts in case the crashes come back.
FAQ | XY News RSS | XY Twitter | Stay home! 🎸 Or wear a mask! 😷

DeadSerious
Posts: 18
Joined: 05 Jan 2010 07:17

Re: Constant Crashes

Post by DeadSerious »

admin wrote:
DeadSerious wrote:
admin wrote:
DeadSerious wrote:Well, I thought you had it licked, but it crashed once last night. Again, while I was using my photo cataloging software. I had turned off the previews, but apparently XY was still previewing through the shell. Still, only one crash in two days is better than what I experienced before.

I tried using Ollydbg, as suggested, but it made no sense to me...sorry.
When you say "apparently XY was still previewing through the shell" you mean XY with AutoRefresh ON was looking at a folder where your photo cataloging software was active?
I meant that I had de-selected all formats under options, but was still getting previews on the preview tab. I de-selected the "automatically show non-previewed..." boxes after that (assuming that now that they were not selected formats, the shell would now handle them). auto-refresh has been on the last couple of days.

On another note, I also removed some programs I hadn't been using, removed my video drivers and re-installed them, and did some other routine maintenance. So far, no more crashes (although I haven't been using it as much the last couple of days). I'm keeping my fingers crossed.
So you suspect the preview to be causing the crashes? Then you should be able to generate a crash by previewing certain file (whatever they are). Independently of auto-refresh or being in the background. Or is it the combination of preview + background?
Just some thoughts in case the crashes come back.
Honestly? I don't really know enough to make anything other than a guess. My guess is that it was a wonky codec that was acting up, and when I got rid of some of those programs, whatever it was went with them. That's assuming the crashes are over, though. I'm gonna give it a few more days before I relax. I wish now that I had written down the programs I uninstalled. I've been trying to do the same types of things with the same programs open to see if I can reproduce a crash.

j_c_hallgren
XY Blog Master
Posts: 5824
Joined: 02 Jan 2006 19:34
Location: So. Chatham MA/Clearwater FL
Contact:

Re: Constant Crashes

Post by j_c_hallgren »

DeadSerious wrote:Anyway, I'll keep trying. I only have 20 days left in my trial period, so I hope I can figure it out by then. And thanks for the continuing help!
As I think you have seen, we take crashes like this as serious things and I also believe you've noticed how Don and the rest of us work as quickly as possible to resolve them...we pride ourselves on rapid response as compared to other FM products so hope you'll take that into consideration when it comes to purchasing XY.
Still spending WAY TOO much time here! But it's such a pleasure helping XY be a treasure!
(XP on laptop with touchpad and thus NO mouse!) Using latest beta vers when possible.

DeadSerious
Posts: 18
Joined: 05 Jan 2010 07:17

Re: Constant Crashes

Post by DeadSerious »

j_c_hallgren wrote:
DeadSerious wrote:Anyway, I'll keep trying. I only have 20 days left in my trial period, so I hope I can figure it out by then. And thanks for the continuing help!
As I think you have seen, we take crashes like this as serious things and I also believe you've noticed how Don and the rest of us work as quickly as possible to resolve them...we pride ourselves on rapid response as compared to other FM products so hope you'll take that into consideration when it comes to purchasing XY.
Very true. Assuming everything continues to work, I'm very pleased with the product and almost certainly will purchase it. (BTW, no crashes today!)

Post Reply