Ntoskrnl.exe
BSOD - appears that ntoskrnl.exe is the cause - a search of my computer for this file shows that I have 27 such files - various sizes but some of the particular file sizes repeat.
1. how many versions of this file should I have - what is the right file size and where should it "live"
Thanks
Oops - yes - happens when Windows Media Center is running (only when)
Hi,
This file is a system component file, and system updates or added components will give it updated versions. You can see that this file can be located under winsxs\certain component name folder.
To analyze you BSOD issue, please upload the dump file here for our research.
Kate Li
TechNet Community Support
Similar Messages
-
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. -
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 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.
ThanksIn 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 -
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] -
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 -
Windows 7 Ult 64 memory mgmt errors ntoskrnl.exe nt+75BC0
Using WhoCrashed I get this error once in a while. Where should I post this question?
On Mon 4/14/2014 3:41:15
PM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\041414-5584-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A
(0x411, 0xFFFFF6800014DFF8, 0xF86000032C9C8886, 0xFFFFF8A025364283)
Error:
MEMORY_MANAGEMENT
file path:
C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This indicates that a severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules.
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.
I got this two days earlier.
On Sat 4/12/2014 12:36:47
AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041114-6115-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A
(0x5003, 0xFFFFF70001080000, 0x161, 0x163000000C2)
Error: MEMORY_MANAGEMENT
file path:
C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This indicates that a severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules.
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.We do need the actual DMP file as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
We prefer at least 2 DMP files to spot trends and confirm the cause.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask
If you are using Blue screen view, who crashed, or a similar application don't. They are wrong at least as often as they are correct
Wanikiya and Dyami--Team Zigzag -
How do you repair ntoskrnl.exe error or system error in windows server 2008 and 2012
hi,
can you repair system file errors like ntoskrnl.exe in windows server 2008 and 2012 like like before in windows server 2003 ?
the steps were repairing ntoskrnl.exe error in windows server 2003
1- have a 2003 cd and from that cd start recovery console and copy from i386 directory ntldr and ntdetect.com to windows /system32 directory on the server and then repairing
2- MBR with fixmbr command and then rebuild BOT.INI file with bootcfg/rebuild .
now my question is how you repair or solve such problem with ntoskrnl.exe error in windows server 2008 and windows server 2012
thanks
johan
h.davidfirst this wil take a lot of time for windows 2008 and 2012 ,
and what about windows 2003 I thing this has no startup repair
thanks
johan
h.david
What will take a lot of time? Repair or clean install? These days one can standup a new VM and have an operating system on it in around 20 minutes or so.
Correct server 2003 is file based deployment and completely different OS from repair perspective as well.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Windows 8.1 BSOD - ntoskrnl.exe
Hi, I've been experiencing BSOD's on a daily basis (only when I am away from my computer) and I'd like to know the root cause of the problems. I've attached several minidump files below. Using Windbg (x64) the only problem I can see is ntoskrnl.exe being
unable to load (either corrupted or missing). sfc/scannow has detailed several problems relating to ntoskrnl.exe as well
https://onedrive.live.com/redir?resid=6e6984aa2d967f21%212299
Thanks!
BillYou've recommended the opposite of what I was told last time: "The crashes are being caused by you
NVidia display driver. Please uninstall an "clean" reinstall the current driver version".
Last time I had BSOD problems I was using version 326.19 (at least one year old) and now I have the most recent version. As a result, I do not believe this is the cause of the BSOD's.
Also, I do not see the same thing you do when opening the minidump file, as follows:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040815-36484-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 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`0a282000 PsLoadedModuleList = 0xfffff802`0a55b250
Debug session time: Wed Apr 8 14:02:21.387 2015 (UTC - 6:00)
System Uptime: 0 days 20:32:22.558
* 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
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe0019c12a760, fffff8020c30e960, ffffe001a1f67680}
***** 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!_DEVICE_OBJECT ***
*** 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!_IRP ***
*** 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!_IRP ***
*** 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!TRIAGE_9F_POWER ***
*** 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!_IRP ***
*** 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!_IO_STACK_LOCATION ***
*** 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!_IRP ***
*** 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!_DEVICE_OBJECT ***
*** 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. *** -
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 -
Touchsmart 310-1110uk - BSoD caused by ntoskrnl.exe
I have had seemingly random Blue Screens of Death when shutting down on my HP Touchsmart 310-1110uk over the last few months. Sometimes when shutting down, the "Shutting down..." message is displayed for a long time and then the BSoD appears. This only happens occasionally and most of the time it shuts down fine. The blue screen only ever appears when shutting down.
It seemed to happen when Connectify was running but after looking into Connectify BSoD problems it seems that this bug was fixed after version 3, and I am running 3.3.0.23104 Pro. Therefore I don't think Connectify is the problem.
I have uploaded the a .zip of the dump files from "C:\Windows\Minidumps" to Dropbox here:
http://dl.dropbox.com/u/9154836/Minidump.zip
I have also downloaded BlueScreenView to try and analyse the error logs. Most of the crashes seem to be the same with the following:
Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug Check Code: 0x0000009f
Caused By Driver: ntoskrnl.exe
Caused By Address: [mostly "ntoskrnl.exe+7cd40" or "ntoskrnl.exe+7cc40"]
I have uploaded the full HTML BlueScreenView report here:
http://dl.dropbox.com/u/9154836/report.html
I haven't installed many programs which might have caused the problem. This has been happening since November 2011 and the only thing I installed around then was Connectify.
From what I can tell it seems to be a driver issue, but because this only happens occasionally (at seemingly random times when shutting down) it's almost impossible to troubleshoot by disabling individual drivers (i.e. trial and error).
I would appreciate some help on this, if you could provide some guidance on fixing this or ask for more specific information.I have had seemingly random Blue Screens of Death when shutting down on my HP Touchsmart 310-1110uk over the last few months. Sometimes when shutting down, the "Shutting down..." message is displayed for a long time and then the BSoD appears. This only happens occasionally and most of the time it shuts down fine. The blue screen only ever appears when shutting down.
It seemed to happen when Connectify was running but after looking into Connectify BSoD problems it seems that this bug was fixed after version 3, and I am running 3.3.0.23104 Pro. Therefore I don't think Connectify is the problem.
I have uploaded the a .zip of the dump files from "C:\Windows\Minidumps" to Dropbox here:
http://dl.dropbox.com/u/9154836/Minidump.zip
I have also downloaded BlueScreenView to try and analyse the error logs. Most of the crashes seem to be the same with the following:
Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug Check Code: 0x0000009f
Caused By Driver: ntoskrnl.exe
Caused By Address: [mostly "ntoskrnl.exe+7cd40" or "ntoskrnl.exe+7cc40"]
I have uploaded the full HTML BlueScreenView report here:
http://dl.dropbox.com/u/9154836/report.html
I haven't installed many programs which might have caused the problem. This has been happening since November 2011 and the only thing I installed around then was Connectify.
From what I can tell it seems to be a driver issue, but because this only happens occasionally (at seemingly random times when shutting down) it's almost impossible to troubleshoot by disabling individual drivers (i.e. trial and error).
I would appreciate some help on this, if you could provide some guidance on fixing this or ask for more specific information. -
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... -
File ntoskrnl.exe status: 0xc0000098
SCCM 2012 R2 CU2 Single Primary Site Server
Trying to deploy Windows Server 2008 R2 to Dell server.
File ntoskrnl.exe status: 0xc0000098
Any suggestions on troubleshooting. I think the following action plan for now:
0xc000098 translates to Status_File_Invalid. The volume for a file has been externally altered such that the opened file is no longer valid. Seems like the machine is unable to locate the hard disk. Can you deploy Windows Server
2012 image?
1. Check the boot options in BIOS and ensure it is correct
2. Run hard drive diagnostics
3. Run Windows Memory Diagnostics Tool
4. Boot into safe mode with command prompt and type dispart to check if HD is being detected.
Check out the following article:
Fix Boot Error 0xC0000098 (Windows Boot Configuration Data file does not contain a valid OS entry)
http://www.prime-expert.com/articles/b18/fix-0xC0000098-windows-bcd-does-not-contain-valid-os-entry.php
Fix: 0xc0000098 Error In Windows 8
http://www.thewindowsclub.com/0xc0000098-error-windows-8-helpStrangely we are able to install Windows Server 2012 R2 image to the same machine.
However it errors out with Windows Server 2008 R2 Image. We tried different media for 2008 R2.
Any suggestions on proceeding with troubleshooting. -
BSOD "ntoskrnl.exe" - system recovery did not work
Hi, I keep getting BSOD repeatedly whenever i log into windows normally. I can only access my laptop through safe mode w/networking. anyways i have narrowed the problem down to the driver "ntoskrnl.exe" However I dont know what is causing the problem
and how to fix it.
here is the link from my onedrive for kernel dump file:
https://onedrive.live.com/redir?resid=9997264A2CACAA02%21116
Dump File : 082614-111447-01.dmp
Crash Time : 8/26/2014 3:04:11 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`032e1c3f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082614-111447-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 287,608
Dump File Time : 8/26/2014 3:17:08 PMNHJ
These crash was caused by your Symantec killing netio.sys. I would remov Symantec and use MSE in its place
Symantec is a frequent cause of BSOD's.
I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
http://www.microsoft.com/security_essentials/
For Norton 360 use this http://symantec.pcperformancetools.com/norton-360-how-to-uninstall.html
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\082614-111447-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\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 Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a6890
Debug session time: Tue Aug 26 15:04:11.347 2014 (UTC - 4:00)
System Uptime: 0 days 0:02:27.283
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff800032e1c3f}
*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
Probably caused by : NETIO.SYS ( NETIO!WfpExpireEntryLru+17 )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032e1c3f, address which referenced memory
Debugging Details:
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003510100
GetUlongFromAddress: unable to read from fffff800035101c0
0000000000000000 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+4f
fffff800`032e1c3f 488713 xchg rdx,qword ptr [rbx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff8800a7f3230 -- (.trap 0xfffff8800a7f3230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a138b50 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800a7f3430 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032e1c3f rsp=fffff8800a7f33c0 rbp=0000000000000008
r8=fffff8800a7f3430 r9=fffff88001d8aca0 r10=0000000000000000
r11=0000000000000040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f:
fffff800`032e1c3f 488713 xchg rdx,qword ptr [rbx] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032d8169 to fffff800032d8bc0
STACK_TEXT:
fffff880`0a7f30e8 fffff800`032d8169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a7f30f0 fffff800`032d6de0 : 00000000`00000010 fffff880`0a7f3420 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0a7f3230 fffff800`032e1c3f : 00000000`00000003 00000000`00000002 00000000`00000003 00000000`00000002 : nt!KiPageFault+0x260
fffff880`0a7f33c0 fffff880`01b419c7 : 00000000`00000008 fffff880`0a7f36a0 00000000`00008900 fffffa80`081b47c8 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f
fffff880`0a7f3410 fffff880`01ce608d : fffffa80`0bfe79d0 fffffa80`0c08b8a0 fffff880`0a7f36a0 00000000`00008900 : NETIO!WfpExpireEntryLru+0x17
fffff880`0a7f3460 fffff880`01cad7b7 : 00000000`00000004 fffff880`01b10030 fffffa80`0bfe7a20 00000000`00000001 : tcpip!WfpAleCloseRemoteEndpointConnection+0x2d
fffff880`0a7f3490 fffff880`01d25e5b : fffffa80`0bfe79d0 fffffa80`0b9e2cda 00000000`00000001 fffffa80`0bfe79d0 : tcpip! ?? ::FNODOBFM::`string'+0x20f72
fffff880`0a7f35e0 fffff880`01d261e2 : 00000089`00000000 fffffa80`0b9e2c10 fffffa80`089266a0 00000000`00000001 : tcpip!WfpAleHandleSendCompletion+0xeb
fffff880`0a7f3700 fffff880`01d306b2 : fffff880`0a7f3ba8 00000000`00000001 00000000`00000000 fffffa80`08159f18 : tcpip!WfpAlepAuthorizeSendCompletion+0x32
fffff880`0a7f3750 fffff880`01ba7af2 : fffffa80`00000089 fffff800`00000089 fffffa80`0bc9d370 00000000`00000001 : tcpip!WfpAleCompleteOperation+0x162
fffff880`0a7f37f0 fffff880`076e67bb : 00000000`00000000 00000000`00000000 fffffa80`0bc737c0 00000000`00000030 : fwpkclnt!FwpsCompleteOperation0+0x1e
fffff880`0a7f3820 00000000`00000000 : 00000000`00000000 fffffa80`0bc737c0 00000000`00000030 00000000`00000089 : SYMNETS+0x1e7bb
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!WfpExpireEntryLru+17
fffff880`01b419c7 488b4310 mov rax,qword ptr [rbx+10h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: NETIO!WfpExpireEntryLru+17
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 5294760d
IMAGE_VERSION: 6.1.7601.18327
FAILURE_BUCKET_ID: X64_0xA_NETIO!WfpExpireEntryLru+17
BUCKET_ID: X64_0xA_NETIO!WfpExpireEntryLru+17
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xa_netio!wfpexpireentrylru+17
FAILURE_ID_HASH: {fcdee258-ad7b-b100-5f3a-ac9544c5fd1f}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag -
BSOD - Server 2008 R2 - ntoskrnl.exe
I've been having an issue lately with a BSOD happening multiple times during the day. I have DMP logs and used BlueScreenView to get some basic information (I know that this is as helpful as it is useless) which seems to show that ntoskrnl.exe is
causing the crashes. There are 6 servers, 1 is used by IT and doesn't seem to have had this issue while the other 5 are part of a load balanced environment and have been having this issue in some cases 5 times a day. These are RD servers.
The servers were all working perfectly fine until our company purchased and installed a piece of software called Screwdrivers/Simplify Printing. This software seems to be the cause of the crashes and I have contacted their support regarding this.
But while I wait I figure it might be a good idea to ask if the DMP files actually could provide more information as to what specifically is causing the crashes.
For those who don't know, Screwdrivers is a utility to help with printing (driverless printing from the RD server to the workstation using the Screwdrivers driver) and I'm wondering if there is a specific model of printer causing the crashes or
a specific workstation side driver or if its just one or a few users that are causing the crashes. Obviously BlueScreenView isn't giving any good information but if the DMP file contains more information that may help I figure that it's worth looking into.
The BSOD error is below:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.18.10
Locale ID: 1033
Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA801CCD9060
BCP3: FFFFFA801CCD9340
BCP4: FFFFF80001D85270
OS Version: 6_1_7601
Service Pack: 1_0
Product: 18_3
I have uploaded the DMP and NFO files zipped to my onedrive but I can't post until my account gets verified but once I can post the link I will gladly or you
could try to find my post with the same topic title.
https://onedrive.live.com/embed?cid=CBD3F774506379E4&resid=CBD3F774506379E4%21148&authkey=AK0BPufjZy24HYQ
I am currently running the verifier.exe tool as suggested to see if any more information can be obtained. It has been running for about 3 hours now so we'll see what results I get.
I have posted this on answers microsoft com and ZigZag3143 has advised me that it might be good to post here and after looking at the DMP files ZigZag has found the following...
"These were literally all critical process termination (0xF4) meaning something causes an OS process to terminate unexpectedly.
The running process at the time of the crash was Simplifiy notification but there is nothing definitive. I would run driver verifier on
one of the servers (non production) as verifier will crash it when the mis-behaving driver is loaded or makes a bad call
One other thing of note was that vmdebug.sys Replay Debugging Driver from VMware, Inc. was also in the stack."
The company we bought the software from is looking into this on their end but I figured the DMP files could potentially help get some more information. I'm hoping that maybe there's a way to find out if its a single printer model, a certain local
workstation printer driver, a certain user, a certain PC, or something else. These are RDP server so there's upwards of 50+ users on each of the 5 servers at any given time and to have the servers just randomly restart is really frustrating for our users
as this is arguably the most important system (next to payroll of course lol).
Thanks,
RyanHi Ryan,
For Bug Check 0xF4, it indicates that a process or thread crucial to system operation has unexpectedly exited
or been terminated. For more details, please refer to following article.
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION
As you know, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. Please refer to following article
and check if help you to analyze Bug check 0xF4.
Debugging a Bugcheck 0xF4
However, it is not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service
and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Hope this helps.
Best regards,
Justin Gu
Maybe you are looking for
-
Hi friends, In SRM, po approval W/f is in completed status. PO is replicated in R/3. But SRM status is not updated. Is there any way we can update SRM status? regards, Vittalprasad
-
Help.. best way to share FC projects between 4 computers
Hi There, We are a small video production company and we use four computers to edit, one Mac Pro, two iMacs and a Macbook Pro. The problem we have is that we often need to move the projects from one computer to another, so different members of the te
-
AIR for IOS GeolocationEvent Altitude problem
I'm testing a simple geolocation app using the code from this tutorial. http://www.youtube.com/watch?v=1YRJuBqHK2A The event.latitude and event.longitude come through correctly but the altitude is coming out as the default value, 0. I've tested this
-
I am trying to update my ipad mini to both the new 7.0.4 & everytime I get past the agree screen to the verify it tells me I am not connected to the internet when I clearly am. What am I doing wrong?
-
Playback won't stop in multicam sequence
Here's a new one. When editing a multicamera sequence, I keep running into this weird phenomenon where I can't stop the playback. I hit the space bar, start making cuts, then when I want to stop I hit the space bar again and nothing happens. The se