Crashes on Windows XP

Post by **watchmaker** » 31.03.2012 19:28:20

No crashes.

Post by **watchmaker** » 27.03.2012 22:38:59

I'll try this version tomorrow.

Post by **Patrick** » 27.03.2012 20:54:59

watchmaker wrote:Application error: dexpot.exe, v. 1.5.0.99, module user32.dll, v. 5.1.2600.2981, address 0x0000baad.

Ok. Can you confirm that the problem is fixed in build 1858?

Post by **watchmaker** » 26.03.2012 23:29:49

Application error: dexpot.exe, v. 1.5.0.99, module user32.dll, v. 5.1.2600.2981, address 0x0000baad.

0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 64 65 78 ure dex
0018: 70 6f 74 2e 65 78 65 20 pot.exe
0020: 31 2e 35 2e 30 2e 39 39 1.5.0.99
0028: 20 69 6e 20 75 73 65 72 in user
0030: 33 32 2e 64 6c 6c 20 35 32.dll 5
0038: 2e 31 2e 32 36 30 30 2e .1.2600.
0040: 32 39 38 31 20 61 74 20 2981 at
0048: 6f 66 66 73 65 74 20 30 offset 0
0050: 30 30 30 62 61 61 64 0d 000baad.
0058: 0a .

Post by **Patrick** » 26.03.2012 22:30:49

Maybe you have to turn on Windows error reporting. Or use Dr. Watson (Start > Run > drwtsn32.exe) to enable crash dump generation and then send in the .dmp file.

Post by **watchmaker** » 26.03.2012 10:49:37

No such events at all.

Post by **Patrick** » 25.03.2012 21:55:48

Look for an "Application Error" event, rather than "Application Popup".

Post by **watchmaker** » 25.03.2012 20:35:48

: event.JPG (33.78 KiB) Viewed 8545 times

And no more info.

Post by **Patrick** » 25.03.2012 19:07:33

Windows Event Viewer > Application.

Post by **watchmaker** » 25.03.2012 18:08:37

The same crash in wk3+dk2, with the same addresses. How to find the module?

Post by **Patrick** » 25.03.2012 17:58:15

Clippy! I think they finally killed him in Office 2007, so unfortunately I can't test this myself.

Post by **watchmaker** » 25.03.2012 17:51:30

Office Agent? The text-to-speech talking character thing?

The funny paper clip with eyes which displays tips and notifications.

: agent.bmp (32.87 KiB) Viewed 8557 times

Post by **Patrick** » 25.03.2012 17:45:53

The absolute address isn't really useful. I'd need faulting module and offset. Anyway, the crash has nothing to do with wk3. It's a Windows XP problem, that's already fixed in Dexpot 1.5.16. The fix will be in the next 1.6 beta as well.

watchmaker wrote:Sometimes Dexpot loses Office 2003 Agent (or makes it inaccessible) when placing two or more Word windows on different desktops.

Office Agent? The text-to-speech talking character thing?

Post by **watchmaker** » 25.03.2012 17:35:31

Sometimes Dexpot loses Office 2003 Agent (or makes it inaccessible) when placing two or more Word windows on different desktops. If I move the windows to Desktop 1, the Agent becomes accessible again.

Post by **watchmaker** » 25.03.2012 17:33:26

Instruction at 0x77d3baad tried to access memory at 0x0080a004. The same crash on wk2-ppp after using wk3.

PS. These addresses are from wk2-ppp, on wk3 they may be different.

Post by **Patrick** » 25.03.2012 16:59:15

According to my magic crystal ball, the crashes occur in user32.dll at offset 0x01948d. Correct?

Why are using the debug builds from this thread anyway? Do you have trouble with lost windows?

Post by **watchmaker** » 25.03.2012 16:49:21

Build 1805-WK3 crashes two or three times per hour. Reverted to WK2PPP.