BSOD driver_power_state_failure brand new laptop

Hi all,

I would like to let you know my problems. Since a couple of days I am having that error everysingle day more or less.
DSC07680.JPG


My laptop is an ASUS K53S :
Intel® Core™ i7 2670QM/2630QM Processor,
Intel® HM65 Express Chipset

I need help please;)
 
Hi again friends, after check with Windbg my minidump I found this:


Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************
 
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80089e4060, Physical Device Object of the stack
Arg3: fffff80004bd73d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800a6aa7d0, The blocked IRP
 
Debugging Details:
------------------
 
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: NT!_DEVICE_OBJECT                            ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_IRP                                      ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_IRP                                      ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!TRIAGE_9F_POWER                            ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_IRP                                      ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_IO_STACK_LOCATION                        ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_IRP                                      ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_DEVICE_OBJECT                            ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
*************************************************************************
***                                                                  ***
***                                                                  ***
***    Either you specified an unqualified symbol, or your debugger  ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a  ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that  ***
***    enabling unqualified symbol resolution with network symbol    ***
***    server shares in the symbol path may cause the debugger to    ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.    ***
***                                                                  ***
***    For some commands to work properly, your symbol path          ***
***    must point to .pdb files that have full type information.      ***
***                                                                  ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                  ***
***    Type referenced: nt!_KPRCB                                    ***
***                                                                  ***
*************************************************************************
 
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
 
MODULE_NAME: nt
 
FAULTING_MODULE: fffff80003218000 nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3
 
DRVPOWERSTATE_SUBCODE:  3
 
DEVICE_OBJECT: fffffa80089e4060
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0x9F
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from fffff800033016c2 to fffff800032971c0
 
STACK_TEXT:
fffff800`04bd7388 fffff800`033016c2 : 00000000`0000009f 00000000`00000003 fffffa80`089e4060 fffff800`04bd73d8 : nt+0x7f1c0
fffff800`04bd7390 00000000`0000009f : 00000000`00000003 fffffa80`089e4060 fffff800`04bd73d8 fffffa80`0a6aa7d0 : nt+0xe96c2
fffff800`04bd7398 00000000`00000003 : fffffa80`089e4060 fffff800`04bd73d8 fffffa80`0a6aa7d0 00000000`00000000 : 0x9f
fffff800`04bd73a0 fffffa80`089e4060 : fffff800`04bd73d8 fffffa80`0a6aa7d0 00000000`00000000 00000000`00000000 : 0x3
fffff800`04bd73a8 fffff800`04bd73d8 : fffffa80`0a6aa7d0 00000000`00000000 00000000`00000000 fffff800`0343eb20 : 0xfffffa80`089e4060
fffff800`04bd73b0 fffffa80`0a6aa7d0 : 00000000`00000000 00000000`00000000 fffff800`0343eb20 fffff800`00000002 : 0xfffff800`04bd73d8
fffff800`04bd73b8 00000000`00000000 : 00000000`00000000 fffff800`0343eb20 fffff800`00000002 00000000`00018000 : 0xfffffa80`0a6aa7d0
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:
nt+7f1c0
fffff800`032971c0 48894c2408      mov    qword ptr [rsp+8],rcx
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  nt+7f1c0
 
FOLLOWUP_NAME:  MachineOwner
 
IMAGE_NAME:  ntoskrnl.exe
 
BUCKET_ID:  WRONG_SYMBOLS
 
Followup: MachineOwner
---------


I think is something regarding one driver which it could be unupdated?

Regards,
 
Since this is brand new our advice here at TechSpot is to contact the manufacture's Tech Support and have them fix it. This is their problem and not your problem. The only problem with Asus is their tech support is very poor. Don't let them give you the run around. If you bought it from a store such as best Buy return it pronto. If they won't help, etc. Tell them you want your money back.
 
I've seen this caused by an incorrect bios setting... Sojiyo, have you changed any bios settings?
 
Back