windows 10 random blue screening

[red98talon]

I've been having some crazy issues since i upgraded my pc and upgraded to windows 10. i keep getting bsod while gaming and watching youtube videos. i've tested ram with memtest, tested cpu with prime95, stress tested the video card. bought new power supply and new hard drive. ssd's have the newest firmware and all drivers have been updated. bios was updated also. the bsod i have been getting are irql not less or equal, memory management, and dpc watchdog violation. i've pretty much ruled out the hardware but cannot figure out why i am getting these blue screens.

here is one of the dump files https://drive.google.com/file/d/0BxdWot9jFcvbdlJoNEJ5OElRRG8/view

pc specs
i7 7700k
gtx 1070
16 gigs corsair vengeance
asus strix z270H

here is a whocrashed summary

On Tue 11/7/2017 8:10:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\110717-4578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF801D73A78FC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 11/7/2017 8:10:34 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!RtlAnsiStringToUnicodeString+0xF5)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF801D73A78FC)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: ntdll.sys .
Google query: ntdll.sys IRQL_NOT_LESS_OR_EQUAL

this is the first time it has shown a driver which was ntdll.sys. i searched google but only fix seems to be reinstall video drvers which i have done, but did not fix the issue.

 

[The Paladin]

I looked at your dump file and an important thing should be doine to figure out your problem

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
[/b]Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80074410370, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

you have to run the trace command -k and it should lead you closer to your issue, I lean towards either an older motherboard driver or a video card driver, was this a windows 10 clean install or a windows 10 upgrade from window 7 /8/8.1 ?
ref: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation

 

[red98talon]

I looked at your dump file and an important thing should be doine to figure out your problem

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
[/b]Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80074410370, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

you have to run the trace command -k and it should lead you closer to your issue, I lean towards either an older motherboard driver or a video card driver, was this a windows 10 clean install or a windows 10 upgrade from window 7 /8/8.1 ?
ref: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation

this was a clean install by usb from microsoft. i have the newest drivers from asus website and invidias website. i have no idea how to run a stack trace. this is the first time i've heard of it. how would i run this?

 

[Paul NZ]

This file TslGame.exe may have something to do with it. According to Google it's something to do with Steam

It may belong to PUBg

 

[red98talon]

This file TslGame.exe may have something to do with it. According to Google it's something to do with Steam

It may belong to PUBg

yea tsigame.exe is the main application for pubg. this happens mostly when i play pubg but also happens during youtube videos.

 

[Paul NZ]

Thats probably the main cause then . Whoever made it, tell them what the stop error is. And ask them how to fix it

 

[red98talon]

Thats probably the main cause then . Whoever made it, tell them what the stop error is. And ask them how to fix it

It's not that because it also does it when I'm watching a YouTube video. It also did it when I was on the loading screen off league of legends. The only time it doesnt do it is when I'm idle on the desktop

 

[red98talon]

bump. anyone have any other ideas?