Frequent BSOD, new computer

Hello Eternaltheft.

Your crash dumps are not showing any finite probable cause.

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.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also Upload a snapshot Using Speccy.

• Download and install Speccy.
• File> Save snapshot.
• Save it on desktop.
• Zip it and upload it following following Screenshots and Files - Upload and Post in Seven Forums .

_____________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8801c670000, 0, fffff80003095bbb, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!GreGetDIBitsInternal+d6 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8801c670000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003095bbb, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c7100
GetUlongFromAddress: unable to read from fffff800032c71c0
 fffff8801c670000 Nonpaged pool

FAULTING_IP: 
nt!ExAcquireResourceSharedLite+110
fffff800`03095bbb 498b03          mov     rax,qword ptr [r11]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8801e16c670 -- (.trap 0xfffff8801e16c670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=02121c0c06129093 rbx=0000000000000000 rcx=fffff880121f8790
rdx=fffff880121f87a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003095bbb rsp=fffff8801e16c800 rbp=0000000000000000
 r8=fffff880121f8790  r9=0000000000000000 r10=0000000000000001
r11=fffff8801c670000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!ExAcquireResourceSharedLite+0x110:
fffff800`03095bbb 498b03          mov     rax,qword ptr [r11] ds:fffff880`1c670000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000310dbe0 to fffff8000308fb80

STACK_TEXT:  
fffff880`1e16c508 fffff800`0310dbe0 : 00000000`00000050 fffff880`1c670000 00000000`00000000 fffff880`1e16c670 : nt!KeBugCheckEx
fffff880`1e16c510 fffff800`0308dcae : 00000000`00000000 fffff880`1c670000 fffff880`1e16c800 fffffa80`10c64f90 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`1e16c670 fffff800`03095bbb : 00000000`00000a7c 00000000`00000000 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x16e
fffff880`1e16c800 fffff800`03098b13 : 00000000`00000000 fffffa80`129c98c0 00000000`00000000 fffff880`1e16c938 : nt!ExAcquireResourceSharedLite+0x110
fffff880`1e16c870 fffff960`0014c536 : fffff880`1e16c938 00000000`00000004 fffffa80`112d3b70 fffff800`03333244 : nt!ExEnterPriorityRegionAndAcquireResourceShared+0x23
fffff880`1e16c8a0 fffff960`001628ed : 00000000`00000100 00000000`78051748 00000000`00000000 fffffa80`00000040 : win32k!GreGetDIBitsInternal+0xd6
fffff880`1e16c990 fffff800`0308ee13 : 00000000`6f0114ed 00000000`78051748 00000000`00000000 00000000`00000040 : win32k!NtGdiGetDIBitsInternal+0x3cd
fffff880`1e16ca70 00000000`7560062a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011de38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7560062a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!GreGetDIBitsInternal+d6
fffff960`0014c536 488b1523602500  mov     rdx,qword ptr [win32k!ghsemDynamicModeChange (fffff960`003a2560)]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!GreGetDIBitsInternal+d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51aeb1a7

FAILURE_BUCKET_ID:  X64_0x50_win32k!GreGetDIBitsInternal+d6

BUCKET_ID:  X64_0x50_win32k!GreGetDIBitsInternal+d6

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

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Let us know the results.
__________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff8800457b360, fffff98003f1ce10, 0}

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

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

Let us know how the computer is running, after a couple of days or at the occurence of the next BSOD, whichever is earlier.

Feedback is necessary, you know :)

Have a look at this thread: BSOD League Of Legends, Memory management error 0X1a

I hope you get something useful there.

He first switched it to integrated only, to make it sure that if there is no trouble with the integrated graphics. When it is sure, he switched back to switchable.