Re: Bad Image Checksum comdlg32.dll
From: TerryW (prog_at_vbssys.com)
Date: 07/09/04
- Next message: KM: "Re: Netbios naming <informational only>"
- Previous message: Bob Floyd: "Re: Netbios naming <informational only>"
- In reply to: Slobodan Brcin \(eMVP\): "Re: Bad Image Checksum comdlg32.dll"
- Next in thread: Slobodan Brcin \(eMVP\): "Re: Bad Image Checksum comdlg32.dll"
- Reply: Slobodan Brcin \(eMVP\): "Re: Bad Image Checksum comdlg32.dll"
- Reply: KM: "Re: Bad Image Checksum comdlg32.dll"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 09 Jul 2004 12:58:00 -0500
Thanks for the help...
This is the first time i have attempted to debug a box. I haven't
downloaded symbols yet but I am getting a warning that states
WARNING: netbt overlaps ndisuio
WARNING: netbt_fbb6e000 overlaps netbt
*** Fatal System Error: 0xc0000221
(0xE140C858,0x0000000,0x0000000,0x0000000)
Bad image checksum...
The BSOD is inconsistent, happening 50-75% of the time.
Any help or comments would be appreciated.
TIA
Terry
On Fri, 9 Jul 2004 15:49:47 +0200, "Slobodan Brcin \(eMVP\)"
<sbrcin@ptt.yu> wrote:
>http://www.microsoft.com/whdc/devtools/debugging/default.mspx
>
>Regards,
>Slobodan
>
>"TerryW" <prog@vbssys.com> wrote in message news:p08te011fd29i2osvdpttcikvsqg9el71a@4ax.com...
>> On Wed, 7 Jul 2004 19:34:26 -0700, "KM" <konstmor@nospam_yahoo.com>
>> wrote:
>>
>> The issue occurs both on cd or over network.
>>
>> I don't know how to use KD? (Kernal Debugger?)
>>
>> I see the problem with or without EWF
>>
>> Thanks for your response,
>>
>> Could you tell me where I can find information on KD?
>>
>> TIA
>>
>> Terry
>>
>> >Terry,
>> >
>> >A couple of things which you may have already tried.
>> >
>> >Does the issue occur if you copy the new image files not over network? (e.g.
>> >over a CD).
>> >
>> >If the BSOD appears consistently, are you able to attach KD to the target to
>> >see what is going on while it crashes?
>> >
>> >Do you see BSODs if you disable EWF or remove it completely?
>> >Btw, how do you enable EWF? I suppose you do that after you deploy the
>> >image.
>> >
>> >My first thought was Q816654 but you mentioned you installed it already.
>> >
>> >KM
>> >
>> >> We have successfully built images before but this new release isn't
>> >> working so well. It regularly BSODs with bad image checksum on
>> >> various files comdlg32.dll other dlls... The two main differences
>> >> with the two builds is that the working one was deployed on a cd and
>> >> didn't include DotNet. The new one is deployed via the network and
>> >> contains DotNet. Both use ewf. If we are patient it will boot but I
>> >> would give it 50/50. If this is a problem with the operating system
>> >> XPE why doensn't it occur all of the time? If it is the hardware why
>> >> does it do it to all machines?
>> >>
>> >>
>> >> I have put autoChk, chkNTFS, chkDsk on the build since we have started
>> >> having problems but I don't think they are of any use with the ewf on
>> >> and they haven't seemed to help.
>> >>
>> >> To deploy via the net I use xcopy /e /g /h /k
>> >>
>> >> current service pack is 1
>> >> QFE Installed: Q811279_XPE_SP2_x86_ENU.exe ,
>> >> Q816654_XPE_SP2_x86_ENU.exe
>> >> Ntfs.sys is versioned 5.1.2600.1106
>> >>
>> >> Does anyone have any ideas?
>> >>
>> >> TIA
>> >> Terry
>> >
>>
>
- Next message: KM: "Re: Netbios naming <informational only>"
- Previous message: Bob Floyd: "Re: Netbios naming <informational only>"
- In reply to: Slobodan Brcin \(eMVP\): "Re: Bad Image Checksum comdlg32.dll"
- Next in thread: Slobodan Brcin \(eMVP\): "Re: Bad Image Checksum comdlg32.dll"
- Reply: Slobodan Brcin \(eMVP\): "Re: Bad Image Checksum comdlg32.dll"
- Reply: KM: "Re: Bad Image Checksum comdlg32.dll"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|