Frequent DRIVER_POWER_STATE_FAILURE in Matlab on new Toshiba Laptop

Hagen · 18 Aug 2016

Hi Forum,

I'm writing on behalf of my girlfriend who has a new Laptop, Toshiba SATELLITE P50-C with Intel Core i7-6700HQ CPU and NVIDIA GeForce GTX 950M. She manually installed Windows 10 Pro x64 on it. She hasn't used it extensively so far, mainly for her student projects involving Matlab and Microsoft Word.
Sadly, she has been getting a lot of BSODs with DRIVER_POWER_STATE_FAILURE, alone today it happened 3 times so far. These always seem to be caused by interacting with figures Matlab. She already tried reinstalling Matlab, but no change. I also manually installed the latest NVIDIA driver from their website and updated the Intel Graphics driver through the device manager using windows update. However, none of this has helped.
Is it possible, that this is a hardware problem? My girlfriend is seriously thinking about returning the laptop, which would be a shame because it is otherwise a very nice one...

I hope you can help us, and looking forward to your answers!

philc43 · 18 Aug 2016

Hello Hagen and welcome to TenForums :)

I notice that in her eventlog she has lots of hardware related errors:

Code:

Event[17506]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2016-08-18T13:47:36.004
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-KVSGCNF
  Description: 
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus:Device:Function: 0x0:0x1C:0x2
Vendor ID:Device ID: 0x8086:0xA112
Class Code: 0x30400

The details view of this entry contains further information.

I have seen this type of thing before and a search on Google will show you that it has been happening a lot. Toshiba may have updated drivers to help with this problem. It is not clear if it relates just to the graphics drivers so it would be worth updating the LAN and wifi drivers as well as any others you can see that have recent updates provided by Toshiba.

axe0 · 18 Aug 2016

You just need to know how to use the information :)

To find what is causing this, we'll use the device ID to search in the msinfo32.nfo

Code:

Event[17506]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2016-08-18T13:47:36.004
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-KVSGCNF
  Description: 
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus:Device:Function: 0x0:0x1C:0x2
Vendor ID:Device ID: 0x8086:0xA112
Class Code: 0x30400

The details view of this entry contains further information.

We have a shared memory address with the chipset & LAN.
Attachment 96802

For the BSODs, it is basically the Nvidia display driver causing the trouble.
Simply check Toshiba for driver updates or reinstall the drivers :)

Code:

2: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff800`05840000 fffff800`06591000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 11 00:20:31 2016 (5782CA2F)
    CheckSum:         00D0B030
    ImageSize:        00D51000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Hagen · 18 Aug 2016

Thanks for your answers :)

We completely unistalled the Nvidia drivers and installed the latest ones from their website. We also installed Wifi, LAN, Bluetooth and chipset drivers from the Toshiba support site and then installed a BIOS update from the same site.

We'll see if the BSODs still occur, however we checked the Event Viewer and those WHEA errors definitely still occur

axe0 said:

To find what is causing this, we'll use the device ID to search in the msinfo32.nfo
...
We have a shared memory address with the chipset & LAN.

Is there a way of preventing htis shared memory address?

axe0 · 18 Aug 2016

Sharing addresses isn't an issue, it is actually one of the services that the Memory Management of Windows provides.