The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    I need the audio driver for the MX6131 (I have already read the posts in this forum regarding this topic, it did not work)

    Discussion in 'Gateway and eMachines' started by mrkylewood, Oct 1, 2010.

  1. mrkylewood

    mrkylewood Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    I am having much trouble over a driver issue for a laptop. The laptop had a virus and it had the original factory installed os. The sound worked great. I decided to format it...this is where the trouble begins. It is a gateway mx6131. It is well documented that the drivers that Gateway supplies via their website are usually highly inaccurate. I have crawled the deepest depths of the internet looking for a driver that would work with this computer...and I have come up empty handed

    I have tried this audio driver http://forum.notebookreview.com/gateway-emachines/40330-mx6131-driver-list.html

    I have tried this audio driver http://forum.notebookreview.com/gateway-emachines/39835-mx6131-audio-wireless-drivers.html

    I have tried the ones supplied on gateway's site

    I have tried these Gateway MX6131 | 2 of 4

    Esssentially, the overwhelming opnion is that the driver is a Conexant or a realtek. I have yet to get either to work.

    I have received a couple of differnet reactions to the driver install. With some of the realtek drivers, it will install fine, show up normal in the device manager, but no sound is ever created.

    The Conexant driver usually gave me blue screen errors. Some forum proposed I use the build in AC97 intel driver. I have installed many, many drivers and have never run into one I could not install. Listed below is some hardware information. If anyone can help, I will be indebted to you forever.

    Device Instance Id
    PCI\VEN_8086&DEV_24C5&SUBSYS_0360107B&REV_03\3&61AAA01&0&FD

    Hardware Ids
    PCI\VEN_8086&DEV_24C5&SUBSYS_0360107B&REV_03
    PCI\VEN_8086&DEV_24C5&SUBSYS_0360107B
    PCI\VEN_8086&DEV_24C5&CC_040100
    PCI\VEN_8086&DEV_24C5&CC_0401

    Compatible Ids
    PCI\VEN_8086&DEV_24C5&REV_03
    PCI\VEN_8086&DEV_24C5
    PCI\VEN_8086&CC_040100
    PCI\VEN_8086&CC_0401
    PCI\VEN_8086
    PCI\CC_040100
    PCI\CC_0401

    Enumerator
    PCI

    Devnode Flags
    DN_HAS_PROBLEM
    DN_DISABLEABLE
    DN_NT_ENUMERATOR
    DN_NT_DRIVER

    Ejection Relations
    PCI\VEN_8086&DEV_24CC&SUBSYS_00000000&REV_03\3&61aaa01&0&F8
    PCI\VEN_8086&DEV_24CA&SUBSYS_0360107B&REV_03\3&61aaa01&0&F9
    PCI\VEN_8086&DEV_24C3&SUBSYS_0360107B&REV_03\3&61aaa01&0&FB
    PCI\VEN_8086&DEV_24C6&SUBSYS_0360107B&REV_03\3&61aaa01&0&FE

    Current Power State
    D3

    Power Capablilites
    PDCAP_D0_SUPPORTED
    PDCAP_D3_SUPPORTED

    POwer State Mappings
    S0 -> D0
    S1 -> Unspecified
    S2 -> Unspecified
    S3 -> D3
    S4 -> D3
    S5 -> D3
     
    mrkylewood, Oct 1, 2010
    #1
  2. mrkylewood

    mrkylewood Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    I also have the minidump file that the bsod of created, if that helps.


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


    Loading Dump File [g:\mini.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    WARNING: Inaccessible path: 'c:\windows\i386'
    Symbol search path is: srv*c:\symbols* Symbol information
    Executable search path is: c:\windows\i386
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
    Debug session time: Fri Oct 1 23:00:57.014 2010 (GMT-5)
    System Uptime: 0 days 0:19:54.593
    Loading Kernel Symbols
    ...............................................................
    ....................................................
    Loading User Symbols
    Loading unloaded module list
    .....................
    Unable to load image camc6hal.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for camc6hal.sys
    *** ERROR: Module load completed but symbols could not be loaded for camc6hal.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {0, 16, 0, ee96a791}

    Probably caused by : camc6hal.sys ( camc6hal+9791 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000016, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: ee96a791, address which referenced memory

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


    READ_ADDRESS: 00000000

    CURRENT_IRQL: 16

    FAULTING_IP:
    camc6hal+9791
    ee96a791 8b01 mov eax,dword ptr [ecx]

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 8054071d to ee96a791

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f88cb560 8054071d 81f92368 00000060 00010016 camc6hal+0x9791
    f88cb560 00000000 81f92368 00000060 00010016 nt!KiInterruptDispatch+0x3d


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    camc6hal+9791
    ee96a791 8b01 mov eax,dword ptr [ecx]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: camc6hal+9791

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: camc6hal

    IMAGE_NAME: camc6hal.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 424c7de0

    FAILURE_BUCKET_ID: 0xD1_camc6hal+9791

    BUCKET_ID: 0xD1_camc6hal+9791

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000016, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: ee96a791, address which referenced memory

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


    READ_ADDRESS: 00000000

    CURRENT_IRQL: 16

    FAULTING_IP:
    camc6hal+9791
    ee96a791 8b01 mov eax,dword ptr [ecx]

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 8054071d to ee96a791

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f88cb560 8054071d 81f92368 00000060 00010016 camc6hal+0x9791
    f88cb560 00000000 81f92368 00000060 00010016 nt!KiInterruptDispatch+0x3d


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    camc6hal+9791
    ee96a791 8b01 mov eax,dword ptr [ecx]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: camc6hal+9791

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: camc6hal

    IMAGE_NAME: camc6hal.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 424c7de0

    FAILURE_BUCKET_ID: 0xD1_camc6hal+9791

    BUCKET_ID: 0xD1_camc6hal+9791

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000016, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: ee96a791, address which referenced memory

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


    READ_ADDRESS: 00000000

    CURRENT_IRQL: 16

    FAULTING_IP:
    camc6hal+9791
    ee96a791 8b01 mov eax,dword ptr [ecx]

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 8054071d to ee96a791

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f88cb560 8054071d 81f92368 00000060 00010016 camc6hal+0x9791
    f88cb560 00000000 81f92368 00000060 00010016 nt!KiInterruptDispatch+0x3d


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    camc6hal+9791
    ee96a791 8b01 mov eax,dword ptr [ecx]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: camc6hal+9791

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: camc6hal

    IMAGE_NAME: camc6hal.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 424c7de0

    FAILURE_BUCKET_ID: 0xD1_camc6hal+9791

    BUCKET_ID: 0xD1_camc6hal+9791

    Followup: MachineOwner
    ---------
     
    mrkylewood, Oct 1, 2010
    #2