BSOD randomly daily, error 0x0000001e


  1. Posts : 5
    Windows 7 Ultimate x64 SP1 6.1.7600 N/A Build 7600
       #1

    BSOD randomly daily, error 0x0000001e


    Hello, I'm running into some issues daily, even playing with many graphics drivers and such.

    Last time it happened when trying to launch a full screen game, but it can happen at any time.


    Last two error codes that happened both yesterday:
    0x0000003b
    0x0000001e

    I've attached a zip of logs and bsod dumps. Please let me know if you need anything else to diagnose. Thanks a bunch in advance!
      My Computer


  2. Posts : 5
    Windows 7 Ultimate x64 SP1 6.1.7600 N/A Build 7600
    Thread Starter
       #2

    I preemptively ran a memtest x86 all night and it turned out with no errors.
      My Computer


  3. Posts : 2,781
    Windows 10 Pro x64
       #3

    The BSOD causing the problem is your Bigfoot Wireless Driver. Try to upgrade it or uninstall it.
      My Computer


  4. Posts : 5
    Windows 7 Ultimate x64 SP1 6.1.7600 N/A Build 7600
    Thread Starter
       #4

    Thanks Laith, I see the line in the most recent BSOD: Probably caused by : bflwfx64.sys ( bflwfx64+3810 )
    I've updated the bigfoot qualcomm drivers and hopefully that doesnt cause any issues anymore. Will let you know if I still get any more BSODs.

    How about the second to most recent BSOD? Any idea what caused that? Seems like desktop window manager.. but I like my Aero themes . Any way to fix it without disabling it?

    Here's my debugger output:
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960002a2945, Address of the instruction which caused the bugcheck
    Arg3: fffff88009665110, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

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


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

    FAULTING_IP:
    win32k!MulAssociateSharedSurface+15
    fffff960`002a2945 4c8b98300d0000 mov r11,qword ptr [rax+0D30h]

    CONTEXT: fffff88009665110 -- (.cxr 0xfffff88009665110;r)
    rax=0000000000000000 rbx=fffff900c4b4ed60 rcx=fffffa8012887d70
    rdx=00000000c00069c0 rsi=fffff900c5041ce8 rdi=fffff900c4b4edf8
    rip=fffff960002a2945 rsp=fffff88009665ae0 rbp=ffffffff961243d0
    r8=ffffffff961243d0 r9=000001fe00000400 r10=0000000000000000
    r11=fffff88009665b08 r12=fffff900c010b010 r13=00000000c00069c0
    r14=0000000027c37da0 r15=0000000000000001
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    win32k!MulAssociateSharedSurface+0x15:
    fffff960`002a2945 4c8b98300d0000 mov r11,qword ptr [rax+0D30h] ds:002b:00000000`00000d30=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffff900c4b4ed60 rcx=fffffa8012887d70
    rdx=00000000c00069c0 rsi=fffff900c5041ce8 rdi=fffff900c4b4edf8
    rip=fffff960002a2945 rsp=fffff88009665ae0 rbp=ffffffff961243d0
    r8=ffffffff961243d0 r9=000001fe00000400 r10=0000000000000000
    r11=fffff88009665b08 r12=fffff900c010b010 r13=00000000c00069c0
    r14=0000000027c37da0 r15=0000000000000001
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    win32k!MulAssociateSharedSurface+0x15:
    fffff960`002a2945 4c8b98300d0000 mov r11,qword ptr [rax+0D30h] ds:002b:00000000`00000d30=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: dwm.exe

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

    LAST_CONTROL_TRANSFER: from fffff9600024d365 to fffff960002a2945

    STACK_TEXT:
    fffff880`09665ae0 fffff960`0024d365 : 00000000`00000000 ffffffff`961243d0 00000000`0375f490 00000000`00000000 : win32k!MulAssociateSharedSurface+0x15
    fffff880`09665b10 fffff960`00270749 : 00000000`00000001 fffff880`09665c60 00000000`0375f490 00000000`00009a2c : win32k!GreSetRedirectionSurfaceSignaling+0x125
    fffff880`09665b60 fffff800`02ecbad3 : fffffa80`0fef2060 00000000`00000020 fffff880`09665a10 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x209
    fffff880`09665be0 000007fe`ff4d4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0375f3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`ff4d4efa


    FOLLOWUP_IP:
    win32k!MulAssociateSharedSurface+15
    fffff960`002a2945 4c8b98300d0000 mov r11,qword ptr [rax+0D30h]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: win32k!MulAssociateSharedSurface+15

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5130212e

    IMAGE_VERSION: 6.1.7600.17266

    STACK_COMMAND: .cxr 0xfffff88009665110 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+15

    BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+15

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x3b_win32k!mulassociatesharedsurface+15

    FAILURE_ID_HASH: {08b97eea-ad52-6762-8e6c-277f3c48177d}

    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 2,781
    Windows 10 Pro x64
       #5

    Yea that will probably help, because the BSOD was caused by the Bigfoot wireless driver.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:29.
Find Us