TechSpot

Alcaudsl.sys causing BSOD

By Frac
Jan 11, 2009
  1. alcaudsl.sys
    is my speedtouch modem
    and it caused a bsod yesterday
    any help wat to do?

    this i wat i got when i debugged it

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


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    Debug session time: Sat Jan 10 18:38:45.656 2009 (GMT-8)
    System Uptime: 0 days 0:13:18.266
    Loading Kernel Symbols
    ..................................................................................................................................
    Loading User Symbols

    Loading unloaded module list
    ................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {c0000005, b6439fce, f3b96c40, f3b9693c}

    *** ERROR: Module load completed but symbols could not be loaded for alcaudsl.sys
    Probably caused by : alcaudsl.sys ( alcaudsl+a6fce )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: b6439fce, The address that the exception occurred at
    Arg3: f3b96c40, Exception Record Address
    Arg4: f3b9693c, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    alcaudsl+a6fce
    b6439fce 0fb708 movzx ecx,word ptr [eax]

    EXCEPTION_RECORD: f3b96c40 -- (.exr 0xfffffffff3b96c40)
    ExceptionAddress: b6439fce (alcaudsl+0x000a6fce)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: 00000000
    Attempt to read from address 00000000

    CONTEXT: f3b9693c -- (.cxr 0xfffffffff3b9693c)
    eax=00000000 ebx=00000001 ecx=00002a30 edx=86f5d4a0 esi=867bda40 edi=86ab4c58
    eip=b6439fce esp=f3b96d08 ebp=f3b96d38 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    alcaudsl+0xa6fce:
    b6439fce 0fb708 movzx ecx,word ptr [eax] ds:0023:00000000=????
    Resetting default scope

    PROCESS_NAME: System

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    READ_ADDRESS: 00000000

    BUGCHECK_STR: 0x7E

    DEFAULT_BUCKET_ID: NULL_DEREFERENCE

    LAST_CONTROL_TRANSFER: from b643b9e2 to b6439fce

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f3b96d38 b643b9e2 86edbce0 00000000 867bdc58 alcaudsl+0xa6fce
    f3b96d80 b643d4c3 867bdc58 00000000 87143b80 alcaudsl+0xa89e2
    f3b96dac 80575723 007bdc58 00000000 00000000 alcaudsl+0xaa4c3
    f3b96ddc 804ec6d9 b643d432 867bdc58 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    FOLLOWUP_IP:
    alcaudsl+a6fce
    b6439fce 0fb708 movzx ecx,word ptr [eax]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: alcaudsl+a6fce

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: alcaudsl

    IMAGE_NAME: alcaudsl.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 3cff27f4

    STACK_COMMAND: .cxr 0xfffffffff3b9693c ; kb

    FAILURE_BUCKET_ID: 0x7E_alcaudsl+a6fce

    BUCKET_ID: 0x7E_alcaudsl+a6fce

    Followup: MachineOwner
    ---------
     
  2. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Ideally if you have the option for ethernet on that Alcatel modem, use that
    Then uninstall the USB drivers through add\remove programs
     
  3. Frac

    Frac TS Rookie Topic Starter Posts: 51

    i do have the option but i have a wireless Dlink router connected to it
     
  4. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    I'm only concerned what's plugged into the computer (ie after this conversation - ethernet ;) )
     
  5. Frac

    Frac TS Rookie Topic Starter Posts: 51

    ok im using the ethernet
     
  6. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Well done ;) ;)
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.