BSOD ntoskrnl 186153 on HP Pavilion
When turning off my PC i get a BSOD.
Dump: https://onedrive.live.com/redir?resid=2CDA6EF17EDB9C4B!39072&authkey=!AKBSR-hjY_5v4Yc&ithint=file%2c...
BiosVersion = F.34
BiosReleaseDate = 12/19/2014
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion 17 Notebook PC
SystemFamily = 103C_5335KV G=N L=CON B=HP S=PAV X=Null
SystemVersion = 0975100000405F10000620180
SystemSKU = J3S44EA#UUG
BaseBoardManufacturer = Hewlett-Packard
BaseBoardProduct = 2282
BaseBoardVersion = 77.35
There is a second problem which might be related. When I close the lid of the laptop, an I open it a few minutes later, the screen is death and black. I have to force a shutdown and the restart the PC. This al happens with the power supply connected to the 220 V net.
Here follows also a JRT report:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Junkware Removal Tool (JRT) by Thisisu
Version: 6.4.3 (03.01.2015:1)
OS: Windows 8.1 x64
Ran by Walter on ma 09/03/2015 at 9:56:35,25
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~ Services
~~~ Registry Values
~~~ Registry Keys
Successfully deleted: [Registry Key - Orphan] HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{0E8A89AD-95D7-40EB-8D9D-083EF7066A01}
Successfully deleted: [Registry Key - Orphan] HKEY_CLASSES_ROOT\CLSID\{0E8A89AD-95D7-40EB-8D9D-083EF7066A01}
Successfully deleted: [Registry Key - Orphan] HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{0E8A89AD-95D7-40EB-8D9D-083EF7066A01}
Successfully deleted: [Registry Key - Orphan] HKEY_CLASSES_ROOT\CLSID\{0E8A89AD-95D7-40EB-8D9D-083EF7066A01}
~~~ Files
~~~ Folders
Successfully deleted: [Folder] "C:\Users\Walter\AppData\Roaming\drivercure"
~~~ FireFox
Successfully deleted the following from C:\Users\Walter\AppData\Roaming\mozilla\firefox\profiles\cjify4n2.default\prefs.js
user_pref("extensions.G1acwiedJv.scode", "(function(){try{var url=(window.self.location.href + document.cookie);if(url.indexOf(\"acebook\")>-1||url.indexOf(\"warnalert11.com\"
~~~ Event Viewer Logs were cleared
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Scan was completed on ma 09/03/2015 at 10:12:47,28
End of JRT log
Regards
Walter
Hi
Firstly follow the steps provided in this article to resolve your driver issue
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a...
Checkurtech
****Click the White Kudos star to say thanks****
****Please mark Accept As Solution if it solves your problem****
Similar Messages
-
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. *** -
BSOD ntoskrnl.exe?
Got a bsod with 0x00000124 .
Heard blue screen viewer can be wrong sometimes but it said ntoskrnl.exe was the problem?
Not sure if I'm using this thing correctly but this is the minidump http://1drv.ms/1wvmcmq
Also am running driver verifier and restarted.
It's suppose to take a while right?
And can I continue playing while it runs?Cshn
This was called a BCC124 and it is related to hardware. SInce the DMP references Genuine Intel I would start by running a CPU stress test
Try this free stress test: http://www.mersenne.org/freesoft/
Prime95 Setup;
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
The Test selection box and the stress.txt file describes what components that the program stresses.
Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see
if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though
it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications,
games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether
the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps
above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\110414-2854-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e53890
Debug session time: Tue Nov 4 01:05:10.806 2014 (UTC - 5:00)
System Uptime: 0 days 0:26:06.602
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800703c028, ba000000, 58000402}
Probably caused by : GenuineIntel
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800703c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000058000402, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
fffff880`0310ab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae
FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag -
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 -
Pavilion Elite e9180f freezes, crashes, BSOD
I am one of the many unhappy customers who bought this piece of junk (Pavilion Elite e9180f) and waited too long to return it because in my naivete, I thought it was some kind of simple software issue. Nope! It's definitely something wrong with the hardware, because the freezes and crashes have been happening since day 1, right when I took the thing out of the box.
Yeah, the system is fast and runs Windows Vista great, when it's actually WORKING, which is usually only guaranteed for about the first 5 minutes after you power the system on and boot windows. After that, it's just buying time before it crashes again. Forget trying to get anything done on this computer. Forget about asking this PC to play a video or music file without the files "stuttering" during playback. Even my 7 year old Sony Vaio which is running XP can handle playing an MP3 file without stuttering and crashing!
Like everyone else, the freezes and crashes happen either one of two ways:
1) The machine begins to "stutter", stutter more, then freeze/crash. When I say stutter, I mean I move the mouse, the pointer graphic will hesitate on the screen and lag behind. If you start to play a video or music file, this manifests in an audible "stutter". The stuttering gets worse and worse as minutes pass until eventually it freezes for good, blasting that 1/50th second moment of audio into infinity. You have to reboot immediately if you don't want to go deaf or be driven mad.
2) I will be doing nothing at the time (example, I close all programs out and leave Windows sitting on the main desktop screen), I'll walk out of the room for a minute, then come back and find I can't move the mouse. This system will often lock-up without any warning!
Sometimes I'll get a BSOD or error screen, sometimes I won't (in which case your only option is to do a cold re-boot.) When I do get the BSOD, the error is ALWAYS the "did not get a response from the secondary processor" yada yada. I wish HP would just admit they shipped this model out with a bad processor/motherboard/whatever and do an official recall. I have owned PCs for the last 13 years and this is the worst and most consistently disappointing experience I have ever had.
What is the hardware issue? Which part is the lemon part? The motherboard? The processor? The BSODs seem to indicate a bad processor. I do have the Pegatron Truckee version 1.03 motherboard. Is that the problem?
P.S. I have contacted HP on many occasions about this, literally stayed on the phone for hours with "customer support" (according to one HP rep, 80% of their customer service reps are based outside of the United States...good luck getting any "technical" help from them) to no avail. I did talk to one nice tech support guy in Canada who said "it sounds like your unit has a bad processor", so he had HP send me a box to ship my unit to their repair center so they can replace the processor. However, I have also had HP reps tell me it could be anything from the memory to the hard drive. Multiple HP reps claimed to me that they have "received no complaints" about this system. One guy told me he "thought he got an email last week" regarding "something" about the system, but couldn't remember what it was and he put me on hold while he searched for the email. He never found it. What a joke.
EDIT: Just to clarify, the crashing issue has been happening since day one, but initially I thought it was an issue with Vista. I had never owned or used Vista before, so I thought maybe Vista was just unstable. Nope. I know several people who own Vista and have never experienced these issues. I have downloaded every update from Microsoft/Windows Update. I have upgraded to Vista SP2 with all the latest drivers and software for all of my hardware. No luck. It is definitely a hardware issue. Thank god HP's warranty is good for 1 year (I bought my Elite in July).
Message Edited by Doonyman on 09-24-2009 02:58 AMUnfortunately I have to add my disastrous encounter with HP's E9180F a true lemon HP is selling. I must take some responsibility for not carefully researching this model before I purchased, but I trusted the HP name and got stung- big time.
The scoundrel :
HP and its Pavilion Elite e9180f
Windows 7 64bit
motherboard - Pegatron Truckee ver 1.03
BIOS ver 5.22Intel Core i7 920 @ 2.67GHz
Memory 9206 MB Ram
As so many others have reported my HP E9180f started locking up and going to BSOD right out of the box. My first freeze-up came when I was doing the Windows update process. At first I didn't think much about it but I started getting random freezes a couple time a day. At that point I went online to see if others had experienced the same problem and perhaps had a fix. What I found was very troubling; I found extensive documentation describing my exact problems and what was really horrifying was the reports of how ridiculous HP's help services were treating people with the problem. At first I didn't totally believe what I was reading on HP's own customer forum; I do now.
· I've went through the total recovery process three times now, HP techs have spent hours remotely running my computer, (yes it did lock up on them to)
· I had to upgraded the BIOS. (HP tech tried, said he had, but he hadn't)
· I was directed to clear the BIOS (luckily for me I had the tools
· Updated all drivers again and again.
· Next I was asked to remove the video card, memory, and motherboard power cable and reseat them. I declined because I didn't want to give HP any reason to void my HP 2 year House Call Care Pack which covers this unit. When I invited HP to send a service tech out to perform these tasks, they said that house call only covers part replacement, we weren't replacing a part. I couldn't believe what I was told. Are you feeling my frustration?
Keep in mind that each time HP requests that I make changes, they then ask me to test the system, which I did and each time with the same result, BSOD
I'm heading into my fifth week of working with HP to fix this problem. and I still haven't even been able to get my case moved up to a senior case manager, what a joke HP's help process is.
One conversation I loved was;
HP tech: "I'll have a senior case manager call you within 24 hours."
Skeptical me: "What should I do if I don't get a call?"
Silence, no response.
Me again: "What should I do if I don't get a call?"
HP tech: "That's an impossibility."
Guess what? The impossibility became reality (I bet you guessed) .
HP's last stall tactic was to have me fax them my proof of purchase and invoice and call back in 24 hours. Where have I heard that before? Apparently nothing can go forward until they receive it. So I faxed them the stuff within 10 minutes, and when I called back 24 hours later, guess what, you're right it wasn't on their system yet. I asked couldn't I be escalated to a senior case manager (it's apparent that only a senior case manager can do anything). "No," was the tech's reply, "call back again later".
Please if anyone out there knows the secrete to getting a senior case manager, or an HP tech support number here in the U.S. so I can get this thing fixed I'd love to know it.
Fast becoming HP never again. -
Pavilion dv6-3130tx Blue Screen (BSOD) on adding RAM to second slot
Hi there,
I own a HP Pavilion dv6-3130tx with total of 3gb of RAM, one 1GB chip and one 2 GB chip. Recently I have been getting a lot of system crashes/freezes and occasional Blue Screen of Death (BSOD) with a variety of error messages. On contacting HP care in India they said to check the RAM chips and the slot for any problem. I have identified that the second slot is one creating the problem as the system crashes if use any one of the chips on that slot while both the RAMs work fine on the other slot.
Additionaly the RAM port/slot cannot be replaced as such, and since it is out of warranty getting the motherboard replaced isn't an alternative either.
So does anyone have any idea what might be the best way out of this problem?Did the 3GB of RAM come with the computer or did you upgrade it at some point?
What version of Windows are you using?
-------------How do I give Kudos? | How do I mark a post as Solved? -------------------------------------------------------- -
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 -
HP Pavilion DV6; Black Screen & Atikmpag.sys BSOD with external Monitor
Hello Guys.
I have HP Pavilion DV6 Core i7 with ATI Mobility Radeon HD 5650 Graphics Card. Two weeks ago, I started getting continous Atikmpag,sys BSODs. The operating system also started giving me warnings about the hardrive. After a few days, the BSODs got more frequent. Then one day, I was doing normal stuff on my PC and the Display Driver crashed. Instead of recovering, the PC froze. I forced restart my PC but it got worse. The display of my laptop went black. I connected the laptop to external monitor which detected the display. When I tried to load the windows, it started giving me the Atikmpag.sys BSOD on the start up. Now the operating system works fine in the Safe Mode but with nothing on the laptop's screen. The soultions I have tried so far are.
-Reinstalled the windows thrice
-Removed the drivers and installed the updated ones a bunch of times.
-Rolled back the bios to an earlier version
-Removed the hardrive and tried to load it from an operating system installed on external flash drive
-Tried loading the PC with linux on external flash drive
-Opened the laptop and cleaned it thoroughly
-Removed all the components and plugged them one by one.
-Removed the old Atikmpag.sys in system32 folder and expanded it with the latest ones.
-Installed every thing fresh from HP website
None of these tricks have given me any luck yet. The only way, I could use the operating system in normal mode, is to delete the atikmpag.sys file in safe mode and then log on back in normal mode. I also analysed the minidump file through window debugger and it says that atikmpag.sys is causing this crash with the TDR message. I did all these with an external monitor as the display of the laptop is black since that day.
Below are the detailed specs of my laptop.
OS Name: Microsoft Windows 7 (64 bit) Home Premium
Version: 6.1.7601
System Model: HP Pavilion Dv6 Notebook PC
Processor: Intel Core i7 Q 721 @ 1.60 GHz
Bios Version/Date: Hewlett- Packard F.29, 11/7/2011
Installed Physical Memory (RAM): 6GB
Graphics Card: ATI Mobility Radeon HD 5650 1 GB
I have tried almost every solution available on these forums but still have not gotten any where. I am wondering how could the display, graphics card and hard drive stop working at the same time .
I would really appreciate if someone colud help me through this problem.
Thank you
P.S. Kindly ignore my English mistakes as it is not my first language.Hi Goloono,
Welcome to the HP Forums!
I would like to take a moment and thank you for using the forum, it is a great place to find answers. For you to have the best experience in the HP forum, I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
First I would like to reassure you your English was great, I had no problems understanding you.
I grasp that you are getting a black screen with the error message " Atikmpag.sys".
Here is a link to Troubleshooting Error Messages on a Black Screen that may Occur During Startup or Boot.
Have you run The HP Support Assistant to help with updates and resolving issues.
Here is a link to a Microsoft Community Page with this exact issue. There are some suggestions that may help.
Blue Screen error with atikmpag.sys in Windows 7 .
Here is a link to the HP software and driver page. You will need to input your exact model of DV6 you have and follow the prompts. This page will have the recommended drivers and it will list bios updates. if there are any applicable ones.
HP Drivers & Downloads.
How Do I Find My Model Number or Product Number?
At one point you state you had a hard drive error, to rule that out I would run a diagnostics. SMART Media Test Error Appears when Notebook is Started
Please let me know if this has helped.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping! -
BSOD hal.dll+12903 and ntoskrnl.eve+185543
I have been working on this PC for quit some time the person before me had no records of what was wrong with the PC or what he did to correct it. The PC shuts down at random and freezes at times, I had changed the UPS, the power cord and even noticed that
the heat sink was loose fixed that. Still the PC kept freezing, I decided to go ahead and re-install Win7 now its BSOD and I used Bluescreenview to view the errors and hal.dll and ntoskrnl.exe appeared. I ran a mem test and it was ok ran an HD test and still
good. Any help is appreciated thanks in advance.
Running Win 7 pro 64bit
4gig ram
video: NVIDIA GeForce 8400GS
mobo: P5N-E SLI
==================================================
Dump File : 061914-34788-01.dmp
Crash Time : 6/19/2014 9:02:30 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04cbe038
Parameter 3 : 00000000`b2000000
Parameter 4 : 00000000`00010014
Caused By Driver : hal.dll
Caused By Address : hal.dll+12903
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061914-34788-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 270,984
Dump File Time : 6/19/2014 9:04:35 AM
==================================================
==================================================
Dump File : 061914-38735-01.dmp
Crash Time : 6/19/2014 8:55:48 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`017ac900
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061914-38735-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 270,984
Dump File Time : 6/19/2014 8:57:53 AM
==================================================Tmtz15
There wer all related to hardware and called BCC124
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/
Wanikiya and Dyami--Team Zigzag -
Have a BSOD on my Pavilion p6539uk PC. PC is only about a year old. Windows Home Premium i5 Intel, Explorer 9.
62 and 32 bit . All drivers up-to-date.
All answers welcome!
grandun99Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try another cable
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar
The missing apps could have been done by setting the Restrictions that can hid those apps. If the backup was made with those retrictions set the the Restrictions are also restored.
Thus, if you get it to work restore to factory settings/new iPod, not from backup
You can redownload most iTunes purchases by:
Downloading past purchases from the App Store, iBookstore, and iTunes Store -
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. -
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 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 -
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 -
Graphics Driver Confusion - BSOD HP Pavilion dv9500
My wife has a 32 bit Vista laptop whose service tage translates into a dv9657cl. A few days ago she started getting seemingly random BSODs. When I got a chance to see it, it referenced file nvlddmkm.sys with a stop code of 0x116.
It seemed like a display driver problem so I did a Google search on the error, was taken to an NVIDIA website were I downloaded and installed the latest GeForce driver. I rebooted and gave the laptop to my wife. I felt very good about myself.
A few hours later she gave it back. Trying to watch some video from Facebook gave her the same BSOD error. I went to the HP Driver page, and was prompted to Scan your system for out-of-date and missing drivers and software. Seemed easy enough although I was told I needed some additional software for HP to do the scan. OK. I downloaded some framework software and assumed I would get a scan result.
I did not. Instead it translated my dv9500 to dv9657cl and wanted to know if I needed drivers or to report a problem. Reporting a problem took me to screens that addressed specific error conditions, none of which were the nvlddmkm.sys problem I was encountering. Choosing drivers took me to a page for my laptop and OS. The graphics drivers expanded into 3 choices , each of them saying something to the effect that each selection contained the video driver for the supported notebook models and operating systems.
What? So not only am I not getting a scan result showing me my outdated drivers, but now I have to guess which driver to download. Since I've already given HP my model number and OS, shouldn't they be able to tell me what graphics driver I need?
And what's the scoop on that Scan my system for outdated drivers debacle?Hi @boweasel ,
Thank you for your query, I will do my best to assist you!
Your wife was getting random Blue screens. When you had a chance to check the notebook it referenced this error "e nvlddmkm.sys with a stop code of 0x116. This does seem to indicate a driver error.
I am unsure why the HP scan you system for out of date and missing drivers and software did not work. I am unable to explain why it failed or why the incorrect product was show.
HP does not recommend using drivers from the manufacturer's sites as they have not been tested on your system. The ones listed on the HP driver download page are tested and may have been modified to perform correctly with your notebook.
Here is a link to Downloading or Updating Software and Drivers for HP Computers
I suggest you run the HP Support Assistant to aid with HP updates and resolving issue. The HP support assistant will also list your computer and its exact model under system information to confirm that it is a 9657cl as you stated in the first line of your post. That would also be why the auto scan detected it as such.
If the service tag and the HP support assistant states it is a DV9657cl then that must be what you have. Here is the HP Pavilion dv9657cl product specifications page so you can compare the product numbers to confirm this.
How Do I Find My Model Number or Product Number?
As HP produces many models of the same for different regions. it may list more then one driver for your unit. This is to cover all of them. You would need to select the correct one for the specific device in your system or run an automated tool to select it for you. ( HP Support Assistant)
If you input one model and OS and it detected a different model it may have confused the scan for drivers option.
I hope this helps.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!
Maybe you are looking for
-
When I connect my iPod touch to my computer, I have a list of Events on my iTunes-iPod-Photos. I want to erase these Events. However, the photos are NOT on my MacBook Air-iPhoto. When I check one of the Events and then hit Apply, the photos appear on
-
After having SSO user password through url not working
Hi guys, We have an Institutional portal and BW portal to publish reports. Before the SSO was configured we had some UrlIViews where we fixed a user and password through the url, ie: http://myportal.net:50400/irj/servlet/prt/portal/prtroot/pcd!3apo
-
IOS 7 Usage Messages (Saved) very high
In the past i have freed up 'OTHER' usage (as only shown in itunes) by deleting imessages (mostly with pics and vids). But I have never been able to get OTHER empty, but it would slowly go down as i cleared these msgs up. Now with IOS7 I'm happy to
-
Usage of FM "HR_ABS_ATT_TIMES"
Hi, Any example program to illustrate usage of functional module HR_ABS_ATT_TIMES? Thanks.
-
Hello, I made a distribution kit for one of my programs, but then decided to add onto the program. When I went to build another distribution kit, Labwindows stops partway through and says that NI-488.2 couldn't be found in the directory and to insert