BSOD while watching youtube.

As I am seeing, it is a bloatware caused issue.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {34efa, 2, 1, fffff80003ad7066}

Unable to load image assd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for assd.sys
*** ERROR: Module load completed but symbols could not be loaded for assd.sys
Probably caused by : assd.sys ( assd+2667 )

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

Description here: Driver Reference Table - assd.sys.

Again, another one....

Code:

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


OVERLAPPED_MODULE: Address regions for 'ASMMAP64' and 'WinUsb.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!CmpDereferenceNameControlBlockWithLock+22
fffff800`03d73072 448b06          mov     r8d,dword ptr [rsi]

EXCEPTION_RECORD:  fffff880033af848 -- (.exr 0xfffff880033af848)
ExceptionAddress: fffff80003d73072 (nt!CmpDereferenceNameControlBlockWithLock+0x0000000000000022)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

Description here: Driver Reference Table - ASMMAP64.sys

All those are causing the problems there.

I would suggest you follow the guide Clean Up Factory Bloatware with a special reference to point #13.

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

Have a try.

Good news. :)

Now observe it, see how it works. For any further issues, let us know.

Four crash dumps, four different causes.

Display driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880808df064, 8, fffff880808df064, 5}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys

Could not read faulting driver name
Probably caused by : igdkmd64.sys ( igdkmd64+8904e )

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

I'd suggest you to uninstall the existing display driver, using |MG| Driver Fusion (Driver Sweeper) 1.2.0 Download. Then download it again from Intel Download Center, preferable a release earlier than that of 27th September, that is you using.

File System.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800a623f48, fffff8800a6237a0, fffff8800125d146}

Probably caused by : Ntfs.sys ( Ntfs!NtfsMultipleAsync+26 )

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

1. Update your SSD's Firmware (Skip it, if it is not a SSD)
2. Re-seat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Memory Corruption.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff8800338c518, fffff8800338bd70, fffff80002b4ca7c}

Probably caused by : memory_corruption ( nt!MiRemoveLowestPriorityStandbyPage+1bc )

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

Again, with a different bugcheck

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002a9895e, fffff8800330f758, fffff8800330efb0}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+36e )

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

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Moreover, you should do two more things .....

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

Good! Very good news. Let us know how the computer is performing now.