TechSpot

physical memory dump when wireless connection fails ??

By mentar
Dec 27, 2006
  1. Alright, these blue screens keep happening only when my (wireless) internet connection is active (adapter and modem from D-Link). Since that connection is relatively new (about 1 month), I suspect that there is a hardware conflict or something.

    Here is the .dmp file, I don't understand how to proceeed though :

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


    Loading Dump File [C:\WINNT\Minidump\Mini122706-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 = 0x80481580
    Debug session time: Wed Dec 27 14:04:20.046 2006 (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 000000E1
    Arguments eb4f3ea0 00000002 81b034e8 81b034e8

    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    eb83fd6c 00000000 eb4f3ea0 00000002 81b034e8 nt+0x16c3f

    WaitForEvent failed

    Can soemone point me in the right direction ?

    Thx !
     
  2. Nodsu

    Nodsu TS Rookie Posts: 5,837   +6

    Update the wireless drivers?
     
  3. mentar

    mentar TS Rookie Topic Starter

    Hi, no my drivers are up to date.

    Most of the times, the blue screen complains about OUSBEHCI.SYS, but sometimes also NTOSKRNL.exe.

    Doesn't look nice to me.

    I can almost reproduce the problem, for example plugging out my adapter frequently (not always) results in the blue screen of death.

    I'm thinking maybe my USB port is unstable. I can try some things out, but how does the memory dump help me ?
     
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...