Randomly BSODs caused by ntoskrnl.exe
I have random BSODs, this is the dump file... any ideas? I tried to update all drivers, but I solved nothing.
Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\061114-29937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Error: Attempts to access '061114-29937-01.dmp' failed: 0x0 - The operation completed successfully.
************* Symbol Path validation summary **************
Response Time (ms) Location
Error 061114-29937-01.dmp
Symbol search path is: 061114-29937-01.dmp
Executable search path is:
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff800`6e28e000 PsLoadedModuleList = 0xfffff800`6e5582d0
Debug session time: Wed Jun 11 20:29:12.062 2014 (UTC + 2:00)
System Uptime: 0 days 0:22:21.219
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 133, {1, 1e00, 0, 0}
***** 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
5 times more...
*** 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+153fa0 )
Followup: MachineOwner
Systeminfo:
OS Name: Microsoft Windows 8.1 Pro
OS Version: 6.3.9600 N/A Build 9600
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Original Install Date: 30/10/2013, 13:43:05
System Boot Time: 11/06/2014, 20:29:52
System Manufacturer: TOSHIBA
System Model: Satellite L500
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 37 Stepping 2 GenuineIntel ~2261 Mhz
BIOS Version: TOSHIBA 2.10, 17/05/2011
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume2
Total Physical Memory: 3.958 MB
Available Physical Memory: 1.792 MB
Virtual Memory: Max Size: 7.926 MB
Virtual Memory: Available: 5.492 MB
Virtual Memory: In Use: 2.434 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Logon Server:
\\MicrosoftAccount
Hotfix(s): 56 Hotfix(s) Installed.
[01]: KB2899189_Microsoft-Windows-CameraCodec-Package
[02]: KB2843630
[03]: KB2868626
[04]: KB2883200
[05]: KB2887595
[06]: KB2889543
[07]: KB2891214
[08]: KB2893294
[09]: KB2894029
[10]: KB2894179
[11]: KB2898868
[12]: KB2900986
[13]: KB2901125
[14]: KB2901128
[15]: KB2903939
[16]: KB2904440
[17]: KB2911106
[18]: KB2912390
[19]: KB2913152
[20]: KB2916036
[21]: KB2919355
[22]: KB2919394
[23]: KB2919442
[24]: KB2920189
[25]: KB2923528
[26]: KB2923768
[27]: KB2926765
[28]: KB2928680
[29]: KB2931358
[30]: KB2931366
[31]: KB2939153
[32]: KB2939576
[33]: KB2950153
[34]: KB2953522
[35]: KB2954879
[36]: KB2955164
[37]: KB2956575
[38]: KB2957151
[39]: KB2957189
[40]: KB2957689
[41]: KB2958262
[42]: KB2959977
[43]: KB2961908
[44]: KB2962140
[45]: KB2964718
[46]: KB2964736
[47]: KB2965065
[48]: KB2965142
[49]: KB2965500
[50]: KB2965699
[51]: KB2965788
[52]: KB2966072
[53]: KB2966407
[54]: KB2966804
[55]: KB2969817
[56]: KB976002
Network Card(s): 10 NIC(s) Installed.
[01]: Realtek PCIe FE Family Controller
Connection Name: Ethernet
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[02]: Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC
Connection Name: Wi-Fi
Status: Hardware
not present
[03]: Hyper-V Virtual Ethernet Adapter
Connection Name: Ethernet 6
Status: Media
disconnected
[04]: Hyper-V Virtual Ethernet Adapter
Connection Name: Ethernet 3
Status: Media
disconnected
[05]: Hyper-V Virtual Ethernet Adapter
Connection Name: Ethernet 5
DHCP Enabled: Yes
DHCP Server: 192.168.1.1
IP address(es)
[01]: 192.168.1.129
[02]: fe80::1513:f368:3c1e:c173
[06]: Hyper-V Virtual Ethernet Adapter
Connection Name: Ethernet 4
DHCP Enabled: No
IP address(es)
[01]: 169.254.80.80
[02]: fe80::4892:9cb3:7a80:2057
[07]: VMware Virtual Ethernet Adapter for VMnet1
Connection Name: VMware Network Adapter VMnet1
DHCP Enabled: No
IP address(es)
[01]: 192.168.223.1
[02]: fe80::a11c:f4d5:c02f:9fcf
[08]: VMware Virtual Ethernet Adapter for VMnet8
Connection Name: VMware Network Adapter VMnet8
DHCP Enabled: No
IP address(es)
[01]: 192.168.132.1
[02]: fe80::fc9a:9075:a71e:776c
[09]: TAP-Windows Adapter V9
Connection Name: Local Area Connection 3
Status: Media
disconnected
[10]: Hyper-V Virtual Ethernet Adapter
Connection Name: vEthernet (TAP-Windows Adapter V9 Virtual Switch)
Status: Media
disconnected
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama
Similar Messages
-
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. -
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. -
BSOD SYSTEM_SERVICE_EXEPTION possibly caused by ntoskrnl.exe?
Encounter 3 BSOD in a row within one single day.
bluescreenview says ntoskrnl.exe was related during BSOD happened.
BSOD just like happens every 3-4 hours, when I am opening, virtual box, VS 2013 Ultimate, Eclipse, Apache 2.4, PHP-cgi 5.5.15, MySQL 5.6.
I suspected it was a hardware driver issues, so I tried remove my PCI-E creative sound card and uninstall its driver with only keyboard and mouse attached, but it still happen just moment ago.
Moreover, it also happens before I install MSI Afterburner, so I don't think it was the cause.
Any suggestions?
Thank you very much.
My spec
I5-4670
GTX-770
AsRock Fatal1ty H87 Performance
Crucial M4
Win 8.1 Pro, fully patched
Minidump attached.
https://onedrive.live.com/redir?resid=609F4764A5939498!667&authkey=!AAO2J98g9BTc_d4&ithint=folder%2cdmpHi,
SYSTEM_SERVICE_EXCEPTION (3b)
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
BugCheck 3B, {c0000005, fffff800d504d553, ffffd0002160fd50, 0}
0: kd> ln fffff800d504d553
(fffff800`d504d280) afd!AfdPoll64+0x2d9 | (fffff800`d504dad0) afd!AfdCheckPollEvents
The exception occurred in afd!AfdPoll64+0x2d9.
1. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented
with the latest video card driver and many previous versions, please give the beta driver for your card a try.
2. Navigate to services.msc and disable the nVidia Streaming Service, and then restart the computer.
3. RTCore64.sys is listed and loaded which is RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Windows 7, 8, and 8.1). Please uninstall ASAP!
4.
0: kd> lmvm vuhub
start end module name
fffff800`d6400000 fffff800`d640f000 vuhub (deferred)
Image path: vuhub.sys
Image name: vuhub.sys
Timestamp: Fri Nov 16 10:31:13 2007
Eltima Software USB to Ethernet Connector driver, dated from 2007. This driver either needs to be updated, or if not available, completely uninstalled. It's not compatible with Windows 8/8.1.
http://wiki.eltima.com/user-guides/usb-to-ethernet.html
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
Hello,
One of our clients has an annoying problem with BSODS almost daily cause by ntkrnlmp.exe and I couldn't manage to find what REALLY was the cause. Symbols were properly configure and still no clear infos. If someone can have a look over the Minidumps and/or
Memory.DMP here are both:
https://onedrive.live.com/?cid=E0FCDAC93086F976&id=E0FCDAC93086F976%21123
Thank you,
CozminHi Cozmin V,
This is excessive paged pool usage, this error may occur due to user-mode graphics driver crossing over and passing bad data to the kernel code.
1: kd> !analyze -v
* Bugcheck Analysis
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800030a5aae, Address of the instruction which caused the bugcheck
Arg3: fffff8800864c790, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
fffff800`030a5aae f00fba3100 lock btr dword ptr [rcx],0
CONTEXT: fffff8800864c790 -- (.cxr 0xfffff8800864c790)
rax=fffffa80082d63c0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80082d63c0 rsi=00000000ffffffff rdi=fffffa80082d63c0
rip=fffff800030a5aae rsp=fffff8800864d170 rbp=0000000000000001
r8=0000000000000000 r9=fffff96000365ab8 r10=000000000002fcc7
r11=fffff8800864d1c0 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=fffff900caf4dd30
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26:
fffff800`030a5aae f00fba3100 lock btr dword ptr [rcx],0 ds:002b:00000000`00000000=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff9600060dce0 to fffff800030a5aae
STACK_TEXT:
fffff880`0864d170 fffff960`0060dce0 : 00000000`00000000 000001c4`00000000 0000feed`52052bed 00001f80`00000000 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26
fffff880`0864d1a0 fffff960`00177748 : 00000000`00000001 fffff900`c00b7010 00000000`00000001 fffff900`caf3c370 : cdd!CddBitmapHw::Release+0xc0
fffff880`0864d1e0 fffff960`002b86b4 : 00000000`00000000 00000000`00000000 fffff900`caf3c370 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x358
fffff880`0864d330 fffff960`002b8757 : fffff900`c00b7010 00000000`00000001 fffff900`c00b7010 00000000`00000001 : win32k!vDynamicConvertNewSurfaceDCs+0xd8
fffff880`0864d360 fffff960`002b8ff2 : fffff900`c00b7010 00000000`00000001 fffff900`c8e35280 fffff900`c00b7010 : win32k!bDynamicRemoveAllDriverRealizations+0x6f
FOLLOWUP_IP:
cdd!CddBitmapHw::Release+c0
fffff960`0060dce0 488b4738 mov rax,qword ptr [rdi+38h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: cdd!CddBitmapHw::Release+c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7c546
STACK_COMMAND: .cxr 0xfffff8800864c790 ; kb
FAILURE_BUCKET_ID: X64_0x3B_cdd!CddBitmapHw::Release+c0
BUCKET_ID: X64_0x3B_cdd!CddBitmapHw::Release+c0
Followup: MachineOwner
1: kd> lmvm cdd
start end module name
fffff960`00600000 fffff960`00627000 cdd (pdb symbols) c:\symbols\cdd.pdb\88BFB882815849F88656925A7675F2BA1\cdd.pdb
Loaded symbol image file: cdd.dll
Mapped memory image file: c:\symbols\cdd.dll\4CE7C54627000\cdd.dll
Image path: \SystemRoot\System32\cdd.dll
Image name: cdd.dll
Timestamp: Sat Nov 20 20:55:34 2010 (4CE7C546)
CheckSum: 0002D4F0
ImageSize: 00027000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> lmtsmn
start end module name
fffff880`00f18000 fffff880`00f6f000 ACPI ACPI.sys Sat Nov 20 17:19:16 2010 (4CE79294)
fffff880`068fd000 fffff880`0697d000 ADIHdAud ADIHdAud.sys Wed Jun 16 03:36:52 2010 (4C17D654)
fffff880`048df000 fffff880`04968000 afd afd.sys Sat Nov 20 17:23:27 2010 (4CE7938F)
fffff880`04a39000 fffff880`04a4f000 AgileVpn AgileVpn.sys Tue Jul 14 08:10:24 2009 (4A5BCCF0)
fffff880`02ec4000 fffff880`02ed7180 aksdf aksdf.sys Mon Nov 21 19:09:56 2011 (4ECA3184)
fffff880`032da000 fffff880`032fae00 aksfridge aksfridge.sys Tue Aug 07 18:34:40 2012 (5020EF40)
fffff880`017f2000 fffff880`017fd000 amdxata amdxata.sys Sat Mar 20 00:18:18 2010 (4BA3A3CA)
fffff880`01e50000 fffff880`01e65000 appid appid.sys Sat Nov 20 18:14:37 2010 (4CE79F8D)
fffff880`078fb000 fffff880`07906000 asyncmac asyncmac.sys Tue Jul 14 08:10:13 2009 (4A5BCCE5)
fffff880`013b2000 fffff880`013bb000 atapi atapi.sys Tue Jul 14 07:19:47 2009 (4A5BC113)
fffff880`013bb000 fffff880`013e5000 ataport ataport.SYS Sat Nov 20 17:19:15 2010 (4CE79293)
fffff960`00870000 fffff960`008d1000 ATMFD ATMFD.DLL Sat Nov 20 17:49:28 2010 (4CE799A8)
fffff880`00fe0000 fffff880`00fec000 BATTC BATTC.SYS Tue Jul 14 07:31:01 2009 (4A5BC3B5)
fffff880`04409000 fffff880`04410000 Beep Beep.SYS Tue Jul 14 08:00:13 2009 (4A5BCA8D)
fffff880`04b76000 fffff880`04b87000 blbdrive blbdrive.sys Tue Jul 14 07:35:59 2009 (4A5BC4DF)
fffff880`02fb1000 fffff880`02fcf000 bowser bowser.sys Wed Feb 23 12:55:04 2011 (4D649328)
fffff960`00600000 fffff960`00627000 cdd cdd.dll Sat Nov 20 20:55:34 2010 (4CE7C546)
Unloaded modules:
fffff880`078b6000 fffff880`078c4000 monitor.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`078a8000 fffff880`078b6000 monitor.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`0789a000 fffff880`078a8000 monitor.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`0788c000 fffff880`0789a000 monitor.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`0787e000 fffff880`0788c000 monitor.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
By checking your DMP file, we also found it related to cdd.dll which is the Canonical Display Driver from Microsoft, it's a system file. You could refer to this link for more information about cdd and bitmap
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/bluescreen-error-when-alttabbing-out-of-full/267be931-70b1-482f-8164-c3cd8084def0
We suggest you replace your graphic/display driver and keep them up to date, then check the issue again.
Also you have a lot of outdated drivers on your system including cdd.dll. Please update these drivers for good measure.
If you're still crashing after all of the above, enable Driver Verifier to look for further corruption:
Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows
kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Note: Before enabling Driver Verifier, it is recommended to create a System Restore Point
For more information about Driver Verifier
https://msdn.microsoft.com/en-us/library/windows/hardware/ff545448(v=vs.85).aspx -
Windows 8.1 x64 BSOD on shutdown - ntoskrnl.exe
This has been happening for several months to me, where in Windows 8.1 x64 when I go to shut down to install any Windows updates, I get a BSOD that says REFERENCE_BY_POINTER. I've uploaded the minidump files here:
https://skydrive.live.com/redir?resid=A0FE33D78854B45A!3350&authkey=!AEZUfKou1Y7rQWQ&ithint=folder%2c.dmp
Can someone help me sort out which driver might be causing the problem? Thanks!
actiprosoftware.com - Professional WPF, WinRT, Silverlight, and WinForms UI controls and componentsHi,
The Ntkrnlmp.exe Bluescreen error may be caused by following factors.
Fail to load drivers.
Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
Are damaged or defective.
Are operating outside their specified ranges for temperature, power, or other conditions.
First, I suggest we disable fast boot for Windows 8.1 to check the issue (below steps are ok for Windows 8.1):
Please refer to this article: Disable Windows 8 fast startup (hibernate file)
http://nvidia.custhelp.com/app/answers/detail/a_id/3152/~/disable-windows-8-fast-startup-(hibernate-file)
If the issue persists, to determine the possible cause, I suggest we test the issue in Clean boot mode and Device clean boot mode:
How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista
http://support.microsoft.com/kb/929135
If the issue doesn’t appear, you can determine which one can be the cause by using dichotomy in MSconfig. Checking on half of Non-Microsoft service and restart, determining which half of the services cause the issue and repeating to check half of the problematic
half services.
Device Clean Boot
=================
1. Type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.
2. Expand "Sound, video and game controllers".
3. Right click on your sound card and then click "Properties.
4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.
5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.
Let me know the results after performing my previous suggestions.
If the issue still persist, please post back the latest dump file and system information here for further research.
Kate Li
TechNet Community Support -
X200 Tablet - BSOD -caused by tsmservice.exe
Hello Community,
I got an Lenovo
X200Tablet 7453BD5
BIOS vers.: 7WET71WW (3.21)
I installed a SSD on my Notebook. I installed Windows 7 on it (more than 5 times), the former OS was Vista on the shipped Notebook.
The Software which causes the BSOD is the service 'TabletSVC'/'TABLET Service' with the execution TSMService.exe. If I stop the service or even not allow to start automated it with Windows. I have no problems with shuting down (restart, hibernate, power off) within 15s the notebook is off.
If the service is still running I probably see the shuting down Window for about feeled 10 Minutes until it shows me an BSOD.
What I've tried meantime. Installed other version of the Tablet Shortcut Menu ->[URL=http://support.lenovo.com/de/de/products/laptops-and-netbooks/thinkpad-x-series-tablet-laptops/think...
Tablet Shortcut Menu[/url].
I also installed the system step by step over the lenovo System update, so I saw what caused the problem. Now I use a shortcut on my desktop which do an net stop 'Tablet Service' and an shutdown. That's functionally but not nice.
Does someone else had/have this problem? And have a solution for it?
regards
NorbertThis is caused by an incompatibility between tsmservice.exe and some versions of Lenovo Power Management driver.
Can you check what version of Lenovo Power Management driver is installed?
You need version 1.67.4.5 (or older), or else 1.67.9.3 (or newer).
Versions in between cause this problem. Sorry for this inconvenience. -
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 -
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 -
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 -
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 -
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 INTERNAL POWER ERROR,ntoskrnl.exe driver issue
Hi,i got brand new computer,every component is new except HDD(ata Maxtor 6L250S0 SCSI disck device) .
i5 4670
Kingston hyperx 8gb 1600
asus z87-c motherboard
asus r9 270x dcIIt
OS Windows 7 64 ultimate
and I got BSoD randomly(7 times) when computer is in standby(just turned on,nothing working on it) and when I download something using yTorrent(this happened once).I never got BSoD when I was using internet or playing games.
Minidump:
122613-38813-01.dmp 26.12.2013 20:25:47 INTERNAL_POWER_ERROR 0x000000a0 00000000`00000009 ffffffff`c0000001 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\122613-38813-01.dmp 4 15 7601 276.840 26.12.2013
20:52:35
010114-30435-01.dmp 1.1.2014 4:29:17 INTERNAL_POWER_ERROR 0x000000a0 00000000`00000009 ffffffff`c0000001 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\010114-30435-01.dmp 4 15 7601 276.840 1.1.2014
12:52:26
010214-30685-01.dmp 2.1.2014 19:31:32 INTERNAL_POWER_ERROR 0x000000a0 00000000`00000009 ffffffff`c0000001 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\010214-30685-01.dmp 4 15 7601 276.840 2.1.2014
19:45:16
010714-30747-01.dmp 7.1.2014 14:57:30 INTERNAL_POWER_ERROR 0x000000a0 00000000`00000009 ffffffff`c0000001 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\010714-30747-01.dmp 4 15 7601 276.840 7.1.2014
15:00:33
010714-30498-01.dmp 7.1.2014 16:19:12 INTERNAL_POWER_ERROR 0x000000a0 00000000`00000009 ffffffff`c0000001 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\010714-30498-01.dmp 4 15 7601 276.840 7.1.2014
16:39:58
011014-32105-01.dmp 10.1.2014 15:35:46 INTERNAL_POWER_ERROR 0x000000a0 00000000`00000009 ffffffff`c0000001 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft®
Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\011014-32105-01.dmp 4 15 7601 276.840 10.1.2014
15:39:57
I checked ram using windows diagnostic tool,no errors were found.
Plz help to solve this problem!Your problem lies in the implications arising from these details.
[Drives]
Item Value
Drive C:
Description Local Fixed Disk
File System NTFS
Size 59,90 GB (64.319.647.744 bytes)
Free Space 13,51 GB (14.509.522.944 bytes)
Drive D:
Description Local Fixed Disk
File System NTFS
Size 172,88 GB (185.632.550.912 bytes)
Free Space 18,94 GB (20.333.670.400 bytes)
Your C partition (drive) is too small, except there may be solutions that could help without resizing the partition. You need more free disk space on both partitions.
The free disk space on your D partition needs to be increased from 19gb to 50gb. You need to remove files equal to 30gb from the partition either by moving them to external media or by deleting them. Another option might be to
add an extra internal drive, if that is physically feasible. Alternatively buy a larger hard drive and reinstall your system.
To increase your free disk space on C, type Disk CleanUp in the Search Box above the Start Button and press the ENTER key. Click on OK and after the space calculation you will see a window with a list of Files to delete. Use
the scroll bar to the right of the window to see the entries further down the list. Check the boxes before Service Pack BackUp Files and Windows Update CleanUp and click on OK
http://www.sevenforums.com/tutorials/122262-windows-7-sp1-disk-cleanup-tool.html
The Service Pack BackUp Files and Windows Update CleanUp options can produce significant reductions in disk space used. When you have run Disk CleanUp please let me know how much the free disk space has become.
Hope this helps, Gerry -
Hi there, I'm using an Asus laptop (about 2 years old now) and recently started getting random blue screens. They aren't constant, but frequent enough to be a problem. I've tried doing a memory test on my RAM and did a full scan/repair of my hard drive and
didn't find any errors. Sometimes these blue screens come while i'm logging in (usually the cancel_state_in_completed_irp) after having closed the laptop for the night, sometimes they happen completely randomly while using it or even idling (driver_irql_not_less_or_equal).
I'm living in China so taking it somewhere to be looked at isn't an option, so I was hoping I could find some help here. I'm not exactly sure how to post the dump file info, I've just been using BlueScreenView to look at it, here's the info it gives me:
100214-27705-01.dmp 10/2/2014 1:26:51 PM
CANCEL_STATE_IN_COMPLETED_IRP 0x00000048
fffffa80`0d772590 fffff8a0`196743b8
00000000`00000000 00000000`00000000
PECKP_x64.SYS PECKP_x64.SYS+1160
x64 ntoskrnl.exe+75bc0
C:\Windows\Minidump\100214-27705-01.dmp
8 15 7601
262,144 10/2/2014 1:28:27 PM
093014-28626-01.dmp 9/30/2014 7:26:05 PM
DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1
00000000`00000020 00000000`00000002
00000000`00000000 fffff880`0b37ec24
PECKP_x64.SYS PECKP_x64.SYS+5c24
x64 ntoskrnl.exe+75bc0
C:\Windows\Minidump\093014-28626-01.dmp
8 15 7601
262,144 9/30/2014 7:27:15 PM
I'm not sure these will be helpful but if more info is needed, please let me know. Thanks a lot!Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
-- %systemroot% is the environment variable for your Windows directory. For example, C:\Windows.
2. Copy any and all .DMP files in the Minidump folder to your Desktop, create a new folder on the Desktop to put these .DMP files in, and then zip the folder. You can then either use a 3rd party tool such as 7-Zip/Winrar, or you can use Windows'
default method of zipping folders.
Compress and uncompress files (zip files).
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, and your Minidump folder is empty, you will need
to allow the system to crash once again to generate a crash dump.
3. Upload the .ZIP containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply.
Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel Memory Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel Memory Dumps in the simplest definition is a Kernel Memory Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel Memory Dump is
the best choice. Do note that Kernel Memory Dumps are much larger
in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for
all drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the
system log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama
Maybe you are looking for
-
Need Help in Breaking a big view into multiple small views or tuning the vw
Hi I have the following view can some one help me in breaking the view in small views or any recommendations for tuning it. CODE CREATE OR REPLACE FORCE VIEW "CRUVPD"."PX16_CHK_VW_SUMMARY_VW" ("CIDN", "BATCH_NUMBER", "BUSINESS_UNIT", "CHECK_VOUCHER_N
-
Which fan is best to use with hp dv6-6198sp?
The laptop is orginally a dv6-6153ea but i upgraded the motherboard and cpu to that of a dv6-6198sp, So it now has a ati 6770 and core i7 2670qm which i need to keep cool Temps are reaching 95 on load which i feel isn't that great! I have two fans i
-
How to verify that an event is triggered
Hi Experts, I am running a BW job that is based on an event (or basically a group of events using event collector). Some times, I need to debug it to find out why the job is not triggered and it is very difficult to find out which event was not there
-
Regarding events in alv reports
Dear Friends, Sorry for this post, Events not triggering in alv reports. There is no errors and no warnings.I am using interactive reports. Please tell me where could be i went wrong. It is displaying basic list information but with out event
-
Converting an interactive Flash animation for iOS
Hello - I am a bit of a Flash newbie - but we have some interactive particle simulators that had been programmed in Flash (.swf files). I would like to find a way to convert these into some other format for use in iBooks Author. How difficult would t