0383950drv.sys ???  


  1. Posts : 614
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
       #1

    0383950drv.sys ???


    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Skyler\AppData\Local\Temp\Rar$DIa0.126\081413-32339-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Machine Name:
    Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a1670
    Debug session time: Wed Aug 14 17:39:57.894 2013 (UTC - 5:00)
    System Uptime: 0 days 0:00:08.893
    Loading Kernel Symbols
    .......................................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff880009aaff8, 0, fffff80002eca836, 0}
    
    *** WARNING: Unable to verify timestamp for 0383950drv.sys
    *** ERROR: Module load completed but symbols could not be loaded for 0383950drv.sys
    
    Could not read faulting driver name
    Probably caused by : 0383950drv.sys ( 0383950drv+4bc41 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff880009aaff8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002eca836, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310b100
    GetUlongFromAddress: unable to read from fffff8000310b1c0
     fffff880009aaff8 Nonpaged pool
    
    FAULTING_IP: 
    nt!memcpy+266
    fffff800`02eca836 488b440a08      mov     rax,qword ptr [rdx+rcx+8]
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880009a8e80 -- (.trap 0xfffff880009a8e80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a000739f40
    rdx=ffffffe0002710b0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002eca836 rsp=fffff880009a9018 rbp=fffff880009a90f8
     r8=0000000000007880  r9=00000000000000fa r10=0000000000000000
    r11=fffff8a000738020 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!memcpy+0x266:
    fffff800`02eca836 488b440a08      mov     rax,qword ptr [rdx+rcx+8] ds:fffff880`009aaff8=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002f51be0 to fffff80002ed3c00
    
    STACK_TEXT:  
    fffff880`009a8d18 fffff800`02f51be0 : 00000000`00000050 fffff880`009aaff8 00000000`00000000 fffff880`009a8e80 : nt!KeBugCheckEx
    fffff880`009a8d20 fffff800`02ed1d2e : 00000000`00000000 fffff880`009aaff8 ffff0800`00000000 fffff8a0`00738000 : nt! ?? ::FNODOBFM::`string'+0x4518f
    fffff880`009a8e80 fffff800`02eca836 : fffff800`02efccce fffff8a0`00738000 fffff880`009a90f8 fffff880`037b7000 : nt!KiPageFault+0x16e
    fffff880`009a9018 fffff800`02efccce : fffff8a0`00738000 fffff880`009a90f8 fffff880`037b7000 00000000`000007ff : nt!memcpy+0x266
    fffff880`009a9020 fffff800`02e813d8 : fffff880`009a90f8 fffff880`04fc94d0 fffff880`009a90d0 00000000`00007887 : nt!RtlInsertElementGenericTableFullAvl+0xce
    fffff880`009a9060 fffff880`04fa1c41 : 00000000`00007877 00000000`00000000 00000000`c0000001 fffff880`04fa1e2b : nt!RtlInsertElementGenericTableAvl+0x48
    fffff880`009a90b0 00000000`00007877 : 00000000`00000000 00000000`c0000001 fffff880`04fa1e2b 00000000`78777877 : 0383950drv+0x4bc41
    fffff880`009a90b8 00000000`00000000 : 00000000`c0000001 fffff880`04fa1e2b 00000000`78777877 fffff880`037b003c : 0x7877
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    0383950drv+4bc41
    fffff880`04fa1c41 ??              ???
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  0383950drv+4bc41
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: 0383950drv
    
    IMAGE_NAME:  0383950drv.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cde94bf
    
    FAILURE_BUCKET_ID:  X64_0x50_0383950drv+4bc41
    
    BUCKET_ID:  X64_0x50_0383950drv+4bc41
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm 0383950drv
    start             end                 module name
    fffff880`04f56000 fffff880`04fec000   0383950drv T (no symbols)           
        Loaded symbol image file: 0383950drv.sys
        Image path: \SystemRoot\system32\DRIVERS\0383950drv.sys
        Image name: 0383950drv.sys
        Timestamp:        Sat Nov 13 07:38:07 2010 (4CDE94BF)
        CheckSum:         00091EFC
        ImageSize:        00096000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0383950drv.sys cant find any info on this driver.
    Any help would be appreciated, if found please let me know how and where found. Thanks:)

    Update : Possibly?
    http://h20000.www2.hp.com/bizsupport..._I17346-100181
      My Computer


  2. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #2

    TDSSKILLER

    download link TDSSKiller

    Save to the Desktop

    Right-click the program and select


    When the TDSSKiller console opens, click on: Change Parameters
    Under Additional Options, place a check in the box next to: Detect TDLFS File System

    Click: OK


    Press: Start Scan


    If a suspicious object is detected, the default action is Skip, leave it as is, and click on: Continue
    If malicious objects are found, they show in the Scan results.
    Ensure Cure (the default) is selected, then click: Continue > Reboot now, to finish the cleaning process.
    (Note: If Cure is not available, select Skip, >>Do not select: Delete<<)


    When done, the tool outputs its log to the disk with the Windows Operating System, normally C:\


    Logs have a name like:
    C:\TDSSKiller.X.X.X_12.04.2013_15.31.43_log.txt


    Please post the TDSSKiller log in your reply.
      My Computer


  3. Posts : 614
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #3

    VistaKing said:
    TDSSKILLER

    download link TDSSKiller

    Save to the Desktop

    Right-click the program and select


    When the TDSSKiller console opens, click on: Change Parameters
    Under Additional Options, place a check in the box next to: Detect TDLFS File System

    Click: OK


    Press: Start Scan


    If a suspicious object is detected, the default action is Skip, leave it as is, and click on: Continue
    If malicious objects are found, they show in the Scan results.
    Ensure Cure (the default) is selected, then click: Continue > Reboot now, to finish the cleaning process.
    (Note: If Cure is not available, select Skip, >>Do not select: Delete<<)


    When done, the tool outputs its log to the disk with the Windows Operating System, normally C:\


    Logs have a name like:
    C:\TDSSKiller.X.X.X_12.04.2013_15.31.43_log.txt


    Please post the TDSSKiller log in your reply.
    Well not my pc, i was asking because i couldnt find any info on it.
    Here check this thread
    Help with BSOD (page fault in nonpaged area)
      My Computer


  4. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #4

    Thank you I posted there .
      My Computer


 

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 21:38.
Find Us