Ntoskrnl.exe chewing up CPU

This is driving me crazy.
Running Win8 x64. i7 8GB X1.
Everything up to date.
I'm extremely careful about extra unneeded startup processes etc.
Recently I'll be going along and notice, gee this is running hot and the fan is running constant.
I notice ntoskrnl.exe is chewing 30% CPU
I reboot and things immediately cool down and ntoskrnl.exe is back down to under 1% CPU
I have been having issues with WIFI (that many folks have, running latest from Intel).
Googling ntoskrnl.exe hogging CPU is a common issue but many kernel level drivers fall under that task.
Some folks blame WIFI drivers. But when in this CPU piggy state if I turn WIFI off with the switch, the CPU is still stuck at 30%.
When I reboot I could go for hours with no issue at all.
This did not used to happen and I'm puzzled, but I have been playing with WIFI drivers and settings (which has also been very frustrating, but I have that "Fixed" by a quirky procedure, but don't know if that is anyway related to this CPU pig thing).

I found the problem and once I did find it I googled for it and found a thread right here about it.
http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X220-Ricoh-Media-card-driver-high-system-cpu-u...

Similar Messages

  • Netbeans(java.exe) chewing up CPU

    [Please excuse me if this shows up twice but after make my last post this thread never showed up!]
    Hello, everytime I run an emu, no matter which one including wtk, netbeans java.exe starts chewing up lots of CPU time it's like at 98percent and nb comes to a halt and Ihave to wait a few minutes for it to settle down. I really gets bad when I do , "System.out.println()" on a large buffer that really kills it. so I now I can't display large buffers and I have no alternative.
    What can I do to stop java.exe from chewing up cpu time when I run and/or print large buffers?
    My Environment:
    CPU: AMD 64 +3200
    MEM: 1GB
    OS: XP Pro SP2 (version 5.1 )
    EMU: Nokia S60 3rd Ed. / Nokia S40 / Sun WTK 2.5.1
    Java: 1.5.0_12
    VM: Java Hotspot(TM) Client VM 1.5.0_12-b04
    NB Product Ver: Netbeans IDE 5.5.1 (Build 20070422300)
    I would appreciate any help!
    Thankyou.

    I found the problem and once I did find it I googled for it and found a thread right here about it.
    http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X220-Ricoh-Media-card-driver-high-system-cpu-u...

  • System (ntoskrnl.exe) high cpu usage in Windows 8.1

    Sir/Mam,
    I'm having this issue since last week, when i checked it is the "system" (ntoskrnl.exe) file which is using upto 18-24% of my CPU and causing all other applications to stutter for a second (incluuding Media player, mouse pointer, everything).
    By using a Process Explorer software i found out that it's related to these values running under that file:
    " ntoskrnl.exe!RtlSidHashLookup+0x1ffc  "
    It slows down my PC for a second and it happens after every 5-6 seconds (approx.).
    Using Microsoft Windows 8.1
    Lenovo Z50-70
    Need help.

    Hi,
    The WPA shows that it is WmiPrvSE.exe (WMI Provider Host)that occupies up to 20% CPU, and three threads are the causes, 8328\7988\8828. but hard to find deeper information from this, so please use process Explorer or process monitor to find more information
    about WmiPrvSE.exe and the 3 threads, you can refer to this link
    http://social.technet.microsoft.com/Forums/en-US/77f8bc7d-663c-4c33-b732-f362c5585300/service-host-local-system-is-intermittently-using-30-of-my-cpu-windows-81?forum=w8itproperf
    Regarding to the wireless or LAN driver, I suggest you update the driver to latest version if it doesn't work fine.
    Yolanda Zhu
    TechNet Community Support

  • CPU 99% consumption by ntoskrnl.exe!KeRemoveQueue+0x488

    Hi,
    CPU 99% consumption by ntoskrnl.exe!KeRemoveQueue+0x488
    whats the issue with my windows 8.1 ???

    In order to diagnose your problem we need to run Windows Performance toolkit the instructions for which can be found in this
    wiki
    If you have any questions feel free to ask
    Wanikiya and Dyami--Team Zigzag

  • High CPU usage on all cores by ntoskrnl.exe? Help needed urgently Please.

    ntoskrnl.exe, system, has multiple cores running with high usage, locking up my system when using programs.
    After looking through the forums I did the following:
    I ran
    sfc /scannow but nothing found. 
    I used process Explorer to find that the system has a thread <ntoskrnl.exe!TtlSid HashLookup+0x 1ffc> that
    is using up 40+% of all four cpu cores. Looks like a driver fault with 8.1, but cannot pinpoint the device. Any clues msg me. 
    I have created an etl file that contains usage data. this is present here:
    https://dl.dropboxusercontent.com/u/8554814/highCPUUsage.zip
    Would be a lot of help if this can be resolved. please help.

    forgot to ask, may I know your PC model?
    mostly is related to the network, networking software, or software which need internet connection
    did you already updated all the network driver?
    is there any networking software or downloaded software? may I know your antivirus status? firewall?
    try clean boot and go to safemode to check, choose safe mode only, safe mode with networking and normal mode without internet (unplug cable or disconnect Wifi)

  • Windows 8.1 slows way down by 100% Disk Usage whenever playing PC Games (ntoskrnl.exe System)

    This issue has been going on for just a couple days. As soon as I launch any game on my PC my computer immediately slows to a crawl. It has never froze nor have I got the BSOD. I have noticed (in the task manager) that the System (ntoskrnl.exe)
    sucks the life out of my Disk and it jumps to 90-100%.  I have read about 50 articles about this and many people seem to have unique reasons why this happens. It has never happened before on Win7 and just started happening in Win 8.1. So things I have
    tried:
    Disable unnecessary windows services.
    Changed Power Options and tweaked with some of the advanced settings.
    Scanned for Malware (none found)
    Scanned for viruses (none found) 
    Disabled Windows Media Center (since the problem started shortly after installing it)
    Performed Deep scan for viruses in the registry (none found)
    Windows Memory Diagnostics Tool (no errors found) 
    As I type this I am performing another virus scan and my Disk is at 99% as shown in the task manager. I assume this is because of Norton (and System) sucking up the HDDs. Like I said this happens every time during
    gaming. Not sure if there is a connection between the two. That is just when I notice the issue.
    So the problem at hand makes gaming (and any other application while gaming) nearly impossible. The games and programs all work just at a very slow speed. I finally asked tech support from Microsoft and they said (without letting me explain much
    detail) that I had a virus and they tried to sell me anti-virus software. Anyone able to help me resolve this issue? It is "killing" me that I cannot find a resolution for this. 
    I will post screen shot of anything that might be of help if you need it. 
    Thanks

    In order to diagnose your problem you will need to download and install the below
    Install the WPT (windows Performance Toolkit) 
    http://www.microsoft.com/en-us/download/details.aspx?id=30652
    Help with installation (if needed) is here
    When you have, open an elevated command prompt and type the following 
    WPRUI.exe (which is the windows performance recorder) and check off the boxes for the following:
    First level triage, CPU usage, Disk IO.  
    If your problem is not CPU or HD then check off the relevant box/s as well (for example networking or registry)  Please configure yours as per the below snip
    Click Start
    Let it run for 60 secs or more and save the file (it will show you where it is being saved and what the file is called)
    Zip the file and upload to us on Onedrive (or any file sharing service) and give us a link to it in your next post.
    Wanikiya and Dyami--Team Zigzag

  • Explorer.exe consuming 100% CPU after resuming from hibernation

    Hello,
    For the last months, I repeatedly have the problem that sometimes (every 2nd or 3rd time) after resuming from hibernation, in a few cases also after disconnecting from the Internet, one or more instances of explorer.exe are consuming 100% CPU, but never
    the shell instance.
    I tried figuring out what it was doing, but I was unsuccessful so far.
    Here is a stack of the thread which consumed most of the CPU:
    0, ntoskrnl.exe!KiDeliverApc+0x166
    1, ntoskrnl.exe!KiSwapThread+0x31f
    2, ntoskrnl.exe!KiCommitThreadWait+0x129
    3, ntoskrnl.exe!ExpWaitForResource+0x29f
    4, ntoskrnl.exe!ExEnterPriorityRegionAndAcquireResourceExclusive+0x1ad
    5, win32k.sys!EnterCritAvoidingDitHitTestHazard+0x13
    6, win32k.sys!NtUserMessageCall+0x28
    7, ntoskrnl.exe!KiSystemServiceCopyEnd+0x13
    8, user32.dll!NtUserMessageCall+0xa
    9, user32.dll!SendMessageWorker+0x168
    10, user32.dll!SendMessageW+0xfb
    11, ExplorerFrame.dll!CNscTree::_TreeInvalidateItemInfo+0xd0
    12, ExplorerFrame.dll!CNscTree::_EnumBackgroundDone+0xb4a14
    13, ExplorerFrame.dll!CNscTree::OnQIUpdateEnumDone+0x93
    14, ExplorerFrame.dll!CNscEnumQueueItem::Dispatch+0xcf
    15, ExplorerFrame.dll!CTaskLock::DispatchQueueItem+0xc5
    16, ExplorerFrame.dll!CNscTree::_SubClassTreeWndProc+0x118
    17, ExplorerFrame.dll!CNscTree::s_SubClassTreeWndProc+0x5f
    18, comctl32.dll!CallNextSubclassProc+0xe0
    19, comctl32.dll!MasterSubclassProc+0xa2
    20, user32.dll!UserCallWinProcCheckWow+0x149
    21, user32.dll!DispatchMessageWorker+0x1a7
    22, AppVEntSubsystems64.dll!VirtualizeCurrentThread+0x1e492
    23, ExplorerFrame.dll!CExplorerFrame::FrameMessagePump+0xe3
    24, ExplorerFrame.dll!BrowserThreadProc+0x5e
    25, ExplorerFrame.dll!BrowserNewThreadProc+0x3a
    26, ExplorerFrame.dll!CExplorerTask::InternalResumeRT+0x12
    27, ExplorerFrame.dll!CRunnableTask::Run+0x114
    28, shell32.dll!CShellTaskThread::ThreadProc+0x2a3
    29, shell32.dll!CShellTaskThread::s_ThreadProc+0x2f
    30, SHCore.dll!StrRetToBSTR+0x19f
    31, kernel32.dll!BaseThreadInitThunk+0x22
    32, ntdll.dll!RtlUserThreadStart+0x34
    I was hoping I could identify a rogue shell extension or something similar, but I didn't find any such evidence so far.
    In case you need this information, this is a list of my shell extensions/copy hooks/context menu handlers/drag&drop handlers (without duplicates):
    + " SkyDrivePro1 (ErrorConflict)" "Microsoft OneDrive for Business Extensions" "Microsoft Corporation" "c:\program files\microsoft office 15\root\vfs\programfilesx64\microsoft office\office15\grooveex.dll" "12.11.2014 01:13"
    + "{C52AF81D-F7A0-4AAB-8E87-F80A60CCD396}" "" "Apache Software Foundation" "c:\program files (x86)\openoffice 4\program\shlxthdl\shlxthdl.dll" "20.09.2013 12:50"
    + "{C52AF81D-F7A0-4AAB-8E87-F80A60CCD396}" "" "Apache Software Foundation" "c:\program files (x86)\openoffice 4\program\shlxthdl\shlxthdl_x64.dll" "20.09.2013 12:41"
    + "7-Zip" "7-Zip Shell Extension" "Igor Pavlov" "c:\program files\7-zip\7-zip32.dll" "18.04.2011 19:34"
    + "7-Zip" "7-Zip Shell Extension" "Igor Pavlov" "c:\program files\7-zip\7-zip.dll" "18.04.2011 19:35"
    + "ANotepad++64" "ShellHandler for Notepad++ (64 bit)" "" "c:\program files (x86)\notepad++\nppshell_06.dll" "12.05.2014 10:49"
    + "Ath_CopyHook" "Bluetooth File Transfer Plugin" "Qualcomm®Atheros®" "c:\program files (x86)\bluetooth suite\folderviewimpl.dll" "25.09.2013 10:58"
    + "Atheros" "Atheros Bluetooth Module" "Qualcomm®Atheros®" "c:\program files (x86)\bluetooth suite\btvappext.dll" "25.09.2013 10:58"
    + "DropboxExt" "Dropbox Shell Extension" "Dropbox, Inc." "c:\users\david\appdata\roaming\dropbox\bin\dropboxext64.24.dll" "24.06.2014 01:32"
    + "DropboxExt1" "Dropbox Shell Extension" "Dropbox, Inc." "c:\users\david\appdata\roaming\dropbox\bin\dropboxext.24.dll" "24.06.2014 01:31"
    + "FTShellContext" "Atheros Bluetooth Module" "Qualcomm®Atheros®" "c:\program files (x86)\bluetooth suite\shellcontextext.dll" "25.09.2013 10:58"
    + "GDContextMenu" "Google Drive shell extension" "Google" "c:\program files (x86)\google\drive\contextmenu64.dll" "16.01.2015 01:57"
    + "GDriveBlacklistedOverlay" "Google Drive shell extension" "Google" "c:\program files (x86)\google\drive\googledrivesync64.dll" "16.01.2015 01:56"
    + "igfxcui" "igfxpph Module" "Intel Corporation" "c:\windows\system32\igfxpph.dll" "09.09.2013 18:26"
    + "LockHunterShellExt" "LockHunter Explorer Extension" "Crystal Rich Ltd" "c:\program files\lockhunter\lhshellext32.dll" "25.03.2009 08:53"
    + "LockHunterShellExt" "LockHunter Explorer Extension" "Crystal Rich Ltd" "c:\program files\lockhunter\lhshellext64.dll" "28.04.2009 10:21"
    + "PDF Shell Extension" "PDF Shell Extension" "Adobe Systems, Inc." "c:\program files (x86)\common files\adobe\acrobat\activex\pdfshell.dll" "11.05.2013 10:34"
    + "PushbulletCtx" "" "" "File not found: :/Program Files (x86)/Pushbullet/pushbullet_ctx.DLL" ""
    + "RecuvaShellExt" "Recuva shell extensions" "Piriform Ltd" "c:\program files\recuva\recuvashell64.dll" "14.03.2014 12:41"
    + "SD360" "360 Total Security" "" "c:\program files (x86)\360\total security\menuex64.dll" "12.01.2015 03:55"
    + "SourceGearDiffMergeShellExtension32" "SourceGear DiffMerge ShellExtension 32" "SourceGear LLC" "c:\program files (x86)\sourcegear\common\diffmerge\sourcegeardiffmergeshellextension32.dll" "23.10.2013 19:15"
    + "SourceGearDiffMergeShellExtension64" "SourceGear DiffMerge ShellExtension 64" "SourceGear LLC" "c:\program files\sourcegear\common\diffmerge\sourcegeardiffmergeshellextension64.dll" "23.10.2013 19:17"
    + "StartMenuExt" "Start Menu Helper Extension" "IvoSoft" "c:\windows\syswow64\startmenuhelper32.dll" "20.04.2014 18:17"
    + "StartMenuExt" "Start Menu Helper Extension" "IvoSoft" "c:\windows\system32\startmenuhelper64.dll" "20.04.2014 18:16"
    + "WinRAR32" "WinRAR shell extension" "Alexander Roshal" "c:\program files\winrar\rarext32.dll" "02.12.2014 11:07"
    + "WinRAR" "WinRAR shell extension" "Alexander Roshal" "c:\program files\winrar\rarext.dll" "02.12.2014 11:07"
    + "WinSCPCopyHook" "Drag&Drop shell extension for WinSCP (64-bit)" "Martin Prikryl" "c:\program files (x86)\winscp\dragext64.dll" "14.08.2013 12:22"
    I you have any clue what might be going, I would be very happy to hear it. It's really annoying, as I have to kill explorer.exe and thereby close all my folder windows when this happens.
    Thank you!
    Best regards,
    David Trapp

    Hello,
    thanks for having a look. However, I already ran SFC before posting on this forum (as part of my own investigation) and it came back clean. RescueTime (a time tracking tool) is probably not the culprit because it happened also several times in the past without
    RescueTime being running (that was because I had accidentally removed it from autorun at that time).
    Unfortunately, I can't follow your "invalid date" explanation. I don't think an "invalid date" is anywhere involved; in fact, the method in question is called "_TreeInvalidateItemInfo" and not "_TreeInvalidDateItemInfo"
    (note that there is only one "d"), so I assume its job is just to invalidate (and in turn, refresh) the cached information about nodes in the left pane's folder tree of the explorer window(s) - since the folder tree is the only NamespaceTreeControl
    (whose corresponding class name is CNscTree) in explorer folder view windows. As I see it, something is causing explorer to repeatedly refresh the folder tree data, but I am stuck at finding out what exactly.
    Best regards,
    David Trapp
    EDIT: Disassembling ExplorerFrame!CNscTree::_TreeInvalidateItemInfo confirms that, because it seems to call TreeView_SetItem for a tree node and its parent (possibly with all fields set to *_CALLBACK), and CNscTree::_UpdateItemDisplayInfo
    for the parent node.
    EDIT2: I'd love to dig more into the trace, however I am hitting a wall at function names/addresses. Everywhere where I would expect a function name/address (such as the "by stack" views), I only see question marks instead. What
    could be the reason?

  • BSOD ntoskrnl.exe?

    Got a bsod with 0x00000124 .
    Heard blue screen viewer can be wrong sometimes but it said ntoskrnl.exe was the problem?
    Not sure if I'm using this thing correctly but this is the minidump http://1drv.ms/1wvmcmq
    Also am running driver verifier and restarted.
    It's suppose to take a while right?
    And can I continue playing while it runs?

    Cshn
    This was called a BCC124 and it is related to hardware.  SInce the DMP references Genuine Intel I would start by running a CPU stress test
    Try this free stress test:  http://www.mersenne.org/freesoft/
    Prime95 Setup;
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
    The Test selection box and the stress.txt file describes what components that the program stresses.
    Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see
    if that helps.
    If you continue to get BSODs here are some more things you may want to consider.
    This is usually heat related, defective hardware, memory or even processor though
    it is"possible" that it is driver related (rare).
    Stop 0x124 - what it means and what to try
    Synopsis:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
     Generic "Stop 0x124" Troubleshooting Strategy:
    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
    ways.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
    free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications,
    games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether
    the machine is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
    Should you find yourself in the situation of having performed all of the steps
    above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
    More advanced reading can be found here from a MS MVP IT PRO
    http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\110414-2854-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\symbols*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
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e53890
    Debug session time: Tue Nov 4 01:05:10.806 2014 (UTC - 5:00)
    System Uptime: 0 days 0:26:06.602
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa800703c028, ba000000, 58000402}
    Probably caused by : GenuineIntel
    Followup: MachineOwner
    6: kd> !analyze -v
    * Bugcheck Analysis *
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800703c028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000058000402, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR: 0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: chrome.exe
    CURRENT_IRQL: f
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    STACK_TEXT:
    fffff880`0310ab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME: GenuineIntel
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    IMAGE_VERSION:
    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae
    FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Disk utilization 100% for very long time - ntoskrnl.exe

    I have HP ProBook 4530s running Windows 8.1 Pro x64. Until recently it worked without any problem but since last week disk utilization has been constantly 100% immediately after laptop has been turned on and I have logged on with my domain user account (this
    morning 100% disk utilization lasted for almost half an hour). In task manager ntoskrnl.exe is the one who is killing my hard disk. Is there any official Microsoft solution for this - I definitely want to avoid reinstalling Windows from scratch. I saw on net
    this was almost common bug in Windows 8.1 but without any solution working 100%.

    In order to diagnose your problem you will need to download and install the below
    Install the WPT (Windows Performance Toolkit) 
    http://www.microsoft.com/en-us/download/details.aspx?id=30652
    Help with installation (if needed) is here
    When you have, open an elevated command prompt and type the following 
    WPRUI.exe (which is the windows performance recorder) and check off the boxes for the following:
    First level triage (if available), CPU usage, Disk IO.  
    If your problem is not CPU or HD then check off the relevant box/s as well (for example networking or registry)  Please configure yours as per the below snip
    Click Start
    Let it run for 60 secs or more and save the file (it will show you where it is being saved and what the file is called)
    Zip the file and upload to us on Onedrive (or any file sharing service) and give us a link to it in your next post.
    Wanikiya and Dyami--Team Zigzag

  • BSOD DRIVER_POWER_STATE FAILURE 0x1000009f ntoskrnl.exe

    Hi there,
    I get a BSOD every once in a while, but only for a few weeks by now:
    Sometimes while working on the computer it just freezes (not using any certain program), I can't use my mouse/ keyboard, sound stops, waiting a long time sometimes helps, but after 10-15 minutes I usually give up and reset.
    Then rebooting most of the time does not work propperly: The computer waits about 30secs showing my motherboard instructions (BIOS key, boot menu key, ...), then freezes for about 5-10 minutes showing the windows logo and saying something like "windows
    is starting up" (the black screen with the 4 colored windows logo). Sometimes it doesn't continue from there at all. If it does the computer runs fine (after the 10min boot). Otherwise I reset it again, Windows asks whether I want to start normal or safe
    mode, normal works.
    Yesterday windows told me while booting that I'd need to do a system restore, did that. Works for now, but I'd like to really solve the problem.
    Checking the last crashes I always have the same BSOD:
    Problemsignatur
    Problemereignisame:    BlueScreen
    Betriebsystemversion:    6.1.7601.2.1.0.256.1
    Gebietsschema-ID:    1031
    Weitere Informationen über das Problem
    BCCode:    1000009f
    BCP1:    0000000000000004
    BCP2:    0000000000000258
    BCP3:    FFFFFA8003CFF040
    BCP4:    FFFFF80000B9C510
    OS Version:    6_1_7601
    Service Pack:    1_0
    Product:    256_1
    Bucket-ID:    X64_0x9F_4_IMAGE_nvstor.sys
    Serverinformationen:    7ef390d9-572b-4571-853a-9a9c91b1c365
    I'm not really into understanding the Minidump, just saw it it the ntoskrnl.exe at ntoskrnl.exe+ 78a8a causing the problem. My Minidump: https://www.dropbox .com/s/1351wa0e47hs4qt/042614-411998-01.dmp (delete the space behind dropbox. Can't upload files...)
    My system:
    AMD Athlon II X2 250 (3.0Ghz)
    Asus M4N68T-M LE V2
    Sapphire/ AMD HD4850
    2x2GB RAM
    anything missing?
    Thanks for your help!

    Thanks very much for the kernel-dump!
    DRIVER_POWER_STATE_FAILURE (9f)
    This bug check indicates that the driver is in an inconsistent or invalid power state.
    0: kd> knL
    # Child-SP RetAddr Call Site
    00 fffff800`00b9c4d8 fffff800`02d117e6 nt!KeBugCheckEx
    01 fffff800`00b9c4e0 fffff800`02ec234c nt!PnpBugcheckPowerTimeout+0x76
    02 fffff800`00b9c540 fffff800`02c8a85c nt!PopBuildDeviceNotifyListWatchdog+0x1c
    03 fffff800`00b9c570 fffff800`02c8a6f6 nt!KiProcessTimerDpcTable+0x6c
    04 fffff800`00b9c5e0 fffff800`02c8a5de nt!KiProcessExpiredTimerList+0xc6
    05 fffff800`00b9cc30 fffff800`02c8a3c7 nt!KiTimerExpiration+0x1be
    06 fffff800`00b9ccd0 fffff800`02c778ca nt!KiRetireDpcList+0x277
    07 fffff800`00b9cd80 00000000`00000000 nt!KiIdleLoop+0x5a
    Not really much info in the call stack, just a few PnP routines that call into the bugcheck eventually. No driver in the stack, etc.
    0: kd> !locks
    **** DUMP OF ALL RESOURCE OBJECTS ****
    KD: Scanning for held locks..
    Resource @ nt!IopDeviceTreeLock (0xfffff80002e83ce0) Shared 1 owning threads
    Threads: fffffa8003cff040-01<*>
    KD: Scanning for held locks.
    Resource @ nt!PiEngineLock (0xfffff80002e83be0) Exclusively owned
    Contention Count = 11
    NumberOfExclusiveWaiters = 1
    Threads: fffffa8003cff040-01<*>
    Threads Waiting On Exclusive Access:
    fffffa8003cfe660
    0: kd> !thread fffffa8003cff040
    THREAD fffffa8003cff040 Cid 0004.002c Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
    fffff88002fd21f0 SynchronizationEvent
    Not impersonating
    DeviceMap fffff8a0000060c0
    Owning Process fffffa8003cecb30 Image: System
    Attached Process N/A Image: N/A
    Wait Start TickCount 5039734 Ticks: 38462 (0:00:10:00.011)
    Context Switch Count 356079 IdealProcessor: 0 NoStackSwap
    UserTime 00:00:00.000
    KernelTime 00:00:05.896
    Win32 Start Address nt!ExpWorkerThread (0xfffff80002c89150)
    Stack Init fffff88002fd2db0 Current fffff88002fd1f10
    Base fffff88002fd3000 Limit fffff88002fcd000 Call 0
    Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP RetAddr : Args to Child : Call Site
    fffff880`02fd1f50 fffff800`02c755f2 : fffffa80`03cff040 fffffa80`03cff040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`02fd2090 fffff800`02c8699f : fffffa80`07524c80 fffff800`02c64a72 00000000`00000000 fffffa80`04686000 : nt!KiCommitThreadWait+0x1d2
    fffff880`02fd2120 fffff880`010dbf21 : fffffa80`06ea6600 00000000`00000000 fffff880`02fd2600 fffffa80`06ea6600 : nt!KeWaitForSingleObject+0x19f
    fffff880`02fd21c0 fffff880`010ddb41 : 00000000`00000000 fffff880`02fd2620 fffff880`010e9a60 00000000`00000000 : storport!RaSendIrpSynchronous+0x71
    fffff880`02fd2220 fffff880`010e13f1 : 00000000`00000000 fffff880`00000000 fffff880`02fd24c0 fffff880`02fd2628 : storport!RaidBusEnumeratorIssueSynchronousRequest+0x91
    fffff880`02fd2330 fffff880`010e151e : fffffa80`068d2ad0 fffff880`00000000 fffff880`02fd2420 fffff880`02fd24c0 : storport!RaidBusEnumeratorIssueReportLuns+0x71
    fffff880`02fd2380 fffff880`010e789b : 00000000`00000000 fffff6fc`00000000 00000000`00000000 fffff880`02fd24c0 : storport!RaidBusEnumeratorGetLunListFromTarget+0xae
    fffff880`02fd2400 fffff880`010e79e4 : fffff800`02eba540 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidBusEnumeratorGetLunList+0x5b
    fffff880`02fd2490 fffff880`010e7ad6 : fffffa80`047a81b0 00000000`00000001 00000000`00000000 fffffa80`047a81b0 : storport!RaidAdapterEnumerateBus+0x94
    fffff880`02fd2600 fffff880`01126812 : 00000000`00000000 fffff880`010ce8f1 fffff880`01126b20 00000000`000000ca : storport!RaidAdapterRescanBus+0x76
    fffff880`02fd2710 fffff880`01126a20 : fffffa80`055de090 00000000`00000000 fffffa80`047a81b0 fffffa80`055de090 : storport!RaidAdapterQueryDeviceRelationsIrp+0xa2
    fffff880`02fd2750 fffff880`01126bb4 : fffffa80`055de090 fffff880`010ec110 fffffa80`047a8060 00000000`00010286 : storport!RaidAdapterPnpIrp+0x150
    fffff880`02fd27b0 fffff800`0303c18e : fffffa80`055de090 fffffa80`0652cdc0 fffffa80`047a8060 fffff880`009ed180 : storport!RaDriverPnpIrp+0x94
    fffff880`02fd27f0 fffff800`0303c4fa : 00000000`00000000 fffffa80`0652cdc0 fffff800`02d7fed0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`02fd2830 fffff800`0303e847 : fffff800`02e839a0 fffffa80`03cb7b10 00000000`00000002 00000000`00000540 : nt!PnpQueryDeviceRelations+0xfa
    fffff880`02fd28f0 fffff800`0306ee3c : fffffa80`03cb7b10 fffffa80`03cb003c fffffa80`03cb7b10 00000000`00000002 : nt!PipEnumerateDevice+0x117
    fffff880`02fd2950 fffff800`0306f448 : fffff800`02e81560 00000000`00000000 00000000`00000001 fffff800`02eeae08 : nt!PipProcessDevNodeTree+0x21c
    fffff880`02fd2bc0 fffff800`02d82827 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
    fffff880`02fd2c10 fffff800`02c89261 : fffff800`02d82500 fffff800`02e25201 fffffa80`03cff000 fffffa80`00000000 : nt!PnpDeviceActionWorker+0x327
    fffff880`02fd2cb0 fffff800`02f1c2ea : 3155082d`4e082847 fffffa80`03cff040 00000000`00000080 fffffa80`03cecb30 : nt!ExpWorkerThread+0x111
    fffff880`02fd2d40 fffff800`02c708e6 : fffff880`009ed180 fffffa80`03cff040 fffff880`009f7f40 396b8f38`688d3667 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fd2d80 00000000`00000000 : fffff880`02fd3000 fffff880`02fcd000 fffff880`02fd29e0 00000000`00000000 : nt!KxStartSystemThread+0x16
    There's no IRP list to run !irp on, however, we have a bit more of an informative call stack. We can see various
    storport.sys (Microsoft Storage Port driver) calls. With that said, it looks like we may have possibly had an I/O request (ultimately an IRP) sent along the Disk, and to the storage driver. Now, the better question is, what did
    storport.sys do with it? Unfortunately, with no IRP list, I don't know!
    In the mean time, if you crash again, here's what I can tell you:
    1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.
    Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:
    C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
    and rename AODDriver2.sys to AODDriver.2old
    and then Restart.
    2. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes as it's very likely causing file system conflicts:
    Avira removal - http://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/88
    MSE -http://windows.microsoft.com/en-us/windows/security-essentials-download
    3.
    0: kd> lmvm asacpi
    start end module name
    fffff880`04232000 fffff880`0423a000 ASACPI (deferred)
    Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
    Image name: ASACPI.sys
    Timestamp: Sun Mar 27 22:30:36 2005
    ASACPI.sys is dated from 2005, Asus ATK0110 ACPI Utility (a known
    BSOD maker in Win7 and Win8). Also a part of many Asus utilities. The pre-2009 driver causes many BSOD's. With that said, either update your utilities via Asus' website, or uninstall
    all of them ASAP. I recommend the latter as Asus' bloatware is generally useless.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Probably caused by : ntoskrnl.exe ( nt+72f40 )

    Dear Friend,
    I have a windows server 2008R2 running on Hyper v .The host machine is running windows server2012.on this server,Exchange application is running.This server is getting rebooted itself on every 15-20 days.the mini blue dumb for the issue is as below.Please
    help me for the solution.
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Administrator\Desktop\032214-16718-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: *** Invalid ***
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    Executable search path is:
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                   
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 7601.22411.amd64fre.win7sp1_ldr.130801-1934
    Machine Name:
    Kernel base = 0xfffff800`01a07000 PsLoadedModuleList = 0xfffff800`01c4b6d0
    Debug session time: Sat Mar 22 18:41:25.076 2014 (UTC + 5:30)
    System Uptime: 38 days 7:36:33.296
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                   
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 4A, {7773132a, 2, 0, fffff88002594b60}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!KPRCB                                     
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!KPRCB                                     
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    Probably caused by : ntoskrnl.exe ( nt+72f40 )
    Followup: MachineOwner
    ---------

    Hi,
    Before you start to use WinDbg you also need to configure the symbol path – just go to file->symbol file path and the path you need to enter for the Microsoft public symbol
    server is:
    http://msdl.microsoft.com/download/symbols
    The related article:
    Setting up WinDbg and Using Symbols
    http://blogs.msdn.com/b/emeadaxsupport/archive/2011/04/10/setting-up-windbg-and-using-symbols.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Since i up graded to itunes 10.5.2 i cannot access itunes store fully ,i have apple mobile device exe eating my cpu at 97% and now i tried to sync my ipod and it said that i needed to restore my ipod ,this i did and now i cant access my ipod library

    this has got ridiculous now i cant access itunes tore,my ipod says there is no music on it even though i watched it sync nearly 5000 tunes and the program apple mobile device exe eats my cpu at 97% it slows my computer to a crawl should have had the courage of my convictions and stuck to itunes version9 at least that worked.tried resetting netsh winsock,flushing my dns all not worked.this has to be sorted out...and quick

    Hi,
    I have tried and confimed that you can download the previous version from some web-site about the version 10.5.1.42.
    Remove/un-install 10.5.2.11 and restart your computer.
    Install the old version 10.5.1.42
    and then you can find the "Devices" on the left column and showing synchronizing when you connect the cable.
    Good luck

  • Ntoskrnl.exe 100% disk usage windows 8.0 and 8.1

    This is a bug report. I hope Microsoft will take it seriously as it took me a whole day and much stress to track it down. Basically my problem was the same as this: http://slopjong.de/2013/04/23/extremely-high-disk-activity-with-windows-8-and-how-to-fix-it/
    However in the graphic on this site it appears to show that Virtualbox is the culprit. However this is unlikely to be the case, as the author of the site fixed his problem by following his own advice. This is an extremely common problem as this Google search
    indicates:
    https://www.google.co.uk/#q=ntoskrnl.exe+100+disk+usage+windows+8
    To attempt to address my own problem first I disabled all non-microsoft services in Windows 8.1 professional. When this had no effect on the problem, I then disabled all non-essential Microsoft services. In turn. when this has no effect I disabled all user
    installed start-up items. Again when this failed to have an impact, I changed my browser from Firefox to Google Chrome, as I noted that the extremely high disk utilisation was at it's worst when using Firefox. This also had no effect.
    I then tried a variation of my search on Google "ntoskrnl.exe 100 disk usage windows 8" (I can't remember the exact variation) and stumbled over the above site at the beginning of this message. I had by that point tried everything that was in my power
    to try. But I noted from this article that the author recommended changing the power plan from 'balanced', to 'high performance'. Since I had   exhausted every other avenue, I decided to try this and like magic, instantly it worked. So there is clearly
    a bug in Windows 8.1 (and 8 prior to this) that causes 100% disk utilisation. I thought someone at MS might like to know about it and come up with a way to fix it.
    Below is my system configuration. Please note this system configuration may contain a number of errors, as it was generated with several non-essential Microsoft services disabled. I do not believe these issues need to be addressed. However the issue of 100%
    disk utilisation when using a 'balanced' power plan on Windows 8.1 (and 8.0) almost certainly does.
    PS
    This message board system will not allow me to post my full system configuration. MS need a better bug reporting system! Apple allow the public to submit bug reports, so why not Microsoft too. The public can find useful bugs!

    Hi,
    Thanks for your detailed description.
    We considered that the culprit for every computer is different. For the specific PC, we need to analyze the specific issue.
    Please trace the performance using the Windows performance toolkit.
    http://msdn.microsoft.com/en-us/library/hh162945.aspx
    The download link is below:
    http://www.microsoft.com/en-US/download/details.aspx?id=39982
    Then upload the .etl file to Skydrive. We will help you analyze.
    Karen Hu
    TechNet Community Support

  • Windows 8.1 installation first reboot 0xc000007b ntoskrnl.exe missing or contains errors

    I'm trying to install Windows 8.1 (with updata 1) using UEFI on my Intel DP45SG.
    Starting up the installation by using UEFI works fine, but after the files have been copied and the system reboots I get the following error code: 0xc000007b ntoskrnl.exe missing or contains errors
    I've tried reformatting my USB stick and recopying the files, as well as re downloading the installation files but this hasn't resolved the problem.
    Is there anything I can try to fix this? Perhaps give some commands in the commands prompt?

    Hi Gi,
    It might be caused by changes in Windows 8 PnP in which Boot Start Drivers are not installed by default.
    Please try following
    the instructions as mentioned in the KB aticle.
    https://support.microsoft.com/en-us/kb/2751461?wa=wsignin1.0
    Regards,
    D. Wu
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Plugin-container.exe is EATING cpu clock cycles and slowing down my computer big-time. Is there a fix to prevent this, or do I just have to disable this subsidiary program and take the consequences?

    Whenever I have an audiovisual display running in a Firefox (5.0) tab, the program "plugin-container.exe" swamps my CPU, jumping up to 95% of processing clock cycles. This makes all online video displays hang and jump, and it's a pain in the neck. Is there any way to mitigate this?

    That's supposed to indicate it's your plug-ins like Flash that is the problem.
    You might try changing hardware acceleration, a setting within Flash either turn if off or on.

Maybe you are looking for