BSODs on Asus X541UAK

Hello,

I just got a Asus X541UAK laptop about a month ago and recently experienced 2 BSODs (October 5th and 11th). I am running Windows 10 x64 and have installed the latest Creator's Update. I have attached my system information, as well as my Crash Minidump files in a OneDrive folder below. I do believe that I have the latest drivers installed from the Asus website but am unsure whether this is the issue: ASUS VivoBook Max X541UA Driver & Tools| Laptops | ASUS Global.

Crash Minidumps - OneDrive
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Thank you sincerely,
Kevin

Hi,

philc43 said:

Please refer to several recent threads that have BSOD events associated with ASUS laptops and while watching youtube videos. They have all been fixed by using an older version of the rtwlane.sys driver. You have the same problem.
For example: BSOD watching videos on youtube, error Watchdog Violation.

FIX here: BSOD, everytime i watch videos on youtube, DPC watchdog violation - Windows 10 Forums


This is from the analysis which show the realtek driver as culprit:

Code:

0x00000133:    [SPECIAL] DPC_WATCHDOG_VIOLATION (2017-10-06 00:30:25) [Windows 10] 
 
CAUSED BY:     rtwlane.sys [2017-05-18] * Realtek PCI-E Wireless LAN NIC NDIS Driver * => http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=21&Level=4&Conn=3  
 
PROCESS:       System

Thank you, I've tried the older driver and it resulted in another BSOD. Any idea about the second dump file (experienced today)? Thanks for your kind assistance.

try a driver from beginning of 2016 or 2015. The driver is showing up in every dump as root cause. If u receive another BSOD after downgrading the driver, please post a new DM Log Collector zip

Thank you, I rolled back the Realtek RTL8723BE Wireless LAN 802.11n PCI-E NIC driver which had the rtwlane.sys property. Should I roll back any other drivers (e.g. Realtek PCIe FE Family Controller) as well?

no, this should be sufficient

Hi,
Does the 2nd crash dump file (please see link below) suggest an issue with the Intel Graphics Driver? I currently have the latest Intel Graphics Driver from Asus. Thank you.
OneDrive

There was a 3rd bsod mini dump dated today, 10/11/2017 that displayed the same misbehaving driver.
As BSODHunter indicated this driver needs to be replaced not with an updated driver but with a rolled back driver.
This problem was more frequent months ago and in multiple threads various drivers were used.
So make sure you install an older driver.
Windows by default may update drivers.
Use the information in this link to turn off Windows updates of non-Microsoft drivers.
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows Update Activation Tutorials
Then roll back the driver.
The Intel graphics driver was a prior bsod on 9/17/2017 but did not appear in the October bsod mini dumps.
If you want to you can almost always update and replace drivers.
The Realtek/Asus notebook is the exception where the driver needs to be rolled back.

rtwlane.sys

Realtek PCI-E Wireless LAN NIC NDIS Driver

http://www.realtek.com.tw/downloads/...Level=4&Conn=3

Code:

Name    [00000001] Realtek RTL8723BE Wireless LAN 802.11n PCI-E NICAdapter Type    Ethernet 802.3Product Type    Realtek RTL8723BE Wireless LAN 802.11n PCI-E NICInstalled    YesPNP Device ID    PCI\VEN_10EC&DEV_B723&SUBSYS_172311AD&REV_00\0023B7FEFF4CE00000Last Reset    2017-10-11 12:23 AMIndex    1Service Name    RTWlanEIP Address    192.168.0.23, fe80::c492:60a:b18f:22e9IP Subnet    255.255.255.0, 64Default IP Gateway    192.168.0.1DHCP Enabled    YesDHCP Server    192.168.0.1DHCP Lease Expires    2017-10-11 12:23 PMDHCP Lease Obtained    2017-10-11 12:23 AMMAC Address    ‪3C:A0:67:1C:43:CA‬I/O Port    0x0000DF00-0x0000DFFFMemory Address    0xEF0FC000-0xEF0FFFFFIRQ Channel    IRQ 4294967286Driver    c:\windows\system32\drivers\rtwlane.sys (2023.55.415.2017, 6.50 MB (6,813,664 bytes), 2017-07-14 8:08 AM)

Code:

2017-10-11 4:17 AM    Windows Error Reporting    Fault bucket 0x133_DPC_nt!KeAccumulateTicks, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 77074f4e-0664-44eb-afc9-f66d8ac17783

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff803a8476348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\101117-37734-01.dmp
\\?\C:\Windows\Temp\WER-41078-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4835.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C3D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C4D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_df3635ec4af82d66241d5e2a32d4c723bb3a02c_00000000_cab_1e939b66

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0c77db7e-6cbf-4403-836a-dbcef7c6f947
Report Status: 268435456
Hashed bucket:2017-10-05 10:39 PM    Windows Error Reporting    Fault bucket 0x133_DPC_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 7f4deacd-41f9-4863-a6fc-3add16d99a14

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff80358a6e348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100517-30578-01.dmp
\\?\C:\Windows\Temp\WER-174531-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E85.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6EE3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F03.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_487ba615fe9971909626aced82c91a2ff6b377c5_00000000_cab_29980c4d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 52076946-c847-4cd6-8141-628751fb2566
Report Status: 268435456
Hashed bucket:

Code:

2017-10-05 11:16 PM    Windows Error Reporting    Fault bucket AV_rtwlane!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: f3cdfbcf-bd7a-45ee-a408-e005a700dc8f

Problem signature:
P1: d1
P2: 10
P3: 2
P4: 0
P5: fffff805ca02275e
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100517-33187-01.dmp
\\?\C:\Windows\Temp\WER-146156-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE2C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF36.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF56.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_f4134df1c7ff568fb222291032b47ae705d3a_00000000_cab_214cd52e

Analysis symbol: 
Rechecking for solution: 0
Report Id: aa6bc32c-2b13-486f-bbe3-fcbb129be79d
Report Status: 268435456
Hashed bucket:2017-09-17 2:07 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_IMAGE_igdkmd64.sys_GEN9KBL_0_DISPLAY, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 6af527e8-75df-4134-91a2-2c0b458fbde3

Problem signature:
P1: 117
P2: ffff958598df54a0
P3: fffff80823353010
P4: 0
P5: 458
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170916-2206.dmp
\\?\C:\Windows\Temp\WER-527234-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B84.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6BA3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6BB4.tmp.txt
\\?\C:\Windows\Temp\WERA736.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_ed69fde3fb5254a5658d77124aefede2de401b_00000000_cab_0828a949

Analysis symbol: 
Rechecking for solution: 0
Report Id: 71cc5866-e0b3-48f3-92fe-93044a136531
Report Status: 268435456
Hashed bucket:

Code:

2017-10-05 10:35 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff80358a6e348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100517-30578-01.dmp
\\?\C:\Windows\Temp\WER-174531-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E85.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6EE3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F03.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_487ba615fe9971909626aced82c91a2ff6b377c5_00000000_cab_03886f31

Analysis symbol: 
Rechecking for solution: 0
Report Id: 52076946-c847-4cd6-8141-628751fb2566
Report Status: 4
Hashed bucket:2017-10-11 4:16 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 0
P3: 501
P4: 500
P5: fffff803a8476348
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\101117-37734-01.dmp
\\?\C:\Windows\Temp\WER-41078-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4835.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C3D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C4D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_df3635ec4af82d66241d5e2a32d4c723bb3a02c_00000000_cab_038f4caa

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0c77db7e-6cbf-4403-836a-dbcef7c6f947
Report Status: 4
Hashed bucket:
2017-10-05 11:15 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: d1
P2: 10
P3: 2
P4: 0
P5: fffff805ca02275e
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\100517-33187-01.dmp
\\?\C:\Windows\Temp\WER-146156-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE2C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF36.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF56.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_f4134df1c7ff568fb222291032b47ae705d3a_00000000_cab_039bdf74

Analysis symbol: 
Rechecking for solution: 0
Report Id: aa6bc32c-2b13-486f-bbe3-fcbb129be79d
Report Status: 4
Hashed bucket:

Thank you both BSODHunter and zbook for your replies. I have uploaded a new zip file of my computer, but think that I have rolled back the offending driver. Is there anything else I should do to prevent further BSODs? You guys are awesome! :)

The current driver that was just installed was:
rtwlane.sys (2023.40.801.2016, 5.85 MB (6,131,720 bytes), 2017-07-14 8:08 AM)
The driver that was installed that had produced the last bsod mini dump was:
rtwlane.sys (2023.55.415.2017, 6.50 MB (6,813,664 bytes), 2017-07-14 8:08 AM)
So you now have the rolled back driver dated 2016.


New problems have been identified.
Please upgrade/reinstall the bios firmware.


The event log displayed these problems:

Code:

Event[14675]:  Log Name: System  Source: ACPI  Date: 2017-10-11T13:15:07.812  Event ID: 13  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-A9CBLI4  Description: : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

Code:

Event[14656]:  Log Name: System  Source: ACPI  Date: 2017-10-11T02:33:48.098  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-A9CBLI4  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.Event[14657]:  Log Name: System  Source: ACPI  Date: 2017-10-11T02:33:50.144  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-A9CBLI4  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.Event[14658]:  Log Name: System  Source: ACPI  Date: 2017-10-11T02:33:50.910  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-A9CBLI4  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.Event[14659]:  Log Name: System  Source: ACPI  Date: 2017-10-11T02:33:51.020  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-A9CBLI4  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.Event[14660]:  Log Name: System  Source: ACPI  Date: 2017-10-11T02:33:51.598  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-A9CBLI4  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.

Code:

Event[14611]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-10-11T02:32:36.115  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-A9CBLI4  Description: A corrected hardware error has occurred.Component: PCI Express Root PortError Source: Advanced Error Reporting (PCI Express)Bus:Device:Function: 0x0:0x1C:0x5Vendor ID:Device ID: 0x8086:0x9D15Class Code: 0x30400The details view of this entry contains further information.Event[14612]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2017-10-11T02:32:36.115  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-A9CBLI4  Description: A corrected hardware error has occurred.Component: PCI Express Root PortError Source: Advanced Error Reporting (PCI Express)Bus:Device:Function: 0x0:0x1C:0x5Vendor ID:Device ID: 0x8086:0x9D15Class Code: 0x30400The details view of this entry contains further information.