Ntoskrnl.exe causing "DRIVER_POWER_STATE_FAILURE" in case of sleep

Similar Questions

• BSOD caused by ntoskrnl.exe - bug DRIVER_POWER_STATE_FAILURE

  Hi all

  I'd appreciate help with my laptop problems I don't know neither the cause nor the solution...

  For several months, my laptop refuses to close directly. I explain: when I want to stop it, any reboot my laptop and I have to stop him again so he can actually stopped. In addition, at each attempt to stop / restart, I have this incredible Blue Screen of Death for 15 to 20 minutes, then my laptop actually restarts. Once it has restarted, it works normally for 3 minutes and then freezes for a duratation ranging from 5 min to 40 min...

  In addition, since the beginning of these problems, my laptop detects no USB devices (mouse, external driver...)...

  Please help me, this situation is driving me crazy...

  My laptop is an Asus ux32v and runs on 64-bit processor - i5 3317U and Windows 8 (if it helps).

  Here is the link to my minidump files:

  https://www.dropbox.com/sh/ix3bf3v7aog2xz5/AAAcgX3yNBDWVAj5JXs9JNzSa?DL=0

  I tried to open these files with software like BlueScreenView but couldn't do much about it. What I realized is that it was caused by ntoskrnl.exe.

  Thank you in advance for your help!

  MS

  It is possible because you do not remove it completely.  He was always loaded into the current DMP file

  You do not update to win 8.1.  I'll wait until you do.

• Ntoskrnl.exe causing blue screen saying "DRIVER_POWER_STATE_FAILURE" in Windows Vista

  At random intervals (and I mean, it may happen by week or 1This 2This every 2 months) I get a blue screen.  I said "DRIVER_POWER_STATE_FAILURE" and made a dump.  It doesn't happen ever if I'm doing something important, like writing a paper for school or by downloading a video for a class online.

  So far, I have:

  • Analysis of material of Ran
  • New Windows Vista installation with all updates for the OS and programs
  • Installed on another hard drive with all the updates to the OS and core programs

  Nothing has worked so far.

  My Info to the computer:

  http://S217.Photobucket.com/albums/cc205/psychobarbiehaxor/?action=view¤t=Compinfo.jpg

  The file of errors:

  http://S217.Photobucket.com/albums/cc205/psychobarbiehaxor/?action=view¤t=ErrorInfo.jpg

  Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE

  DRIVER_POWER_STATE_FAILURE bug control has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.

  http://msdn.Microsoft.com/en-us/library/ff559329%28VS.85%29.aspx

  Please copy the files of the dmp to the C:\Windows\Minidump folder first on your desktop, zip dmp all in 1 zip file and download the zipfile to your Skydrive [1] and post a link here, so that I can look at landfills.

  André

  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 [1]

  "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• Ntoskrnl.exe + df273 and ntoskrnl.exe + 70740 DRIVER_POWER_STATE_FAILURE

  Hello

  I've read all the forum and the same problems in microsoft answers com

  but nothing helped...

  I have the model of the laptop MSI GT70 0ND

  Windows 7 64 bit - Ultimate

  I7 - 3630QM - 2.40 GHz

  8 GB RAM

  Intel HD4000 and Geforce MX GT675

  1 TB HARD DRIVE

  The laptop runs normally. The only problem is when I come back from work and I started cold and after 5 minutes of BSOD POWER STATE ALREADY

  I saved the dmp file and I am sharing this now...

  Link: http://www.mediafire.com/download/6if350f0isy3uak/063016-17144-01.dmp

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.1.7600.2.0.0.256.1
  Locale ID: 1031

  More information about the problem:
  BCCode: 9f
  BCP1: 0000000000000003
  BCP2: FFFFFA80079DBA20
  BCP3: FFFFF800047D5748
  BCP4: FFFFFA800D4ECC50
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

  If anyone can help me, I will be very aprriciate.

  better compliance

  Kriss

  Related to your driver nVidia video

  Completely, remove the current (or software) driver and install the latest driver available.  For instructions on how to do read everything to update the drivers of my partner JMH3143 http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149 here

  0: kd >! devstack fffffa80079dea10
  ! DevObj! DrvObj! DevExt ObjectName
  fffffa800a687040 \Driver\nvlddmkm fffffa800a687190 InfoMask field not found for _OBJECT_HEADER to fffffa800a687010

  fffffa80079d1860 \Driver\ACPI fffffa80073ddd50 InfoMask field not found for _OBJECT_HEADER to fffffa80079d1830

  > fffffa80079dea10 \Driver\pci fffffa80079deb60 cannot read the offbeat info from nt! ObpInfoMaskToOffset

  ! DevNode fffffa80079d78b0:
  DeviceInst is "PCI\VEN_10DE & DEV_11A7 & SUBSYS_10D91462 & REV_A1\4 & 31a1af22 & 0 & 0008"
  ServiceName is "nvlddmkm"

• Ntoskrnl.exe + 78a8a (DRIVER_POWER_STATE_FAILURE) - Windows 7 x 64

  Lately, I get the BSOD 5 times a day.

  I enclose below the dump files

  http://www.girlshare.ro/34038244.9

  http://www.girlshare.ro/34038244.9

  If anyone can help I would really appreciate it

  Ricklys

  These have been associated with RtsUStor.sys USB Mass Storage Driver for 2 K/XP/Vista/Win7 of Realtek Semiconductor Corp.  I remove the current driver and install the latest driver available.

  

• Windows 8 blue screen - DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe

  I have a new Sony Vaio Pro and have experienced outages of system 3 times.  All the accidents that happened after I've restored from hibernation and were related to the bug check DRIVER_POWER_STATE_FAILURE.  After the first two accidents, I ran Sony diagnostics on the memory and hard drive SSD and they passed the test.  I even sent my Vaio Pro to the repair depot to Sony for a test on the memory, hard drive and other hardware and they all passed.

  I found my Vaio Pro last Wednesday and updated the Windows 8 from scratch.  This morning, after the resumption of hibernation, I realized my Bluetooth mouse did not work.  So I stop the laptop hoping a restart could solve the problem.  However, it took almost 5 minutes before they would stop and restart Windows gave a warning:

  "Experienced problem with closed Windows.  Your PC fell on problem.  This problem case your PC to restart.

  BlueScreen Viewer it pointing DRIVER_POWER_STATE_FAILURE caused by driver ntoskrnl.exe.

  BlueScreen details as follows:

  A problem has been detected and Windows has shut down to prevent damage to your computer.

  The problem seems to be caused by the following file: ntoskrnl.exe

  DRIVER_POWER_STATE_FAILURE

  If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

  Check to make sure any new hardware or software is installed correctly.

  If it is a new installation, ask your hardware manufacturer or software, the Windows updates, you might need.

  If problems continue, disable or remove any newly installed hardware or software. Disable the BIOS memory options such as implementing caching or shading.

  If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options and then

  select Safe Mode.

  Technical information:

  STOP: 0X0000009F (0X000000000000012C, 0XFFFFFA80196707C0, 0 X 0000000000000004, 0XFFFFF880009EC810)

  Ntoskrnl.exe - address 0xfffff80189072106 base at 0xfffff8018901e000 DateStamp

  0x51a966cd

  Here's my minidump file:

  https://DL.dropboxusercontent.com/u/1928780/093013-7531-01.dmp

  File Msinfo32.NFO:

  https://DL.dropboxusercontent.com/u/1928780/Msinfo32.nfo

  Dump file memory (do not know why this file is nearby big 550MO):

  https://DL.dropboxusercontent.com/u/1928780/memory.dmp

  p.s. I think this may have something to do with my Bluetooth driver I had experienced many times the Bluetooth driver has been disabled by Windows and the event viewer reported "the Local Bluetooth is not indeterminate way and will not be used.  The driver has been unloaded. "

  Thanks in advance,

  William

  Hi William,.

  The attached file of the DMP is the error checking DRIVER_POWER_STATE_FAILURE (9f) .

  This bug check indicates that the driver is in an inconsistent or invalid power state.

  9F, {4, 12 c, fffffa80196707c0, fffff880009ec810} error checking

  Parameter 1 of the bugcheck is 4 , which indicates that the transition of power over waiting to synchronize with the Pnp subsystem.

  The 2nd setting is 12 c , which indicates that it is exceeded for a total of 12 seconds.

  By default, the crash dump is failing UsbHub3.sys who is the pilot of HUB-USB3 (System driver and not the true cause, and is due to the fault by something else).

  If we look further into the dump:

  ERROR: Module load completed but symbols could not be loaded for btmhsf.sys

  FAILURE_BUCKET_ID: 0x9F_4_btmhsf_IMAGE_UsbHub3.sys

  Implicit thread is now fffffa80 196707 c 0

  ^^ If we run one! thread on the address fffffa80 196707 c 0:

  Child-SP RetAddr: Args to child: call Site
  fffff880 '20b42f20 fffff801' 890bb7cb: fffffa80'00000001 00000000'00000000 00000000'00000003 00000000'00000000: nt! KiSwapContext + 0 x 76
  fffff880 '20b 43060 fffff801' 890ba60f: fffffa80'18b23ef8 fffff880 '0115a 178 00000000 00000000' fffff880' 0622a 202: nt! KiCommitThreadWait + 0x23b
  fffff880'20 b 43120 fffff880'06114700: fffffa80 '16115fd8 fffff880' 00000001 00000000' 00000000 00000000'00000000: nt! KeWaitForSingleObject + 0x1cf
  "fffff880 '20b431b0 fffff880' 06117ef0: 00000000 ' 00000018 fffff880 ' 0622a2f8 00000000'00000000 00000000'00000018: btmhsf+ 0 x 33700
  fffff880 '20b431f0 fffff880' 060fb1e4: fffffa80'17 has 00030 fffff880 '20b433b0 fffff880' 0622a2f8 00000000' 00000000: btmhsf+ 0x36ef0
  fffff880 '20b 43260 fffff880' 060e2b84: 0000057f 'e9eaddd8 00000000' 00000127 fffff880 '0622a2f8 fffff880' 0115 has 178: btmhsf+ 0x1a1e4
  fffff880 '20b432b0 fffff880' 060e2cce: 00000000'00000008 fffff880 '20b 43370 00000000'00000008 fffff880' 20b 43378: btmhsf+ 0x1b84
  fffff880 '20b432e0 fffff880' 0114ecb0: fffffa80'16153860 00000000 00000000' fffff8a0 '04c3a748 fffff801' 89403cfe: btmhsf+ 0x1cce
  "fffff880 '20b 43310 fffff880' 010e881d: 00000000 ' 00000127 fffff880 ' 20b433b0 00000000'00000119 fffffa80'16153860: Wdf01000! FxPkgPnp::PnpEventSurpriseRemoveIoStarted + 0x2c
  "fffff880 '20b 43340 fffff880' 010e9032: fffffa80 ' 16153980 fffffa80' 16153988 fffffa80 ' 16153860 fffff880 ' 20b434c0: Wdf01000! FxPkgPnp::PnpEnterNewState + 0x1a1
  "fffff880 '20b433e0 fffff880' 010e8cdd: 00000000 ' 00000000 fffff880 ' 20b434c0 fffffa80 ' 16153970 fffffa80' 16153860: Wdf01000! FxPkgPnp::PnpProcessEventInner + 0 x 122
  fffff880'20 b 43450 fffff880'0114 701 d: 00000000 00000000' fffffa80 '16153860 fffff880' 00000000 00000000 00000000': Wdf01000! FxPkgPnp::PnpProcessEvent + 0x18d
  fffff880 '20b434f0 fffff880' 010d1ecf: fffffa80'16141 b 30 fffff880 '20b 43570 00000000 00000000' fffffa80' 1615d1d0: Wdf01000! FxPkgFdo::_PnpSurpriseRemoval + 0 x 25
  fffff880 '20b 43520 fffff880' 010c99da: fffffa80'197 b 9010 fffffa80 '197b 9010 fffffa80' 197b 9010 00000000 00000000': Wdf01000! FxPkgPnp::Dispatch + 0x18f
  "fffff880 '20b 43580 fffff880' 010c9aa6: fffffa80' 197b 9010 00000000'00000005 fffffa80 ' 161531 c 0 fffff880 ' 062fca20: Wdf01000! FxDevice::Dispatch + 0x19a
  fffff880 '20b435c0 fffff880' 062e3cbe: fffffa80 '197b 9010 00000000 00000005' fffffa80' 1615e190 00000000' 00000000: Wdf01000! FxDevice::DispatchWithLock + 0xa6
  fffff880 '20b 43600 fffff880' 062e3484: fffffa80 '197b 9010 00000000 00000000' fffffa80' 1615e190 00000000' 00000000: bthport! BthDefaultPnpHandler + 0x2a
  fffff880 '20b 43630 fffff880' 062e2cc1: fffffa80 ' 1615e190 fffff880 '062fca17 fffffa80' 1615e190 fffffa80 ' 197b 9010: bthport! BthHandleSurpriseRemoval + 0xc4
  fffff880 '20b436b0 fffff880' 062e2b04: fffffa80' 197b 9010 00000000'00000701 fffff880 '062fca20 fffff880' 20b 43800: bthport! BthHandlePnp + 0x16d
  fffff880 '20b 43700 fffff801' 8940a8f7: fffffa80 '1615e040 00000000' c00000bb 00000000 00000000' fffff880' 00a 82180: bthport! BthDispatchPnp + 0 x 68
  "fffff880'20 b 43750 89526 fffff801 39 d: 00000000 ' 00000017 fffff880 ' 20b 43819 fffffa80 ' 16137710 fffffa80' 16137060: nt! IopSynchronousCall + 0xc7
  fffff880 '20b437c0 fffff801' 895265e6: fffff8a0 ' 04069710 00000000'00000308 fffffa80' 16137060 00000000 00000000': nt! IopRemoveDevice + 0xd9
  fffff880'20 b 43880 fffff801'89526501: fffffa80'16137710 00000000 00000000' fffff8a0 '0c432a01 fffff880' 20b 43930: nt! PnpSurpriseRemoveLockedDeviceNode + 0xaa
  fffff880'20b438d0 fffff801'89526468: fffff8a0 00000000'00000000 00000000'00000000 ' 0c432a70 fffffa80'16137710: nt! PnpDeleteLockedDeviceNode + 0x5d
  fffff880 '20b 43910 fffff801' 89525bcb: 00000000 00000000' fffff880 '20b43a70 fffff8a0' 0b89e6f0 00000000'00000005: nt! PnpDeleteLockedDeviceNodes + 0 x 98
  fffff880 '20b 43970 fffff801' 893b52e5: fffff880'20b43b88 00000000 00000000' fffff8a0 ' 05764100 fffff8a0' 00000000: nt! PnpProcessQueryRemoveAndEject + 0x2c3
  fffff880'20b43ae0 fffff801'89418346: fffff8a0'04069710 00000000'00000000 00000000'00000001 00000000'00000000: nt! PnpProcessTargetDeviceEvent + 0x9d
  "fffff880 '20b43b20 fffff801' 890b62a1: fffffa80 ' 196707 c 0 fffff8a0 ' 0b89e6f0 fffff801 ' 8941805 c fffffa80' 16748130: nt! PnpDeviceEventWorker + 0x2ea
  "fffff880 '20b43b80 fffff801' 8904afd9: fffffa80 ' 00180000 00000000 00000080' fffff801 ' b 890, 6160 fffffa80 196707 c 0: nt! ExpWorkerThread + 0 x 142
  fffff880 '20b43c10 fffff801' 890ff7e6: fffff880 ' 00a 82180 fffffa80 ' 196707 c 0 fffffa80 ' 06741b 00 fffffa80' 06765940: nt! PspSystemThreadStartup + 0 x 59
  fffff880'20b43c60 00000000' 00000000: fffff880 '20b 44000 fffff880' 20b3e000 00000000'00000000 00000000'00000000: nt! KiStartSystemThread + 0x16

  We can see the various routine calls BTHUSB Device bthport.sys (Bus Bluetooth driver) who then finally enter various before btmhsf.sys some error checking.

  btmhsf.sys is the Intel Proset Bluetooth HighSpeed filter driver and probably the culprit here. Update this driver ASAP - http://downloadcenter.intel.com/default.aspx?iid=gg_support-EN_01+home_downloadctr
  or uninstall it if you do not plan to use BlueTooth.

  ---------------------------------------------------------------------

  If after doing the above, you are still blocked, remove and replace AVG with built-in Windows Defender from Windows 8 for temporary troubleshooting purposes:

  -AVG removal tool http://www.Avg.com/us-en/utilities

  In addition, to answer your question as to why the MEMORY. DPM is so important because it's a dump of memory rather than a small kernel. Kernel memory dumps contain all the kernel memory was working with and that was in use at the time of the accident, that is why it is larger and provides much more information.

  Kind regards

  Patrick

• After sleep ntoskrnl.exe error 0x0000009f DRIVER_POWER_STATE_FAILURE

  DRIVER_POWER_STATE_FAILURE after sleep

  When I put my laptop to sleep by closing the lid or choosing sleep from the beginning, I get a bsod (ntoskrnl.exe 0x0000009f DRIVER_POWER_STATE_FAILURE) when the recovery.
  BlueScreenView report:http://dl.dropbox.com/u/12993257/bsod.htm
  Empty the file: http://dl.dropbox.com/u/12993257/091211-34538-01.zip
  Also, for some reason that I do not get the bsod when it puts itself in standby (IE after expire) but I understand when it hibernate itself.
  Any help is appreciated!
  Phil

  Hi chubble10,

  Method 1
  I suggest you try the steps from the following links:

  Stop error when you upgrade a computer that is running Windows 7 or Windows Server 2008 R2 standby or into hibernation, or when you restart the computer: "0x9F".
  http://support.Microsoft.com/kb/975599

  stop "0x0000009F" error message when a computer enters and fate of putting into hibernation in Windows 7 or Windows Server 2008 R2
  http://support.Microsoft.com/kb/981848

  Method 2
  This issue could be due to corruption of the graphics card driver. I suggest you to update the graphics card drivers.

  Updated a hardware driver that is not working properly
  http://Windows.Microsoft.com/en-in/Windows7/update-a-driver-for-hardware-that-isn ' t-work correctly

• BSOD, BCCode f9, caused by ntoskrnl.exe, could you please help me with this?

  I get the BSOD with f9 code and I do not understand what is? Could you please advice what may cause this? I'm not sure,
  It happen when I stop or restart (15 minutes with him saying to stop) followed by BSOD (pilot State power failure).
  Once I'm back I can see that Windows has recovered from unexpected shutdown down. Using BlueScreenView tells me that ntoskrnl.exe is the cause.
  I was wondering if it has something to do with the USB Ports, because it won't work as a plug-and-Play (need to reboot USB is plugged).

  I reinstall all the USB drivers.

  My system:
  ASUS Z170A
  nVIDIA GTX 980ti

  850 M2 OF EVO 250 GB SSD

  Intel Core i7 - 4700 k
  32 GB of RAM (4 sticks 8 GB)
  Windows 7 64 bit

  All up to date.

  ==================================================
  Name of the file: ntoskrnl.exe
  Address of stack: ntoskrnl.exe + e23f0
  Address: Fffff800'0325e000
  Address: Fffff800'03844000
  Size: 0x005e6000
  Time stamp: 0x5708972e
  Time string: 09/04/2016 13:46:22
  Product name: Microsoft® Windows® Operating System
  File description: NT kernel & system
  File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
  Company: Microsoft Corporation
  Full path: C:\Windows\system32\ntoskrnl.exe
  ==================================================
  ==================================================
  Dump file: 081316-13447 - 01.dmp
  Crash time: 13/08/2016-12:46:05
  Bug Check String: DRIVER_POWER_STATE_FAILURE
  Bug check code: 0x0000009f
  Parameter 1: 00000000'00000003
  Parameter 2: fffffa80'1a0f1060
  Parameter 3: fffff800'052373 d 8
  Parameter 4: fffffa80'1f739c60
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 6f400
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
  CPU: x 64
  Plant address: ntoskrnl.exe + 6f400
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\081316-13447-01.dmp
  Number of processors: 8
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 1 250 528
  Dump of file time: 13/08/2016-12:47
  ==================================================

  Hello

  There is a possibility that there is a problem with a driver on your PC. Here are a few things to try:
  • If you know which driver is causing the problem, update.
  • Make sure your hardware drivers are updated.

  Please keep us updated.

  Kind regards.

• BSOD ntoskrnl.exe + 72 0x0000009f DRIVER_POWER_STATE_FAILURE has 40

  I almost brand new HP ProBOOK 450 G2 with Windows 7 Enterprise, just noticed today the first Memory Dump, thought then to ask... like the laptop is under warranty... laptop computer is on battery power and the battery is dead so saw the light flashing 'orange' and he got the memory dump and he came down, the battery was finished It happened... but its still not the right way to go then... I have through the app "BlueScreenView" about something, but he could not say exactly... searched thing many error BSOD here in the office, but none had the same error, sharing so if someone is kind enough to help.

  Dump file 050415-21028 - 01.dmp
  Time of the accident 04/05/2015-11:01:32
  Bug Check String DRIVER_POWER_STATE_FAILURE
  Bug check code 0x0000009f
  Parameter 1 00000000'00000003
  Parameter 2 fffffa80'07f37a10
  Parameter 3 fffff800'048943 d 8
  Parameter 4 fffffa80'08da0010
  Caused by the driver Ntoskrnl.exe
  Caused by the address ntoskrnl.exe + 72 has 40

  DMP file: http://1drv.ms/1K9FKRC

  Thanks in advance

  ONE

  This phenomenon was related to rtlane.sys NDIS Driver of Realtek Semiconductor Corporation.  I remove the current driver and install the latest driver available.

• DRIVER_POWER_STATE_FAILURE ntoskrnl.exe e58d2

  I'm the blockages of the system and this is the error I get: driver_power_state_failure ntoskrnl.exe e58d2

  Here is a paste of bluescreenview log:

  ==================================================
  Dump file: 111914-29234 - 01.dmp
  Crash time: 19/11/2014-15:39:27
  Bug Check String: DRIVER_POWER_STATE_FAILURE
  Bug check code: 0x0000009f
  Parameter 1: 00000000'00000003
  Parameter 2: fffffa80'07581680
  Parameter 3: fffff800'04895748
  Parameter 4: fffffa80 12854 c. 60
  Caused by the driver: ntoskrnl.exe
  Caused by the 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)
  CPU: x 64
  Plant address: ntoskrnl.exe + 75bc0
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\111914-29234-01.dmp
  Number of processors: 8
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 1 475 032
  Dump of file time: 19/11/2014-15:41:49
  ==================================================

  Someone has an idea of what is causing this crash? Let me know what I can provide. I'm stumped on this one.

  Shaun

  I don't know your config so can suggest only you remove the current driver and then install a new one without having to reboot.  You can also contact the computer manufacturer for information about the procedure to update.

• BSoD, which is related to ntoskrnl.exe error

  Hello. I've known a few occasional BSODS, all associated with ntoskrnl.exe. Two of them were 0 x 124, while the most recent is a 0 x 101. I already ran Ccleaner in case it was a registry problem, but I doubt it. I also did a BIOS update for a couple of months. My specs are:

  Windows 7 x 64

  CPU: AMD FX-6300

  GPU: AMD Radeon HD 7750

  Motherboard: Asus M5A78L-M LX3

  Bluescreenview ran, so I'll post the reports here. Thanks for your help.

  ==================================================
  Dump file: 111614-47096 - 01.dmp
  Crash time: 15/11/2014 19:37:06
  Bug Check String:
  Bug check code: 0 x 00000101
  Parameter 1: 00000000'00000021
  Parameter 2: 00000000'00000000
  Parameter 3: fffff880'02f65180
  Parameter 4: 00000000'00000002
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 75bc0
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
  CPU: x 64
  Plant address: ntoskrnl.exe + 75bc0
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\111614-47096-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 275 608
  Dump of file time: 16/11/2014-09:36:27
  ==================================================

  ==================================================
  Dump file: 111314-38657 - 01.dmp
  Crash time: 13/11/2014-18:35:27
  Bug Check String:
  Bug check code: 0 x 00000124
  Parameter 1: 00000000'00000000
  Parameter 2: fffffa80'07fa3038
  Parameter 3: 00000000'00000000
  Parameter 4: 00000000'00000000
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 4adb5c
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
  CPU: x 64
  Plant address: ntoskrnl.exe + 4adb5c
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\111314-38657-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 262 144
  Dump of file time: 13/11/2014-18:35:49
  ==================================================

  ==================================================
  Dump file: 110514-33540 - 01.dmp
  Crash time: 11/05/2014-19:49:30
  Bug Check String:
  Bug check code: 0 x 00000124
  Parameter 1: 00000000'00000000
  Parameter 2: fffffa80'07f7e6c8
  Parameter 3: 00000000'00000000
  Parameter 4: 00000000'00000000
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 4adb5c
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.18526 (win7sp1_gdr.140706 - 1506)
  CPU: x 64
  Plant address: ntoskrnl.exe + 4adb5c
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\110514-33540-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 262 144
  Dump of file time: 11/05/2014-19:49:52
  ==================================================

  GT

  Both have been BCC124 two materials

  Stop 0 x 124 is a hardware error
  If you are overclocking try to reset your settings to standard processor and see if that helps.

  If you keep getting the BSOD here are things more than you may want.
  This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.
  
  Stop 0 x 124 - what it means and what to try
  Synopsis:
  A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
  Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.
  

  Generic troubleshooting ' Stop 0 x 124 ":

  1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.
  (2) ensure that the machine is sufficiently cooled.
  If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).
  3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
  It is best to run the latest drivers anyway.
  (4) update the BIOS of your motherboard according to the manufacturer's instructions and clear CMOS.
  Their website should provide detailed instructions on the brand and model-specific procedure.
  (5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
  At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.
  6) trying (stress) test these hardware components that can be put to the test artificially.
  The most obvious examples are the RAM and HDD (s).
  For the RAM, use the 3 rd-party memtest86 utility to run several hours a test value. (6-8 passes to stress the ram)
  For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".
  Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.
  7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
  Who stops working mitigate the problem of the 0 x 124, jump to the next step.
  If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
  Smash back, obviously the latest addition of software may be somehow connected to the root cause.
  If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
  Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:
  (8) clean and carefully remove the dust inside the machine.
  Reinstall all memory modules and connectors.
  Use a can of compressed air to clean the RAM DIMM supports 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 that can be eliminated.
  Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

  If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

  
  
  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/

• Several BSOD with error different ntoskrnl.exe + 75c00 involving most of the messages

  I am running Windows 7 64 bit on a homemade pc with the Asus motherboard, 8 GB of ram and a quad-core processor amd; If you need more specific information please ask. Most of the Bluescreens have different error messages, but all except one have been
  Ntoskrnl.exe "caused by the driver" and "caused by the address. Most occurred when playing computer games. in the middle of the test I have updated my graphics card drivers and a few various other and I checked the ram to find errors although I should probably give him a half-dozen more going on.

  I will try to download a few zippers of depressed on skydrive. bear with me, I never did this before. NOPE, I can't. I can't even * find * skydrive. Someone please care to direct me to how it works yet? * edit *-it won't let me zip minidumps anyway. I give up. I'm about to perform technical support on this thing with his sledgehammer.

  I tried to analyze the accident using windbg, but it fails to load the symbols for ntoskrnl. Here are some summaries of crash as recovered by the blue screen:

  062713-13478 - 01.dmp 27/06/2013-21:31

  KMODE_EXCEPTION_NOT_HANDLED

  0x0000001E

  FFFFFFFF "c0000005

  fffff800'02e86d9c

  00000000 00000000'

  FFFFFFFF'ffffffff

  Ntoskrnl.exe ntoskrnl.exe + 75c00 NT Kernel & System Microsoft® Windows® operating system Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318 - 1533) x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062713-13478-01.dmp 4 15 7601 276 080 6/27/2013 21:31:51

  062913-14024 - 01.dmp 29/06/2013-07:34:23

  KMODE_EXCEPTION_NOT_HANDLED

  0x0000001E

  FFFFFFFF "c0000005

  fffff800'03159 cd 0

  00000000 00000000'

  FFFFFFFF'ffffffff

  CLASSPNP. CLASSPNP SYS. SYS + 1901 x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062913-14024-01.dmp 4 15 7601 276 080 29/6/2013 07:35:21

  062913-13384 - 01.dmp 29/06/2013 18:54:47

  IRQL_NOT_LESS_OR_EQUAL

  0x0000000A ffffba80'09f27a60

  00000000'00000002

  00000000 00000000'

  fffff800'02f31c5f

  Ntoskrnl.exe ntoskrnl.exe + 75c00

  NT kernel & system Microsoft® Windows® operating system Microsoft Corporation

  6.1.7601.18113 (win7sp1_gdr.130318 - 1533) x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062913-13384-01.dmp 4 15 7601 276 080 29/6/2013 18:55:47

  062913-13962 - 01.dmp 29/06/2013-01:30:16

  PM MEMORY_MANAGEMENT

  0x0000001A

  00000000'00041284

  fffff680'0012 d 001

  00000000'00000250

  fffff700'01080000

  Ntoskrnl.exe ntoskrnl.exe + 75c00 NT Kernel & System Microsoft® Windows® operating system Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318 - 1533) x 64 ntoskrnl.exe + 75c00 C:\Windows\Minidump\062913-13962-01.dmp 4 15 7601 276 080 29/6/2013 13:31:17

  No specific information but if you look at the history of BIOS updated between your BIOS Setup and the last BIOS available you would appreciate that a number of improvements have been made.

  You cannot count any error report when you have detected a faulty RAM. RAM corrupt system files, making it unreliable reports. When you installed the replacement RAM you run the System File Checker.
  http://support.Microsoft.com/kb/929833

  I won't say there is no risk of update the BIOS, but if the instructions are followed carefully you shouldn't encounter any problem. The caveat is that you should not threatened the data files which can easily be saved on an external. You can't replace family photos and others.

• Stop: 0x000000d1 the problem seems to be caused by the following file: ntoskrnl.exe DRIVER_IRQL_NOT_LESS_OR_EQUAL

  I get the BSOD every once in a while during a variety of programs. I've updated all my drivers. I use bluescreenview watching dump files and that's what I have.

  A problem has been detected and Windows has been shut down to avoid damage
  on your computer.
  The problem seems to be caused by the following file: ntoskrnl.exe
  DRIVER_IRQL_NOT_LESS_OR_EQUAL
  If this is the first time you've seen this stop error screen,
  Restart your computer. If this screen appears again, follow
  the following steps:
  Check to make sure any new hardware or software is installed correctly.
  If this is a new installation, ask your hardware manufacturer or software
  the Windows updates, you might need.
  If problems continue, disable or remove any newly installed hardware
  or software. Disable the BIOS memory options such as implementing caching or shading.
  If you need to use safe mode to remove or disable components, restart
  your computer, press F8 to select Advanced Startup Options and then
  select Safe Mode.
  Technical information:
  STOP: 0X000000D1 (0XFFFFB880018FA1A0, 0 X 0000000000000002, 0 X 0000000000000008,
  0xffffb880018fa1a0)
  Ntoskrnl.exe - address 0xfffff800030dc1c0 base at 0xfffff8000305d000 DateStamp
  0x4fa390f3

  Hello

  Ntoskrnl.exe is a component of Windows which means than anything else he has led astray.

  BlueScreenView is a great tool for searching for information on minidumps. In particular
  the bottom panel where display the information on 3rd party drivers is useful. Of course
  other debuggers, such as WinDBG, might be able to glean information from minidumps.

  ------------------

  Resolve errors stop (blue screen) in Windows 7 - has a section for if you can or cannot start Windows.
  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  For the methods of troubleshooting blue screen using BlueScreenView and MyEventViewer see my answers
  in this thread - top 3 RESPONSES (+ 1 other).

  http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-system/sometimes-i-get-a-blue-screen-when-using-IE-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

  We can analyze the minidumps if make you it available to the SkyDrive or another file
  sharing sites (such as MediaFire). If you have problems to download the copy of minidumps
  for the office or in the Documents folder and download them from there.

  ZIP or download the content of the C:\Windows\minidump

  Use SkyDrive to upload collected files.
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  ==============================================================

  BCCode: D1 0x000000D1

  Check these KB

  Stop error when you resume a computer that is running Windows 7 or Windows Server 2008 R2
  from sleep or standby extended: "STOP: 0x000000D1".
  http://support.Microsoft.com/kb/978982

  Stop error on a computer based on Windows Server 2008 R2 or Windows 7 during operation
  system uses a storport virtual miniport driver to save a dump file or a file of hibernation: "0x000000D1.
  http://support.Microsoft.com/kb/2320550

  Those 7 other KB Articles are available
  http://support.Microsoft.com/search/default.aspx?mode=a&query=0x000000D1&SPID=14019&catalog=LCID%3D1033&1033comm=1&Res=10

  --------------------------------------------------

  Think video drivers especially if it may be others. Refer to the section of driver in my credits
  methods of troubleshooting blue screen below. BIOS, chipset of low level drivers and
  antispyway/antivirus/security programs can also cause this. Check the resolution of the problems and
  When you arrive at the driver and tests of memory sections do reference to generic methods in following
  message and then back to the if necessary troubleshooting tool.

  Cause

  A driver tried to access a pageable (or that is completely invalid) address while the IRQL was too high.

  This bug check is usually caused by drivers who used a wrong address.

  If the first parameter has the same value as the fourth parameter, and the third parameter indicates a runtime operation, this bug check was probably caused by a driver who was trying to run code when the code itself has been paginated outside. The possible causes for the error page are:

  • The function was marked as pageable and was operating at an IRQL higher (including obtaining a lock).
  • The function call was made to a function in another pilot, and that this driver has been unloaded.
  • The function was called by using a function pointer that was an invalid pointer.

  
  BCCode: d1 0x000000d1<-- read="" this="">
  * 1210.html? order = votes http://www.faultwire.com/solutions-fatal_error/Driver-IRQL-not-less-or-Equal-0x000000D1-

  =========================================

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  -------------------------------------------------------------------------

  Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
  info that would help. Such as ITC and 4 others entered at the bottom left. And all others
  error information such as codes of STOP and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

  As examples:

  BCCode: 116
  BCP1: 87BC9510
  BCP2: 8C013D80
  BCP3: 00000000
  BCP4: 00000002

  or in this format:

  Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during 'blue screen of death '.
  hangs and displays information about all accidents of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
  There are other causes.

  You can do mode if necessary safe or the Vista DVD command prompt or
  Options recovery if your system is installed by the manufacturer.

  How to start on the System Recovery Options in Windows 7
  http://www.SevenForums.com/tutorials/668-system-recovery-options.html

  You can try a system restore to a point before the problem started when one exists.

  How to do a system restore in Windows 7
  http://www.SevenForums.com/tutorials/700-system-restore.html

  -------------------------------------------------------------------------

  Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

  Enter this at the command prompt - sfc/scannow

  How to fix the system files of Windows 7 with the System File Checker
  http://www.SevenForums.com/tutorials/1538-SFC-SCANNOW-Command-System-File-Checker.html

  How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
  generates cbs.log Windows Vista (and Windows 7)
  http://support.Microsoft.com/kb/928228

  The log can give you the answer if there is a corrupted driver. (Says not all possible
  driver problems).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

  How to run the check disk at startup in Windows 7
  http://www.SevenForums.com/tutorials/433-disk-check.html

  -------------------------------------------------------------------------

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  Installation and update of drivers to 7 (update drivers manually using the methods above is preferred
  to make sure that the latest drivers from the manufacturer of system and device manufacturers are located)
  http://www.SevenForums.com/tutorials/43216-installing-updating-drivers-7-a.html

  Stop Windows 7 to automatically install device drivers
  http://helpdeskgeek.com/Windows-7/stop-Windows-7-from-automatically-installing-device-drivers/

  Turn off Windows Update Device Driver search prompt in Windows 7 / Vista (for the professional, full and Enterprise edition)
  http://www.AddictiveTips.com/Windows-tips/disable-Windows-Update-device-driver-search-prompt/

  -------------------------------------------------------------------------

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting Vista Blue Screen, error of JUDGMENT (and Windows 7)
  http://www.chicagotech.NET/Vista/vistabluescreen.htm

  Understanding and decoding BSOD (blue screen of death) Messages
  http://www.Taranfx.com/blog/?p=692

  Windows - troubleshooting blue screen errors
  http://KB.wisc.edu/page.php?id=7033

  -------------------------------------------------------------------------

  In some cases, it may be necessary.

  Startup Options recovery or Windows 7 disk repair

  How to run a startup repair in Windows 7
  http://www.SevenForums.com/tutorials/681-startup-repair.html

  How to start on the System Recovery Options in Windows 7
  http://www.SevenForums.com/tutorials/668-system-recovery-options.html

  How to create a Windows 7 system repair disc
  http://www.SevenForums.com/tutorials/2083-system-repair-disc-create.html

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

• Blue screen error crash, caused by drivers: ntoskrnl.exe, Wdf01000.sys and tcpip.sys

  original title: Blue error screen, accident of death caused by drivers: ntoskrnl.exe, Wdf01000.sys and tcpip.sys

  I currently own an Aura of Alienware Dell, it's an amazing computer. The only problem is that I had a lot of problems, I was able to permanently fix all except this issue. I'll randomly crash blue screen, usually it doesn't happen often and it is normally not triggered by something specific, rarely it will crash at startup. I was able to download an application that can read the cache/dump blue screen crashes:

  34 accidents

  one was caused by Wdf01000.sys

  three was a result of tcpip.sys

  and all the rest of ntoskrnl.exe

  I don't know what caused it, I've had this computer for about a year now and I've never had this problem before. I don't remember an update of the cause, or by downloading any strange apps, downloads or viruses. (I had wiped my computer about 3 months ago)

  I don't know too much about software,

  Any help is appreciated.

  Hi bloo532,

  1. what application did you use to read dump files?

  2. did you of recent changes on the computer?

  It resembles that of the driver on the computer is causing the blue screen.

  Check if the problem persists in safe mode.

  Start your computer in safe mode

  http://Windows.Microsoft.com/en-us/Windows7/start-your-computer-in-safe-mode

  Restart the computer to return to normal mode

  Also make sure that all drivers are up to date on the computer.

  See the link below and try them the steps mentioned, check if it helps.

  Resolve stop (blue screen) error in Windows 7

  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

   

  If the previous step fails, then you will need to provide the minidump files.

  Use SkyDrive download collected files and after shot/screenshot.

  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  I hope this helps!

  Halima S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• blue screen caused by driver ntoskrnl.exe

  original title: BSOD caused by driver ntoskrnl.exe

  I received several BSOD for some time now, usually 1 day a week, I'll take 4-5 in a row.  They always come when I'm starting, often after installing something (a different application each time).  Uninstalling these does not help.  It never happened when already in a windows session.  I have updated all drivers listed on the HP (model 8540p) website.  Here is an example of a landfill; Each dump is the same with exception to Param 4 (and, of course, the time and filename)

  Bug Check String	Bug check code	Param 1	Param 2	Param 3	Parameter 4	Caused by the driver	Caused by address
  IRQL_NOT_LESS_OR_EQUAL	0x0000000A	0	2	0	fffff800'032937 d 5	Ntoskrnl.exe	Ntoskrnl.exe + 80640

  The other 'setting 4"of are
  fffff800'032877 d 5
  fffff800'032df7d5
  fffff800'0328e7d5
  fffff800'0328a7d5
  fffff800'0329c7d5
  fffff800'032cd7d5
  fffff800'032937 d 5

  Edit: format for moving things to adapt to changes.  Last digit of Param 1-3 are listed.  Figures are all zeros.

  .rar is fine.

  With the Windows Debugger (WinDbg) the minidump files show the driver who caused the accident is the CipcCdp.sys:

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck A, {0, 2, 0, fffff800032d97d5}

  Failed to load image \SystemRoot\system32\DRIVERS\CipcCdp.sys, 0n2 error Win32
  WARNING: Unable to verify timestamp for CipcCdp.sys
  ERROR: Module load completed but symbols can be loaded for CipcCdp.sys
  Probably caused by: CipcCdp.sys (CipcCdp + 1bfa)

  The CipcCdp.sys, which is dated July 21, 2010, seems to be a driver for Cisco IP Communicator.

  Can you try to update or, if necessary, uninstall the Cisco IP Communicator software and see if the BSOD solve.

  Same driver, causing the crash even in the following link:

  http://www.SevenForums.com/crashes-debugging/149525-IRQL_NOT_LESS_OR_EQUAL-b-c-i-connected-2-monitors.html

  The Cisco IP Communicator software is unable to uninstall itself so if you are still experiencing a BSOD after update or uninstall please provide the files minidump resulting.