BSOD Watching Streaming

MetalRainbow · 18 Nov 2015

First off I'm on a fresh install of windows 10 x64 the latest Nov. build
I was watching some streams on twitchtv just letting it play not doing anything else on the Pc after two hours of that the bsod occurred saying system_service_exception.
Bluescreenviewer stated a bug check code of 0x0000003b (video?). And highlighted the NTFS.sys+11b88 and ntoskrnl.exe+14cfe9 as the cause? I'm not that tech savvy to understand what it means..I went and ran a disk check that passed same with sfc/scannow no problems found. So any help would be appreciated.

Attachment 49189

axe0 · 20 Nov 2015

Hi MetalRainbow,

Please uninstall Avast and use Windows Defender as alternative.
Avast - Uninstall Completely - Windows 7 Help Forums

Code:

*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys

To clear this up

Bluescreenviewer stated a bug check code of 0x0000003b (video?). And highlighted the NTFS.sys+11b88 and ntoskrnl.exe+14cfe9 as the cause?

NTFS.sys is a driver for the file system a.k.a. hard drive, if this driver is causing problems in most cases it means the hard drive is giving problems or something related to the hard drive.
Ntoskrnl.exe is a driver used in the boot process, this driver is extreme rarely the cause as it is usually only flagged because it is the last active. If ntoskrnl.exe is truly the cause you would experience a lot more problems.

The 0x3B means an exception has occured. Normally, a driver stores data in the memory for later use. When a driver is trying to access the data it appears this data is corrupted. The driver cannot use this data because it didn't expect it, the system has noticed it and called a bugcheck (bluescreen) to prevent data loss. The driver cannot use the data, because what would have happened could cause many problems, but the driver would still have used it.
Note: it could mean the memory is the cause or the 1st driver has stored the data in the wrong memory address.

This is the case I see a lot, but it is usually with a driver and memory, not with the file system.

Let me know how it goes :)