0X0000009F DRIVER_POWER_STATE_FAILURE

Similar Questions

• Bluescreens ~ 15 min interval... 0X0000009F DRIVER_POWER_STATE_FAILURE

  Hi I'm Philipp,

  and I hope you can help me with this problem:

  My system is a Win7 64 bit old for two months on a Toshiba Tecra Notebook z50. During the first-updates Windows appears the first Bluescreen.

  I tried to solve the problem 0x0000009f DRIVER_POWER_STATE_FAILURE, but actually I get stuck.

  I trie to identify the driver, which seems to cause the problem.

  The Dumpfile indicates the following:

  ==================================================
  Dump file: 060315-10764 - 01.dmp
  Time of the accident: 03.06.2015 15:34:29
  Bug Check String: DRIVER_POWER_STATE_FAILURE
  Bug check code: 0x0000009f
  Parameter 1: 00000000'00000003
  Parameter 2: fffffa80 107 c 0970
  Parameter 3: fffff800'00b9e3d8
  Parameter 4: fffffa80'0d88fc60
  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\060315-10764-01.dmp
  Number of processors: 4
  Main version: 15
  Minor Version: 7601
  Empty the file size: 1.027.896
  Dump of file time: 03.06.2015 15:35:27
  ==================================================

  Thanks for your support,

  Regards Philipp

  Also the link to the minidump and MSinfo32:

  https://onedrive.live.com/redir?RESID=9F39027DBFE5299D! 109 & authkey =! ACdpcx4LGKdn_1k & ithint = the file % 2czip

  They are all connected to iusb3hub.sys driver hub USB 3.0 of Intel Corporation.  Remove the driver current completely and install the latest driver available.

  

• 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 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.

• (0 X 00000003 0X0000009F DRIVER_POWER_STATE_FAILURE BSOD,

  Hello!

  Whenever I try to shut down the computer during the night when I am finished working, it doesn't seem to stop. When I stopped him, he just starts to go through the process, but ultimately a BSOD occurs, which forces me to shut down the computer manually by holding the power button.

  Here, I have attached mini-decharges for three consecutive days that had the same BSOD on shutdown, all the files in the links are the same:

  https://rapidshare.com/files/3053652346/minidumps.rar
  http://www.Filefactory.com/file/c18d1c2/n/minidumps.rar
  http://www.mediafire.com/?60phwhgyabsygmf

  My computer model is Toshiba Satellite x 205-sli2 where it is useful.

  I hope that you will be able to help me with this problem. Thank you!

  Hello

  Results verified BlueScreenView WinDBG / DumpCHK.
  
  The Bug_Check were all 9F CAUSE RTKVHDA.sys, which is the function Realtek (r) High Definition Audio driver.

  9F error checking, {3, 8e46d180, 9429cb30, c64c0188}
  Probably caused by: RTKVHDA.sys
  Nom_image: RTKVHDA.sys
  MODULE_NAME: RTKVHDA

  RTKVHDA.sys dated 28/07/2009 Realtek (r) High Definition Audio Driver to function.

  Loaded symbol image file: RTKVHDA.sys
  Image path: \SystemRoot\system32\drivers\RTKVHDA.sys
  Image name: RTKVHDA.sys
  Timestamp: Kills Jul 28 06:02:38 2009 (4A6EF6EE)

  1. update RealTek Audio Codec driver.

  Driver Realtek HD Audio Codec of USA - right side-
  http://www.Realtek.com/default.aspx

  2.check with Toshiba Support, their drivers and documentation online and ask in their forums
  on the problems known. Look for the updates to the BIOS, chipset of low level drivers and major
  embedded device drivers. Also update all drivers - run DriverView - important separate device
  SEE to hide drivers Microsoft - those without drain update in their name.

  TOSHIBA = BiosVendor
  BiosVersion = V2.10
  BiosReleaseDate = 20/12/2007<- check="" for="" updates="" to="" the="" bios,="" low="" level="" chipset="" drivers,="" and="" the="">
  device embedded and separate drivers.
  TOSHIBA = SystemManufacturer
  SystemProductName = Satellite X 205
  Family = ABCDEFGHIJKLMNOPQRSTUVWXYZ
  SystemVersion = PSPBUU-01900J
  SystemSKU = 012345678912345678912345678
  TOSHIBA = BaseBoardManufacturer

  3 use the other methods in the troubleshooters below.

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

  Check this KB:

  The shutdown process does not terminate and you receive an error message on a computer that is
  running Windows Vista or Windows Server 2008: "Stop 0x0000009F"
  http://support.Microsoft.com/kb/972109

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

  You use Roxio or Nero programs? They have been known to cause this problem even
  If they worked well for a long period of time. If so check with their support.

  Check this thread for more information on using BlueScreenView, MyEventViewer and other methods of
  Troubleshoot BlueScreens - answers top 3 (+ 1 more).

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/blue-screen-plug-and-play-detected-an-error-most/3deab2fa-4000-4136-8c78-a3d22b1db009

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

  References to Vista also apply to Windows 7.

  This "might" be a power problem, even if this isn't the most common cause - in this case
  It seems that the PSU could be the fault.

  9F is probably a driver issue. Security/antivirus/antispware programs can also cause these issues.
  Have you added the recent devices or the updated drivers - don't forget to check in the Windows updates to see
  If a driver has been updated before this happen. This can also be caused by a loose card or cable
  and even a weak power supply.

  This error means that a driver does not properly support the power state. Check in Control Panel - device
  Manager to ensure that the drivers are not stop during sleep - double-click adapter - NETWORK adapter
  and WIFI - healthy and others - tab power management - uncheck allow the computer to turn off.
  Maybe the only has a problem.

  Start - type in the search - find MSCONFIG in top - right, click on – RUN AS ADMIN

  General tab - tick this box start Diagnostic - APPLY / OK - REBOOT

  Try it now. If the computer still blue screens thinks that video driver. Otherwise think the card NETWORK, Wifi, sound, or...
  (and it might still be video interacts with something else). See following message for my
  generic driver update methods.

  BCCode: 9F 0x0000009F<-- read="" this="">
  * 1167.html? order = date http://www.faultwire.com/solutions-fatal_error/Driver-Power-State-Failure-0x0000009F-

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

  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 without if needed fail or the Vista DVD or recovery command prompt mode
  Options if your system was installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

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

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.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 analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
  generates in Windows Vista cbs.log
  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 Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.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

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

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

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

  Troubleshooting, STOP error blue screen Vista
  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.

  The Options or Vista recovery disk Startup Repair

  How to do a startup repair
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.

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

• Blue screen 0x0000009f DRIVER_POWER_STATE_FAILURE death in newly acquired ASUS laptop computer g750JM

  Hi, I get a blue screen of death every time in a while for no discernible reason. I've had this laptop for about 2 weeks, I just received my third blue screen of death about an hour ago. The location of the address is the same, bug control code, the driver is ntoskrnl.exe

  Landfills are:

  https://www.dropbox.com/sh/w7k1x6zs8c7i4bz/AADWTHwEluQNtq1gExw2rgB3a

  I hope someone can help

  Hello

  I've been scouring the internet for weeks looking for help with my BSOD problems.  I finally made a discovery that fixed it all and thought I'd share it with as many people as possible.

  Some background on my question:

  I installed the 337,88 and the beta drivers but kept on getting random BSOD due a DRIVER_POWER_STATE_FAILURE.  I watched the dump file and debugged myself as BlueScreenviewer offered no answers for me.  He showed a driver ntoskrnl.exe and dig more pci.sys has shown to be the culprit, but this may not be true.  More digging in the minidump gave nviddmkm.sys, so naturally I thought it was a driver problem. (I have a background inproramming, so I was able to do a pretty thorough analysis of the file).  I installed the 332,50 drivers and no more problems.  However, I was not satisfied with this solution.  I did more research on the internet and several other cases have been solved by powering down of overclocking.  I had already uninstalled GPUTweak, so what else could it be?

  Well, the BIOS has the answers.  Here is my solution:

  1. turn off your laptop.  (Full stop)
  2. press the power button.
  3. quickly and repeatedly hit the F2 key to enter the BIOS setup.
  4. go to the "Advanced" tab
  5 scroll down to "Graphical Configuration" and press the Enter"" key.
  6. highlight "Turbomaster setting" and press the Enter"" key.
  7. you will see two options, 'Activate' and 'Disable', choose 'disable '.
  8. Finally, press the "Esc" key and go to the tab "Quit" and "save changes and exit".

  You can now install the latest drivers without experiencing a BSOD.  I hope I helped.  If you guys have any questions be sure to ask me, I'l answer to the best of my ability.

• 0x0000009f DRIVER_POWER_STATE_FAILURE ntoskrnl.exe blue screen error / ntoskrnl.exe + 5 has 220

  Need help... My ASUS N43SL got BSOD every time I try to Hibernate. (Windows Pro 8, update Windows 7 via Windows site)

  Stop and restart Mode did not.
  It comes to my minidump link... https://SkyDrive.live.com/redir?RESID=F266C2A31EC1D90D! 344

  The minidump file showed a DRIVER_POWER_STATE_FAILURE (9f) referencing the ndiswan.sys.

  Other users report similar errors and Connectify and Kaspersky installed for example here , the problem seems to be Connectify or Connectify clashing with Kaspersky.

  Try to uninstall Connectify and, if him persists error uninstall Kaspersky and use alternative security such as firewall and antivirus integrated Windows 8 (Windows Defender) software.

  Also, the driver verifier seems to be activated which should not be enabled under normal circumstances also to 'turn off' the driver verifier:

  Start > type verifier.exe and press 'Enter' on the keyboard > clear the existing settings > finish > click 'Yes' to the message to delete the settings and exit the program

• DRIVER_POWER_STATE_FAILURE 00000000'00000003

  Hi all

  I try everything I install windows 7 and 8 and 8.1 same problem I try to also update same driver problem

  Toshiba L50T-A

  I think that this problem of material

  DRIVER_POWER_STATE_FAILURE ntoskrnl.exe

  DRIVER_POWER_STATE_FAILURE 00000000'00000003

  101413 58187 - 01.dmp 14/10/2013-09:43:06 00000000'00000003 ffffe000 "013b01c0 fffff801" 0x0000009f DRIVER_POWER_STATE_FAILURE 546e5960 ffffe000'00f9ec50 ntoskrnl.exe ntoskrnl.exe + 1500 has a 1500 0 C:\Windows\Minidump\101413-58187-01.dmp 9600 + 0 x 64 ntoskrnl.exe 15 8 1 043 760 10/14/2013 09:45:02

  dumfiles

  https://SkyDrive.live.com/redir?RESID=18BA779B1B55F962! 3306 & authkey =! AKzuMlPiUWHvjOs

  Info

  https://SkyDrive.live.com/redir?RESID=18BA779B1B55F962! 3307 & authkey =! AAhN15P5WE0sAqQ

  Hello

  Please follow my recommendation above and activate the driver verifier.

  Kind regards

  Patrick

• Satellite A100-914 - stop after 10 minutes on

  Satellite A100-914 - Vista Home 32-bit edition

  For some time, whenever I turn on the computer it off after 10 minutes. Usually I restarted and then everything was ok, but these days, it seems to stop several times.

  In my screen displays the blue screen saying on: driver_power_state_failure...

  I've updated to Vista, a patch which should solve this problem, but the problem of still images.

  I have also updated the Bios of Toshiba, and then I get a Warner 0251 checksum bad - default configuration used.

  I also have problems with superfetch and search for host when I connect to the internet... but it is perhaps another question...

  Thanks in advance
  Daniel

  Hello

  What to say...

  Regarding the automatically close downs;
  For me, it looks a bit like overheating. Maybe you should check if the temperature is not too high and check if the cooling modules are working properly and it can cool the laptop properly. Sometimes the dust inside the laptop could have a bad influence on cooling.

  Regarding the system BIOS checksum bad - default configuration used:
  Try to access the BIOS and set the default BIOS settings. Then save the changes and restart the laptop.

  Regarding the MS patch:
  I found this Microsoft Knowledgebase document:
  The STOP Error Messages troubleshooting 0x0000009F DRIVER_POWER_STATE_FAILURE in Windows
  http://support.Microsoft.com/kb/246243

  It is said that this problem occurs when drivers do not properly handle power state transition requests.
  The error message most often occurs during one of the following actions:
  -Closing
  -Suspension or out of standby mode
  -Suspension or out of hibernation

  Check solution proposals in the document of Microsoft.
  If this does not help, I guess it's a hardware problem and you will need to contact the ASP in your country.

  Good luck

• BSOD on shutdown/reboot bug check 9f

  I get d BSOD saying DRIVER_POWER_STATE_FAILURE
  all d minidumps are in given link
  I've updated all my drivers for a version more recent but problem still persits
  Product F2C09PA #ACJ number

  Operating system: Windows 8.1 64bits

  Report Viewer blue screen:

  062814-35812 - 01.dmp 2014/06/28 02:14:47 DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000 00000003' ffffe001 '46cbe730 fffff802' e7dfe930 ffffe001'4e104250 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062814-35812-01.dmp 4 15 9600 706 528 2014/06/28 09:25:09
  062714-36859 - 01.dmp 2014/06/27 20:20:55 ffffe000 'eb7ed060 ffffd001' 00000000'00000003 0x0000009f DRIVER_POWER_STATE_FAILURE c0fec930 ffffe000'fabc76f0 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062714-36859-01.dmp 4 15 9600 722 816 2014/06/27 21:42:43
  062614-49375 - 01.dmp 26/06/2014-15:12:54 fffff802 '5249ce70 fffff802' 00000000'00000008 0x0000007f UNEXPECTED_KERNEL_MODE_TRAP 5248df40 fffff802'4f6ece94 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062614-49375-01.dmp 4 15 9600 288 768 26/06/2014-15:14:45
  062614-46765 - 01.dmp 26/06/2014-15:06:15 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000'00000008 '28df5e70 fffff803' fffff803 28ddff60 fffff803'26ef3f2c werkernel.sys werkernel.sys + a238fe70 x 64 ntoskrnl.exe + 153fa0 C:\WINDOWS\Minidump\062614-46765-01.dmp 4 15 9600 289 632 26/06/2014-15:07:58
  
  Minidump:

  Debug version of Microsoft Windows (R) 6.3.9600.17029 X 86
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [E:\ImageDiags_1.8.56.0\Minidumps\062614-41046-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: * invalid *.
  ****************************************************************************
  * Loading of the symbol may be unreliable without a symbol search path. *
  * Use .symfix to get the debugger to choose a symbol path. *
  * After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
  ****************************************************************************
  Executable search path is:
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  * *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable. *
  * using the argument y < symbol_path > then to start the debugger. *
  * using the .sympath and .sympath + *.
  *********************************************************************
  Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
  WARNING: Unable to verify timestamp for ntoskrnl.exe
  ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
  Windows 8 Kernel Version 9600 MP (4 procs) free x 64
  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 9600.17085.amd64fre.winblue_gdr.140330 - 1035
  Computer name:
  Kernel base = 0xfffff800 '48a7f000 PsLoadedModuleList = 0xfffff800' 48d492d0
  The debugging session: Thu Jun 26 19:28:32.858 2014 (UTC + 05:30)
  System Uptime: 0 days 0:57:48.770
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  * *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable. *
  * using the argument y < symbol_path > then to start the debugger. *
  * using the .sympath and .sympath + *.
  *********************************************************************
  Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
  WARNING: Unable to verify timestamp for ntoskrnl.exe
  ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ............................................................
  Loading user symbols
  Loading unloaded module list
  ...........

  Summary of the symbol load error *.
  Name of the module error
  Ntoskrnl the system cannot find the specified file

  You can solve most symbol related issues by turning the symbol loading diagnostics (! sym noisy) and repeating the command that caused the symbols to load.
  You should also check that your symbol search path (.sympath) is correct.
  *******************************************************************************
  * *
  * Bugcheck analysis *.
  * *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  9F error checking, {3, ffffe001b66a2060, ffffd000c51e1930, ffffe001ca506790}

  The kernel symbols are FALSE. Correct symbols to do the analysis.

  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: NT! _DEVICE_OBJECT *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _IRP *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _IRP *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! TRIAGE_9F_POWER *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _IRP *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _IO_STACK_LOCATION *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _IRP *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _DEVICE_OBJECT *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _KPRCB *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! KPRCB *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _KPRCB *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! KPRCB *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _KPRCB *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _KPRCB *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _IRP *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _KPRCB *.
  *** ***
  *************************************************************************
  *************************************************************************
  *** ***
  *** ***
  Either you have specified an absolute symbol, or your debugger *.
  has no information complete symbol. Absolute symbol *.
  resolution is disabled by default. Please specify a *.
  complete symbol module! NomSymbole, or activate the resolution *.
  symbols unskilled by typing '.symopt 100 '. Note that *.
  allowing unqualified symbol with the network symbol resolution *.
  shares of server in the symbol path can cause the debugger to *.
  appear to hang for long periods of time when an incorrect *.
  symbol name is typed or the symbol of the network server is down. ***
  *** ***
  For some commands work properly, your symbol path *.
  should point to .pdb files have the type information complete. ***
  *** ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information. The contact group that *.
  you provided with these symbols, if you need this command for *.
  work. ***
  *** ***
  Type referenced: nt! _KPRCB *.
  *** ***
  *************************************************************************
  Probably caused by: ntoskrnl.exe (nt + 153fa0)

  Follow-up: MachineOwner
  ---------

  Rather you should mention that I don't have symbols told me how to get them

  and this link Forum called youtube video and youtube video was useless by itself it did not show how to solve my problem.

  But in any case I solved it and here is how I did it

  1. restored by computer laptop to an earlier time of the first restore point was himself on the day where the problem started, but nevertheless I did

  2 uninstalled all my network drivers and all tha application uses internet (Hotspot service as conectify) except of WEb browsers

  3. in the event viewer WIndows stopped all service ontenet which appear to come from a third party application or so.

  4. voila it worked

  5. thanks for your useless highly appreciated <

• Displaying the right information to get a BSOD error help

  When your computer crashes and displays a blue screen there are often very valuable information about the photo that will allow users to help you solve your problem and to know what is causing this blue screen appears.

  Looking at the image at the end of the article you will see two sections highlighted, you will always want to post this information in your forum thread when looking for help she will be the most critical part of troubleshooting. The top tells us what's happening and said background where it goes to. We have just responded to two of the most important issues when you try to solve a problem.

  What's not?

  Where is the problem isolated to?

  Most of the text is quite annoying, but if that's important to you then it may be important for us. We have all seen what looks like a BSOD, but we do not know what your BSOD.

  There are more important questions that you can answer that will help your troubleshoot BSOD error message.

  1. What is your system brand and model? We know that you have an HP computer, but there are tons of computers. We need to know your specific model to ensure you use the appropriate drivers and we recommend the proper drivers.
  2. What is your version of Windows and the Service pack?
  3. Are you running a 64 bit or 32 bit OS?
  4. What is your Internet browser and version?
  5. Does your system use IDE or SATA disk drives?
  6. What virus protection software and current malicious software do you use? Is up to date?
  7. The issue occurred after an interruption of the power supply as an abnormal termination or power failure?
  8. What has changed recently?
  9. Does this happen often you can effectively reproduce the problem? If you can easily reproduce what steps can you take to reproduce the problem.

  Here is a list of the most common mistakes of the BSOD you can see

  • Stop 0 x 00000003 UNSYNCHRONIZED_ACCESS
  • Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL
  • Stop 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
  • Stop 0 x 00000023 FAT_FILE_SYSTEM
  • Stop 0 x 00000024 NTFS_FILE_SYSTEM
  • Stop 0x0000002E DATA_BUS_ERROR
  • Stop 0x0000003F NO_MORE_SYSTEM_PTES
  • Stop 0 x 00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
  • Stop 0 x 00000050 PAGE_FAULT_IN_NONPAGED_AREA
  • Stop 0x0000006B PROCESS1_INITIALIZATION_FAILED
  • Stop 0 x 00000073 CONFIG_LIST_FAILED
  • Stop 0 x 00000074 BAD_SYSTEM_CONFIG_INFO
  • Stop 0 x 00000076 PROCESS_HAS_LOCKED_PAGES
  • Stop 0 x 00000077 KERNEL_STACK_INPAGE_ERROR
  • Stop 0 × 00000079 MISMATCHED_HAL
  • Stop 0x0000007A KERNEL_DATA_INPAGE_ERROR
  • STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
  • Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  • Stop 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
  • Stop 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
  • Stop 0x0000009C MACHINE_CHECK_EXCEPTION
  • STOP 0x0000009F DRIVER_POWER_STATE_FAILURE
  • Stop 0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY
  • Stop 0x000000C2 BAD_POOL_CALLER
  • Stop DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000C4
  • Stop 0x000000CA PNP_DETECTED_FATAL_ERROR
  • Stop 0x000000CB DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
  • Stop 0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
  • STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
  • Stop 0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
  • Stop 0x000000D8 DRIVER_USED_EXCESSIVE_PTES
  • Stop 0x000000DA SYSTEM_PTE_MISUSE
  • STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
  • Stop 0x000000ED UNMOUNTABLE_BOOT_VOLUME
  • Stop 0x000000F2 HARDWARE_INTERRUPT_STORM
  • Stop 0x000000F4 CRITICAL_OBJECT_TERMINATION
  • Stop 0x000000FC ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
  • STOP 0x000000FE BUGCODE_USB_DRIVER
  • Stop 0xC0000218 UNKNOWN_HARD_ERROR
  • STOP 0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
  • Stop 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
  • STOP 0xC0000244 STATUS_AUDIT_FAILED

  

  This thread is purely an informative thread. If you are experiencing a BSOD error please create a new thread ensure you provide information that questions on this thread.

  While many BSOD errors may be troubleshooting-made the same way, there is an amount of many of them and they should be troubleshoot-carried out on their own.

  If you have anything else you want to add or general BSOD issues then you can post them here, but if you ask about anything that requires real troubleshooting it should be in its own thread.

• Western Digital 2 to my direct book DT RJ45 Network Attached Storage

  I wonder if anyone else has problems with the Vista SP2 attempt to install the driver for this device (Driver ID 20438948)?

  When an attempt is made to install this driver, the installation fails.  Unfortunately, it corrupts the Vista SP2 operating system because shadow copies no longer able to do so and when a restart is attempted, the restart will fail with a 0x0000009F - DRIVER_POWER_STATE_FAILURE BSOD.  Recovery involves a reboot in the repair console, then a restore of the system, reboot followed.  Tent a system without enter repair console restore fails because of damage to the operating system.

  Once this is done, and the system reboots, shadow copy and restarts on own work.

  I must stress that without this driver recommended, the drive is accessed as a network attached device or if specific folders are mapped as drive letters.

  Thanks for reading time and possible responses.

  Jim

  Hello

  I would like to inform you that, given that the pilot exited WDC they would need to update the driver, because we provided them with Vista Service Pack 2 specification, they are responsible for the update of drivers.

  WDC Contact: http://support.wdc.com/contact/index.asp?wdc_lang=en

• Windows crashes with a gurgling noise. BSOD

  Hello

  I demoted Windows 8.1 for windows 7 because of the buzzing and gel all in game (a message indicates graph pilots stopped responding and recovered). Unfortunately, the problem persists. The pop up message for not responding in what is the graphics card, I downloaded a fix it file from microsoft and installed it. Now, the message does not appear, but it still freezes with buzzing noise. When I tried to restart, the laptop remained black screen for awhile and then BSOD.

  Sound card: Realtek

  Graphics card: Nvidia 540M

  If that helps.

  I've updated the recent nvidia and realtek drivers and the problem persists. So I restored the drivers to drivers provided with Dell L502X. I used to play these games without any problems in the past in the same laptop.

  I paste some elements of the dump files, I hope that this helps to determine the problem.

  "" 062915-22557 - 01.dmp 29/06/2015-20:25:37 00000000 0x0000009f DRIVER_POWER_STATE_FAILURE ' 00000003 fffffa80 ' 07d29a10 fffff800 ' 044523 d 8 fffffa80 ' 0a6db4b0 ntoskrnl.exe ntoskrnl.exe + 748c0 NT Kernel & System Microsoft® Windows® operating system Microsoft Corporation 6.1.7601.18869 (win7sp1_gdr.150525 - 0603) x 64 ntoskrnl.exe + 748c0 C:\Windows\Minidump\062915-22557-01.dmp 8 15 7601 765 440 29/06/2015-20:26:43

  27752 062715 - 01.dmp 27/06/2015-16:06:06 0 x 00000116 fffffa80'0b0694e0 fffff880 "040cb008 ffffffff" c000009a 00000000'00000004 dxgkrnl.sys dxgkrnl.sys + 5d134 x 64 ntoskrnl.exe + 748c0 C:\Windows\Minidump\062715-27752-01.dmp 8 15 7601 562 128 27/06/2015-16:07:09

  "062515-72493 - 01.dmp 25/06/2015 23:23:21 0 x 00000116 fffffa80'0ab8d4e0 fffff880 ' 042 d 0008 ffffffff" c000009a 00000000'00000004 dxgkrnl.sys dxgkrnl.sys + 5d134 x 64 ntoskrnl.exe + 748c0 C:\Windows\Minidump\062515-72493-01.dmp 8 15 7601 564 704 25/06/2015 23:25:28

  Thank you

  Alfred

  These accidents are called BCC116 and are associated with your video subsystem.  Please follow the instructions of this wiki

  

• Windows 7 blue screen: DRIVER_POWER_STATE_FAILURE STOP: 0x0000009f (0 x 00000003,... ntkrnlpa.exe)

  Hi all

  I got a blue screen today with my Windows 7 which is something disappointing and I don't want to do it again, can someone check the dump for me file and tell me what is the cause?

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

  DRIVER_POWER_STATE_FAILURE

  Technical information:

  STOP: 0X0000009F (0 X 00000003, 0X8903B458, 0X83133AE0, 0X88B16008)

  Ntkrnlpa.exe - address 0x830eaf1c base at 0x8300c000 DateStamp 0x4f5583be

  ********************************************************************************

  I have:

  Intel i5 760
  4 GB of ram
  Windows 7 32 bit
  Comodo 5.10.228257.2253
  NOD32 4.2.71.2

  In case there is something wireless (I read something on this, but not sure!), I have:

  Device USB of TP-link wireless (& TP-link utility)
  SecurityKISS tunnel software
  proXPN vpn software

  Drivers:
  Microsoft virtual Wifi Miniport adaprot
  Realtek PCIe GBE controller (disabled)
  TP - LINK 150Mbps Wireless N adapter Lite
  Unknown device
  TP - LINK 150Mbps Wireless N adapter Lite

  VirtualBox has been running a win XP version that has Avast & Comodo

  At the point of issue, virtualbox was operating in full screen, Firefox open and no one to the PC (no action)

  I downloaded the dump file to:
  http://DepositFiles.com/files/q4ebw15vb
  Password: win7win

  Thank you

  Hello

  You have made any changes to your computer recently?

  I suggest you to follow the steps and check if it helps.

  Method 1: Disconnect all external devices except your mouse and your keyboard and check what is happening.

  Method 2:

  Step 1: Login to the Safe Mode and then check if it helps.

  Start your computer in safe mode

  Step 2: Perform a clean boot Hardware and a software clean boot, and then check if it helps.

  (a) click "Start" and type "DEVMGMT. MSC"in the search text box and press enter

  (b) develop "audio, video and game controllers".

  (c) right click on your sound card, select "Properties".

  (d) 'Pilot' click, click Disable the selected device. Click OK

  (e) Please use the same method to disable other devices such as: Modem, network card, CD - R drive. Please note that some devices such as the video card are not available should be disabled.

  (f) Please restart the computer.

  Note: do not forget to activate the devices to return after you complete your troubleshooting.

  Method 3: You can also check out the link and then check if it helps.

  Resolve stop (blue screen) error in Windows 7

• DRIVER_POWER_STATE_FAILURE - 0x0000009f - c:\windows\system32\drivers\sptd.sys

  DRIVER_POWER_STATE_FAILURE

  0x0000009F

  Parameter 1: 00000000'00000003

  Parameter 2: fffffa80'059 c 0880

  Parameter 3: fffff880'02ece7f0

  Parameter 4: fffffa80'080 c 7670

  Caused by the driver: c:\windows\system32\drivers\sptd.sys

  Caused by the address: c:\windows\system32\drivers\sptd.sys + 1dc3c

  CPU: x 64

  Plant address: ntoskrnl.exe + 5 has 540

  Then view the last dump using BlueScreenView file

  on the lower panel. I see two entries with a red nail... namely

  ntosknrl.exe and c:\windows\system32\drivers\sptd.sys

  This BSOD occur usually when I try to use my secondary video card... a Nvidia Geforce 610 m. I tried updating the driver, put it back, for a newer version or even an older version supplied by the manufacturer of the laptop. But the BSOD stop then re - occurring when the system restarts after a few attempts also. and I look in Device Manager and I see that my other card video (nvidia) is missing from the list. but then returns after a few stops more or less.

  ASUS k55

  all stock, nothing has changed...

  Hello

  c:\windows\system32\drivers\sptd.sys is pass it through Direct host SCSI - Daemon Tools (called BSOD issues). Please remove it as soon as POSSIBLE with the uninstall tool - http://www.duplexsecure.com/en/downloads

  Kind regards

  Patrick