locked
No dump file. Blue Screen. RRS feed

  • Question

  • I have an HP mini with windows 7 and have been unable to fix the Blue screen error I keep encountering.

    I've posted on a few different forums, but as no dump file seems to be created, no one has been able to tell me how to fix it.

    All the settings are as they should be for a dump file to be created, but still nothing. Is there any other way anyone knows of to fix this awful blue screen?


    I'm so sorry, I just realised I posted this in the wrong section and I don't know how to move it :(
    • Edited by booknet Sunday, January 8, 2012 1:36 AM
    • Moved by Carey FrischMVP Sunday, January 8, 2012 4:33 AM Move to more appropriate forum category (From:Windows XP Service Pack 3 (SP3))
    Sunday, January 8, 2012 1:34 AM

Answers

  • Looks to be due to a network driver, bcmw16.sys. If Google indicates
    correctly, it is a Broadcom wireless card. Your particular driver is
    old, from 2009,
     
    0: kd> lmvm bcmwl6
    start    end        module name
    8ae1d000 8af35000   bcmwl6   T (no symbols)
        Loaded symbol image file: bcmwl6.sys
        Image path: bcmwl6.sys
        Image name: bcmwl6.sys
        Timestamp:        Thu Mar 26 18:58:48 2009 (49CC24C8)
        CheckSum:         0011A306
        ImageSize:        00118000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
     
    0: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 81838d13, address which referenced memory
     
    Debugging Details:
    ------------------
     WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81967700
    Unable to read MiSystemVaType memory at 819470c0
     00000000
     
    CURRENT_IRQL:  2
     
    FAULTING_IP:
    nt!memcpy+33
    81838d13 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0xA
     
    PROCESS_NAME:  System
     
    LAST_CONTROL_TRANSFER:  from 84e78ab7 to 81838d13
     
    STACK_TEXT:
    a33208b8 84e78ab7 00000000 847f78d4 000005fc nt!memcpy+0x33
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a332097c 84e78b20 aca0c650 aca0c6f0 84dc4708 0x84e78ab7
    a3320998 84e78c5f aca0c650 84dc4708 00000001 0x84e78b20
    a33209bc 86df8c1e 86e4d9cc 84dc4708 845900e0 0x84e78c5f
    a33209ec 8ae6ea2f 845900e0 aca0c650 00000000 ndis+0x1c1e
    a3320a6c 8ae32f13 00000001 846e7000 00000000 bcmwl6+0x51a2f
    a3320a9c 8ae343cb 84454000 851f1460 00000000 bcmwl6+0x15f13
    a3320b48 8ae3b10c 84454000 851f1460 a3320b88 bcmwl6+0x173cb
    a3320c08 8ae3d4f7 84454000 8441def8 847f78a4 bcmwl6+0x1e10c
    a3320c38 8ae3e6ed ffffffff a3320ca0 846a2008 bcmwl6+0x204f7
    a3320c54 8ae71984 00008000 00000000 00000001 bcmwl6+0x216ed
    a3320c74 86e4d309 846a21c8 00000000 a3320ca0 bcmwl6+0x54984
    a3320cb0 86e2e6b2 846a555c 006a5548 00000000 ndis+0x56309
    a3320d10 86e15976 846a561c 00000000 add65740 ndis+0x376b2
    a3320d50 819efd16 00000000 b745dbdc 00000000 ndis+0x1e976
    a3320d90 81891059 86e1588b 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    bcmwl6+51a2f
    8ae6ea2f ??              ???
     
    SYMBOL_STACK_INDEX:  5
     
    SYMBOL_NAME:  bcmwl6+51a2f
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: bcmwl6
     
    IMAGE_NAME:  bcmwl6.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  49cc24c8
     
    FAILURE_BUCKET_ID:  0xA_bcmwl6+51a2f
     
    BUCKET_ID:  0xA_bcmwl6+51a2f
     
    Followup: MachineOwner
    ---------
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Arthur Xie Tuesday, January 17, 2012 5:17 AM
    Tuesday, January 10, 2012 6:24 AM

All replies

  • Hi,
     
    A lot of people post BSOD issues here... so no worries. Which blue
    screen error code do you receive? If the system is bootable, what type
    of memory dump is configured and how large is your page file?
     
     

    -- Mike Burr
    Technology
    Sunday, January 8, 2012 7:26 AM
  • I don't know, I'm sure I'll be getting one again soon and I'll be sure to write it down.

    I have the same settings that are set in the link at the bottom of your post, I just have no memory dump. I found a Memory.dmp in C:/Windows, below all of the folders. It's 817,811 kb, does that sound like it could be the memory dump file i'm looking for?

    Sunday, January 8, 2012 3:38 PM
  • When a BSOD (Blue Screen of Death) system failure occurs for most users there is insufficient time to note down in full what it says; the exact text is important to anyone trying to diagnose what is wrong. You can gain the time needed when the error next occurs by following the procedure described below.


    If you haven't done so already disable automatic restart on system failure. This should help by allowing time to write down the Stop Error code and related information properly. Select Start, right click on Computer select Properties, Advanced System Settings, Start-Up and Recovery, System Failure and uncheck the box before Automatically Restart. Do not re-enable automatic restart on system failure after getting this information as this setting is best left to not to allow Automatic Restart.

    If the system failure occurs during the booting of the computer you need to try a different approach. You can access the Windows Advanced Options Menu on many computers by constantly pressing the F8 (Function) key during Start-Up and selecting the option - Disable automatic restart on system failure. This method is not always easy to use as it can be difficult to depress the F8 at exactly the right time. Try again if it does not work first time. On some computers a different key has to be used.

    Please post a copy of your dumpfile as a shared file to your Sky Drive with a link here.
    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    Hope this helps, Gerry
    Sunday, January 8, 2012 4:25 PM
  • For advice on how to configure your system to create dump files please read:
    http://support.microsoft.com/kb/254649

    The dumpfile will be created at c:\windows\minidump. You may need to change your settings in Windows to be able to see the file. To show hidden files type Folder Options in the search box above the Start button and select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and "Hide protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.


    Hope this helps, Gerry
    Sunday, January 8, 2012 4:45 PM
  • The box before 'Show hidden files' is checked and 'hide protected operating system files' is unchecked.

     I have a DUMP5a93, and DUMP397e both are 175 kbs. Is there any chance those are the dump files, they are just being saved to the wrong place?

    The number on the blue stop screen is

    Stop:0x0000000A(0x00000000,0x00000007,0x8183CD13)

    • Edited by booknet Sunday, January 8, 2012 5:54 PM
    Sunday, January 8, 2012 5:45 PM
  • Bug check code 0xA
    http://msdn.microsoft.com/en-us/library/ff560129(v=VS.85).aspx

    I don't know. I suggest you post copes to your Sky Drive with a link here.

    That Bug Check Code would normally have four parameters but you are only giving three?


    Hope this helps, Gerry
    Sunday, January 8, 2012 11:53 PM
  • Hi,
     
    The memory.dmp in Windows is what we are looking for, based on the error
    you wrote down, this is a starting point for troubleshooting,
     
     
    Additionally, if you would like help, please upload the dump to skydrive
    and post a link,
     
     
    Since this seems to be a full/kernel memory dump, the file may need to
    be compressed and split,
     
     

    -- Mike Burr
    Technology
    • Proposed as answer by Arthur Xie Monday, January 9, 2012 2:35 AM
    Monday, January 9, 2012 2:28 AM
  • First, thank you so much for the line showing how to post to skydrive. That was so much simpler than the one I first saw, lol.

    I uploaded the dump file, here is the link

    https://skydrive.live.com/#cid=05BD00B7B27D6D13&id=5BD00B7B27D6D13%21115

    Monday, January 9, 2012 11:30 PM
  • Looks to be due to a network driver, bcmw16.sys. If Google indicates
    correctly, it is a Broadcom wireless card. Your particular driver is
    old, from 2009,
     
    0: kd> lmvm bcmwl6
    start    end        module name
    8ae1d000 8af35000   bcmwl6   T (no symbols)
        Loaded symbol image file: bcmwl6.sys
        Image path: bcmwl6.sys
        Image name: bcmwl6.sys
        Timestamp:        Thu Mar 26 18:58:48 2009 (49CC24C8)
        CheckSum:         0011A306
        ImageSize:        00118000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
     
    0: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 81838d13, address which referenced memory
     
    Debugging Details:
    ------------------
     WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81967700
    Unable to read MiSystemVaType memory at 819470c0
     00000000
     
    CURRENT_IRQL:  2
     
    FAULTING_IP:
    nt!memcpy+33
    81838d13 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0xA
     
    PROCESS_NAME:  System
     
    LAST_CONTROL_TRANSFER:  from 84e78ab7 to 81838d13
     
    STACK_TEXT:
    a33208b8 84e78ab7 00000000 847f78d4 000005fc nt!memcpy+0x33
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a332097c 84e78b20 aca0c650 aca0c6f0 84dc4708 0x84e78ab7
    a3320998 84e78c5f aca0c650 84dc4708 00000001 0x84e78b20
    a33209bc 86df8c1e 86e4d9cc 84dc4708 845900e0 0x84e78c5f
    a33209ec 8ae6ea2f 845900e0 aca0c650 00000000 ndis+0x1c1e
    a3320a6c 8ae32f13 00000001 846e7000 00000000 bcmwl6+0x51a2f
    a3320a9c 8ae343cb 84454000 851f1460 00000000 bcmwl6+0x15f13
    a3320b48 8ae3b10c 84454000 851f1460 a3320b88 bcmwl6+0x173cb
    a3320c08 8ae3d4f7 84454000 8441def8 847f78a4 bcmwl6+0x1e10c
    a3320c38 8ae3e6ed ffffffff a3320ca0 846a2008 bcmwl6+0x204f7
    a3320c54 8ae71984 00008000 00000000 00000001 bcmwl6+0x216ed
    a3320c74 86e4d309 846a21c8 00000000 a3320ca0 bcmwl6+0x54984
    a3320cb0 86e2e6b2 846a555c 006a5548 00000000 ndis+0x56309
    a3320d10 86e15976 846a561c 00000000 add65740 ndis+0x376b2
    a3320d50 819efd16 00000000 b745dbdc 00000000 ndis+0x1e976
    a3320d90 81891059 86e1588b 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    bcmwl6+51a2f
    8ae6ea2f ??              ???
     
    SYMBOL_STACK_INDEX:  5
     
    SYMBOL_NAME:  bcmwl6+51a2f
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: bcmwl6
     
    IMAGE_NAME:  bcmwl6.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  49cc24c8
     
    FAILURE_BUCKET_ID:  0xA_bcmwl6+51a2f
     
    BUCKET_ID:  0xA_bcmwl6+51a2f
     
    Followup: MachineOwner
    ---------
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Arthur Xie Tuesday, January 17, 2012 5:17 AM
    Tuesday, January 10, 2012 6:24 AM
  • It turns out it is my broadcom driver.

    I have a broadcom 802.11g and I need to update it with one that is compatible with windows 7. Where do I download one for windows 7 compatible with the one I already have? How do I know if its compatible?

     

     

    • Edited by booknet Thursday, January 12, 2012 12:39 AM
    Wednesday, January 11, 2012 11:46 PM