2 identical systems, 1 with software problems [dump included]

admin note: I know it will be longer but the dump files are easier to look at if in normal text than as code - especially since our bug chasers all have large monitors. So I'm editing out the code switch.

I have two identical systems. Both have the same hardware, software, and BIOS versions. Whenever I try to burn a DVD with the second system, the DVD software crashes and creates a dump file. Both systems have the same processes running, and all processes are the same version.

The hard drives are swappable, so I swapped drives to confirm that it is not a hardware issue. The first system crashes when it uses the hard drive from the second system.

The systems each have an Intel RC440BX motherboard, Pentium II 450, 128 meg RAM, 40 gig HD, Iomega 100 Zip drive, Sony DRU510A DVD burner, Windows 2000 Service Pack 3, BIOS version P14 (both configured exactly the same).

The software that is crashing is Veritas RecordNow DX v4.60.0.0 (MyCD.EXE). It crashes as soon as I click on the disk copy wizard. Here is the debug log:

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\Documents and Settings\All Users\Documents\DrWatson\user.dmp]
User Dump File: Only application data is available

Windows 2000 Version 2195 UP Free x86 compatible
Product: WinNt
Debug session time: Thu Mar 3 16:22:28.662 2005 (GMT-8)
System Uptime: 0 days 0:06:03.352
Process Uptime: not available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINNT;C:\WINNT\system32;C:\WINNT\system32\drivers
.......................................
(264.2dc): Access violation - code c0000005 (!!! second chance !!!)
eax=00000000 ebx=77e89b18 ecx=0012e946 edx=00000001 esi=78025744 edi=015148b4
eip=00000000 esp=0012e7e0 ebp=0012e94c iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
00000000 ?? ???
0:000> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

***** OS symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify checksum for VxBlock.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VxBlock.dll -
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for cehelper.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for cehelper.dll -
*** ERROR: Module load completed but symbols could not be loaded for MyCD.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for MSVBVM60.DLL -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for USER32.dll -

FAULTING_IP:
+0
00000000 ?? ???

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

FAULTING_THREAD: 000002dc

DEFAULT_BUCKET_ID: APPLICATION_FAULT

PROCESS_NAME: MyCD.exe

MODULE_NAME: VxBlock

FAULTING_MODULE: 77f80000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP: 3e076662

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

READ_ADDRESS: 00000000

BUGCHECK_STR: ACCESS_VIOLATION

THREAD_ATTRIBUTES:
LAST_CONTROL_TRANSFER: from 01512676 to 00000000

STACK_TEXT:
0012e7dc 01512676 0017d045 0012e946 0012e945 0x0
WARNING: Stack unwind information not available. Following frames may be wrong.
0012e94c 100084f8 0017d045 0012e968 00000000 VxBlock!QueryCd+0x118
0012f980 00518709 01483dd4 0017d045 0012fb10 cehelper!DllUnregisterServer+0x6b67
0012f9e8 004e7649 0015a2a8 0012fb10 0012fac4 MyCD+0x118709
0012fb38 004e7393 00141200 0012fb7c 0012fbd0 MyCD+0xe7649
0012fbc4 6602aef0 00141200 0012fbe0 0041dcaf MyCD+0xe7393
0012fbd0 0041dcaf 001412cc 0041d0a8 0012fc2c MSVBVM60!BASIC_CLASS_Invoke+0xdfe
0012fbe0 6602aecd 0041dcaf 0012fc9c 00000002 MyCD+0x1dcaf
0012fc2c 66023162 0012fcdc 0012fc9c 00000002 MSVBVM60!BASIC_CLASS_Invoke+0xddb
0012fd00 66022ff1 01223d94 01221544 01206f78 MSVBVM60!EVENT_SINK_AddRef+0x5deb
0012fd24 6602acf1 01223d94 00000000 00000000 MSVBVM60!EVENT_SINK_AddRef+0x5c7a
0012fd3c 660213a8 01223d94 00020276 00000113 MSVBVM60!BASIC_CLASS_Invoke+0xbff
0012fd64 66020361 01223d94 00020276 00000113 MSVBVM60!EVENT_SINK_AddRef+0x4031
0012fdc0 77e11d0a 00020276 00000113 00020276 MSVBVM60!EVENT_SINK_AddRef+0x2fea
0012fde0 77e11bc8 660202b7 00020276 00000113 USER32!DispatchMessageW+0x26
0012fe6c 77e172b4 0012fe90 00000001 66014979 USER32!GetAppCompatFlags2+0x555
0012feb8 660148b2 ffffffff 0120374c 01200000 USER32!DispatchMessageA+0xb
0012fefc 66014790 0120381c ffffffff 00000264 MSVBVM60!_vbaInStr+0x2f0
6601a360 66010e00 6601178a 660d41d8 660d4203 MSVBVM60!_vbaInStr+0x1ce


FAILED_INSTRUCTION_ADDRESS:
+0
00000000 ?? ???

FOLLOWUP_IP:
VxBlock!QueryCd+118
01512676 660fbe45f9 movsx ax,byte ptr [ebp-0x7]

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: VxBlock!QueryCd+118

IMAGE_NAME: VxBlock.dll

STACK_COMMAND: ~0s ; kb

BUCKET_ID: WRONG_SYMBOLS

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

eax=00000000 ebx=77e89b18 ecx=0012e946 edx=00000001 esi=78025744 edi=015148b4
eip=00000000 esp=0012e7e0 ebp=0012e94c iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
00000000 ?? ???
ChildEBP RetAddr Args to Child
0012e7dc 01512676 0017d045 0012e946 0012e945 0x0
WARNING: Stack unwind information not available. Following frames may be wrong.
0012e94c 100084f8 0017d045 0012e968 00000000 VxBlock!QueryCd+0x118
0012f980 00518709 01483dd4 0017d045 0012fb10 cehelper!DllUnregisterServer+0x6b67
0012f9e8 004e7649 0015a2a8 0012fb10 0012fac4 MyCD+0x118709
0012fb38 004e7393 00141200 0012fb7c 0012fbd0 MyCD+0xe7649
0012fbc4 6602aef0 00141200 0012fbe0 0041dcaf MyCD+0xe7393
0012fbd0 0041dcaf 001412cc 0041d0a8 0012fc2c MSVBVM60!BASIC_CLASS_Invoke+0xdfe
0012fbe0 6602aecd 0041dcaf 0012fc9c 00000002 MyCD+0x1dcaf
0012fc2c 66023162 0012fcdc 0012fc9c 00000002 MSVBVM60!BASIC_CLASS_Invoke+0xddb
0012fd00 66022ff1 01223d94 01221544 01206f78 MSVBVM60!EVENT_SINK_AddRef+0x5deb
0012fd24 6602acf1 01223d94 00000000 00000000 MSVBVM60!EVENT_SINK_AddRef+0x5c7a
0012fd3c 660213a8 01223d94 00020276 00000113 MSVBVM60!BASIC_CLASS_Invoke+0xbff
0012fd64 66020361 01223d94 00020276 00000113 MSVBVM60!EVENT_SINK_AddRef+0x4031
0012fdc0 77e11d0a 00020276 00000113 00020276 MSVBVM60!EVENT_SINK_AddRef+0x2fea
0012fde0 77e11bc8 660202b7 00020276 00000113 USER32!DispatchMessageW+0x26
0012fe6c 77e172b4 0012fe90 00000001 66014979 USER32!GetAppCompatFlags2+0x555
0012feb8 660148b2 ffffffff 0120374c 01200000 USER32!DispatchMessageA+0xb
0012fefc 66014790 0120381c ffffffff 00000264 MSVBVM60!_vbaInStr+0x2f0
6601a360 66010e00 6601178a 660d41d8 660d4203 MSVBVM60!_vbaInStr+0x1ce
start end module name
00400000 00660000 MyCD MyCD.exe Fri Mar 14 18:34:41 2003 (3E729141)
01510000 01517000 VxBlock VxBlock.dll Mon Dec 23 11:39:14 2002 (3E076662)
019d0000 01a06000 vxdmdbtn vxdmdbtn.ocx Thu Jan 16 18:38:35 2003 (3E276CAB)
02900000 0290d000 UmLoader UmLoader.DLL Thu Feb 13 15:22:53 2003 (3E4C28CD)
02ac0000 02b0b000 vxdmdpb vxdmdpb.ocx Thu Jan 16 18:38:42 2003 (3E276CB2)
02b60000 02bc8000 PX PX.DLL Thu Feb 06 18:15:36 2003 (3E4316C8)
02be0000 02c23000 PXDRV PXDRV.DLL Fri Feb 21 12:25:27 2003 (3E568B37)
02c40000 02c63000 PXMAS PXMAS.DLL Thu Feb 06 18:14:41 2003 (3E431691)
02c80000 02cee000 PXWAVE PXWAVE.DLL Thu Feb 06 18:14:23 2003 (3E43167F)
02d60000 02d6b000 CDR4DLL CDR4DLL.DLL Fri Oct 04 14:59:59 1996 (325588DF)
10000000 10023000 cehelper cehelper.dll Fri Mar 14 18:33:44 2003 (3E729108)
277b0000 27850000 mscomct2 mscomct2.ocx Tue Mar 14 09:39:28 2000 (38CE7950)
66000000 66153000 MSVBVM60 MSVBVM60.DLL Fri May 26 23:40:03 2000 (392F6DC3)
695e0000 69609000 OLEPRO32 OLEPRO32.DLL Tue Jul 23 00:14:10 2002 (3D3D0242)
6a8f0000 6a910000 MSVFW32 MSVFW32.dll Tue Nov 30 01:33:38 1999 (384399F2)
6c370000 6c462000 MFC42 MFC42.DLL Tue Nov 30 01:33:16 1999 (384399DC)
74870000 74886000 AVIFIL32 AVIFIL32.dll Tue Nov 30 01:31:17 1999 (38439965)
749a0000 749c4000 asycfilt asycfilt.dll Tue Jul 23 00:13:32 2002 (3D3D021C)
759b0000 759b6000 LZ32 LZ32.DLL Tue Nov 30 01:30:58 1999 (38439952)
76620000 76630000 MPR MPR.DLL Tue Jul 23 00:14:00 2002 (3D3D0238)
76b30000 76b6d000 comdlg32 comdlg32.dll Tue Jul 23 00:13:20 2002 (3D3D0210)
770f0000 772ed000 msi msi.dll Fri Jul 12 15:21:09 2002 (3D2F5655)
77410000 77423000 MSACM32 MSACM32.dll Tue Nov 30 23:37:29 1999 (3844D039)
77570000 775a0000 WINMM WINMM.dll Tue Nov 30 23:37:28 1999 (3844D038)
77800000 7781e000 WINSPOOL WINSPOOL.DRV Tue Jul 23 00:13:17 2002 (3D3D020D)
77820000 77827000 VERSION VERSION.dll Tue Nov 30 23:37:27 1999 (3844D037)
779b0000 77a4b000 OLEAUT32 OLEAUT32.dll Tue Jul 23 00:13:16 2002 (3D3D020C)
77a50000 77b45000 ole32 ole32.dll Tue Jul 23 00:13:16 2002 (3D3D020C)
77b50000 77bd9000 COMCTL32 COMCTL32.DLL Tue Jul 23 00:13:16 2002 (3D3D020C)
77c70000 77cba000 SHLWAPI SHLWAPI.DLL Tue Jul 23 00:13:15 2002 (3D3D020B)
77d30000 77da1000 RPCRT4 RPCRT4.DLL Tue Jul 23 00:13:15 2002 (3D3D020B)
77db0000 77e0d000 ADVAPI32 ADVAPI32.dll Tue Jul 23 00:13:14 2002 (3D3D020A)
77e10000 77e75000 USER32 USER32.dll Tue Jul 23 00:13:14 2002 (3D3D020A)
77e80000 77f36000 KERNEL32 KERNEL32.dll Tue Jul 23 00:13:13 2002 (3D3D0209)
77f40000 77f7c000 GDI32 GDI32.DLL Tue Jul 23 00:13:13 2002 (3D3D0209)
77f80000 77ffb000 ntdll ntdll.dll Tue Jul 23 00:13:13 2002 (3D3D0209)
78000000 78046000 MSVCRT MSVCRT.dll Thu Sep 20 14:52:56 2001 (3BAA6538)
780c0000 78121000 MSVCP60 MSVCP60.dll Wed Jun 17 11:52:10 1998 (3588105A)
782f0000 78536000 SHELL32 SHELL32.dll Tue Jul 23 00:13:17 2002 (3D3D020D)
Closing open log file c:\debuglog.txt

 

Code:

0012e7dc 01512676 0017d045 0012e946 0012e945 0x0
0012e94c 100084f8 0017d045 0012e968 00000000 VxBlock!QueryCd+0x118
0012f980 00518709 01483dd4 0017d045 0012fb10 cehelper!DllUnregisterServer+0x6b67
0012f9e8 004e7649 0015a2a8 0012fb10 0012fac4 MyCD+0x118709
0012fb38 004e7393 00141200 0012fb7c 0012fbd0 MyCD+0xe7649
0012fbc4 6602aef0 00141200 0012fbe0 0041dcaf MyCD+0xe7393

This stack indicates the crash is the result of stack corruption. It is doing a function named 'QueryCD'. This is their code, we dont know how it works, but im going to go out on a limb and say its making a query to the CD. My guess is its interrogating the hardware drive itself to determine its capabilities or state. Since its only the one machine crashing, perhaps the hardware itself have some strange setting the software doesnt expect. Have you looked for an updated burner BIOS? Ill bet if you swap cddrives, you can reproduce the problem as well. If so, i'd say that one of the burners isnt compatible/broken/screwy and will not work with the software you are using. Ill note the crashing module is 3 years old, there may be an update availible from your vendor.

 

It's not a hardware issue.

Thanks for the response.

From my previous post:

So it is not a hardware issue.

All BIOS, software, and firmware versions are identical. I wrote down a complete list of all of the processes that are running. I compared the two systems. All processes running are the same, version included.

I don't post easy ones.

 

Another dump file related to the same problem.



I got the following dump file when selected "Eject" from the context menu for the burner drive. Hopefully it contains more clues.

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\Documents and Settings\All Users\Documents\DrWatson\user.dmp]
User Dump File: Only application data is available

Windows 2000 Version 2195 UP Free x86 compatible
Product: WinNt
Debug session time: Mon Mar 7 12:14:38.742 2005 (GMT-8)
System Uptime: 0 days 0:01:04.422
Process Uptime: not available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINNT;C:\WINNT\system32;C:\WINNT\system32\drivers
.................
(3f8.120): Access violation - code c0000005 (!!! second chance !!!)
eax=00000000 ebx=77e89b18 ecx=0012f5ee edx=00000001 esi=78025744 edi=008048b4
eip=00000000 esp=0012f488 ebp=0012f5f4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
00000000 ?? ???
0:000> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

***** OS symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify checksum for VxBlock.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VxBlock.dll -
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for TFSWCMD.EXE
*** ERROR: Module load completed but symbols could not be loaded for TFSWCMD.EXE
*** ERROR: Symbol file could not be found. Defaulted to export symbols for KERNEL32.dll -

FAULTING_IP:
+0
00000000 ?? ???

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

FAULTING_THREAD: 00000120

DEFAULT_BUCKET_ID: APPLICATION_FAULT

PROCESS_NAME: TFSWCMD.EXE

MODULE_NAME: VxBlock

FAULTING_MODULE: 77f80000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP: 3e076662

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

READ_ADDRESS: 00000000

BUGCHECK_STR: ACCESS_VIOLATION

THREAD_ATTRIBUTES:
LAST_CONTROL_TRANSFER: from 00802676 to 00000000

STACK_TEXT:
0012f484 00802676 00000045 0012f5ee 0012f5ed 0x0
WARNING: Stack unwind information not available. Following frames may be wrong.
0012f5f4 00409ff0 00000045 0012f714 0012fe6c VxBlock!QueryCd+0x118
0012fd48 00401cc5 00000045 00000001 018ada2c TFSWCMD+0x9ff0
0012fe58 0040848d 00000003 0012fe6c 00000000 TFSWCMD+0x1cc5
0012feec 0040840d 00000000 00000000 7ffdf000 TFSWCMD+0x848d
0012ff34 0040c7ae 00400000 00000000 0013310a TFSWCMD+0x840d
0012ffc0 77e9ca90 018ada2c 77f82b95 7ffdf000 TFSWCMD+0xc7ae
0012fff0 00000000 0040c6e0 00000000 000000c8 KERNEL32!CreateProcessW+0x15a6


FAILED_INSTRUCTION_ADDRESS:
+0
00000000 ?? ???

FOLLOWUP_IP:
VxBlock!QueryCd+118
00802676 660fbe45f9 movsx ax,byte ptr [ebp-0x7]

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: VxBlock!QueryCd+118

IMAGE_NAME: VxBlock.dll

STACK_COMMAND: ~0s ; kb

BUCKET_ID: WRONG_SYMBOLS

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

eax=00000000 ebx=77e89b18 ecx=0012f5ee edx=00000001 esi=78025744 edi=008048b4
eip=00000000 esp=0012f488 ebp=0012f5f4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
00000000 ?? ???
ChildEBP RetAddr Args to Child
0012f484 00802676 00000045 0012f5ee 0012f5ed 0x0
WARNING: Stack unwind information not available. Following frames may be wrong.
0012f5f4 00409ff0 00000045 0012f714 0012fe6c VxBlock!QueryCd+0x118
0012fd48 00401cc5 00000045 00000001 018ada2c TFSWCMD+0x9ff0
0012fe58 0040848d 00000003 0012fe6c 00000000 TFSWCMD+0x1cc5
0012feec 0040840d 00000000 00000000 7ffdf000 TFSWCMD+0x848d
0012ff34 0040c7ae 00400000 00000000 0013310a TFSWCMD+0x840d
0012ffc0 77e9ca90 018ada2c 77f82b95 7ffdf000 TFSWCMD+0xc7ae
0012fff0 00000000 0040c6e0 00000000 000000c8 KERNEL32!CreateProcessW+0x15a6
start end module name
00230000 0026a000 tfswcres tfswcres.dll Wed Mar 12 10:16:43 2003 (3E6F798B)
00400000 0043e000 TFSWCMD TFSWCMD.EXE Wed Mar 12 10:15:43 2003 (3E6F794F)
00800000 00807000 VxBlock VxBlock.dll Mon Dec 23 11:39:14 2002 (3E076662)
00c40000 00c4b000 CDR4DLL CDR4DLL.DLL Fri Oct 04 14:59:59 1996 (325588DF)
10000000 1000f000 tfswapi tfswapi.dll Wed Mar 12 10:15:11 2003 (3E6F792F)
779b0000 77a4b000 OLEAUT32 OLEAUT32.dll Tue Jul 23 00:13:16 2002 (3D3D020C)
77a50000 77b45000 ole32 ole32.dll Tue Jul 23 00:13:16 2002 (3D3D020C)
77b50000 77bd9000 COMCTL32 COMCTL32.DLL Tue Jul 23 00:13:16 2002 (3D3D020C)
77c70000 77cba000 SHLWAPI SHLWAPI.DLL Tue Jul 23 00:13:15 2002 (3D3D020B)
77d30000 77da1000 RPCRT4 RPCRT4.DLL Tue Jul 23 00:13:15 2002 (3D3D020B)
77db0000 77e0d000 ADVAPI32 ADVAPI32.dll Tue Jul 23 00:13:14 2002 (3D3D020A)
77e10000 77e75000 USER32 USER32.dll Tue Jul 23 00:13:14 2002 (3D3D020A)
77e80000 77f36000 KERNEL32 KERNEL32.dll Tue Jul 23 00:13:13 2002 (3D3D0209)
77f40000 77f7c000 GDI32 GDI32.DLL Tue Jul 23 00:13:13 2002 (3D3D0209)
77f80000 77ffb000 ntdll ntdll.dll Tue Jul 23 00:13:13 2002 (3D3D0209)
78000000 78046000 MSVCRT MSVCRT.dll Thu Sep 20 14:52:56 2001 (3BAA6538)
782f0000 78536000 SHELL32 SHELL32.dll Tue Jul 23 00:13:17 2002 (3D3D020D)
Closing open log file c:\debuglog.txt

 

This second dump confirms the phenomenon is as Joe said, VXBLOCK.DLL is crashing on this machine, and its pretty old. You'll need to contact Veritas for further support after looking for updates on thier web site. You should also check the bios for both the CD burner drive and the machines to make sure they are the latest, since it appears to be crashing in a function named QueryCD.

 

This is a mission critical system that has been working for years.

I cannot update the software as a bandaid approach. The system was working. I need to find what created the problem and resolve it. Updating the software may interfere with the mission critical software on the system. It is not your normal desktop PC. It is used in a lab environment. These are specialized systems that collect data.

Both PCs were originally configured the same and tested a couple of years ago. They should be identical. Somebody added or removed something on this one that caused the burner software to crash. Unfortunatly, I do not know what was added or removed.

I did just find a Microsoft DLL called CLBCATQ version 2000.02.3497.0000 that is running on the system that works. It is missing on the one that crashes. All other DLLs running are identical.

 

It is a violation of almost every EULA I've ever read to dissassemble commercial code for any purpose. Niether joe or I can crack open that dump and tell you why it crashed by reading thier code. Not that its hard to do, its just against the terms of the agreement. If contacting the vendor is not an option, the limits of what can be done with a debugger are now exhausted by us non-veritas employees.

Since thats not an option, and you don't think it has to do with any of the things suggested, I can only recommend you use some of the internet tools to do a regdiff and file comperision between the nodes and look for deltas. Try running a regmon and filemon (from sysinternals.com) and see if they expose any behavior you could use as a landmark (such as trying to open a file that doesn't exist).

 

I am already using Sysinternals.

I used Process Explorer to pick apart what I have already.

Veritas no longer supports this software. It is now supported by Sonic Solutions.

Thanks for the input so far. I will keep plugging away and post any other findings.

 

What are the CLB files.

What are the CLB files in the C:\WINNT\Registration directory? I noticed that one is listed in the list of DLLs loaded on the system that works.

 

thats the com+ registration database. i see no evidence that this software uses com.

 

Why would one load a CLB file, and not the other?

The system that works loads a CLB file and CLBCATQ.DLL. The one that fails does not. What causes these two files to load?

 

Could someone please answer my question...

I am still waiting for an answer.

 

The COM+ Catalog
http://msdn.microsoft.com/library/d...s/cossdk/htm/pgdeployingapplications_5cmf.asp

How to clean up a damaged COM+ catalog
http://support.microsoft.com/default.aspx?scid=kb;en-us;315296

Have you looked in :\WINDOWS\system32\Com\comexp.msc to see if you have the same related com objects registered? Have you run the regdiff or regmon recommended?

 

Thanks for answering.

I was actually asking this question as a post mortem. I fixed the problem by ghosting the backup image onto the machine. We needed the system for an important job, so I could not spend any more time figuring out how it got ******* up to begin with.

I am really now just curious as to what a CLB file is and what it is used for. I already read the Microsoft articles that you pointed out, but it still did not make any sense to me.

 

CLB files are just goo from the com+ system. They are dynamic. If you futz around with configs and new registrations, you can watch them get updated and replaced.