BSOD with Procaster?

Discussion in 'Windows Desktop Systems' started by zapoqx, Jun 17, 2010.

  1. zapoqx

    zapoqx Striking Master

    Messages:
    461
    Location:
    AZ, USA
    So I sometimes stream on livestream with procaster. Except I realize I could never stream for long periods of time without an issue rising. I thought I fixed the issue from happening, but then I found my system BSODs badly after some time the streaming is going (I've narrowed it down to anywhere between 30 min to 2 hours til when the BSOD occurs).
    I looked up the error online but either I didn't type the right thing in google or it really didn't have my issue when I was putting in the report. I decided to use debug tools to find out a little of whats going on. It said the following:
    Code:
    BugCheck 100000D1, {14, 2, 0, accd6b62}
    
    Probably caused by : afd.sys ( afd!AfdCopyMdlChainToMdlChain+d2 )
    -----------
    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: 00000014, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: accd6b62, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS:  00000014 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    afd!AfdCopyMdlChainToMdlChain+d2
    accd6b62 8b7814          mov     edi,dword ptr [eax+14h]
    
    CUSTOMER_CRASH_COUNT:  2
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  PMB.exe
    
    LAST_CONTROL_TRANSFER:  from accd7137 to accd6b62
    
    STACK_TEXT:  
    a982ab28 accd7137 89427da8 00000006 00000000 afd!AfdCopyMdlChainToMdlChain+0xd2
    a982ab88 accd661e 00000dc4 00000020 accd661e afd!AfdBReceive+0x133
    a982ac30 accd42d7 89b17580 89c4f7b8 a982ac64 afd!AfdReceive+0x599
    a982ac40 804ef19f 89c4f6a0 892fa7c0 806e6410 afd!AfdDispatchDeviceControl+0x53
    a982ac50 8057f982 892fa89c 89b17580 892fa7c0 nt!IopfCallDriver+0x31
    a982ac64 805807f7 89c4f6a0 892fa7c0 89b17580 nt!IopSynchronousServiceTail+0x70
    a982ad00 80579274 00000584 00000304 00000000 nt!IopXxxControlFile+0x5c5
    a982ad34 8054163c 00000584 00000304 00000000 nt!NtDeviceIoControlFile+0x2a
    a982ad34 7c90e514 00000584 00000304 00000000 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    02eafc6c 00000000 00000000 00000000 00000000 0x7c90e514
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    afd!AfdCopyMdlChainToMdlChain+d2
    accd6b62 8b7814          mov     edi,dword ptr [eax+14h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  afd!AfdCopyMdlChainToMdlChain+d2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: afd
    
    IMAGE_NAME:  afd.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  48a40333
    
    FAILURE_BUCKET_ID:  0xD1_afd!AfdCopyMdlChainToMdlChain+d2
    
    BUCKET_ID:  0xD1_afd!AfdCopyMdlChainToMdlChain+d2
    Unfortunately, I can't seem to get an accurate description on what the hell pmb.exe is or what afd.sys makes use of.

    So, can someone help me out?
    Thanks in advance!

    P.S. I wasn't sure to post this in the applications forums due to questioning if it was an application itself or if it was more of a driver issue and such. If you'd like, I can attach a zip of the minidump and the error message.