Re: Determine cause of bugcheck

From: Peter 'EPLAN' LANGSTOEGER (peter_at_langstoeger.at)
Date: 11/12/05 

Date: 12 Nov 2005 16:14:40 +0100

In article <1131804685.569369.296080@o13g2000cwo.googlegroups.com>, "Thorsten Jens" <thojens@gmx.de> writes:
>Peter 'EPLAN' LANGSTOEGER wrote:
>> In article <1131798831.593906.113680@g44g2000cwa.googlegroups.com>, "Thorsten Jens" <thojens@gmx.de> writes:
>> >Jeff Cameron wrote:
>> >> What is the BUGCHECK error message?
>> >
>> >That is a good question. I don't get anything after that on the serial
>> >port. Is there a file I could inspect after rebooting?
>>
>> If you have a crash dump file (active, during crash) you could
>>
>> $ ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMP
>> SDA> CLUE CRASH
>> or
>> SDA> SHOW CRASH
>>
>> Don't forget, the next shutdown (or crash) invalidates the contents
>> of the dump file.
>
>The first crash that produces the dump file or the crash after that?

The dump file is NOT produced at crash/dump time (only filled up) !

It must be created before and must be big enough (or the crash dump will
be incomplete, but usable). It is opened on VMS boottime (to prevent
successfull deletion of the file - thus freeing up the diskblocks [for
allocation by another files] which are already told to the savedump code)
to avoid overwriting valid files on disk (because crashdump is written by
primitive code not checking filestructures at this time)

The SYSGEN parameters SAVEDUMP (overwrite dump) and DUMPSTYLE (compressed
and/or selective dump, ...) and the DOSD feature are for a later discussion.

>Because I would have to reset/reboot to actually analyze that file.

This I don't understand. Is the computer already shutdown since the crash
or is it still running ? Did you have a SYSDUMP.DMP before (it is usually
created at VMS installtion/configuration time) ? Yes, you need a running
VMS to do a ANAL/CRASH. 

-- 
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail  peter@langstoeger.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

Relevant Pages

  • Re: Vista crashing, I need a way to know whats wrong
    ... The second "crash" sounds more like a hardware freeze, not an operating system issue but rather a problem component. ... This is probably the first time since december 2007 when I bought my laptop with Vista. ... The WER* files are not at there mentioned place, but the dump file is there. ...
    (microsoft.public.windows.vista.hardware_devices)
  • Re: Vista crashing, I need a way to know whats wrong
    ... This file transfer session will be removed once you upload the file. ... The second "crash" sounds more like a hardware freeze, not an operating system issue but rather a problem component. ... This is probably the first time since december 2007 when I bought my laptop with Vista. ... The WER* files are not at there mentioned place, but the dump file is there. ...
    (microsoft.public.windows.vista.hardware_devices)
  • RE: [2003SP1] Regular bluescreens on domaincontroller.
    ... To locate the exact problem of the stop error, we need to analyze the crash ... we cannot help you analyze the dump file in ... â??A damaged device driver or system service. ...
    (microsoft.public.windows.server.general)
  • Re: Server 2008 x64 crashing
    ... The scan engine 9.000.1003 that was released 11/17/09 had the crash problem. ... Page c74fc not present in the dump file. ... An exception happened while executing a system service routine. ... FOLLOWUP_NAME: MachineOwner ...
    (microsoft.public.windows.server.general)
  • Re: Memory corruption and Dump Stack trace
    ... create a dump file. ... you can use JIT debugging to invoke the debugger ... crashes very randomly and thus hard to reproduce the crash. ...
    (microsoft.public.vc.mfc)
Quantcast