BSoD when uploading anything 1e FFFFFFFFC0000005

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Home Premium
       #1

    BSoD when uploading anything 1e FFFFFFFFC0000005


    OS : Windows 7 Home Premium 64-Bit Operating System
    Came with the PC*

    Acer Predator G5900
    Intel Core i5 CPU 650 @ 3.20GHz
    6.00GB Installed Memory


    Hey all, first time poster so apologies in advance for any shortcomings.

    For a while now i've had an issue with the BSoD. Whenever i try to upload anything to the internet (the issue is particularly noticeable with facebook) my computer freezes up, and then proceeds to BSoD. As a result of this i am unable to attach any files to this post, however i can provide you the information i do have.

    System restore has been attempted to no avail.

    Thanks for any help, it is much appreciated


    BCCode: 1e
    BCP1: FFFFFFFFC0000005
    BCP2: FFFFF88004FF9D80
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\012712-44881-01.dmp
    C:\Users\Oli\AppData\Local\Temp\WER-90667-0.sysdata.xml


    ~~ On a separate occasion this was the error:


    BCCode: 1e
    BCP1: FFFFFFFFC0000005
    BCP2: FFFFF880057B8D8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    Last edited by Temperance; 27 Jan 2012 at 18:43.
      My Computer


  2. Posts : 9
    Windows 7 Home Premium
    Thread Starter
       #2

    Just got another one



    BCCode: 116
    BCP1: FFFFFA800A460460
    BCP2: FFFFF8800F5A49C8
    BCP3: 0000000000000000
    BCP4: 0000000000000002
      My Computer


  3. Posts : 1,782
    Windows 7 Home Premium 64bit
       #3
      My Computer


  4. Posts : 9
    Windows 7 Home Premium
    Thread Starter
       #4

    Thanks for the reply, I've attached the appropriate files.
      My Computer


  5. Posts : 9
    Windows 7 Home Premium
    Thread Starter
       #5

    Hope that's all the info you need.
      My Computer


  6. Posts : 9
    Windows 7 Home Premium
    Thread Starter
       #6

    bump.
      My Computer


  7. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #7

    Your last several crashes, 22 since May '11, are the same.
    STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
    Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
    This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    The driver being blamed, in all crashes, is ksecdd.sys - Kernel Security Support Provider Interface
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004ff9d80, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    +6637333939373934
    fffff880`04ff9d80 a8ac            test    al,0ACh
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003aca100
     0000000000000000 
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    BUGCHECK_STR:  0x1E_c0000005
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    EXCEPTION_RECORD:  fffff88004ffaca8 -- (.exr 0xfffff88004ffaca8)
    ExceptionAddress: fffff880015c76b3 (ksecdd!KsecProcessSecurityContext+0x0000000000000293)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000010
    Attempt to read from address 0000000000000010
    
    TRAP_FRAME:  fffff88004ffad50 -- (.trap 0xfffff88004ffad50)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000001bd4590
    rdx=fffff88004ffaf78 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880015c76b3 rsp=fffff88004ffaee0 rbp=0000000000000000
     r8=fffff88004ffafe8  r9=0000000001bd4590 r10=fffffa80055533f0
    r11=fffff8a003b42000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    ksecdd!KsecProcessSecurityContext+0x293:
    fffff880`015c76b3 ff5010          call    qword ptr [rax+10h] ds:00000000`00000010=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800039234fb to fffff80003897c40
    
    STACK_TEXT:  
    fffff880`04ff9cc8 fffff800`039234fb : 00000000`0000001e ffffffff`c0000005 fffff880`04ff9d80 00000000`00000000 : nt!KeBugCheckEx
    fffff880`04ff9cd0 fffff800`038ebbb4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KipFatalFilter+0x1b
    fffff880`04ff9d10 fffff800`038c3a7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x83d
    fffff880`04ff9d50 fffff800`038c34fd : fffff800`039dac24 fffff880`04ffb5a0 00000000`00000000 fffff800`0381b000 : nt!_C_specific_handler+0x8c
    fffff880`04ff9dc0 fffff800`038c22d5 : fffff800`039dac24 fffff880`04ff9e38 fffff880`04ffaca8 fffff800`0381b000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`04ff9df0 fffff800`038d3361 : fffff880`04ffaca8 fffff880`04ffa500 fffff880`00000000 fffff880`04ffb0d0 : nt!RtlDispatchException+0x415
    fffff880`04ffa4d0 fffff800`038972c2 : fffff880`04ffaca8 fffff880`04ffb100 fffff880`04ffad50 fffff880`04ffb120 : nt!KiDispatchException+0x135
    fffff880`04ffab70 fffff800`03895e3a : 00000000`00000000 00000000`00000010 00000000`00000000 fffff880`04ffb100 : nt!KiExceptionDispatch+0xc2
    fffff880`04ffad50 fffff880`015c76b3 : fffff880`00000000 fffff880`04ffaf58 00000000`00000000 fffff880`04ffb0d0 : nt!KiPageFault+0x23a
    fffff880`04ffaee0 fffff880`015d76a6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : ksecdd!KsecProcessSecurityContext+0x293
    fffff880`04ffafe0 fffff880`018e33a4 : 00000000`00000000 fffff8a0`00000000 fffffa80`0a4ec400 00000000`00000000 : ksecdd!InitializeSecurityContextW+0x66
    fffff880`04ffb040 fffff880`018e422e : 00000000`00022770 00000000`00022770 00000000`00000100 01ccdd47`dc74e257 : tcpip!WfpAlepCreateTokenFromLogonId+0x1c4
    fffff880`04ffb160 fffff880`018e3122 : fffffa80`09f431e0 fffffa80`0a4ec470 fffffa80`09f431e0 fffffa80`058ec5b0 : tcpip!WfpAleCreateTokenFromLogonId+0x2e
    fffff880`04ffb1e0 fffff880`018e3795 : 00000000`00000000 fffffa80`0a4ec470 00000000`00000000 fffffa80`09f431e0 : tcpip!WfpAlepSetSecurity+0x282
    fffff880`04ffb2b0 fffff880`01904890 : 00000000`00004800 fffff800`03b8f4f4 00000000`0000fffc fffffa80`05a69490 : tcpip!WfpAleProcessSecureSocketControl+0xa5
    fffff880`04ffb440 fffff880`01904227 : 00000000`00000000 fffff880`018fb973 fffff880`04ffb6b0 fffffa80`058ec5b0 : tcpip!TcpSetSockOptEndpoint+0x150
    fffff880`04ffb540 fffff800`038a4618 : 80000800`00000000 80000800`00000001 00000000`00000000 00000000`00000000 : tcpip!TcpTlEndpointIoControlEndpointCalloutRoutine+0x107
    fffff880`04ffb5a0 fffff880`019042b0 : fffff880`01904120 00000000`00000000 fffff880`0178e500 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`04ffb680 fffff880`01292056 : fffffa80`0a54bf01 fffffa80`09de5160 fffffa80`0a54bf40 00000000`00000000 : tcpip!TcpTlEndpointIoControlEndpoint+0x70
    fffff880`04ffb6f0 fffff880`012916e0 : 00000000`980000c8 00000000`00000000 fffffa80`09de5160 fffffa80`05805ea0 : afd!WskProTLControlRequest+0x136
    fffff880`04ffb780 fffff880`01291afb : fffffa80`056761e0 fffffa80`09de5160 fffffa80`05805ea0 fffff800`03a38a08 : afd!WskProControlSocketCore+0x110
    fffff880`04ffb800 fffff880`071d46c0 : fffffa80`00000468 fffffa80`056761e0 00000000`00000000 00000000`000007ff : afd!WskProAPIControlSocket+0x9b
    fffff880`04ffb870 fffff880`071d3de6 : 00000000`00000001 fffff880`012a3400 00000000`00000000 00000000`00000700 : mrxsmb!SmbWskSetSocketOptions+0x1f0
    fffff880`04ffb930 fffff880`071cc082 : fffffa80`05a87940 fffffa80`05b5ea01 00000000`00000080 fffffa80`05a87940 : mrxsmb!SmbWskInitiateAsynchronousConnect+0x1a6
    fffff880`04ffba80 fffff880`071d23a9 : 00000000`00000000 00000000`00000008 fffffa80`05b5ea90 00000000`00000000 : mrxsmb!RxCeInitiateConnectRequest+0x52
    fffff880`04ffbab0 fffff880`071d2ba5 : fffff880`071e6f00 fffffa80`05b5ea90 fffff880`0161b110 00000000`aaaaaaaa : mrxsmb!RxCeBuildConnectionOverMultipleTransports+0x659
    fffff880`04ffbc40 fffff880`016011b1 : fffff880`0161c4a8 00000000`00000080 fffff880`0161b110 fffffa80`05b5eb30 : mrxsmb!RxCeInitiateConnection+0x151
    fffff880`04ffbc80 fffff800`03b32fee : fffff880`0161c4a8 fffff880`0161c8f8 fffff880`04ffbd00 fffffa80`09f45700 : rdbss!RxpWorkerThreadDispatcher+0x1a1
    fffff880`04ffbd40 fffff800`038895e6 : fffff880`03164180 fffffa80`09f45750 fffffa80`088fa040 fffff880`01435384 : nt!PspSystemThreadStartup+0x5a
    fffff880`04ffbd80 00000000`00000000 : fffff880`04ffc000 fffff880`04ff6000 fffff880`04ff9de0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ksecdd!KsecProcessSecurityContext+293
    fffff880`015c76b3 ff5010          call    qword ptr [rax+10h]
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  ksecdd!KsecProcessSecurityContext+293
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ksecdd
    
    IMAGE_NAME:  ksecdd.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ec483fd
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_ksecdd!KsecProcessSecurityContext+293
    
    BUCKET_ID:  X64_0x1E_c0000005_ksecdd!KsecProcessSecurityContext+293
    
    Followup: MachineOwner
    ---------
    Uninstall Mcaffe anti-virus, it is known to cause crashes on some Windows 7 systems.
    How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

    You can use MSE while analyzing the crashes.
    Microsoft Security Essentials*- Free Antivirus for Windows
    Use the Windows Firewall also, check that it is enabled.

    These drivers are out of date and known to cause BSoDs:

    Code:
    GEARAspiWDM.sys Mon May 18 20:17:04 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes
    Uninstall iTunes, for testing purposes.

    Code:
    hamachi.sys  Thu Feb 19 18:36:41 2009 - LogMeIn Hamachi Virtual etwork interface driver
    Update the driver/app or uninstall LogMeIn.

    Code:
    mwlPSDFilter.sys Tue Jun 02 18:07:30 2009 - EgisTec Inc. Fingerprint Biometrics
    Go to your Acer Support/Driver website and update this driver and all the others you find there.

    Windows System Event Logs:

    Several McAfee related errors, confirmation it is causing instability.
    Code:
    Event[7]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-01-27T23:02:45.831
      Event ID: 7001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Oli-PC
      Description: 
    The McAfee Network Agent service depends on the McAfee Firewall Core Service service which failed to start because of the following error: 
    The dependency service or group failed to start.
    Last edited by Dave76; 30 Jan 2012 at 09:53.
      My Computer


  8. Posts : 9
    Windows 7 Home Premium
    Thread Starter
       #8

    Thank you very much! I'll do what i can to get it sorted, fingers crossed
      My Computer


  9. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #9

    Please re-read my last post as I have been updating information as I found it.
      My Computer


  10. Posts : 9
    Windows 7 Home Premium
    Thread Starter
       #10

    Thanks very much, i'll have a crack at all of these and let you know the results
      My Computer


 
Page 1 of 2 12 LastLast

  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 11:25.
Find Us