1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista Dump Data : BSoD 0x000000BE, bcmwl6.exe

Discussion in 'Legacy Windows' started by rpj187, 2014/07/08.

  1. 2014/07/08
    rpj187

    rpj187 Inactive Thread Starter

    Joined:
    2014/07/08
    Messages:
    2
    Likes Received:
    0
    I keep receiving blue screens of death while playing the game Diablo II. I bought this computer for the purpose of playing the game so any don't use that program suggestions will not help. I followed the directions for data dump collection and here are the results. I have included 3 of these dump files. Any help would be greatly appreciated.

    __________________________________________________________

    Opened log file 'c:debuglog.txt'

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


    Loading Dump File [C:\Windows\Minidump\Mini070714-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    Windows Vista Kernel Version 6000 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16575.x86fre.vista_gdr.071009-1548
    Machine Name:
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Mon Jul 7 23:23:51.161 2014 (UTC - 5:00)
    System Uptime: 0 days 12:40:25.988
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {5b1cc88c, 2, 0, 8b513413}

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

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: 5b1cc88c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8b513413, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac
    Unable to read MiSystemVaType memory at 821117e0
    5b1cc88c

    CURRENT_IRQL: 2

    FAULTING_IP:
    bcmwl6+62413
    8b513413 668b710c mov si,word ptr [ecx+0Ch]

    CUSTOMER_CRASH_COUNT: 3

    ______________________________________________________________

    Opened log file 'c:debuglog.txt'

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


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

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    Windows Vista Kernel Version 6000 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16575.x86fre.vista_gdr.071009-1548
    Machine Name:
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Mon Jul 7 10:42:38.372 2014 (UTC - 5:00)
    System Uptime: 0 days 0:13:57.873
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {15b08bfb, 2, 1, 8d5114d3}

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

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: 15b08bfb, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 8d5114d3, address which referenced memory

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

    ________________________________________________________________

    Opened log file 'c:debuglog.txt'

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


    Loading Dump File [C:\Windows\Minidump\Mini070714-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    Windows Vista Kernel Version 6000 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16575.x86fre.vista_gdr.071009-1548
    Machine Name:
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Mon Jul 7 10:28:20.966 2014 (UTC - 5:00)
    System Uptime: 3 days 18:36:13.556
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {c8800024, 2, 0, 8b02e413}

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

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: c8800024, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8b02e413, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac
    Unable to read MiSystemVaType memory at 821117e0
    c8800024

    CURRENT_IRQL: 2

    FAULTING_IP:
    bcmwl6+62413
    8b02e413 668b710c mov si,word ptr [ecx+0Ch]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: Game.exe

    TRAP_FRAME: 80605cd8 -- (.trap 0xffffffff80605cd8)
    .trap 0xffffffff80605cd8
    ErrCode = 00000000
    eax=86eaba38 ebx=85f797ac ecx=c8800018 edx=80605df8 esi=85cd5000 edi=85f797ac
    eip=8b02e413 esp=80605d4c ebp=80605d54 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    bcmwl6+0x62413:
    8b02e413 668b710c mov si,word ptr [ecx+0Ch] ds:0023:c8800024=????
    .trap
    Resetting default scope
     
    Last edited: 2014/07/08
  2. 2014/07/08
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,680
    Likes Received:
    104
    Please post one complete dump as per our instructions:

    Follow these instructions to post a Dump Data Log.

    But it looks like to be caused by the wireless driver.
     

  3. to hide this advert.

  4. 2014/07/11
    rpj187

    rpj187 Inactive Thread Starter

    Joined:
    2014/07/08
    Messages:
    2
    Likes Received:
    0
    Okay, here is one dump. If it is the wireless driver, how do I go about repairing or replacing this specific driver?

    _________________________________________________________________

    Opened log file 'c:debuglog.txt'

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


    Loading Dump File [C:\Windows\Minidump\Mini070714-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    Windows Vista Kernel Version 6000 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16575.x86fre.vista_gdr.071009-1548
    Machine Name:
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Mon Jul 7 10:28:20.966 2014 (UTC - 5:00)
    System Uptime: 3 days 18:36:13.556
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {c8800024, 2, 0, 8b02e413}

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

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: c8800024, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8b02e413, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac
    Unable to read MiSystemVaType memory at 821117e0
    c8800024
     
  5. 2014/07/14
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Well, the dump is incomplete and missing quite a bit of data. But all are pointing to your wireless driver, so I suggest you start by looking for an update from Dell
     
    Arie,
    #4

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.