Jump to content

fixed: Causing Audio Device Lost on Microsoft Surface Book & Surface Pro4


remyc

Recommended Posts

There's a fatal problem on using AIDA64 on Microsoft Surface Book and Surface Pro4. 

 

It seems AIDA64 could cause the audio device on Surface being disabled with a blue screen error, DRIVER_POWER_STATES_FAILURE  .

 

Audio device would be lost after reboot. The only way to recover is hardware reset or opening UEFI to turn off and turn on internal audio device again.

 

Although it wouldn't happen every time launching AIDA64, the probability is very high.

Link to comment
Share on other sites

  • 2 weeks later...

What version of AIDA64 are you using? I'm just asking because we've already fixed a similar issue about Surface Pro 4 and Surface Book in AIDA64 v5.60.

Thanks,

Fiery

Hi Fiery, this problem is still there. I've tried the latest version 5.75.3900. If I keep AIDA64 opening for some time, audio device would be disabled.

Link to comment
Share on other sites

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Finally, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Let me know if you experience any issues after issuing each of those 3 dumps.

Thanks,

Fiery

Link to comment
Share on other sites

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Finally, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Let me know if you experience any issues after issuing each of those 3 dumps.

Thanks,

Fiery

 

 

ISA Sensor Dump
 
Motherboard ID      : <DMI>
Motherboard Model   : Microsoft Surface Book
Motherboard Chipset : Intel Sunrise Point-LP, Intel Skylake-U
 
DMI MB Manufacturer : Microsoft Corporation
DMI MB Product      : Surface Book
DMI MB Version      : 
DMI MB Serial       : A11405310683552A
DMI SYS Manufacturer: Microsoft Corporation
DMI SYS Product     : Surface Book
DMI SYS Version     : D:0B:08F:1C:03P:38
DMI SYS Serial      : 015053755257
DMI BIOS Version    : 90.1281.768
 
ITE SuperIO Port           = 00h
ITE SuperIO HWMonitor Port = 0000h (0000h / 0000h)
ITE SuperIO Device ID      = 0000h (0000h / 0000h)
ITE SuperIO Version        = 00h   (  00h /   00h)
 
Winbond SuperIO Port              = 2Eh
Winbond SuperIO HWMonitor Port/60 = 0000h (0000h / 0000h)
Winbond SuperIO HWMonitor Port/64 = 0000h (0000h / 0000h)
Winbond SuperIO Device ID         = 8528h (8528h / 0000h)
 
Fintek SuperIO Port           = 00h
Fintek SuperIO HWMonitor Port = 0000h (0000h / 0000h)
Fintek SuperIO Device ID      = 0000h (0000h / 0000h)
 
SMSC SuperIO Port           = 00h
SMSC SuperIO HWMonitor Port = 0000h (0000h / 0000h)
SMSC SuperIO Device ID      = 8528h (8528h / 0000h)
 
ASpeed SuperIO Port = 00h
 
------[ ACPI Temperatures & Fans ]------
 
_TZ_.THM0._TMP             : 
_TZ_.THM1._TMP             : 
_TZ_.THR0._TMP             : 
_TZ_.THR1._TMP             : 
_TZ_.TZ00._TMP             : 
_TZ_.TZ01._TMP             : 
_TZ_.RTMP                  : 
_TZ_.RFAN                  : 
_TZ_.RFAN(0)               : 
_TZ_.RFAN(1)               : 
_SB_.ATKD._HID             : 
_SB_.ATKD.TMPR             : 
_SB_.PCI0.LPC0.EC0_.CCTV   : 
_SB_.PCI0.LPC0.EC0_.LRPM   : 
_SB_.PCI0.LPC0.EC0_.HRPM   : 
_SB_.PCI0.SBRG.EC0_.ECPU   : 
_SB_.PCI0.SBRG.EC0_.TACH(0): 
_SB_.PCI0.SBRG.EC0_.TACH(1): 
_SB_.PCI0.SBRG.EC0_.TAH0   : 
_SB_.PCI0.SBRG.EC0_.TAH1   : 
_SB_.PCI0.SBRG.EC0_.ST00   : 
_SB_.PCI0.SBRG.EC0_.SC01   : 
_SB_.PCI0.SBRG.EC0_.SC02   : 
_SB_.PCI0.SBRG.EC0_.SC03   : 
_SB_.PCI0.SBRG.EC0_.SC04   : 
_SB_.PCI0.SBRG.EC0_.SC05   : 
_SB_.PCI0.SBRG.EC0_.SC06   : 
_SB_.PCI0.SBRG.EC0_.TH0R   : 
_SB_.PCI0.SBRG.EC0_.TH1R   : 
_SB_.PCI0.SBRG.EC0_.F0TS   : 
_SB_.PCI0.SBRG.EC0_.F1TS   : 
_SB_.PCI0.PIB_.EC0_.TCRT   : 
_SB_.PCI0.SBRG.EC0_.CTPM   : 
_SB_.PCI0.SBRG.EC__.CPUT   : 
_SB_.PCI0.SBRG.EC__.SYST   : 
_SB_.PCI0.LPC_.EC0_.CTMP   : 
_SB_.PCI0.LPCB.EC0_.CTMP   : 
_SB_.PCI0.LPC_.EC0_.TMP1   : 
_SB_.PCI0.LPC_.EC0_.TMP2   : 
_SB_.PCI0.LPC_.EC0_.TMPI   : 
_SB_.PCI0.LPC_.EC0_.TMPV   : 
_SB_.PCI0.LPCB.EC0_.A1TP   : 
_SB_.PCI0.LPCB.EC0_.A2TP   : 
_SB_.PCI0.LPCB.EC0_.FAN0   : 
_SB_.PCI0.LPCB.EC__.TS1R   : 
_SB_.PCI0.LPCB.EC__.TS2R   : 
_SB_.PCI0.LPCB.EC__.TS3R   : 
_SB_.PCI0.LPCB.EC__.F1FL   : 
_SB_.PCI0.LPCB.EC__.F1FH   : 
_SB_.PCI0.LPCB.EC__.F2FL   : 
_SB_.PCI0.LPCB.EC__.F2FH   : 
_SB_.PCI0.LPC_.H8EC.RTMP   : 
_SB_.PCI0.LPC_.H8EC.LTMP   : 
_SB_.PCI0.LPC_.H8EC.MTMP   : 
_SB_.PCI0.LPC_.H8EC.GTMP   : 
_SB_.PCI0.LPCB.H8EC.CTMP   : 
_SB_.PCI0.LPCB.H8EC.DTMP   : 
_SB_.PCI0.LPCB.H8EC.GTMP   : 
_SB_.PCI0.LPCB.H8EC.ITMP   : 
_SB_.PCI0.LPCB.H8EC.MTMP   : 
_SB_.PCI0.LPCB.H8EC.STMP   : 
_SB_.PCI0.LPCB.H8EC.PFAN   : 
_SB_.PCI0.LPCB.EC0_.OTPC   : 
_SB_.PCI0.LPCB.EC0_.VGAT   : 
_SB_.PCI0.LPCB.EC0_.CHPT   : 
_SB_.PCI0.LPCB.EC0_.CPUT   : 
_SB_.PCI0.LPCB.EC0_.SYST   : 
_SB_.PCI0.LPCB.EC0_.DTS1   : 
_SB_.PCI0.LPCB.EC0_.DTS2   : 
_SB_.PCI0.LPCB.EC0_.DIMM   : 
_SB_.PCI0.LPCB.EC0_.FANH   : 
_SB_.PCI0.LPCB.EC0_.FANL   : 
_SB_.PCI0.LPCB.EC0_.CUTP   : 
_SB_.PCI0.LPCB.EC0_.PHTP   : 
_SB_.PCI0.LPCB.EC0_.DIMT   : 
_SB_.PCI0.LPCB.EC0_.INLE   : 
_SB_.PCI0.LPCB.EC0_.PANT   : 
_SB_.PCI0.LPCB.EC0_.F0RM   : 
_SB_.PCI0.LPCB.EC0_.F0DT   : 
_SB_.PCI0.LPCB.EC0_.F1RM   : 
_SB_.PCI0.LPCB.EC0_.F1DT   : 
_SB_.PCI0.SBRG.EC0_.CUTP   : 
_SB_.PCI0.SBRG.EC0_.PHTP   : 
_SB_.PCI0.SBRG.EC0_.DIMT   : 
_SB_.PCI0.SBRG.EC0_.INLE   : 
_SB_.PCI0.SBRG.EC0_.PANT   : 
_SB_.PCI0.SBRG.EC0_.F0RM   : 
_SB_.PCI0.SBRG.EC0_.F0DT   : 
_SB_.PCI0.SBRG.EC0_.F1RM   : 
_SB_.PCI0.SBRG.EC0_.F1DT   : 
_SB_.SAMB.TMPC             : 
_SB_.SAMB.TMPH             : 
_SB_.STR0._TMP             : 
_SB_.STR1._TMP             : 
_SB_.STR2._TMP             : 
_SB_.STR3._TMP             : 
_SB_.STR4._TMP             : 
_SB_.STR5._TMP             : 
_SB_.STR6._TMP             : 
_SB_.STR7._TMP             : 
CPUT                       : 
GPUT                       : 
SYST                       : 
FANT                       : 
BATT                       : 
 
 
SMBus Dump (Full)
------[ AIDA64 Extreme v5.75.3900 ]------
 
------[ Microsoft Windows 10 Pro 10.0.14393.187 (64-bit) ]------
 
------[ Motherboard Info ]------
 
Motherboard ID      : <DMI>
Motherboard Model   : Microsoft Surface Book
Motherboard Chipset : Intel Sunrise Point-LP, Intel Skylake-U
 
DMI MB Manufacturer : Microsoft Corporation
DMI MB Product      : Surface Book
DMI MB Version      : 
DMI MB Serial       : A11405310683552A
DMI SYS Manufacturer: Microsoft Corporation
DMI SYS Product     : Surface Book
DMI SYS Version     : D:0B:08F:1C:03P:38
DMI SYS Serial      : 015053755257
DMI BIOS Version    : 90.1281.768
 
------[ 0 SMBuses detected ]------
 
 
 Embedded Controller Dump
------[ AIDA64 Extreme v5.75.3900 ]------
 
------[ Microsoft Windows 10 Pro 10.0.14393.187 (64-bit) ]------
 
------[ Motherboard Info ]------
 
Motherboard ID      : <DMI>
Motherboard Model   : Microsoft Surface Book
Motherboard Chipset : Intel Sunrise Point-LP, Intel Skylake-U
 
DMI MB Manufacturer : Microsoft Corporation
DMI MB Product      : Surface Book
DMI MB Version      : 
DMI MB Serial       : A11405310683552A
DMI SYS Manufacturer: Microsoft Corporation
DMI SYS Product     : Surface Book
DMI SYS Version     : D:0B:08F:1C:03P:38
DMI SYS Serial      : 015053755257
DMI BIOS Version    : 90.1281.768
 
------[ Embedded Controller at 0066/0062 via Port I/O / Bank #0 ]------
 
0000  00 4D 12 16  00 00 00 00  00 07 00 20  02 00 00 00  .M......... ....
0010  00 00 A2 02  00 00 04 0C  72 02 40 02  40 02 F4 0B  ........r.@.@...
0020  00 0F 10 06  04 0D 80 03  60 03 F0 05  04 0D 00 00  ........`.......
0030  00 52 0A 15  01 29 13 16  00 00 00 00  00 00 00 00  .R...)..........
0040  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0050  00 00 00 04  0C C8 21 00  00 00 00 01  00 64 00 E4  ......!......d..
0060  08 E4 08 00  00 FC 21 E0  00 4B 00 53  09 4C 1D 31  ......!..K.S.L.1
0070  00 D7 20 A6  B0 44 59 4E  00 00 00 00  00 00 00 00  .. ..DYN........
0080  00 58 39 30  36 39 37 31  00 4C 49 4F  4E 00 00 31  .X906971.LION..1
0090  30 38 30 35  00 00 00 00  00 00 00 00  00 00 00 00  0805............
00A0  00 00 00 F4  0B C9 21 9A  02 A1 02 01  00 62 00 1F  ......!......b..
00B0  19 DD 19 48  0D FC 21 80  00 5A 00 90  1A 4C 1D 31  ...H..!..Z...L.1
00C0  00 3F 20 C1  8F 53 4D 50  00 99 99 99  99 99 99 99  .? ..SMP........
00D0  99 58 39 30  36 39 38 30  00 4C 49 4F  4E 00 31 30  .X906980.LION.10
00E0  31 30 38 30  35 0F 0F 00  00 00 00 00  00 00 00 02  10805...........
00F0  00 00 00 00  00 00 37 19  00 00 00 00  00 00 00 00  ......7.........
 
Time #1 = 171
Time #2 = 0
 
Link to comment
Share on other sites

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Finally, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Let me know if you experience any issues after issuing each of those 3 dumps.

Thanks,

Fiery

By the way, I found the audio device was turned to abnormal power state again after I got the 3 dumps. 

 

Here's the way to check if it occurs before blue screen. Right click the speaker icon in the bottom right corner of Windows 10 task bar. And then click Playback devices. 

The sound panel wouldn't popup if the audio device has been turned to abnormal power state. And blue screen DRIVER_POWER_STATES_FAILURE  would also occur after several minutes.

 

The audio devices would keep disabled for a long time and wouldn't recover even you restart or force shut down Surface.

The quick way I found to deal with it is hardware reset. Force shutdown Surface first, and hold volume up and power button for more than 30 seconds. And then turn on Surface again.

Link to comment
Share on other sites

Thank you. The SMBus workaround is working properly, so the culprit is most likely the Embedded Controller. Can you please repeat only the Embedded Controller Dump, and let us know whether or not it triggers the issue?

Thanks,

Fiery

 

Thanks Fiery, I've tried that any of the 3 dump action could trigger the issue. If I tried to do any sound related action (e.g. change volume) just after or during dump, it would be triggered. It would be safe if wait several second after dump. 

Link to comment
Share on other sites

Thank you. I have to say, that's quite puzzling. Can you please check what happens if you just start AIDA64, without performing any dumps and without navigating to any info pages? If it works properly that way, then please try to go to the Motherboard / Chipset page. I suppose it would trigger the issue.

Link to comment
Share on other sites

  • 4 weeks later...
On 2016/9/20 at 2:35 AM, Fiery said:

Thank you. I have to say, that's quite puzzling. Can you please check what happens if you just start AIDA64, without performing any dumps and without navigating to any info pages? If it works properly that way, then please try to go to the Motherboard / Chipset page. I suppose it would trigger the issue.

You are right! If I try to open sound panel immediately just after go to Motherboard / Chipset page, it triggered the issue. Is there any possible solution to avoid the strange problem?

Link to comment
Share on other sites

On ‎2016‎. ‎10‎. ‎27‎. at 11:56 AM, remyc said:

It seems work. Thank you very much. BTW, Has this fix been included in the latest stable version, 5.80.4000?

Yes, of course it's included. Thank you for the feedback, I'm glad the bug fix worked out :) 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...