Windows 10: Recurring BSODs when attempting to watch Youtube videos

Hello all,

Over the last few days I have started to encounter a few BSODs, with the error IRQL_NOT_LESS_OR_EQUAL, although this is not the only error.

On the first occasion I paid little attention to the error and any potential causes, assuming it to be a one-off, though it has now happened on consecutive days.

Both yesterday and today, crashes occured whilst watching youtube videos, with audio hanging and producing a single constant tone as the computer then goes to a BSOD with the aforementioned error message. The BSOD states that the computer is sending data and will restart upon reaching 100%, although on every occasion it has remained at this stage for over 10 minutes.

[Here is an Imgur link to a Speccy screenshot of my specs](https://i.imgur.com/x9PRi85.png)

The computer is approximate 14 months old and until this point I have had absolutely no problems.


Between the crash yesterday and today, I uploaded the minidump (which I now no longer have) to OSR online and after briefly looking through the analysis nothing jumped out at me as being an obvious cause, and most of the analysis seems to match the report from the crash this morning. After yesterday's crash I went in to Device Manager and updated any drivers I could, as well as running Nvidia Geforce Experience and updating to the latest graphics driver. I have checked Windows Update to confirm I was running the latest version and I have also run scans on both Windows Defender and Malwarebytes.


[Here is a Dropbox link to the minidump from this morning's crash](https://www.dropbox.com/s/23n9q5mo1haeah9/072418-5859-01.dmp?dl=0)

and here was the analysis when I uploaded it to OSR online:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`fd096000 PsLoadedModuleList = 0xfffff802`fd4501f0
Debug session time: Tue Jul 24 04:31:50.206 2018 (UTC - 4:00)
System Uptime: 0 days 16:45:27.439
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff9b8bd042f6c0, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802fd134148, address which referenced memory

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

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

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffff9b8bd042f6c0

CURRENT_IRQL: 0

FAULTING_IP:
nt!PpmIdleExecuteTransition+68
fffff802`fd134148 48898c24a0000000 mov qword ptr [rsp+0A0h],rcx

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

TRAP_FRAME: ffff9b8bd022f490 -- (.trap 0xffff9b8bd022f490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffc58d22079328
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802fd134148 rsp=ffff9b8bd022f620 rbp=ffffc58d22079010
r8=00000000ffffffff r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na po nc
nt!PpmIdleExecuteTransition+0x68:
fffff802`fd134148 48898c24a0000000 mov qword ptr [rsp+0A0h],rcx ss:0018:ffff9b8b`d022f6c0=ffffc58d22079328
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff802fd23ef69 to fffff802fd22e430

STACK_TEXT:
ffff9b8b`d022f348 fffff802`fd23ef69 : 00000000`0000000a ffff9b8b`d042f6c0 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffff9b8b`d022f350 fffff802`fd23bbe5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9b8b`d022f490 fffff802`fd134148 : ffffc58d`22079328 ffffd800`d6ea8ec8 00000039`9cc98349 00000039`9cc978d8 : nt!KiPageFault+0x425
ffff9b8b`d022f620 fffff802`fd133f55 : 0000017d`92255e90 00000000`00000544 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0x68
ffff9b8b`d022fa00 fffff802`fd231b5c : ffffffff`00000000 ffffd800`d6ea3180 ffffd800`d6eb3200 ffffc58d`28bd0340 : nt!PoIdle+0x345
ffff9b8b`d022fb60 00000000`00000000 : ffff9b8b`d0230000 ffff9b8b`d0229000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PpmIdleExecuteTransition+68
fffff802`fd134148 48898c24a0000000 mov qword ptr [rsp+0A0h],rcx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!PpmIdleExecuteTransition+68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5b48247f

FAILURE_BUCKET_ID: X64_AV_nt!PpmIdleExecuteTransition+68

BUCKET_ID: X64_AV_nt!PpmIdleExecuteTransition+68

Followup: MachineOwner
---------

I've since once more checked in device manager that all drivers were up to date, as well as removing all USB connections except keyboard and mouse, yet I've just had another BSOD this evening, once again whilst watching a Youtube video. [Here's the minidump](https://www.dropbox.com/s/0p9f3nhsnj5np64/072418-5015-01.dmp?dl=0)


A consistent factor in the minidumps seems to be point to image_name ntkrnlmp.exe, which has left me unsure how to proceed as I am aware this is a windows component, I was instead expecting to see a specific driver name so I'm rather confused.


I am keen to hear from you guys what more I need to do to work out what is the cause of this problem and how to fix it.

Thanks in advance.

:)

 

Recurring "DPC_WATCHDOG_VIOLATION" BSoD's only while watching YouTube


Asus Notebook + BSOD while watching youtube can be just this one thing:

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

 

BSOD watching youtube


@zbook

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

 

Random BSOD while watching Youtube video


Was watching a Youtube video when suddenly I got this BSOD called UNEXPECTED_STORE_EXCEPTION

Thanks in advance!