The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    BSOD DRIVER_POWER_STATE_FAILURE - 15 980M

    Discussion in '2015+ Alienware 13 / 15 / 17' started by matthebatness, Jun 29, 2015.

  1. matthebatness

    matthebatness Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Hi everyone,
    I Have a new Alienware 15 with the 980M since 2 weeks. So far I like it although I am having some BSOD DRIVER_POWER_STATE_FAILURE with it. Just got my fourth while surfing the internet. I have all the latest drivers and Windows Updates. I am able to play Witcher 3, GTA 5, Far Cry 4 and most games at max settings with good performance. I will post my Who Cashed bellow :
    On Mon 2015-06-29 1:09:03 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\062915-16734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
    Bugcheck code: 0x9F (0x3, 0xFFFFE001BB5EE060, 0xFFFFD00119086960, 0xFFFFE001C57596E0)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Tue 2015-06-16 6:42:07 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\061615-15406-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3BA8F2)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801C0A538F2, 0xFFFFD0002556E270, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 353.30
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 353.30
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 353.30 , NVIDIA Corporation).
    Google query: NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION

    On Mon 2015-06-08 11:51:30 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\060815-15453-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
    Bugcheck code: 0x9F (0x3, 0xFFFFE000589A3880, 0xFFFFF80176667960, 0xFFFFE000589DB860)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Sat 2015-06-06 1:43:23 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\060515-14906-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
    Bugcheck code: 0x9F (0x3, 0xFFFFE001B64A6060, 0xFFFFD001D2379960, 0xFFFFE001B64DA930)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    If anyone could help me it would be greatly appreaciated. It's frustrating to have a brand new computer that BSOD's.
    Thank you !
     
  2. Mickbt26

    Mickbt26 Notebook Evangelist

    Reputations:
    55
    Messages:
    634
    Likes Received:
    37
    Trophy Points:
    41
    It sounds very similar to mine when I first got my 17R2. I had constant BSODs, Lockups and random freezes out of the box.

    I phoned DELL CS and it was diagnosed as a faulty mainboard. So they sent a tech out to replace it the next day. It has been fine since it was changed other than some throttle issues but that's another story.

    I would phone CS and see what they can do for you. They are really helpful.

    Good luck
     
  3. matthebatness

    matthebatness Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Hi Mickbt26, thank you for your answer I will consider strongly contacting them. Although My laptop works fine most of the time I I am hoping it is not a hardware issue. You say you had freezing and lockups, I don't. But still I would not want my laptop to start freezing randomly after some time. Has anyone else experience same issue as mine ? Thank you !
     
  4. Game7a1

    Game7a1 ?

    Reputations:
    529
    Messages:
    3,159
    Likes Received:
    1,040
    Trophy Points:
    231
    I may have had this happened on my laptop, but I fixed it by reinstalling both the Intel and Nvidia Graphics drivers (latest from respective websites and I uninstalled them because that's the only way to install the Intel Graphics Driver).
     
  5. matthebatness

    matthebatness Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Thank you for your answer Game7a1, I a reassured It might be simply a driver issue and not a motherboard problem, I will do a clean install of my drivers and see if it helps. You should be able to see if you had the same exact error with Who Crashed on your pc, thank you !
     
  6. Game7a1

    Game7a1 ?

    Reputations:
    529
    Messages:
    3,159
    Likes Received:
    1,040
    Trophy Points:
    231
    Oh I would remember what BSODs I get thanks to bluescreenview, but usually, getting those drivers helped me.
    I'm thinking it is a driver problem since the Nvidia driver is cited, but I do think the Intel driver is also part of the problem.
     
  7. matthebatness

    matthebatness Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Thank you again for your input. I will look at bluescreenview I did not know this program, seems usefull ! I will post back here if I still get an issue after reinstalling drivers