Solved My laptop blue screens while watching YouTube or Twitch

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Welcome to our Community
Wanting to join the rest of our members? Feel free to sign up today.
Sign up
Status
Not open for further replies.

siggtrygg

PCHF Member
PCHF Member
Jul 18, 2017
5
1
23
Hello, I have a ASUS X555L laptop running windows 10. It's been working fine since I got it last year but recently sometimes while watching YouTube videos or Twitch streams, the laptop will freeze. Sometimes it will recover and start working in a few seconds, other times it crashes. When it does I get a WATCHDOG_VIOLATION stop code. I tried looking this part up and the help I got online said it could be caused by outdated drivers, or overheating. I manually went through the my driver list and checked for updates on each one, but the crash still happened. I'm not sure I can rule out overheating, but I highly doubt it cause the crash can occur within even an hour of the laptop staring up. Any ideas on how I could fix this?
 

jmarket

PCHF's Almighty Ruler
PCHF Owner
Support Team
Security Team
Jan 10, 2015
2,242
505
PCHF Bunker
pchelpforum.net
I've analyzed your dump files. I will get @phillpower2 to aid in my search as my symbols seem to be mixed for your files.

You're getting a lot of DPC_WATCHDOG errors. Have you added any new hardware or software recently?
 

phillpower2

You can call me Ad
Administrator
Support Team
Sep 9, 2016
5,669
592
56
Hello folks,

I'm not sure I can rule out overheating, but I highly doubt it cause the crash can occur within even an hour of the laptop staring up.
siggtrygg
Overheating can cause all sorts of weird but definitely not wonderful behavior and believe it or not one of them is problems with drivers and/or hardware malfunctioning due to the same cause.

Looked at your last three dmps siggtrygg and the constant in the three of them is the Realtek PCI-E Wireless LAN NIC NDIS Driver rtwlane.sys, see info here provided courtesy of
John Carrona, note the info that I have highlighted first in blue and then in red, your penultimate crash also mentioned the two drivers in blue so a possible conflict but the other two dmps only point towards the rtwlane.sys driver, ASUS do not provide any Windows 10 64-bit specific drivers for your computer meaning that you should try the Windows 8.1 64-bit version which you can download from Realtek Wireless Lan Driver and Application here

Download and save the driver to your notebooks desktop, create a new restore point, uninstall the present Realtek NIC driver, restart the computer in Safe Mode only (no networking) install the newly saved Realtek NIC drivers, restart the notebook and test.

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff801fc626540

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

OVERLAPPED_MODULE: Address regions for 'mrxsmb20' and 'IntcDAud.sys' overlap

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff801fc2a8fb7 to fffff801fc3d5960

STACK_TEXT:
fffff801`fdd6bd88 fffff801`fc2a8fb7 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff801`fdd6bd90 fffff801`fc2a6c18 : 00000161`6a3802db 00000000`00000000 fffff801`fc212d90 fffff780`00000320 : nt!KeAccumulateTicks+0x407
fffff801`fdd6bdf0 fffff801`fc2144e5 : fffff801`fc25f2e0 fffff801`fc25f2e0 00000000`00000001 00000000`00000000 : nt!KeClockInterruptNotify+0xb8
fffff801`fdd6bf40 fffff801`fc299c26 : fffffe9e`968e12a9 00000000`00000000 ffffcd80`a59e4500 fffff801`fc3d6c37 : hal!HalpTimerClockIpiRoutine+0x15
fffff801`fdd6bf70 fffff801`fc3d6fda : fffff801`fdd641c0 00000161`6a37c2af 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x106
fffff801`fdd6bfb0 fffff801`fc3d7427 : 00000001`ffffff02 fffffff6`00000002 ffff8f8b`00000000 00001f80`002b0252 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`fdd64140 fffff801`fc212cf6 : fffff801`fc63c550 00000000`00000000 fffff801`fc5c2180 fffff801`fc3d7434 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`fdd642d0 fffff80d`bd130918 : fffff801`fdd64518 00000000`00000001 fffff801`fdd64400 fffff80d`bd1cedd7 : hal!KeStallExecutionProcessor+0x146
fffff801`fdd64360 fffff801`fdd64518 : 00000000`00000001 fffff801`fdd64400 fffff80d`bd1cedd7 ffff8f8b`07a00000 : rtwlane+0x30918
fffff801`fdd64368 00000000`00000001 : fffff801`fdd64400 fffff80d`bd1cedd7 ffff8f8b`07a00000 fffff80d`bd29fd1d : 0xfffff801`fdd64518
fffff801`fdd64370 fffff801`fdd64400 : fffff80d`bd1cedd7 ffff8f8b`07a00000 fffff80d`bd29fd1d ffffcd80`a6a3c000 : 0x1
fffff801`fdd64378 fffff80d`bd1cedd7 : ffff8f8b`07a00000 fffff80d`bd29fd1d ffffcd80`a6a3c000 ffff8f8b`07ffdec0 : 0xfffff801`fdd64400
fffff801`fdd64380 ffff8f8b`07a00000 : fffff80d`bd29fd1d ffffcd80`a6a3c000 ffff8f8b`07ffdec0 ffff8f8b`08b93a40 : rtwlane+0xcedd7
fffff801`fdd64388 fffff80d`bd29fd1d : ffffcd80`a6a3c000 ffff8f8b`07ffdec0 ffff8f8b`08b93a40 00000000`00000000 : 0xffff8f8b`07a00000
fffff801`fdd64390 ffffcd80`a6a3c000 : ffff8f8b`07ffdec0 ffff8f8b`08b93a40 00000000`00000000 ffff8f8b`08c00000 : rtwlane+0x19fd1d
fffff801`fdd64398 ffff8f8b`07ffdec0 : ffff8f8b`08b93a40 00000000`00000000 ffff8f8b`08c00000 00000000`00000000 : 0xffffcd80`a6a3c000
fffff801`fdd643a0 ffff8f8b`08b93a40 : 00000000`00000000 ffff8f8b`08c00000 00000000`00000000 ffff8f8b`07a00000 : 0xffff8f8b`07ffdec0
fffff801`fdd643a8 00000000`00000000 : ffff8f8b`08c00000 00000000`00000000 ffff8f8b`07a00000 fffff80d`bd46c2c8 : 0xffff8f8b`08b93a40


STACK_COMMAND: kb

FOLLOWUP_IP:
rtwlane+30918
fffff80d`bd130918 4883eb01 sub rbx,1

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: rtwlane+30918

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: rtwlane

IMAGE_NAME: rtwlane.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 591d043d

FAILURE_BUCKET_ID: X64_0x133_rtwlane+30918

BUCKET_ID: X64_0x133_rtwlane+30918
 

siggtrygg

PCHF Member
PCHF Member
Jul 18, 2017
5
1
23
Ok, I successfully installed the new LAN driver. I will get back to you later if it still acts up. Thanks for the help
 

phillpower2

You can call me Ad
Administrator
Support Team
Sep 9, 2016
5,669
592
56
You are welcome and please do let us know how things go (y)
 

siggtrygg

PCHF Member
PCHF Member
Jul 18, 2017
5
1
23
Hello, things were working for a few days but it seems the problem resurfaced. Here are the recent dump files.
 

Attachments

Malnutrition

Malnurished Mod
Moderator
Security Team
Jul 22, 2016
3,397
552
Sysnative Tool.

1. Download the Sysnative BSOD Dump + System File Collection App - save to Documents folder -
2. Run the app - Double-click on the downloaded EXE file
Output = new folder created in Documents + a zipped version -- SysnativeFileCollectionApp + SysnativeFileCollectionApp.zip

Step 2: MiniToolBox Scan


Please download MINITOOLBOX and run it.

Checkmark following boxes:



Flush DNS
Reset FF proxy Settings
Reset Ie Proxy Settings
Report IE Proxy Settings
Report FF Proxy Settings
List content of Hosts
List IP configuration
List Winsock Entries
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size
List Devices (problems only)



Click Go post the result.

Step 3: HijackThis.




1- Please Click HERE to download HijackThis. -- Unzip to your desktop.
2- Right click run as admin.
3- Click on the Main Menu button if not already there.
4- Select Do a system scan and save a logfile.
5- Copy paste the log here.
 

siggtrygg

PCHF Member
PCHF Member
Jul 18, 2017
5
1
23
Nvm, I think I fixed it. I had installed a program recently (after I fixed the first crashes) that was messing with the registry. Once I uninstalled it I haven't had any problems. Thanks again for the help.
 
  • Like
Reactions: vger
Status
Not open for further replies.