DUMP DATA, need help with obscure crash

I am new here. I am trying to find out why our application, running on a software tester's system, crashes that doesn't crash on other systems. She has Dr Watson, and has sent me the drwtsn32.log and user.dmp. When I generate the log using your guidelines, this is what I get in my c:\debuglog.txt. What else can I instruct her to do to get more information, and what else can I provide you to get assistance? Thanks!

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\AccumarkProject\accumark822\susanne\user.dmp]
Minidump does not have system info
Could not open dump file [C:\AccumarkProject\accumark822\susanne\user.dmp], HRESULT 0x80004005
"Unspecified error "

 

Tell the user to set System Properties, Startup and Recovery, Settings, to provide a large model dump file: http://support.microsoft.com/kb/314103

Remember too that the dump file can be in either of two locations, depending on the crash:

A critical program error occurs:
The DUMP file will be found in \Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

For BSOD errors the DUMP file will be found at C:\WINDOWS\Minidump\MEMORY.DMP (mini-model setting) or be found for large model settings at C:\MEMORY.DMP

Your particular results suggest that you used the critical program dump log, and that it was essentially empty. It is likely you want the MEMORY.DMP file instead, found in a different location.

 

OK, thanks! here is the generated dump data

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
User Mini Dump File with Full Memory: Only application data is available

Comment: 'Dr. Watson generated MiniDump'
Windows XP Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Wed Dec 27 15:54:33.000 2006 (GMT-5)
System Uptime: 0 days 6:29:33.000
Process Uptime: 0 days 0:01:58.000
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
.....................................................................................................................
Loading unloaded module list
.............
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(10e4.9ec): Access violation - code c0000005 (first/second chance not available)
eax=b5780009 ebx=00000003 ecx=b5780009 edx=b578000d esi=00000010 edi=0b66bef0
eip=3e235580 esp=0012ee94 ebp=0012eec4 iopl=0 nv up ei ng nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000286
*** WARNING: Unable to verify checksum for grade.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for grade.dll -
grade!CWptChain::AddSmoothNewPoints+0x3d0:
3e235580 8b4108 mov eax,dword ptr [ecx+8] ds:0023:b5780011=????????
0:000> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify checksum for sil2000.exe
*** ERROR: Module load completed but symbols could not be loaded for sil2000.exe
*** WARNING: Unable to verify checksum for diag.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for diag.dll -

FAULTING_IP:
grade!CWptChain::AddSmoothNewPoints+3d0
3e235580 8b4108 mov eax,dword ptr [ecx+8]

EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
.exr ffffffffffffffff
ExceptionAddress: 3e235580 (grade!CWptChain::AddSmoothNewPoints+0x000003d0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: b5780011
Attempt to read from address b5780011

DEFAULT_BUCKET_ID: APPLICATION_FAULT

PROCESS_NAME: sil2000.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

READ_ADDRESS: b5780011

BUGCHECK_STR: ACCESS_VIOLATION

LAST_CONTROL_TRANSFER: from 3e136642 to 3e235580

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012eec4 3e136642 0b66beec 00000010 00000000 grade!CWptChain::AddSmoothNewPoints+0x3d0
0012eee4 3e135e7b 00000003 00000008 0b641330 grade!P_PIECE:repareGradedWpts+0x5b2
0012ef34 3e13607f 00000008 00000008 0b641330 grade!P_POINT::SetupGradeArray+0x8bb
0012ef48 3e1360ef 00000008 00000008 00000008 grade!P_POINT::SetupGradeArray+0xabf
0012ef88 3e18bbe8 00000008 00000000 0b641330 grade!P_PIECE:repareGradedWpts+0x5f
0012efe8 3e13bcee 0b641440 0b641330 0074f15a grade!P_PIECE::ChangeNest+0x738
0012eff4 0074f15a 00000000 00000000 00000001 grade!P_PIECE:isplayNestBreaks+0x3e
0012f018 3e13cb9e 00000000 00000000 00000001 sil2000+0x34f15a
0012f05c 77c2c2e3 3e1368f5 0012f04c 00000000 grade!P_PIECE::ConvertGliPoints+0xae
0012f0a8 3e1b4735 000003e8 0b64bf20 00000000 msvcrt!free+0xc8
0012f0cc 7c9105c8 0b669628 0012f1a4 7c910551 grade!P_PIECE::ConvertSingleSize+0x465
0012f0d8 7c910551 00330748 7c91056d 0b669630 ntdll!RtlpFreeToHeapLookaside+0x22
0012f1a4 77c2c2de 00330000 00000040 77c2c2e3 ntdll!RtlFreeHeap+0x1e9
7c91056d c5ffffff ce7c93be ff7c93be 00ffffff msvcrt!free+0xc3
7c910575 ff7c93be 00ffffff 12000000 907c93be 0xc5ffffff
7c910579 00ffffff 12000000 907c93be 90909090 0xff7c93be
7c91057d 12000000 907c93be 90909090 8b55ff8b 0xffffff
7c910581 907c93be 90909090 8b55ff8b 08458bec 0x12000000
7c910585 90909090 8b55ff8b 08458bec 04408b66 0x907c93be
7c910589 8b55ff8b 08458bec 04408b66 0004c25d 0x90909090
7c91058d 08458bec 04408b66 0004c25d 90909090 0x8b55ff8b
7c910591 04408b66 0004c25d 90909090 55ff8b90 0x8458bec
7c910595 0004c25d 90909090 55ff8b90 8b56ec8b 0x4408b66
7c910599 90909090 55ff8b90 8b56ec8b 46ff0875 0x4c25d
7c91059d 55ff8b90 8b56ec8b 46ff0875 d9e85614 0x90909090
7c9105a1 8b56ec8b 46ff0875 d9e85614 66ffffff 0x55ff8b90
7c9105a5 46ff0875 d9e85614 66ffffff 0f08463b 0x8b56ec8b
7c9105a9 d9e85614 66ffffff 0f08463b 000a8e83 0x46ff0875
7c9105ad 66ffffff 0f08463b 000a8e83 0c558b00 0xd9e85614
7c9105b1 0f08463b 000a8e83 0c558b00 67e8ce8b 0x66ffffff
7c9105b5 000a8e83 0c558b00 67e8ce8b b0ffff29 0xf08463b
7c9105b9 0c558b00 67e8ce8b b0ffff29 c25d5e01 0xa8e83
7c9105bd 67e8ce8b b0ffff29 c25d5e01 90900008 0xc558b00
7c9105c1 b0ffff29 c25d5e01 90900008 68909090 0x67e8ce8b
7c9105c5 c25d5e01 90900008 68909090 00000204 0xb0ffff29
7c9105c9 90900008 68909090 00000204 9106f068 0xc25d5e01
7c9105cd 68909090 00000204 9106f068 e7dfe87c 0x90900008
7c9105d1 00000000 9106f068 e7dfe87c 5d8bffff 0x68909090


STACK_COMMAND: ~0s; .ecxr ; kb

FAULTING_THREAD: 000009ec

FOLLOWUP_IP:
grade!CWptChain::AddSmoothNewPoints+3d0
3e235580 8b4108 mov eax,dword ptr [ecx+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: grade!CWptChain::AddSmoothNewPoints+3d0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: grade

IMAGE_NAME: grade.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 458bd5bc

FAILURE_BUCKET_ID: ACCESS_VIOLATION_grade!CWptChain::AddSmoothNewPoints+3d0

BUCKET_ID: ACCESS_VIOLATION_grade!CWptChain::AddSmoothNewPoints+3d0

Followup: MachineOwner
---------

eax=b5780009 ebx=00000003 ecx=b5780009 edx=b578000d esi=00000010 edi=0b66bef0
eip=3e235580 esp=0012ee94 ebp=0012eec4 iopl=0 nv up ei ng nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000286
grade!CWptChain::AddSmoothNewPoints+0x3d0:
3e235580 8b4108 mov eax,dword ptr [ecx+8] ds:0023:b5780011=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0012eec4 3e136642 0b66beec 00000010 00000000 grade!CWptChain::AddSmoothNewPoints+0x3d0
0012eee4 3e135e7b 00000003 00000008 0b641330 grade!P_PIECE:repareGradedWpts+0x5b2
0012ef34 3e13607f 00000008 00000008 0b641330 grade!P_POINT::SetupGradeArray+0x8bb
0012ef48 3e1360ef 00000008 00000008 00000008 grade!P_POINT::SetupGradeArray+0xabf
0012ef88 3e18bbe8 00000008 00000000 0b641330 grade!P_PIECE:repareGradedWpts+0x5f
0012efe8 3e13bcee 0b641440 0b641330 0074f15a grade!P_PIECE::ChangeNest+0x738
0012eff4 0074f15a 00000000 00000000 00000001 grade!P_PIECE:isplayNestBreaks+0x3e
0012f018 3e13cb9e 00000000 00000000 00000001 sil2000+0x34f15a
0012f05c 77c2c2e3 3e1368f5 0012f04c 00000000 grade!P_PIECE::ConvertGliPoints+0xae
0012f0a8 3e1b4735 000003e8 0b64bf20 00000000 msvcrt!free+0xc8 (FPO: [Non-Fpo])
0012f0cc 7c9105c8 0b669628 0012f1a4 7c910551 grade!P_PIECE::ConvertSingleSize+0x465
0012f0d8 7c910551 00330748 7c91056d 0b669630 ntdll!RtlpFreeToHeapLookaside+0x22 (FPO: [Non-Fpo])
0012f1a4 77c2c2de 00330000 00000040 77c2c2e3 ntdll!RtlFreeHeap+0x1e9 (FPO: [Non-Fpo])
7c91056d c5ffffff ce7c93be ff7c93be 00ffffff msvcrt!free+0xc3 (FPO: [Non-Fpo])
7c91056d 00000000 ce7c93be ff7c93be 00ffffff 0xc5ffffff
start end module name
00400000 00be9000 sil2000 sil2000.exe Fri Dec 22 10:35:13 2006 (458BFB31)
01d50000 01d70000 glu32 glu32.dll Wed Aug 04 03:56:07 2004 (41109697)
09dc0000 0a086000 msi msi.dll Mon May 02 11:51:33 2005 (42764C85)
0ae20000 0ae2f000 sqloledb_ae20000 sqloledb.rll Wed Aug 04 01:21:46 2004 (4110726A)
0b000000 0b2c5000 xpsp2res xpsp2res.dll Wed Aug 04 03:56:41 2004 (411096B9)
0ffd0000 0fff8000 rsaenh rsaenh.dll Tue Jul 06 22:17:12 2004 (40EB5D28)
10000000 10165000 og80as og80as.dll Mon Apr 02 15:04:52 2001 (3AC8CD54)
11000000 1104a000 PdsPrefsDiag PdsPrefsDiag.ocx Fri Jan 03 16:14:54 2003 (3E15FD4E)
11070000 11087000 gendb gendb.dll Fri Dec 22 07:34:28 2006 (458BD0D4)
15610000 1561a000 wlookup wlookup.dll Fri Dec 22 08:07:13 2006 (458BD881)
174d0000 174e1000 diag diag.dll Fri Dec 22 07:33:43 2006 (458BD0A7)
19140000 19147000 kmlog kmlog.dll Fri Dec 22 07:36:51 2006 (458BD163)
20000000 20017000 odbcint odbcint.dll Wed Aug 04 03:57:25 2004 (411096E5)
202c0000 202d8000 Tiip_Convert Tiip_Convert.dll Fri Dec 22 08:23:18 2006 (458BDC46)
21a60000 21a8e000 ccfiles ccfiles.dll Fri Dec 22 07:57:26 2006 (458BD636)
21d70000 21d92000 MSMAPI32 MSMAPI32.OCX Thu Jun 18 13:48:36 1998 (358952F4)
23070000 23092000 plotter plotter.dll Fri Dec 22 07:41:34 2006 (458BD27E)
25b40000 25b7b000 Assyst_Convert Assyst_Convert.dll Fri Dec 22 08:10:51 2006 (458BD95B)
263d0000 263e9000 baselng baselng.dll Fri Dec 22 07:32:29 2006 (458BD05D)
2a650000 2a66e000 CopyModel CopyModel.dll Fri Dec 22 08:11:24 2006 (458BD97C)
2a870000 2a897000 AccuGrid AccuGrid.dll Fri Dec 22 07:30:30 2006 (458BCFE6)
2ca30000 2ca52000 prefdll prefdll.dll Fri Dec 22 08:14:25 2006 (458BDA31)
2dc30000 2dc42000 ccdb ccdb.dll Fri Dec 22 07:32:44 2006 (458BD06C)
2fd40000 2fda8000 dbaccess dbaccess.dll Thu Dec 21 10:49:51 2006 (458AAD1F)
37470000 374e0000 AccuMarkCreator AccuMarkCreator.dll Fri Dec 22 08:09:58 2006 (458BD926)
37510000 3759f000 Stpplot Stpplot.dll Fri Dec 22 09:00:22 2006 (458BE4F6)
381f0000 38210000 ApparelInterchange ApparelInterchange.dll Fri Dec 22 07:31:59 2006 (458BD03F)
3e120000 3e2a1000 grade grade.dll Fri Dec 22 07:55:24 2006 (458BD5BC)
3f2c0000 3f2d3000 Investronica_Convert Investronica_Convert.dll Fri Dec 22 08:12:48 2006 (458BD9D0)
45540000 4561c000 gfxcom gfxcom.dll Fri Dec 22 07:35:45 2006 (458BD121)
4dd00000 4dd81000 sqloledb sqloledb.dll Wed Aug 04 03:59:04 2004 (41109748)
531e0000 532fa000 dbmgt dbmgt.dll Fri Dec 22 07:36:23 2006 (458BD147)
54510000 54516000 hpgl hpgl.dll Fri Dec 22 07:36:36 2006 (458BD154)
5a2c0000 5a2d2000 webpdm webpdm.dll Wed Dec 27 14:06:57 2006 (4592C451)
5ad70000 5ada8000 uxtheme uxtheme.dll Wed Aug 04 03:56:43 2004 (411096BB)
5b860000 5b8b4000 netapi32 netapi32.dll Thu Aug 17 08:28:27 2006 (44E460EB)
5d090000 5d12a000 comctl32 comctl32.dll Fri Aug 25 11:45:58 2006 (44EF1B36)
5dca0000 5dce5000 iertutil iertutil.dll Tue Oct 17 15:57:14 2006 (4535359A)
5ed00000 5edcc000 opengl32 opengl32.dll Wed Aug 04 03:57:44 2004 (411096F8)
5edd0000 5ede7000 olepro32 olepro32.dll Wed Aug 04 03:57:43 2004 (411096F7)
605d0000 605d9000 mslbui mslbui.dll Wed Aug 04 03:58:39 2004 (4110972F)
60e30000 60e47000 msdatl3 msdatl3.dll Wed Aug 04 03:57:49 2004 (411096FD)
61410000 61534000 urlmon urlmon.dll Wed Nov 08 00:03:34 2006 (45516526)
66000000 66152000 msvbvm60 msvbvm60.dll Mon Feb 23 23:15:40 2004 (403ACFEC)
662b0000 66308000 hnetcfg hnetcfg.dll Wed Aug 04 03:56:16 2004 (411096A0)
68100000 68124000 dssenh dssenh.dll Fri May 14 21:06:23 2004 (40A56D0F)
68ab0000 68b32000 Lectra_Convert Lectra_Convert.dll Fri Dec 22 08:13:16 2006 (458BD9EC)
69240000 692bf000 DXFToAIParser DXFToAIParser.dll Fri Dec 22 08:12:16 2006 (458BD9B0)
69e80000 69e8f000 filebrowse filebrowse.dll Fri Dec 22 08:07:25 2006 (458BD88D)
6d4f0000 6d50b000 dbnetlib dbnetlib.dll Wed Aug 04 03:56:12 2004 (4110969C)
6dae0000 6dae3000 CommonLngRes CommonLngRes.dll Fri Dec 22 07:32:56 2006 (458BD078)
6ec70000 6ecb4000 DXF_Convert DXF_Convert.dll Fri Dec 22 08:12:36 2006 (458BD9C4)
6f170000 6f1bc000 filegbr filegbr.dll Fri Dec 22 08:07:45 2006 (458BD8A1)
71a50000 71a8f000 mswsock mswsock.dll Wed Aug 04 03:59:20 2004 (41109758)
71a90000 71a98000 wshtcpip wshtcpip.dll Wed Aug 04 03:57:49 2004 (411096FD)
71aa0000 71aa8000 ws2help ws2help.dll Wed Aug 04 03:57:39 2004 (411096F3)
71ab0000 71ac7000 ws2_32 ws2_32.dll Wed Aug 04 03:57:38 2004 (411096F2)
71ad0000 71ad9000 wsock32 wsock32.dll Wed Aug 04 03:57:51 2004 (411096FF)
71b20000 71b32000 mpr mpr.dll Wed Aug 04 03:56:46 2004 (411096BE)
71bf0000 71c03000 samlib samlib.dll Wed Aug 04 03:56:29 2004 (411096AD)
71c10000 71c1e000 ntlanman ntlanman.dll Wed Aug 04 03:57:00 2004 (411096CC)
71c80000 71c87000 netrap netrap.dll Wed Aug 04 03:56:35 2004 (411096B3)
71c90000 71cd0000 netui1 netui1.dll Wed Aug 04 03:56:39 2004 (411096B7)
71cd0000 71ce7000 netui0 netui0.dll Wed Aug 04 03:56:38 2004 (411096B6)
71f80000 71f84000 security security.dll Wed Aug 04 03:56:50 2004 (411096C2)
73160000 731d7000 oledb32 oledb32.dll Wed Aug 04 03:57:40 2004 (411096F4)
735a0000 735c5000 scrrun scrrun.dll Wed Aug 04 03:56:46 2004 (411096BE)
73760000 737a9000 ddraw ddraw.dll Wed Aug 04 03:56:16 2004 (411096A0)
73bc0000 73bc6000 dciman32 dciman32.dll Wed Aug 04 03:56:15 2004 (4110969F)
73dd0000 73ece000 Mfc42 Mfc42.dll Wed Aug 04 03:56:21 2004 (411096A5)
74320000 7435d000 odbc32 odbc32.dll Wed Aug 04 03:57:17 2004 (411096DD)
74720000 7476b000 MSCTF MSCTF.dll Wed Aug 04 03:57:30 2004 (411096EA)
74d30000 74d50000 oledlg oledlg.dll Sat Aug 18 01:33:18 2001 (3B7DFE1E)
75350000 75361000 oledb32r oledb32r.dll Wed Aug 04 03:57:41 2004 (411096F5)
755c0000 755ee000 MSCTFIME MSCTFIME.IME Wed Aug 04 03:57:31 2004 (411096EB)
75e90000 75f40000 sxs sxs.dll Thu Oct 19 09:56:28 2006 (4537840C)
75f60000 75f67000 drprov drprov.dll Wed Aug 04 03:57:02 2004 (411096CE)
75f70000 75f79000 davclnt davclnt.dll Wed Aug 04 03:56:08 2004 (41109698)
76080000 760e5000 Msvcp60 Msvcp60.dll Wed Aug 04 03:59:13 2004 (41109751)
76390000 763ad000 imm32 imm32.dll Wed Aug 04 03:56:30 2004 (411096AE)
763b0000 763f9000 comdlg32 comdlg32.dll Wed Aug 04 03:56:32 2004 (411096B0)
765b0000 765d5000 msdart msdart.dll Wed Aug 04 03:57:45 2004 (411096F9)
76600000 7661d000 cscdll cscdll.dll Wed Aug 04 03:56:07 2004 (41109697)
76780000 76789000 shfolder shfolder.dll Wed Aug 04 03:56:40 2004 (411096B8)
767a0000 767b3000 ntdsapi ntdsapi.dll Wed Aug 04 03:56:57 2004 (411096C9)
767f0000 76817000 schannel schannel.dll Wed Aug 04 03:56:39 2004 (411096B7)
76980000 76988000 linkinfo linkinfo.dll Wed Aug 31 21:41:53 2005 (43165C61)
76990000 769b5000 ntshrui ntshrui.dll Wed Aug 04 03:57:09 2004 (411096D5)
769c0000 76a73000 userenv userenv.dll Wed Aug 04 03:56:41 2004 (411096B9)
76b20000 76b31000 atl atl.dll Wed Aug 04 03:56:55 2004 (411096C7)
76d60000 76d79000 iphlpapi iphlpapi.dll Fri May 19 08:59:41 2006 (446DC13D)
76f20000 76f47000 dnsapi dnsapi.dll Mon Jun 26 13:37:10 2006 (44A01B46)
76f60000 76f8c000 wldap32 wldap32.dll Wed Aug 04 03:56:43 2004 (411096BB)
76fb0000 76fb8000 winrnr winrnr.dll Wed Aug 04 03:56:35 2004 (411096B3)
76fc0000 76fc6000 rasadhlp rasadhlp.dll Mon Jun 26 13:37:10 2006 (44A01B46)
76fd0000 7704f000 clbcatq clbcatq.dll Tue Jul 26 00:39:44 2005 (42E5BE90)
77050000 77115000 comres comres.dll Wed Aug 04 03:56:36 2004 (411096B4)
77120000 771ac000 oleaut32 oleaut32.dll Wed Aug 04 03:57:39 2004 (411096F3)
773d0000 774d3000 comctl32_773d0000 comctl32.dll Fri Aug 25 11:45:55 2006 (44EF1B33)
774e0000 7761d000 ole32 ole32.dll Tue Jul 26 00:39:47 2005 (42E5BE93)
77920000 77a13000 setupapi setupapi.dll Wed Aug 04 03:56:32 2004 (411096B0)
77a20000 77a74000 cscui cscui.dll Wed Aug 04 03:56:08 2004 (41109698)
77a80000 77b14000 crypt32 crypt32.dll Wed Aug 04 03:56:01 2004 (41109691)
77b20000 77b32000 msasn1 msasn1.dll Wed Aug 04 03:57:23 2004 (411096E3)
77b40000 77b62000 apphelp apphelp.dll Wed Aug 04 03:56:36 2004 (411096B4)
77c00000 77c08000 version version.dll Wed Aug 04 03:56:39 2004 (411096B7)
77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 03:59:14 2004 (41109752)
77c70000 77c93000 msv1_0 msv1_0.dll Wed Aug 04 03:59:11 2004 (4110974F)
77d40000 77dd0000 user32 user32.dll Wed Mar 02 13:09:29 2005 (42260159)
77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 03:56:23 2004 (411096A7)
77e70000 77f01000 rpcrt4 rpcrt4.dll Wed Aug 04 03:56:30 2004 (411096AE)
77f10000 77f57000 gdi32 gdi32.dll Wed Dec 28 21:54:35 2005 (43B34FEB)
77f60000 77fd6000 shlwapi shlwapi.dll Thu Sep 14 04:31:29 2006 (45091361)
77fe0000 77ff1000 secur32 secur32.dll Wed Aug 04 03:56:49 2004 (411096C1)
7c800000 7c8f4000 kernel32 kernel32.dll Wed Jul 05 06:55:00 2006 (44AB9A84)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 03:56:36 2004 (411096B4)
7c9c0000 7d1d5000 shell32 shell32.dll Thu Jul 13 09:33:24 2006 (44B64BA4)

Unloaded modules:
37000000 37013000 EntApi.dll
Timestamp: Mon Aug 08 14:26:18 2005 (42F7A3CA)
Checksum: 00000000
76bf0000 76bfb000 PSAPI.DLL
Timestamp: Wed Aug 04 03:56:58 2004 (411096CA)
Checksum: 0000A29B
74e30000 74e9c000 RichEd20.dll
Timestamp: Wed Aug 04 03:56:28 2004 (411096AC)
Checksum: 000765F3
75f80000 7607d000 browseui.dll
Timestamp: Thu Sep 14 04:31:25 2006 (4509135D)
Checksum: 00104A04
77760000 778d0000 shdocvw.dll
Timestamp: Mon Sep 04 02:12:56 2006 (44FBC3E8)
Checksum: 00171D7B
754d0000 75550000 CRYPTUI.dll
Timestamp: Wed Aug 04 03:56:06 2004 (41109696)
Checksum: 0008752B
771b0000 7727e000 WININET.dll
Timestamp: Wed Nov 08 00:03:34 2006 (45516526)
Checksum: 000C94A4
0a9a0000 0a9a9000 Normaliz.dll
Timestamp: Thu Jun 29 11:05:42 2006 (44A3EC46)
Checksum: 00010188
76c30000 76c5e000 WINTRUST.dll
Timestamp: Wed Aug 04 03:56:41 2004 (411096B9)
Checksum: 0003069E
76c90000 76cb8000 IMAGEHLP.dll
Timestamp: Wed Aug 04 03:56:25 2004 (411096A9)
Checksum: 0002E238
69450000 69466000 faultrep.dll
Timestamp: Wed Aug 04 03:56:05 2004 (41109695)
Checksum: 000148FF
76f50000 76f58000 WTSAPI32.dll
Timestamp: Wed Aug 04 03:57:55 2004 (41109703)
Checksum: 00008C06
76360000 76370000 WINSTA.dll
Timestamp: Wed Aug 04 03:56:40 2004 (411096B8)
Checksum: 00014D19
Closing open log file c:\debuglog.txt

 

What medium are you installing from here?

If a CD or DVD is it the same one that installed to the other machine.

What I see here is curupted install files.

Either the media is damaged or the CD/DVD reader is weak.

More possible if a burnt CDR as opposed to a pressed factory disk.

You should try this same install on another XP computer with this same media.

If it does install that rules out a bad CD/DVD disk, but not the possibility that the other computer has a week CD/DVD drive.

To test that copy it the Install CD to a folder on the good computer (if on a network) then share the folder and install from there. Or even share the CD.

Run a Lens cleaner on the CD/DVD Drive.

Get back to us.

Mike

 

It would help to have some additional logs. The processor points through it pointer DS to a nonsensical place when it crashes:

grade!CWptChain::AddSmoothNewPoints+0x3d0:
3e235580 8b4108 mov eax,dword ptr [ecx+8] ds:0023:b5780011=????????
ChildEBP RetAddr Args to Child


There is nothing there for it to move a stored value. And, it is clearly an area of memory reserved.

If you want to avoid the tedium of additional log postings, at least start with a test of the RAM on this machine. I suspect you have a case where a bit was flipped:

There are several ways to do this.
See the comments by "mailman" and "cpc2004" at points #10 and #12 in this recent discussion for ideas: http://www.windowsbbs.com/showthread.php?t=59942

 

Yep

Would give similar output.

Has this machine had any other problems. BSOD's, freezes or reboots?

Problems running other programs.

Mike

 

To answer the questions posed above...

1. We are installing from a network, so any media related devices in question (CD, DVD, drives, etc) can be ruled out.

2. What additional logs can I post that would be helpful? I don't mind the tedium of additional log postings, I'm just happy to be getting the help!

3. This is not a RAM related problem to a particular machine. This problem occurs on other machines as well, BSOD's, freezes or reboots are not related either.

It is a software problem that occurs when doing a Save. This is a large graphical application, and ONLY when it is configured to output data to a SQL Server, only in certain cases that I cannot seem to pinpoint, the software crash will occur in different places that are completely unrelated to SQL server.

The generated Dr. Watson logs show that it crashes in different places each time. For example, several crashes in a row resulted in FAULTS occuring in (function: ntdll!wcsncpy), then next in (function: <nosymbols>).
Sometimes it will crash in the graphical code, (grade!P_POINT__ReplaceRefInNotches), (grade!CWptChain::AddSmoothNewPoints) or (function: MFC42!Ordinal2761), other times it crashes in the main application (function: sil2000).

What is this telling me?

Thanks for your help.

 

There you go now we have some specific info.

Answer these to further help us help you.

Does the Developer of this program have specified memory and disk space requirements.


Number one below is the most important of all.
1. Does this program run perfectly on any computer over a period of time?

2. If so what is the main diffferences between the systems?

3. Does it run OK on a machine without SQL?

4. Are any of the computers SERVERS?

5. Have you increased the Virtual memory (PageFile) to allow for these huge files (what is huge to you)? If not check the virtual memory settings!

6. Are these computers TOTALLY up to date with Winupdate?

7. Does this program cleanup after itsself? IE after running for some time is it filling the disk or leaving huge temp files?

If so try a temp clean a couple of times a day for a while to see if this is an issue.

Another test is to try it with only minimal other services running. Even turning off the Firewall and Virus scanner if nessesary.

Ball is now in your park!

Mike

 

Just my 2 cents, but I would double check with another antivirus and antispyware scanner. Recently I've seen quite a few crashes caused by virus/spyware activity.

 

Thanks John

Thats what we are all about here getting everyones 2 cents

Then tie them all togather.

That is why I told him to run without the Firewall and even the virus scanner for a while.

They are probably running Norton or Mcafee and both are hard to even uninstall much less disable temorairly.

Mike

 

Please have a RAM test done as discussed earlier.

One of the reasons for asking for additonal DUMP analyses was to see if the instruction pointer was in a different place each time it crashed. From your report it was.

This rules out, at least generally, a program error. It does however strongly rule-in an undedected issue with the RAM on the user machine -- failing, poorly configured or mismatched RAM.

Have them download and use an extended 'T' test on the problem machine(s) the Microsoft OCA memory tester: http://oca.microsoft.com/en/windiag.asp

If the address had not moved around as you describe, a program error would be a more likely explanation. But we would have to see the dumps.

From all indications there is a RAM problem on one or more of the computers at this site. It is not unusual to see clusters like this, when machines are often bought and installed in clumps.

While malware can do odd things, it is unlikely malware would cause the machine to throw this particular class of exceptions.

 

Yes I agree

Although the multiple computers lessens RAM as the root cause it definately needs to be ruled out.

Some of the logs can also be programmer errors.

But that also leads me to ask another question that might point to RAM issues.

Do any of the computers we are dealing with here have other problems BSOD's, freezes, reboots etc? When not running this particular software package?

An additional thing that can be done here is to clear the event logs, then run the program untill it fails and recheck the event logs.

Another thing! Is there 1 specfic thing you can do while running this program that always causes an error?

If so the for sure clear the event logs, cause the program to fail and immediatly check and post the logs to us.


Mike

 

There is nothing unusual having a batch of machines with the same hardware issues; this is actually quite common.

It is typical for a corporate site to purchase 1,000--10,000 identical computers in a single purchase order. Even much smaller sites tend to buy in batches.

This makes them prone to batch run issues -- a bad batch of RAM -- for example, can end up in 10,000 machines at one site.

 

I am actually the developer, and I have finally been able to reproduce the crash on my system. I will now do the RAM test you suggested, as well as the other suggestions posted here. Here are some answers your previous questions...

Does the Developer of this program have specified memory and disk space requirements.
Yes - I found them in the release notes, Hard disk capacity -230 MB free space, Memory - 256 MB minimum

Number one below is the most important of all.
1. Does this program run perfectly on any computer over a period of time?
yes!

2. If so what is the main differences between the systems?
we're all on Windows XP professional

3. Does it run OK on a machine without SQL?
YES! I really think it has to do with SQL space limitations. Changing the SQL server and database has a temporary effect on how reproducable and repeatable the crash is.

4. Are any of the computers SERVERS?
no

5. Have you increased the Virtual memory (PageFile) to allow for these huge files (what is huge to you)? If not check the virtual memory settings!
I don't think there are any huge files that we're dealing with.

6. Are these computers TOTALLY up to date with Winupdate?
yes

7. Does this program cleanup after itsself? IE after running for some time is it filling the disk or leaving huge temp files?
yes, no huge files left behind

If so try a temp clean a couple of times a day for a while to see if this is an issue.

Another test is to try it with only minimal other services running. Even turning off the Firewall and Virus scanner if nessesary.
could give this a try, no internet connections are involved here at all

Ball is now in your park!

Mike

 

Yes that is true.

Don't I know it!

I have been hit with it once or twice in my past 27 years as a Sr. Systems Analyst and Consultant!

But who said that is the case here.

What about it sfairbanks? Are the computers identical, from the same batch or close to it?

Mike

 

Ahh sfairbanks we were posting at the same time.

That helps.

What about the questions in my last 2 posts?

And what is the one thing you can do to cause the error.

And to be clear is this error doable on a cpu with and without SQL!

Mike

 

It uses SQL, so suggesting it be run without it is nonsensical.

 

sfairbanks this message is not really related to your thread just us boys
pe?ing on fire hydrants and tree trunks. Having a little fun!!

So just laugh with us OK! But I am not going to play any more on your thread. Serious from now on "promise ".

Bill please don't use those big fancy words, had to look it up

"nonsensical "
Having no inteligible meaning
Completely devoid of Wisdom or good sense

Besides it is an adjective. You know I don't do good with Adjectives!!!

I bet you talk fancy like that all the time!


Well I never heard him say it uses SQL only that it ran on a machine that had SQL installed. In fact he intimated it ran on non SQL computers.

That might mean you are jumping to conclusions. Dang, see there I had to go look up that word.

His answer to one of my questions:

Even if it uses SQL or not, if does run on a non SQL machine totally without problems it just confirms what sfairbanks and I both are starting to realize, is that SQL is now what we need to look at!

Mike

 

Good morning sfairbanks

Some time ago I had a consult with an SQL problem that turned out to be a problem with the version of Net Framework or having both versions 1 and 2 installed on the SQL server.

I just don't remeber the details.

I actually think I removed version 2.0 (actually removed both and reinstalled only one) but don't remember. There was Microsoft documentation (a known issue) on this also.

Older versions of Net Framework are kept for compatability.

I have a busy morning but later today I will look at my records and do some online research and get back to you.

So you may want to get started by looking up this issue.

Since then there have been updates and patches for both versions of Net Framework and an entirely new release Ver. 3.0

Net Framework is not too hard to uninstall but I would research "Uninstalling Net Framework" if both are installed.

You may want to uninstall all versions of Net Framework and (I would go back with only Ver 3 first) if that didn't work then back to ver 1 then ver 2.

Good luck,
Mike