high cpu/ram usage not related to any visible processes


  1. Posts : 58
    windows 7 premium x64
       #1

    high cpu/ram usage not related to any visible processes


    i have been having unusually high cpu and ram usage thats not connected to any processes i can see in the task manager for about 2 days. today i got a blue screen from it, files are attached. i havent done a system restore yet but i may if its suggested. i've done mbam and avast full scans with no results already. also how do you read the crash dump files?
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    We have a few tutorials on how to get started: Crash and lockup debug 'How To' - Windows 7 Help Forums

    A few recommendations for now would be:
    Comodo and Avast! contribute to BSoDs', Remove them and use Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
    • Do not start the trial version of MalwareBytes

    You may also take a look at:

    Reduce items at start up:
    Your Antivirus software is basically whats just needed there.

    Use the System File Checker tool and Run Disk Check:

    Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:


    Observe for further BSoD;s.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1, {77ac138a, 0, ffff, fffff8800b061ca0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    APC_INDEX_MISMATCH (1)
    This is a kernel internal error. The most common reason to see this
    bugcheck is when a filesystem or a driver has a mismatched number of
    calls to disable and re-enable APCs. The key data item is the
    Thread->CombinedApcDisable field. This consists of two separate 16-bit
    fields, the SpecialApcDisable and the KernelApcDisable. A negative value
    of either indicates that a driver has disabled special or normal APCs
    (respectively) without re-enabling them; a positive value indicates that
    a driver has enabled special or normal APCs (respectively) too many times.
    Arguments:
    Arg1: 0000000077ac138a, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: fffff8800b061ca0, Call type (0 - system call, 1 - worker routine)
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    +0
    00000000`77ac138a ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1
    
    PROCESS_NAME:  HD-Service.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800026851a9 to fffff80002685c00
    
    STACK_TEXT:  
    fffff880`0b061a68 fffff800`026851a9 : 00000000`00000001 00000000`77ac138a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`0b061a70 fffff800`026850e0 : 00000000`000003ec fffffa80`0cfaa260 00000000`0425e550 fffff800`00000008 : nt!KiBugCheckDispatch+0x69
    fffff880`0b061bb0 00000000`77ac138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
    00000000`0425e4c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ac138a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceExit+245
    fffff800`026850e0 4883ec50        sub     rsp,50h
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiSystemServiceExit+245
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6
    
    FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
    
    BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
    
    Followup: MachineOwner
    ---------
    
    
      My Computer


  3. Posts : 58
    windows 7 premium x64
    Thread Starter
       #3

    thanks, i recognize the process, also do you know a way i can get comodo-like notifications for mse? i have unfixable errors from the checkdisk utility and im not sure how to fix those. also i thought that mse wasnt that good based on the av test results.
      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 23:21.
Find Us