Re: windows 2000 crashing randomly

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hello,



It is difficult to determine the root cause of these crashes by just looking
at the !analyze portion of the dumps. You need to gather as much information
as you can.



1.. When did the problem first start to occur?
2.. Were any changes made to the server just prior to this issue? If you
have added any new hardware recently or updated drivers, address them first.
3.. Are you logging any events in the System Log? If you are seeing disk
related or controller related events, address them. If you see resource
related problems, such as ID: 2019 or 2020, address them accordingly.
4.. If you disable 3rd party services, does the problem still occur?


NOTE: You can copy MSConfig from a Windows XP system to Windows 2000 for an
easy method of disabling 3rd party services. Just make sure you don't
disable any service that is required for booting.



If you are constantly getting random bugchecks that vary, for example, Stop:
0x0000001e, 0x00000024, 0x0000000a etc, you can suspect a hardware problem.
Run a full hardware diagnostics on the server. Remove any newly added RAM or
consider using options in the boot.ini to isolation hardware such as numproc
and maxmem.



If the server has hyper-threaded processors and your BIOS/Microcode is older
in date, consider disabling hyper-threading in the BIOS and monitor for any
change in behavior. If the problem goes away, contact your server
manufacturer and ask for an updated BIOS that included Microcode.



If you are also running pre SP4 for Windows 2000, Microsoft recommends you
run the latest Service Pack for Windows 2000. As always, perform regular
backups including system state before applying a service pack, and check
with your server manufacturer for recommended driver and BIOS levels for the
Service Pack you are about to apply.



Related articles:



275678 How to Troubleshoot a STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
Error

http://support.microsoft.com/?id=275678



842465 Stop 7F, 0x00000008 (double-fault) error occurs because of a
single-bit

http://support.microsoft.com/?id=842465



833722 Available switch options for the Windows 2000 Boot.ini file

http://support.microsoft.com/?id=833722



Best regards,



Ronny


"redbulljw" <redbull@xxxxxxxxx> wrote in message
news:uz23OFhyFHA.3320@xxxxxxxxxxxxxxxxxxxxxxx
> This is the dump file of windows 2000 system that crashes on it own every
> once in a while.
>
> Any thought as to why and how to fix?
>
>
>
> Thanks
>
>
>
>
>
> Microsoft (R) Windows Debugger Version 6.5.0003.7
>
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>
> Loading Dump File [C:\Documents and Settings\jj\Desktop\weather
> data\Mini100105-01.dmp] Mini Kernel Dump File: Only registers and stack
> trace are available
>
> Symbol search path is: C:\WINDOWS\Symbols
>
> Executable search path is:
>
> Unable to load image ntoskrnl.exe, Win32 error 2
>
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows 2000
> Kernel Version 2195 (Service Pack 2) MP (2 procs) Free x86 compatible
> Kernel base = 0x80400000 PsLoadedModuleList = 0x804836e0 Debug session
> time: Sat Oct 1 06:18:13.656 2005 (GMT-5) System Uptime: not available
> Unable to load image ntoskrnl.exe, Win32 error 2
>
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel
> Symbols
> ................................................................................................
>
> Loading unloaded module list
>
> .......
>
> Loading User Symbols
>
> *******************************************************************************
>
> * *
>
> * Bugcheck Analysis *
>
> * *
>
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 1E, {c0000005, 8046b9e6, 1, 45}
>
> Probably caused by : ntoskrnl.exe ( nt!VdmpDelayIntApcRoutine+f5 )
>
> Followup: MachineOwner
>
> ---------
>
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: C:\WINDOWS\Symbols
>
> Executable search path is:
>
> Unable to load image ntoskrnl.exe, Win32 error 2
>
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows 2000
> Kernel Version 2195 (Service Pack 2) MP (2 procs) Free x86 compatible
> Kernel base = 0x80400000 PsLoadedModuleList = 0x804836e0 Debug session
> time: Tue Oct 4 14:58:14.718 2005 (GMT-5) System Uptime: not available
> Unable to load image ntoskrnl.exe, Win32 error 2
>
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel
> Symbols
> ................................................................................................
>
> Loading unloaded module list
>
> .....
>
> Loading User Symbols
>
> *******************************************************************************
>
> * *
>
> * Bugcheck Analysis *
>
> * *
>
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 1E, {c0000005, 8046bd32, 0, 0}
>
> Probably caused by : ntoskrnl.exe ( nt!VdmpDelayInterrupt+17c )
>
> Followup: MachineOwner
>
> ---------
>
>
>
> Microsoft (R) Windows Debugger Version 6.5.0003.7
>
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>
> Loading Dump File [C:\Documents and Settings\jj\Desktop\weather
> data\Mini100305-01.dmp] Mini Kernel Dump File: Only registers and stack
> trace are available
>
> Symbol search path is: C:\WINDOWS\Symbols
>
> Executable search path is:
>
> Unable to load image ntoskrnl.exe, Win32 error 2
>
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows 2000
> Kernel Version 2195 (Service Pack 2) MP (2 procs) Free x86 compatible
> Kernel base = 0x80400000 PsLoadedModuleList = 0x804836e0 Debug session
> time: Mon Oct 3 00:32:48.687 2005 (GMT-5) System Uptime: not available
> Unable to load image ntoskrnl.exe, Win32 error 2
>
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel
> Symbols
> ................................................................................................
>
> Loading unloaded module list
>
> .....
>
> Loading User Symbols
>
> *******************************************************************************
>
> * *
>
> * Bugcheck Analysis *
>
> * *
>
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 24, {19025e, eb43f884, eb43f4dc, bfefaf7c}
>
> *** WARNING: Unable to verify timestamp for Ntfs.sys
>
> Probably caused by : hardware ( CODE_ADDRESS_MISMATCH )
>
> Followup: MachineOwner
>
> ---------
>
>
>
>
>
>


.

Relevant Pages

  • Re: Save Dump EVERY time I load XP
    ... Dumprep.exe = Windows Error Reporting Dump Reporting Tool ... Write an event to the system log = dumprep 0-k ... If you have Error Reporting enabled, this entry may show up for the first ...
    (microsoft.public.windowsxp.general)
  • Re: STOP error code (0x000000f4 (0x0000003....) Memory dump & BSOD
    ... downloading symbols package. ... You may get an answer by running the Windows Debugger on the memory dump ...
    (microsoft.public.windowsxp.general)
  • Re: File Attribute Issue & Security
    ... I run Windows Xp Pro on one computer that is shared by 3 ... Immediately after copying to the files to the "DUMP" ... If SOME jpeg files are edited in Adobe and then re-saved ... Error message reports that access to the file to be ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Stop Message 0x7E
    ... so I can change it back to mini dump in the Advanced tab of the System ... The only time I receive a windows error ... >>>> If exception code 0x80000002 occurs, the trap frame will supply additional information. ...
    (microsoft.public.windowsxp.help_and_support)