Win7 BSOD Bugcheck 1000009F DRIVER_POWER_STATE_FAILURE (9f) resolution

Similar Questions

• Wake up - Satellite A300, Win7 BSOD

  Hi there, ive been having a very frustrating of prob with my laptop lately, the problem started when I installed windows 7, installed everything correctly without error, but every time I wake my laptop from sleep mode it BSOD and restarts, after checking the .dmp file, I decided it was a prob with my display driver After updating the prob stil persists, ive went through 4 different drivers with no cure... Ive also updated my bios and it did not fix

  Here's my Minidump files:

  [Minidump .dmp file | http://www545.megaupload.com/files/4d328aa5bccea2f98fa2a6ea2bdd206d/121611-38376-01.dmp]
  [Minidump .txt file | http://www531.megaupload.com/files/46e8201fb71408432cf6b374db152800/121611-38376-01.txt]
  [Windows Event Viewer File | http://www593.megaupload.com/files/600bae8d91f786d1349102cd20c5281f/Windows%20Event%20Viewer.txt]

  Any help is appreciated, thanks

  > im sure it is a problem of graphics as my minidumps say that 'DirectX Graphics Kernel' is the cause of the BSOD.

  I'm not very well if the BSOD is caused by the graphics driver compatibility issue but in general the driver of Toshiba page should not cause BSOD m
  Anyway, there are a few 3rd party pages where you can download updated drivers the: laptopvideo2go.com or omegadrivers.net
  But do not know if these drivers work correctly

  Another tip: I've read that some people could solve the BSOD problems by changing the resolution of the screen and disabling the Aero theme try this out... you may notice some improvements

• HP dv7-1285dx Win7 BSOD errors

  My dv7-1285dx worked perfectly until a few weeks before, now he wants bsod on me at least every other day, sometimes twice a day or more. Various bsod error messages (STOP, IRQ, etc.). No indication of something. At one point last week, I had to use the restore application to return two registry saved back to just run - before that it would not boot.

  Error with nvlddmkm.sys are related to driver Nvidia but that only happened once. The last was something with a pilot and an IRQL is not an error (I'll follow upward with more detailed messages on this subject when they occur - sorry to be vague).

  I have run all equipment, disc tests and memory that are included in the suite of Win7 and run standalone versions similarly people to Acronis. Nothing seems abnormal. I hope that someone can read these dmp files and tell me if something stands out.

  Here is the link to the dmp files: http://www.mediafire.com/rsattler

  Thank you!

  Problem solved by replacing SoDIMM defective.

  Tests with Memtest86 + was very helpful in tracking down the memory defective barrette. I ran the test 4 times to determine which module was the absence of ata and eliminate any hardware problem module slot;

  1. 4 GB SoDIMM in slot 0
  2. 4 GB SoDIMM in slot 1
  3. 2 Gb SoDIMM in slot 0
  4. 2 Gb SoDIMM in slot 1

  I ran each test for ~ hour or two. I thought that I had a problem with the 4 GB SoDIMM but it turned out that the 2 Gb SoDIMM was the culprit with this testing methodology.

  Replaced the 2 GB SoDIMM and revived the test overnight (~ 10 hours) with two SODIMM modules in the machine and found no errors.

• Portege R930 - BSOD when connecting monitor high resolution with HDMI port

  Hello.

  I have a Portege R930 (pt331a-01w001) running Windows 7. All about the laptop works as expected, however, when I connect the laptop on a screen high resolution (2560 x 1440) via the HDMI port, I get a blue screen of death.
  Can I use the HDMI port to connect my 1080 p LCD TV and my monitor to work which is a lower resolution and it works well.

  I tried several cables and different monitors of the same resolution.

  If anyone can help?

  Hello

  Simply said: the laptop not breaks down using external monitor with a less than 2560 x 1440 resolution. Right?

  Find your laptop model.
  [Portege R930 PT331A 01W00101 | http://www.mytoshiba.com.au/support/computers/portege/r930/pt331a-01w00101/specifications]

  and it seems that the device supports the Chipset Intel® QM77 Express and Intel® Graphics Media Accelerator QM77

  I recommend updating the graphics card driver.
  You will find the page of the Toshiba Intel display driver v8.15.10.2712 (Win 7)
  Also, you could test the version downloaded from the Intel page.

• Windows 8, BSOD bugcheck 3B, ATI

  My machine crashed and when I try to check for solutions to a problem, the service is unable to download files to windows error reporting. I put the minidump on my skydrive here http://sdrv.ms/1h3ntG5

  Of a Dumpcheck on the minidump file

  Bugcheck 3B {c0000005, fffff880076650b5, fffff8800f42f050, 0}

  Probably caused by: atikmpag.sys (atikmpag + 480b 5)

  The blue screen that has happened when you try to view a flash video in Internet Explore.

  Install the latest driver for ATI graphics card. You can download ATI form site.

  After installation, restart and monitor the system.

  Ded9

• Ntkrnlmp.exe 0x19 BSOD on Win7

  My PC put a 0 x 19 on Win7 BSOD this week. By WinDbg, I saw the detail below. But I'm not what the problem is. Can you help me on this? Thank you.
  BSOD file: https://1drv.ms/u/s! AtTcAFIw1IN-hAv5b4fW9ZMvxP46

  Some information in the dump file.
  -------------------------------------------------------------------------------
  Error checking 19, {20, fffffa80044d7470, fffffa80044d74f0, 4080002}
  Probably caused by: ntkrnlmp.exe (nt! ExFreePoolWithTag + 18aa)
  Follow-up: MachineOwner
  ---------

  1: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  BAD_POOL_HEADER (19)
  The pool is already damaged at the time of the current request.
  This may or may not be due to the appellant.
  The internal pool links must be traversed to find a possible cause of
  the problem and the pool then special applied to the suspect tags or driver
  Auditor for a suspect driver.
  Arguments:
  Arg1: 0000000000000020, a pool block header size is damaged.
  Arg2: fffffa80044d7470, the pool entry we were looking for on the page.
  Arg3: fffffa80044d74f0, the next entry to the pool.
  Arg4: 0000000004080002, (reserved)

  ...

  DUMP_TYPE: 1
  BUGCHECK_P1: 20
  BUGCHECK_P2: fffffa80044d7470
  BUGCHECK_P3: fffffa80044d74f0
  BUGCHECK_P4: 4080002
  BUGCHECK_STR: 0x19_20
  POOL_ADDRESS: non paged fffffa80044d7470
  ...

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  Nom_processus: System
  CURRENT_IRQL: 0
  ANALYSIS_SESSION_HOST: COMPUTER DESK-NU0LNMM
  ANALYSIS_SESSION_TIME: 30/07/2016 18:26:14.0813
  ANALYSIS_VERSION: 10.0.10586.567 amd64fre
  LAST_CONTROL_TRANSFER: from fffff800047bdcbe to fffff80004687380
  STACK_TEXT:
  "fffff880 '04fb6a48 fffff800' 047bdcbe: 00000000'00000019 00000000'00000020 fffffa80 ' 044 d 7470 fffffa80 ' 044d74f0: nt! KeBugCheckEx
  fffff880 '04fb6a50 fffff800' 04b12e23: fffff800 ' 0483b6e0 fffffa80 '08db9860 fffff800' 69646d4d fffffa80 ' 03fcd660: nt! ExFreePoolWithTag + 0x18aa
  "fffff880 '04fb6b00 fffff800' 048db736: ffffffff ' 8000028 c fffff800 ' 048db700 00000000'00000001 00000000'00000000: nt! PopFreeHiberContext + 0 x 93
  "" fffff880'04fb6b40 fffff800'04690355: fffff800 ' 04830200 fffff800 ' 04980001 fffff880 ' 01cde000 fffffa80 ' 03fcd660: nt! PopUnlockAfterSleepWorker + 0 x 36
  fffff880'04fb6b70 fffff800'04920476: 00000000 00000000' fffffa80 '03fcd660 00000000 00000080' fffffa80' 03fb0040: nt! ExpWorkerThread + 0 x 111
  fffff880'04fb6c00 fffff800'04678726: fffff880'04dd5180 fffffa80 '03fcd660 fffff880' 04ddffc0 00000000'0000000 c: nt! PspSystemThreadStartup + 0x5a
  fffff880'04fb6c40 00000000' 00000000: fffff880'04fb7000 fffff880 '04fb1000 fffff880' 04fb5b30 00000000' 00000000: nt! KiStartSystemThread + 0x16

  STACK_COMMAND: kb
  THREAD_SHA1_HASH_MOD_FUNC: 9cbd837fee095df4f6be091ff8822c987c3e5d8c
  THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e2f0adb349ed2c073eba40583cc96cd00185810e
  THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6
  FOLLOWUP_IP:
  NT! ExFreePoolWithTag + 18aa
  fffff800'047bdcbe cc int 3
  FAULT_INSTR_CODE: c23d83cc
  SYMBOL_STACK_INDEX: 1
  SYMBOL_NAME: nt! ExFreePoolWithTag + 18aa
  FOLLOWUP_NAME: MachineOwner
  MODULE_NAME: nt
  Nom_image: ntkrnlmp.exe
  DEBUG_FLR_IMAGE_TIMESTAMP: 56f579f0
  IMAGE_VERSION: 6.1.7601.23403
  FAILURE_BUCKET_ID: X64_0x19_20_nt! ExFreePoolWithTag + 18aa
  BUCKET_ID: X64_0x19_20_nt! ExFreePoolWithTag + 18aa
  PRIMARY_PROBLEM_CLASS: X64_0x19_20_nt! ExFreePoolWithTag + 18aa
  -------------------------------------------------------------------------------

  Really thanks.

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  2-Memtest. (You can learn more about running memtest here)

• BSoD 0x9f error code

  In recent weeks, my computer started showing a BSoD, titled State pilot failure, whenever I stop, and sometimes, when I restart.  The computer hangs on the closing down of the screen for at least ten minutes, until appears the BSoD, where making me one forced to close.  After having extensively searched through Microsoft' forums and topics of support I still have not found a solution.  I ran Debugging Tools for Windows to open a dump file, and it revealed an error code 0x9f with an ntoskrnl.exe image name.  She led me to believe that my ntoskrnl.exe is corrupted or out of date, but I know that it is not recommended to replace this program unless that busy on a Microsoft OS disc.  I bought my PC from Future Shop, so it isn't an OS disc.

  Some of the solutions related to this error message, he said that the problem was possibly linked to attached USB devices.  The only USB device I connected is an OCZ Eclipse Laser Mouse.

  The BSoD has a side effect that if she interrupts a reboot of the system that is required to complete the system configuration, it leaves such configurations what.

  My PC specs are:
  Manufacturer: gateway
  Model: FX6800 - 03 h
  OS: Windows Vista Home Premium 64-bit
  SP: Service Pack 2
  Processor: Intel Core i7 920

  Here is the report of the bucket.  I'm totally familiar with this program then please let me know what I can do to provide more information if required.

  Microsoft (R) Windows debug 6.11.0001.404 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\Windows\Minidump\Mini091909-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.                 *
  * with the help of the there when you start the debugger argument. *.
  * 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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (8 procs) free x 64
  Product: WinNt, suite: TerminalServer personal TerminalServer
  Computer name:
  Kernel base = 0xfffff800 '02663000 PsLoadedModuleList = 0xfffff800' 02827dd0
  The debugging session: Fri Sep 17 23:57:05.741 2009 (GMT-7)
  System Uptime: 0 days 4:13:43.191
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * 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
  ....
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck 1000009F, {4, 258, fffffa80078fa040, 0}

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

  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, 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 *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, 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 *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, 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 *.
  ***                                                                   ***
  *************************************************************************
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  Probably caused by: ntoskrnl.exe (nt + 5cc7f)

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

  0: kd > nt! _KPRCB
  ^ Syntax error in ' nt! _KPRCB'
  0: kd > referenced: nt! _KPRCB
  ^ Bad registry error in ' referenced: nt! _KPRCB'
  0: kd > nt! _KPRCB
  ^ Syntax error in ' nt! _KPRCB'
  0: kd > y
  ^ Syntax error in '-y'
  0: kd > _NT_SYMBOL_PATH
  ^ Syntax error in "_NT_SYMBOL_PATH.
  0: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  DRIVER_POWER_STATE_FAILURE (9f)
  A driver is causing an inconsistent power state.
  Arguments:
  Arg1: 0000000000000004, the change in diet has expired waiting to synchronize with the Pnp
  subsystem.
  Arg2: 0000000000000258, the time-out in seconds.
  Arg3: fffffa80078fa040, the thread that currently holds the lock of Pnp.
  Arg4: 0000000000000000

  Debugging information:
  ------------------

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

  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, 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 *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, 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 *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, 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 *.
  ***                                                                   ***
  *************************************************************************
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************

  ADDITIONAL_DEBUG_TEXT:
  Use '! findthebuild' command to search for the generation of target information.
  If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.

  MODULE_NAME: nt

  FAULTING_MODULE: fffff80002663000 nt

  DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f

  DRVPOWERSTATE_SUBCODE: 4

  FAULTING_THREAD: fffffa80078fa040

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  BUGCHECK_STR: 0X9F

  CURRENT_IRQL: 0

  LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff800026bfc7f

  STACK_TEXT:
  fffffa60'01daf510 00000001' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000001: nt + 0x5cc7f
  fffffa60 '01daf518 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000001 fffff800'026c3c9b: 0x1

  STACK_COMMAND: .thread 0xfffffa80078fa040; Ko

  FOLLOWUP_IP:
  NT + 5cc7f
  fffff800'026bfc7f 488d8c2400010000 lea rcx, [rsp + 100 h]

  SYMBOL_STACK_INDEX: 0

  SYMBOL_NAME: nt + 5cc7f

  FOLLOWUP_NAME: MachineOwner

  Nom_image: ntoskrnl.exe

  BUCKET_ID: WRONG_SYMBOLS

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

  0: kd >! findthebuild
  FindTheBuild service not found
  0: kd >! findthebuild s; .reload
  Use:! findthebuild [e |-Y] [PEI | s |-r] [-l

  ]
  -E - disables exepath update
  Y - disables friendly update
  -l - hide local sets for the railways (must be last).
  ' *' define first sympath hiding in the local cache.
  Pei - adds sympath and exepath discovery railroads
  -r - sets of paths like sympath and exepath discovery
  s - adds sympath and exepath discovery railroads
  -t--detects the code paths for this trial version
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  0: kd > lmvm nt
  start end module name
  fffff800 ' 02663000 fffff800' 02b7b000 nt T (no symbol)
  Loaded symbol image file: ntoskrnl.exe
  Image path: \SystemRoot\system32\ntoskrnl.exe
  Image name: ntoskrnl.exe
  Timestamp: Fri Apr 10 21:58:39 2009 (49E0237F)
  CheckSum: 00487B 94
  ImageSize: 00518000
  Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

  Any help would be greatly appreciated.  Thank you for your time.

  Hello

  It's a bad driver more likely. Have you added all the other new features or updated drivers just before that
  has started? Look in the Windows updates too to see if new drivers have been added at this time there. Use the utility
  below to read the minidump.

  Here are a few ways to possibly fix the blue screen issue. If you could give the info from the blue screen that would be
  Help. Such as ITC and 4 others entered at the bottom left. And any other information such as STOP error
  codes 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' crashes, and displays the
  information on all accidents of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged drivers, video drivers in particular, but there are other causes.

  You can follow these steps in the Safe Mode if necessary or the command prompt Vista DVD or Options of recovery if your
  system 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, 3rd party keyboard and
  smile, 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 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 - bicycle - Mark Twain said it is good.

• BSOD after Logo Windows at startup: bad driver, AutoFailover

  I get BSOD after Windows Logo at startup. Said Startup Repair: bad driver, AutoFailover.

  Two weeks ago, that I was getting the same BSOD after logo, but only with the bad driver. I not did something to fix it (or Startup Repair), it's just dissapeard after a few days. Also, the last day that I was getting BSOD, the night when I started my pc, it remained 2 minutes at Intel Boot Agent initialization and also 30 seconds to the black screen that follows (before the windows logo). When this situation occurs I get more BSOD. I tried to restart my pc but I stayed another 2 minutes to the Intel Boot Agent initialization. This problem has been fixed in the next morning, when I started my PC, even once, I don't know how, I did nothing. I remember that it is sometimes used to stay 2 minutes Intel Boot Agent, even when I was on Windows Vista, and it also sets automatically.
  I upgraded my BIOS a few weeks before getting the BSOD, but I don't think that's the problem. In addition, there was no new driver installed before getting the BSOD, drivers have been installed after the first BSOD (even if the event viewer and the reliability monitor do not mention the first BSOD, only those who have followed the installation of the driver I know there's a BSOD before, I'm sure.)
  My system: HP Compaq 8510w (Original with windows vista bussines, did a clean install of 7 ultimate)
  BIOS version: F.20

  C: drive has only 10% free space - 15% free space is optimal for Windows

  Please visit the site Web of the manufacturer of the PC and download/install all drivers.  These are devices that lack the drivers:
  *******
  Controller of communication Simple PCI PCI VEN_8086 & DEV_2A04 & SUBSYS_30C5103C & REV_0C\3 & 21436425 & 0 & 18 that the drivers for this device are not installed.

  Serial port PCI PCI VEN_8086 & DEV_2A07 & SUBSYS_30C5103C & REV_0C\3 & 21436425 & 0 & 1 b, that the drivers for this device are not installed.
  No available ACPI\HPQ0006\2 & DABA3FF & 2, the drivers for this device are not installed.

  Base system device PCI VEN_1180 & DEV_0843 & SUBSYS_30C5103C & REV_10\4 & 118B1C9 & 0 & 34F0 the drivers for this device are not installed.

  Fingerprint Sensor USB\VID_08FF & PID_2580\5 & 1E4845E3 & 0 & 2, that the drivers for this device are not installed.

  RICOH PCMCIA\RICOH-BAY8CONTROLLER-F1B2\1 Bay8Controller the drivers for this device are not installed.
  ******
  Please uninstall ATI Tool - it does not work in Win7 and may be responsible for your BSOD (and its drivers are from 2006).  More info here: http://www.carrona.org/drivers/driver.php?id=ATITool.sys

  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  BSOD BUGCHECK SUMMARY
  The debugging session: 05:54:32.426 Fri 31 August 2012 (UTC - 04:00)
  Loading dump file [C:\Users\John\_jcgriff2_\dbug\__Kernel__\083112-17019-01.dmp]
  By: 7601.17803.x86fre.win7sp1_gdr.120330 - 1504
  System Uptime: 0 days 0:00:08.455
  Bugcheck A, {7bcc, 2, 0, 82afb482}
  ERROR: Module load completed but symbols can be loaded for mssmbios.sys
  Probably caused by: ntkrpamp.exe (nt! DeleteNodeFromTree + 46)
  Error checking code 0000000-a
  Arguments 00007bcc ', memory IRQL bitfie 82afb482 00000000' 00000002',' address
  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  BUGCHECK_STR: 0XA
  Nom_processus: System
  FAILURE_BUCKET_ID: 0xA_nt! DeleteNodeFromTree + 46
  MaxSpeed: 2200
  CurrentSpeed: 2194
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  The debugging session: 04:17:05.296 Thu August 23, 2012 (UTC - 04:00)
  Loading dump file [C:\Users\John\_jcgriff2_\dbug\__Kernel__\082312-17004-01.dmp]
  By: 7601.17803.x86fre.win7sp1_gdr.120330 - 1504
  System Uptime: 0 days 0:00:11.356
  CD error checking, {8931d 000, 0, 82a271f2, 0}
  ERROR: Module load completed but symbols can be loaded for mssmbios.sys
  WARNING: Unable to verify timestamp for ATITool.sys
  ERROR: Module load completed but symbols can be loaded for ATITool.sys
  Probably caused by: ATITool.sys (ATITool + 2017)
  000000cD Bugcheck code
  Arguments 8931d 000', memory 00000000' 82a271f2 value ', if not 00000000', int Mm
  DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
  BUGCHECK_STR: 0XCD
  Nom_processus: System
  FAILURE_BUCKET_ID: 0xCD_VRF_ATITool + 2017
  MaxSpeed: 2200
  CurrentSpeed: 2194
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  The debugging session: 04:00:26.646 Thu August 23, 2012 (UTC - 04:00)
  Loading dump file [C:\Users\John\_jcgriff2_\dbug\__Kernel__\082312-21933-01.dmp]
  By: 7601.17803.x86fre.win7sp1_gdr.120330 - 1504
  System Uptime: 0 days 0:00:07.675
  Bugcheck 1000007E, {c0000005, 82c2e4a4, 80786888, 80786460}
  ERROR: Module load completed but symbols can be loaded for mssmbios.sys
  Probably caused by: ntkrpamp.exe (nt! ObpLookupDirectoryEntry + 2 b)
  Bugcheck 1000007E code
  Arguments c0000005", ex-82c2e4a4 ', the 80786888 ad', except 80786460', Contex
  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  Nom_processus: System
  BUGCHECK_STR: 0X7E
  FAILURE_BUCKET_ID: 0x7E_nt! ObpLookupDirectoryEntry + 2 b
  MaxSpeed: 2200
  CurrentSpeed: 2194
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

• BSOD on Sysprep

  I am trying to sysprep my X 1 carbon and after you run sysprep while closing, I get a BSOD with a DRIVER_POWER_STATE_FAILURE. I checked the minidump with bluescreen viewer and the problem driver is listed as ntoskrnl.exe. No idea which driver might cause this?

  Link to photo/image

  Mod comment: Over size photo converted to establish a link. Please visit About-Posting-Pictures-In-The-Forums

  I got a reply on net microsoft technology. I submitted the memory dump, and it turns out that 3 usb driver was causing the problem. I had to uninstall and reinstall all my drivers usb Manager devices, just before you run sysprep. No BSOD after that.

• Y560 pilot State failure BSOD

  Hello

  Today, I went down my bios y560 from 59 to older bios bios.bak (by default). I did it because 59 bios is intensive heat and has problems with gradients. After flashing the bios my laptop has no downtime. I unplugged the power supply, but it continues to run on battery. I can't use the off button. Now a BSOD appeared saying DRIVER_POWER_STATE_FAILURE...

  What should I do?

  replacement ram sticks sometimes helps.

  my bad.

  It seems that your motherboard is dead. Contact lenovo helpline and request replacement free of charge if you have the warranty.

  for Slovakia call: 800-606-040

• BSOD no error checking for does not aspire VN7 - 792G

  Hello world

  I got my aspire VN7 - 792G (v17 nitro Black edition) since November 2015 and since last week, I was doing some odd BSOD bugcheck (0x000001d3) without errors. Using BlueScreenView I noticed that the error came from QCAMainx64.

  This happened last week and so I did a system restore and then updated my drivers wireless at 11.0.0.471. I've also updated my Nvidia drivers to the latest version in the case who had problems.

  I did a sfc scannow which gave rise to no error, I did a check of windows memory which gave rise to no problem and a disk check which resulted without any problem.

  The strangest thing was that the BSOD is produced especially when my laptop was being called in the upper left corner. But after a week of no BSOD they now returned at random moments.

  The first BSOD happened on cdrom.sys and netio.sys (also 0x000001d3) and then 2 other BSOD's happened (one while doing a system restore point) and the other so I just browsing youtube, which happened on the QCAMainx64 again.

  I left the Netherlands in Dubai and I left my receipt to the Netherlands, so I only have a scan of my warranty paper and ordering the product emails to prove that the laptop is mine. I was not able to repair yet because I need my laptop for work as well.

  I'll add my minidump files to this post. If anyone knows anything I might have missed or which is better I can do to avoid BSOD.

  I am running Windows 8.1. It seems that, on the acer site, that I can not download more updates to driver for windows 8.1 because they offer only win 10. And I'd rather not updated for windows 10 in all.

  Thank you for your time.

  http://www.filedropper.com/desktop_27

  Try to update the driver with this version:

  http://www.station-drivers.com/index.php?option=com_remository&Itemid=353&func=FileInfo&ID=2011&lang...

  Click Download, double-click the auto unpacking package and look for a configuration or install the file.

  Web site is 100% reliable.

  have an update on nvidia drivers too:

  http://www.GeForce.com/drivers/results/99508

• HP G42-366TX screen resolution

  After I finished to install 32-bit win7 on my laptop, the maximum resolution is only 1024 x 768... How to get the 1366 x 768 resolution... Please help me... thanks...

  Hello

  Adib says:

  After I finished to install 32-bit win7 on my laptop, the maximum resolution is only 1024 x 768... How to get the 1366 x 768 resolution... Please help me... thanks...

  Have you been to the support page for your laptop? I suggest try drivers for Win 7 32 bit are there. The HP Support Assistant would also be a good candidate to help you locate the appropriate drivers for your laptop.

  Best regards
  ERICO

• BSOD after copying the large number of files from one disk to another

  Hello. I hope you can help because this issue is very frustrating. Just built a new PC:
  -Gigabyte Z97X Gaming 7 mobo
  -8 GB Corsair vengeance 1866 mhz
  -EVGA GTX 770 video
  -CPU Intel 4770K
  -two hard drives of 1 TB WD black in RAID 1
  -one ADATA 256 Gb SSD as drive OS
  -a 1 TB drive Toshiba
  -Windows 7 64-bit professional
  -F3 Bios Rev

  System can work very well for everyday, but when I copy large number of files from one disk to another (i.e. 70 000 files, 80 GB), shortly after (10 to 30 minutes), I get a BSOD bugcheck.

  I ran MEMTEST86 for hours without error. I can run PRIME95 with max heat without error. And as I said, it seems to be fine until I do a copy of large files. It seems not to matter to this disc, I copy to/from. Start WIndows, I see no activity CHKDISK. Ideas?

  Log name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 25/06/2014 19:55:50
  Event ID: 1001
  Task category: no
  Level: error
  Keywords: Classic
  User: n/a
  Computer: Daddys-PC
  Description:
  The computer was restarted after a bugcheck.  The bugcheck was: 00000124 0 x (0 x 0000000000000000, 0xfffffa8008788028, 0x00000000bf800000, 0 x 0000000000200401). A dump was saved in the: C:\Windows\MEMORY. DMP. Report ID: 062514-6692-01.
  The event XML:
  
   
     
      1001
      0
      2
      0
      0
      0 x 80000000000000
     
      32358
     
     
      System
      Daddys-PC
     
   
   
      0 x 00000124 (0 x 0000000000000000, 0xfffffa8008788028, 0x00000000bf800000, 0 x 0000000000200401)
      C:\Windows\MEMORY. DMP
      062514-6692-01
   
  

  No problem, thank you!

  All attached files of the DMP are the verification of bug WHEA_UNCORRECTABLE_ERROR (124) .

  A fatal hardware error occurred. This fatal error data error Architecture WHEA (Windows Hardware).

  If we run one! errrec on the 2nd parameter of the bug check (address of the WER structure), we get the following:

  ===============================================================================
  Section 2: x 86 / x 64 MCA
  -------------------------------------------------------------------------------
  Descriptor of @ fffffa8008788138
  Article @ fffffa80087882c0
  Shift: 664
  Length: 264
  Flags: 0x00000000
  Gravity: Fatal

  Error: Internal unclassified (Proc 4 row 1)
  Status: 0xbf80000000200401
  Address: 0x00000000fee00040
  Misc.       : 0 x 0000000000000086

  Internal unclassified error, this implies that it is not publicly documented and there is no way to identify the error.

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

  1. AppleCharger.sys is listed and charged, which is the driver GIGABYTE on / off Charge. See here for more information - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

  Very annoying software, so please uninstall ASAP!

  2 remove and replace Norton with Microsoft Security Essentials for purposes of troubleshooting temporary, as it can be at the origin of the conflict:

  Removal of Norton- https://support.Norton.com/SP/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;JSESSIONID=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&PVID=f-home

  -MSE http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

  3 uninstall Gigabyte Saver Easy, Easy Tune, as well as all the another bloatware Gigabyte, it is very problematic.

  4.

  2: kd > lmvm marvinbus64
  start end module name
  fffff880' 04c 51000 fffff880'04 c 95000 MarvinBus64 (postponed)
  Image path: \SystemRoot\system32\DRIVERS\MarvinBus64.sys
  Image name: MarvinBus64.sys
  Timestamp: Fri Sep 23 17:17:03 2005

  Pinnacle Studio Marvin Bus driver, dated 2005. Too old to work with the operating system, so please delete the software + the device (if any).

  5 please remove your Rainbow Tech/SafeNet USB security device if there is no update for its software, device drivers are too old.

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

  If all else fails, there's only so much you can do with an error like this, checking until it boils down to a faulty processor that needs to be replaced. Start from 1 and work down:

  1. make sure your temperatures are the norm and nothing is overheating. You can use a program such as Speccy if you want to monitor the time - http://www.piriform.com/speccy

  2 clear your CMOS (or optimized load BIOS default) to ensure that there is no parameter incorrect BIOS - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

  3. make sure that your BIOS is up to date.

  4 if all else fails, the only one left to do is replace your CPU because it is defective.

  Kind regards

  Patrick

• BSOD after monitors

  Hello

  I just start getting some BSOD. Sometimes after that I have spend monitors using the Windows + P shortcut. I start here her connect / disconnect sound over and over, then the BSOD.

  I have an ASUS HD 7970 graphics card

  I use the Windows + shortcut P to switch from a connected DisplayPort Samsung 27 "monitor LED series 8 SyncMaster [S27A850T]

  a connected HDMI Samsung Plasma TV.

  What would someone mind checking the Minidump files to help me work out what is the cause.

  I tried to restore my PC Windows 7 64 bit to a point before the BSOD occurred.

  I have the latest graphics card driver.

  There is an update of the firmware available for your Samsung monitor - did you apply it?  Here is the link: http://www.samsung.com/au/support/newsalert/view?spp_news_seq=36090

  You have a connected Applian/Appliand device.  I asked questions with this device back with another poster several months ago and never received a feedback (so I don't know if there is a problem with the drivers of this company).  I suggest you uninstall it until the system is stable again.

  There are a few known issues with SSD and old storage controller drivers.  Please ensure that your Kingston SSD has the latest firmware installed - and the storage controllers of your motherboard with the latest drivers available from the manufacturer of storage controller.  The Intel controller drivers so your Marvell date from 2011. Please don't forget to use connections to the Intel controller, once the drivers are updated (update the Marvell even if you don't use it).

  As a side note, the GEARAspiWDM.sys has been updated.  I was under the impression that there were not updated available for this purpose (it is usually a part of iTunes).  Have you updated your iTunes between the 2 BSOD?

  Video drivers and pilots antivirus date 2011 - these two must be updated to the latest version available (video drivers from ATI and the site of AVG antivirus site

  I've never used OEM drivers for one of my monitors in the past - but I wonder if this can help your situation.  Unfortunately I'm unable to locate the drivers for the monitor on the Samsung website.  I suggest that you contact their technical support for information about drivers (they can be integrated into Windows).

  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  BSOD BUGCHECK SUMMARY
  The debugging session: Sat Sep 15 2012 05:16:48.258 (UTC - 04:00)
  Loading dump file [C:\Users\John\_jcgriff2_\dbug\__Kernel__\091512-39187-01.dmp]
  By: 7601.17835.amd64fre.win7sp1_gdr.120503 - 2030
  System Uptime: 0 days 4:08:40.195
  WARNING: Unable to verify timestamp for atikmdag.sys
  ERROR: Module load completed but symbols can be loaded for atikmdag.sys
  Bugcheck 1000007E, {ffffffffc0000005, fffff8800784eebf, fffff8800e3beb88, fffff8800e3be3e0}
  Probably caused by: atikmdag.sys (atikmdag + 1e3ebf)
  Bugcheck 1000007E code
  Arguments ffffffff 'c0000005 fffff880' 0784eebf fffff880 '0e3beb88 fffff880' 0e3be3e0
  Nom_processus: csrss.exe
  BUGCHECK_STR: 0X7E
  DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
  FAILURE_BUCKET_ID: X64_0x7E_atikmdag + 1e3ebf
  MaxSpeed: 3330
  CurrentSpeed: 3340
  BiosVersion = 0803
  BiosReleaseDate = 06/08/2012
  SystemManufacturer = system manufacturer
  SystemProductName = system product name
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  The debugging session: Fri Sep 14 06:31:34.007 2012 (UTC - 04:00)
  Loading dump file [C:\Users\John\_jcgriff2_\dbug\__Kernel__\091412-39125-01.dmp]
  By: 7601.17835.amd64fre.win7sp1_gdr.120503 - 2030
  System Uptime: 0 days 11:58:26.944
  WARNING: Unable to verify timestamp for atikmdag.sys
  ERROR: Module load completed but symbols can be loaded for atikmdag.sys
  Bugcheck 1000007E, {ffffffffc0000005, fffff88007882ebf, fffff8800c819b88, fffff8800c8193e0}
  Probably caused by: atikmdag.sys (atikmdag + 1e3ebf)
  Bugcheck 1000007E code
  Arguments ffffffff 'c0000005 fffff880' 07882ebf fffff880 '0c819b88 fffff880' 0c8193e0
  Nom_processus: csrss.exe
  BUGCHECK_STR: 0X7E
  DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
  FAILURE_BUCKET_ID: X64_0x7E_atikmdag + 1e3ebf
  MaxSpeed: 3330
  CurrentSpeed: 3340
  BiosVersion = 0803
  BiosReleaseDate = 06/08/2012
  SystemManufacturer = system manufacturer
  SystemProductName = system product name
  ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

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