debug help request

Hi,

I have a c:\debuglog.txt generated, and could use some help on the crash that was associated with it. The crash is not reproducable, so any advise on what to look for in the code for would be very much appreciated.

Thanks for your help!

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 [S:\gordon\shelley's files\user.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Comment: 'Dr. Watson generated MiniDump'
Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Wed Jun 27 10:51:48.000 2007 (GMT-4)
System Uptime: not available
Process Uptime: 0 days 0:29:57.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
...........................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(4e8.298): Access violation - code c0000005 (first/second chance not available)
eax=0000027c ebx=0012feb8 ecx=00d5f6f0 edx=0012f870 esi=00d5f6f0 edi=0012f966
eip=2fd58f7b esp=0012f864 ebp=0012fbf4 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000212
Unable to load image C:\Program Files\Gerber Technology\AccuMark V8\AccuMark\dbaccess.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for dbaccess.dll
*** ERROR: Module load completed but symbols could not be loaded for dbaccess.dll
dbaccess+0x18f7b:
2fd58f7b 8b08 mov ecx,dword ptr [eax] ds:0023:0000027c=????????
0:000> !analyze -v;r;kv;lmtn;.logclose;q
*** WARNING: Unable to verify checksum for wmedsrv.exe
*** ERROR: Module load completed but symbols could not be loaded for wmedsrv.exe
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


FAULTING_IP:
dbaccess+18f7b
2fd58f7b 8b08 mov ecx,dword ptr [eax]

EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
.exr ffffffffffffffff
ExceptionAddress: 2fd58f7b (dbaccess+0x00018f7b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0000027c
Attempt to read from address 0000027c

PROCESS_NAME: wmedsrv.exe

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

READ_ADDRESS: 0000027c

BUGCHECK_STR: ACCESS_VIOLATION

DEFAULT_BUCKET_ID: STACK_CORRUPTION

LAST_CONTROL_TRANSFER: from 0046ddf0 to 2fd58f7b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012fbf4 0046ddf0 0012fc48 0012feb8 004148d8 dbaccess+0x18f7b
0012fc00 004148d8 0012fc48 0012feb8 0012fda8 wmedsrv+0x6ddf0
0012ff18 00404aef 00408486 00152535 004782d0 wmedsrv+0x148d8
0012ff1c 00408486 00152535 004782d0 00400000 wmedsrv+0x4aef
00404aef 9090c300 90909090 90909090 b9575690 wmedsrv+0x8486
00404af3 90909090 90909090 b9575690 00000009 0x9090c300
00404af7 90909090 b9575690 00000009 47c100be 0x90909090
00404afb b9575690 00000009 47c100be 2c5ebf00 0x90909090
00404aff 00000000 47c100be 2c5ebf00 c7660048 0xb9575690


STACK_COMMAND: ~0s; .ecxr ; kb

FAULTING_THREAD: 00000298

PRIMARY_PROBLEM_CLASS: STACK_CORRUPTION

FOLLOWUP_IP:
dbaccess+18f7b
2fd58f7b 8b08 mov ecx,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dbaccess+18f7b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dbaccess

IMAGE_NAME: dbaccess.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 467c136f

FAILURE_BUCKET_ID: ACCESS_VIOLATION_dbaccess+18f7b

BUCKET_ID: ACCESS_VIOLATION_dbaccess+18f7b

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

eax=0000027c ebx=0012feb8 ecx=00d5f6f0 edx=0012f870 esi=00d5f6f0 edi=0012f966
eip=2fd58f7b esp=0012f864 ebp=0012fbf4 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000212
dbaccess+0x18f7b:
2fd58f7b 8b08 mov ecx,dword ptr [eax] ds:0023:0000027c=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0012fbf4 0046ddf0 0012fc48 0012feb8 004148d8 dbaccess+0x18f7b
0012fc00 004148d8 0012fc48 0012feb8 0012fda8 wmedsrv+0x6ddf0
0012ff18 00404aef 00408486 00152535 004782d0 wmedsrv+0x148d8
0012ff1c 00408486 00152535 004782d0 00400000 wmedsrv+0x4aef
00404aef 9090c300 90909090 90909090 b9575690 wmedsrv+0x8486
00404af3 90909090 90909090 b9575690 00000009 0x9090c300
00404af7 90909090 b9575690 00000009 47c100be 0x90909090
00404afb b9575690 00000009 47c100be 2c5ebf00 0x90909090
00404aff 00000000 47c100be 2c5ebf00 c7660048 0xb9575690
start end module name
00400000 004ae000 wmedsrv wmedsrv.exe Mon Jun 18 16:19:03 2007 (4676E8B7)
01180000 0118f000 sqloledb_1180000 sqloledb.rll Wed Aug 04 01:21:46 2004 (4110726A)
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)
11070000 11088000 gendb gendb.dll Wed May 30 13:33:12 2007 (465DB558)
15610000 1561a000 wlookup wlookup.dll Wed Jan 17 14:41:00 2007 (45AE7BCC)
19140000 19147000 kmlog kmlog.dll Wed Jan 17 14:10:24 2007 (45AE74A0)
20000000 20017000 odbcint odbcint.dll Wed Aug 04 03:57:25 2004 (411096E5)
21a60000 21a8e000 ccfiles ccfiles.dll Wed Jan 17 14:30:50 2007 (45AE796A)
23070000 23092000 plotter plotter.dll Wed Jan 17 14:15:05 2007 (45AE75B9)
263d0000 263e9000 baselng baselng.dll Wed Jan 17 14:06:08 2007 (45AE73A0)
2ca30000 2ca52000 prefdll prefdll.dll Wed Jan 17 14:48:16 2007 (45AE7D80)
2dc30000 2dc42000 ccdb ccdb.dll Wed Jan 17 14:06:23 2007 (45AE73AF)
2fd40000 2fdac000 dbaccess dbaccess.dll Fri Jun 22 14:22:39 2007 (467C136F)
3e120000 3e2a1000 grade grade.dll Wed Jan 17 14:28:50 2007 (45AE78F2)
4bd70000 4bd77000 dbnmpntw dbnmpntw.dll Wed Aug 04 03:56:13 2004 (4110969D)
4dd00000 4dd81000 sqloledb sqloledb.dll Wed Aug 04 03:59:04 2004 (41109748)
4ec50000 4ec6b000 automark automark.dll Wed Jan 17 14:49:18 2007 (45AE7DBE)
531e0000 532fa000 dbmgt dbmgt.dll Wed Jan 17 14:09:57 2007 (45AE7485)
5a2c0000 5a2d2000 webpdm webpdm.dll Fri Jun 22 11:18:56 2007 (467BE860)
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)
60e30000 60e47000 msdatl3 msdatl3.dll Wed Aug 04 03:57:49 2004 (411096FD)
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)
69e80000 69e8f000 filebrowse filebrowse.dll Wed Jan 17 14:41:13 2007 (45AE7BD9)
6d4f0000 6d50b000 dbnetlib dbnetlib.dll Wed Aug 04 03:56:12 2004 (4110969C)
6dae0000 6dae3000 CommonLngRes CommonLngRes.dll Wed Jan 17 14:06:35 2007 (45AE73BB)
6f170000 6f1bc000 filegbr filegbr.dll Wed Jan 17 14:41:32 2007 (45AE7BEC)
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)
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)
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)
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)
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)
767a0000 767b3000 ntdsapi ntdsapi.dll Wed Aug 04 03:56:57 2004 (411096C9)
767f0000 76817000 schannel schannel.dll Wed Apr 25 10:21:15 2007 (462F63DB)
769c0000 76a73000 userenv userenv.dll Wed Aug 04 03:56:41 2004 (411096B9)
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)
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)
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 Thu Mar 08 10:36:28 2007 (45F02D7C)
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 7c8f5000 kernel32 kernel32.dll Mon Apr 16 11:52:53 2007 (46239BD5)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 03:56:36 2004 (411096B4)
7c9c0000 7d1d5000 shell32 shell32.dll Tue Dec 19 16:52:11 2006 (45885F0B)
7df70000 7df92000 oledlg oledlg.dll Mon Oct 16 12:15:00 2006 (4533B004)
7e410000 7e4a0000 user32 user32.dll Thu Mar 08 10:36:28 2007 (45F02D7C)
Closing open log file c:\debuglog.txt

 

Hi, sfairbanks.

Coincidentally, I happened to read your Dec. 2006 thread earlier today (before reading this thread) while I was trying to learn more about BSOD dump analysis. Therefore, I feel I must post here in case it's a "sign ".


I do not claim to be a dump analysis expert. However, while we wait for more/better suggestions, here are my 2 cents.

There are many more references to the dbaccess module in your dump log (though I don't understand them).

According to this 4-page article, Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3 and all of page 4), it appears your BSOD problem might be caused by dbaccess.dll.

Perhaps you recently installed an update that might be causing issues and/or perhaps there is a patch available. Perhaps your recent update installation hiccuped and the dbaccess.dll file is corrupted. Perhaps rolling back to an earlier version of AccuMark will fix things for now.

You might find some helpful information about dbaccess.dll on Gerber Technology's web site about your AccuMark™ version 8 software. I guess the link for getting software updates/information is here. It appears one must be an existing customer with a login/password to access the software update/information section.

 

I don't get a BSOD, but I found a link that was really helpful yesterday and I'd like to share;

http://www.codeproject.com/debug/mapfile.asp

If you follow the instructions to create the .map file with /MAPINFO project options, the map file generated in conjunction with the c:\debuglog.txt will help you to locate the exact line of code that the crash occurred.

Not that this helped me much with my crash, since I traced it to CSession::StartTransaction(), but I thought it was cool anyway.

I think I'll pass on contacting Gerber Technology, since its me! Kind of funny but a little embarrasing

 

Thanks for you follow-up.

After reading your Dec. 27 thread, I thought I might be out of your league with my post. Your follow-up here confirmed it.

In your first post, you asked for "any advise on what to look for in the code" and I thought you were asking about the debuglog.txt "code ". The debug logs are certainly "codes" to me right now anyway. I hadn't realized you were asking about your program code.

Anyway, I'm glad you resolved your issue and posted a follow-up.


Thanks for the link to information about the MAP file program. I saved the link together with this thread for my tinkering next time I run into an application crash that creates a user.dmp file (which - knock on wood - hasn't happened in awhile for me).


I don't have a lot of experience with programming so I want to take advantage of this rare opportunity to get a little feedback from you (software developer) about my suggestion above.

• Apart from my erroneous "BSOD" reference, was my diagnosis and advice sound?
  • Was the problematic code located in dbaccess.dll?
  • Is wmedsrv.exe part of AccuMark?
  • If so, is wmedsrv.exe dependent upon the the integrity of dbaccess.dll for proper operation?

Most of the time, people seeking help in these forums simply want to make their computer behave properly and I certainly don't have access to the source code for most of the files identified in dump logs, much less understand the program code. We're also a bit short on dump log analysis experts around here. AFAIK, only one dump log analysis expert (cpc2004) has stopped in occasionally to help in recent months. Therefore, your additional feedback about my advice given above may help me tweak the way I offer suggestions in the future.

Thanks again for your informative follow-up. I hope this thread helps someone else who happens to come across this thread seeking help with an issue similar to your issue.

EDIT: BTW, thanks for confirming my suspicion my reference to a BSOD was incorrect. I don't often experience my own crashes so your feedback you gave in this regard is very valuable to me. I'll pay closer attention about whether a person's identified dump file is "user.dmp" or "memory.dmp ".

 

Hi mailman,

I would be happy give feedback! You say that most people who post questions just want to find out why their computer is acting strange and make it behave. Software developers know that its their code that's misbehaving and want to know why and where given crash data. Thats why what I found will be helpful for developers and I wanted to share.

Your advise for a non-developer was fine. When I posted my Dec thread I got a lot of advise that was geared toward users, not developers. For example, I was told to run a windows memory diagnostic tool. I did it just out of curiousity, and no one here could figure out why it was running on my ststem - for a very LONG time!

The problem did end up being in dbAccess, but where the crash was led me to believe that it's not obvious that its anything I've written. Which means I really haven't solved the crash, but it hasn't happened again, so who knows? It's in house testing for a particular customer.

wmedsrv is a background process thats run, Accumark is the foreground process and the software product. It just so happens that both proccesses rely on the integrity of dbAccess.

Thankfully, those BSOD's are something that users get, and there's a reason its called the 'Blue Screen of Death', a sign your computer is pretty sick. If I wrote code that caused these, I'd be out of a job

I'm not a dump log analyst expert either, crashes are something we'd like to prevent or fix in a more civilized way! But if a crash address is all we have to go on, it certainly does help to know enough to get by!

Let me know if you'd like more/other feedback.

 

Thanks! I think that about does it for me.

I'll modify my canned Network World reference to not include the dirty "BSOD" acronym. I'm sorry about improperly implying it applied to your software along with all that glaring bold/colored text. Hopefully, anyone who reads this thread won't stop at that post and have a skewed view of your product.

Thanks again for your kindness and helpful feedback. Your professionalism is certainly commendable (especially since you managed to stay out of the sparring that occurred in your Dec. 27 thread and kept the focus on your issue).


Steering this thread back to your current issue...

I hope a dump/debug log analysis expert can help this deserving software developer, sfairbanks, with the issue at hand.

Good luck!