Windows restarting have dump file 1

[TMD]

Can anyone tell from the following minidump files why the pc is crashing, i haven't been using it, it's another users so i don't know what they were doing with it when it crashed.

any help is greatly appreciated.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 07/10/2004
Time: 14:31:12
User: N/A
Computer: WCI_016
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0xbfd197c0, 0x00000000, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini100704-02.dmp.

 

[TMD]

have saved the dump file to text, looks like this:



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


Loading Dump File [C:\WINNT\Minidump\Mini100704-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Thu Oct 07 14:29:41 2004
System Uptime: not available
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Bugcheck code 0000001E
Arguments c0000005 bfd197c0 00000000 00000000

ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
bb3411f8 0000001e c0000005 bfd197c0 00000000 nt+0x30999

WaitForEvent failed
kd> g
^ No runnable debuggees error in 'g'
kd> g
^ No runnable debuggees error in 'g'

Loading Dump File [C:\WINNT\Minidump\Mini100704-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Thu Oct 07 14:29:41 2004
System Uptime: not available
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Bugcheck code 0000001E
Arguments c0000005 bfd197c0 00000000 00000000

ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
bb3411f8 0000001e c0000005 bfd197c0 00000000 nt+0x30999

WaitForEvent failed

 

[bcastner]

http://support.microsoft.com/?kbid=183169

 

[wlfpackr]

May want to check out your video driver. We get this a lot at work on the NetVistas. People here will do a Windows update and use a newer Microsoft video driver which the IBM pc does not like evidently.


=================
There are 10 kinds of people in this world, those that understand binary and those that do not.