Windows 10: BSOD Randomly when watching youtube or rendering videos

The title is not the only time BSOD's occur. they have occured while gaming, on bootup etc.
Also - I get a random graphical error on certain images and on random parts of my screen. these graphical errors do not occur on every photo or all the time.
I have included the logs and a screen shot of the graphical error. The graphics card has just been replaced and it is having the same problem. the Graphics problem only started happening again after one of my most recent BSOD's.

EDIT: DMP FILES 2 REPLYS BELOW

Attachment 132796Attachment 132797

:)

 

BSOD 0x00000124

I noticed bsod often appear when I watch long video Youtube (watched by Edge) or movie (watched K-Lite codec and Windows Movies & TV) in external drive. May it occur because GPU (temperature, driver, ...)?

 

BSOD when watching a video on youtube

ffffe200`7c7f46f8 fffff80d`a357ee47*** WARNING: Unable to verify timestamp for
rtwlane.sys

*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

rtwlane+0xcee47

fffff80d`a2ab0000 fffff80d`a2abe000 CmBatt CmBatt.sys ***** Invalid (9D2FAD19)

fffff80d`9d4d0000 fffff80d`9d4de000 cmimcext cmimcext.sys ***** Invalid (FF4D5961)

fffff80d`9d5a0000 fffff80d`9d642000 cng cng.sys ***** Invalid (F2E91F26)

fffff80d`9f450000 fffff80d`9f461000 CompositeBus CompositeBus.sys ***** Invalid (A29FEBD9)

fffff80d`9f5d0000 fffff80d`9f5e2000 condrv condrv.sys Wed Jun 25 21:27:43 2031 (73A5288F)

fffff80d`9e7e0000 fffff80d`9e7fb000 crashdmp crashdmp.sys Mon Jun 7 22:16:33 1993 (2C13F681)

fffff80d`9de00000 fffff80d`9de8f000 csc csc.sys Sat Jul 4 16:47:41 2037
(7EFA9C6D)

fffff80d`9deb0000 fffff80d`9dedb000 dfsc dfsc.sys Sat Mar 4 05:04:07 2023 (64031797)

fffff80d`9e730000 fffff80d`9e74e000 disk disk.sys Sat Mar 28 14:37:28 2009
(49CE6E68)

fffff80d`a28a0000 fffff80d`a28af000 dptf_acpi dptf_acpi.sys Fri Oct 23 15:24:17 2015 (562A8961)

fffff80d`a2520

For some reason it seems your system driver are corrupt. As you can see below the dates are wrong! Run DISM, to see if the errors can be corrected.

Fix Windows Update errors by using the DISM or System Update Readiness tool.

https://support.microsoft.com/en-us...-by-using-the-dism-or-system-update-readiness

If the issues persists, a system reset is in order, or simply return it as it may still be under warranty.

Recovery options in Windows 10.

https://support.microsoft.com/en-us/help/12415/windows-10-recovery-options

 

There are no dumps in the zip file you uploaded.

Please make sure your PC is configured for small dump files:

How to Configure Windows 10 to Create Dump Files on BSOD

If you run a hard drive cleanup program like CCleaner, stop until this is resolved or change it's settings to not delete dumps or logs:

Attachment 132801

Also noticed 4 of these in the eventlog.txt file:
Code: Event[1897]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-04-29T10:48:35.945 Event ID: 98 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-P5HTM79 Description: Volume C: (\Device\HarddiskVolume4) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally[/quote] and two of these:
Code: Event[1788]: Log Name: System Source: Volsnap Date: 2017-04-28T18:33:09.547 Event ID: 24 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-P5HTM79 Description: There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C:. As a result of this failure all shadow copies of volume C: are at risk of being deleted.[/quote]

 

Ztruker,the disk full event is due to me accidentally setting one of my SSD's to the save location of a 150+gb render in after effects and it filled up. The CHKDSK i will have to look into and perform. Also - I found these 2 DMP files.

Attachment 132809

 

The 4/28 dump shows a fatal machine check occurred:
Code: WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffc9848cadb028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.[/quote] Code: kd> !errrec ffffc9848cadb028 =============================================================================== Common Platform Error Record @ ffffc9848cadb028 ------------------------------------------------------------------------------- Record Id : 01d2c0440090518a Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 4/29/2017 4:32:10 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffc9848cadb0a8 Section @ ffffc9848cadb180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000506e3 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffc9848cadb0f0 Section @ ffffc9848cadb240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : e3 06 05 00 00 08 10 00 - bf fb fa 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffc9848cadb240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffc9848cadb138 Section @ ffffc9848cadb2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 0 Bank 4) Status : 0xbe00000000800400 Address : 0xfffff800d096bdb2 Misc. : 0xfffff800d096bdb2[/quote] This could be caused by a defective/failing CPU, flaky power supply or possibly a device driver.

The 4/29 dump shows a problem with iaStorA.sys.
Code: fffff800`58e7c018 fffff807`40476928Unable to load image \SystemRoot\System32\Drivers\dump_iaStorA.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dump_iaStorA.sys *** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys dump_iaStorA+0xd6928[/quote] Driver Description: Intel RST (Rapid Storage Technology) driver
Driver Update Site: Intel downloads

Try updating to the latest RST available above:
Attachment 132831

The 4/29 dump also indicated a problem with your Nvidia card or driver:
Code: fffff800`58e7c780 fffff807`42490800Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_274d0ab8ee30c459\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x80800[/quote] You already have the latest driver but you could try this:

Remove and install latest Nvidia drivers:

I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem.