TechSpot

Windows 2k crashes when (non-blank) CD / DVD inserted.

By deanburn
Aug 28, 2005
  1. My pc crashes and automatically re-starts when I insert any non-blank CD or DVD in either of my two disk drives.

    Both drives are able to write to CD's OK, but even if you re-insert the written disk in the drive it crashes.

    When I re-boot in safe mode they work fine, so I am guessing it's a software or driver problem, but the system has been working fine for ages. Only thing I can think of is either a bug or one of the microsoft updates I dd a couple of weeks ago.

    The contents of the minidump file are:-

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


    Loading Dump File [C:\WINNT\Minidump\Mini082805-05.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 = 0x804814c0
    Debug session time: Sun Aug 28 13:35:25.156 2005 (GMT+1)
    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 00000044
    Arguments 82e7ac28 00000d39 00000000 00000000

    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bca89088 00000000 82e7ac28 00000d39 00000000 nt+0x1df2c

    WaitForEvent failed


    I have checked for errors with dxdiag and devmgmt.msc etc, but all looks fine.

    Any advice would be greatfully received.

    Ian
     
  2. RealBlackStuff

    RealBlackStuff TS Rookie Posts: 6,503

    What errors do you get in your Event logs?
     
  3. deanburn

    deanburn TS Rookie Topic Starter

    The only 2 significant entries in the event log are:-

    Event Type: Information
    Event Source: ISService
    Event Category: None
    Event ID: 1
    Date: 28/08/2005
    Time: 13:34:41
    User: NT AUTHORITY\SYSTEM
    Computer: FRED
    Description:
    The description for Event ID ( 1 ) in Source ( ISService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt..


    Event Type: Information
    Event Source: Save Dump
    Event Category: None
    Event ID: 1001
    Date: 28/08/2005
    Time: 13:36:13
    User: N/A
    Computer: FRED
    Description:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000044 (0x82e7ac28, 0x00000d39, 0x00000000, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini082805-05.dmp.
     
  4. Samstoned

    Samstoned TechSpot Paladin Posts: 1,018

Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...