Crashes and BSODs after playing games for 30 minutes.

[CloudPhoenix]

After running a video game (Overwatch or Dark Souls 3) for 30-45 minutes, the game either crashes (Dark Souls 3 has stopped working, Overwatch has crashed in the graphics driver, etc.) or causes a BSOD. My graphics card is GTX 1060 and I should be able to play these games without any problems. I've tried running the games with lower settings. Weirdly enough, I can play another game (League of Legends, much less graphics intensive though) without any problems. I've tried formatting my PC and playing the games with nothing installed expect the drivers, to no avail. I've tried reinstalling the graphics drivers for a second time after the format just to be sure as I'm out of ideas. I get a lot of different BSOD messages. The module is usually ntoskrnl.exe, nvlddmkm.sys or dxgmms2.sys but I've got other stuff as well. Neither the GPU nor the CPU are overheating. I used to be able to play Overwatch without any problems a few months ago. (Which is why I first thought this is caused by overheating due to summer) I used FurMark to stress test the GPU and it didn't trigger anything even after I left it running for 50 minutes. I'd really appreciate any insight on these issues. Here are my WhoCrashed reports:

On Mon 17/07/2017 16:18:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071717-4343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xA (0xFFFFD78080C98642, 0x2, 0x0, 0xFFFFF801768EB823)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 17/07/2017 16:18:05 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFD78080C98642, 0x2, 0x0, 0xFFFFF801768EB823)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 15/07/2017 19:17:38 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-4468-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x670B8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8031BE570B8, 0xFFFF96002FBCF9A8, 0xFFFF96002FBCF1F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sat 15/07/2017 18:51:16 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x154 (0xFFFF8C01B76A6000, 0xFFFFD181729286E0, 0x1, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 12/07/2017 23:08:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071217-5484-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2B3E4E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8084BE03E4E, 0xFFFFCF80EA6B4D88, 0xFFFFCF80EA6B45D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2386fda73b467ac8\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 384.76
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 384.76
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 384.76 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




And these are my BlueScreenViewer reports. (This one shows more dumps for some reason)

071717-4343-01.dmp 17/07/2017 16:18:05 IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffd780`80c98642 00000000`00000002 00000000`00000000 fffff801`768eb823 ntoskrnl.exe ntoskrnl.exe+16c4c0 x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071717-4343-01.dmp 4 15 15063 585,316 17/07/2017 16:18:31
071517-4468-01.dmp 15/07/2017 19:17:38 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff803`1be570b8 ffff9600`2fbcf9a8 ffff9600`2fbcf1f0 dxgmms2.sys dxgmms2.sys+655ed x64 dxgmms2.sys+670b8 C:\WINDOWS\Minidump\071517-4468-01.dmp 4 15 15063 680,564 15/07/2017 19:18:03
071517-4765-01.dmp 15/07/2017 18:51:16 0x00000154 ffff8c01`b76a6000 ffffd181`729286e0 00000000`00000001 00000000`00000000 hal.dll hal.dll+253d x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071517-4765-01.dmp 4 15 15063 649,916 15/07/2017 18:51:43
071217-5484-01.dmp 12/07/2017 23:08:37 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff808`4be03e4e ffffcf80`ea6b4d88 ffffcf80`ea6b45d0 nvlddmkm.sys nvlddmkm.sys+2eef1b x64 nvlddmkm.sys+2b3e4e C:\WINDOWS\Minidump\071217-5484-01.dmp 4 15 15063 680,668 12/07/2017 23:09:13
071017-2625-01.dmp 10/07/2017 23:20:11 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00002000 fffff80c`cad99154 00000000`00000000 00000000`54435349 ISCTD64.sys ISCTD64.sys+9154 x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\071017-2625-01.dmp 4 15 15063 431,404 10/07/2017 23:23:00
070917-4734-01.dmp 09/07/2017 23:22:04 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffd881`469851a0 00000000`00000000 fffff808`4daeb548 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+16c3f0 x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\070917-4734-01.dmp 4 15 15063 686,060 09/07/2017 23:22:31
070917-4546-01.dmp 09/07/2017 23:12:41 CRITICAL_PROCESS_DIED 0x000000ef ffff8505`582e47c0 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+16c3f0 x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\070917-4546-01.dmp 4 15 15063 510,844 09/07/2017 23:13:11
070717-4390-01.dmp 07/07/2017 21:59:35 MEMORY_MANAGEMENT 0x0000001a 00000000`00061941 fffff67b`00962000 00000000`00000009 ffffe581`9d337fc0 hal.dll hal.dll+253d x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\070717-4390-01.dmp 4 15 15063 572,220 07/07/2017 22:00:02
062617-5859-01.dmp 26/06/2017 01:37:26 DRIVER_POWER_STATE_FAILURE 0x1000009f 00000000`00000004 00000000`0000012c ffffb207`71444040 fffff801`bb454910 ntoskrnl.exe ntoskrnl.exe+171226 x64 ntoskrnl.exe+171226 C:\WINDOWS\Minidump\062617-5859-01.dmp 4 15 15063 922,852 26/06/2017 01:37:57

 

[Neur0nauT]

Based on the reports you've posted, it looks like there may be a memory leak somewhere. This could be down to faulty system RAM, or overheating on the VRM of your Graphics card. Have you noticed any graphical artefacts during play? Flickering or suchlike? That's a sign of overheating on the graphics card. Unfortunately there is no way to monitor the VRM temps with software. If you're getting artefacts....be prepared to RMA the card.

So next step would be to test your RAM modules using Memtest 86

This will take a while, so best run it overnight, but will rule out possibly faulty RAM or not. If RAM is all good, then consider a full reformat and start your system fresh.

 

[LukeFatwalker]

It's a Memory issue, run a memtest. If the memory fails and you need to install a new batch, be sure to back up your computer first with either a disk imager (i.e. Macrium Reflect) or a snapshot tool (RollBack Rx)

 

[CloudPhoenix]

Based on the reports you've posted, it looks like there may be a memory leak somewhere. This could be down to faulty system RAM, or overheating on the VRM of your Graphics card. Have you noticed any graphical artefacts during play? Flickering or suchlike? That's a sign of overheating on the graphics card. Unfortunately there is no way to monitor the VRM temps with software. If you're getting artefacts....be prepared to RMA the card.

So next step would be to test your RAM modules using Memtest 86

This will take a while, so best run it overnight, but will rule out possibly faulty RAM or not. If RAM is all good, then consider a full reformat and start your system fresh.

Hi, thanks for the reply. I haven't noticed any artifacts, however one time the game crashed and my wallpaper flickered between a solid black color and my original wallpaper a few times and my taskbar disappeared. (I had to restart my PC) This only happened once though. I'll give the memory test a try then. Thank you.

 

[CloudPhoenix]

Based on the reports you've posted, it looks like there may be a memory leak somewhere. This could be down to faulty system RAM, or overheating on the VRM of your Graphics card. Have you noticed any graphical artefacts during play? Flickering or suchlike? That's a sign of overheating on the graphics card. Unfortunately there is no way to monitor the VRM temps with software. If you're getting artefacts....be prepared to RMA the card.

So next step would be to test your RAM modules using Memtest 86

This will take a while, so best run it overnight, but will rule out possibly faulty RAM or not. If RAM is all good, then consider a full reformat and start your system fresh.

Okay, so I've ran memtest86 and it resulted in a sizable amount of errors. I removed one of the RAM sticks and when I powered on the PC, it didn't boot up and alerted me with 3 long beeps. I figured that this was the faulty RAM stick and switched it with the other one. The PC booted up fine however I'm still getting crashes and BSODs. I've just gotten a MEMORY_MANAGEMENT BSOD right now. Could both of my RAM sticks be faulty? I also forgot to mention that BSODs happen more frequently when I use Chrome with a video game running in the background. Also, Chrome crashes and acts weird when a video game is also running. Sometimes I hear a loud buzzing sound from my speakers just before a BSOD.

I don't know if the following is related, but now I remember that about two years ago my RAM was acting up in some way and I tried running a single stick and the same thing happened. (3 beeps, switched to the other stick, etc.) I had 2x 4gb at that time which I upgraded to the 2x 8gb that I have now.

 

[CloudPhoenix]

MERGED QUESTION
Question from CloudPhoenix : "Crashes and BSODs while playing games. Faulty RAM? (Tried memtest86)"

So for the past couple of months I've been having a problem in which playing a video game for 30-45 minutes either causes the game to crash (game.exe has stopped working) or a straight-up BSOD. I was told that this is most likely a memory problem so I tried using memtest86 to test my RAM. It resulted in thousands of errors. I removed one of the RAM sticks and when I powered on the PC, it didn't boot up and alerted me with 3 long beeps. I figured that this was the faulty RAM stick and switched it with the other one. The PC booted up fine however I'm still getting crashes and BSODs. I've got a MEMORY_MANAGEMENT BSOD just now. Could both of my RAM sticks be faulty? I ran another memtest86 with a single stick. This time, only 1 of the 8 sectors returned errors. (Just 8 errors, compared to the thousands of errors I've gotten with 2 sticks)

I've noticed that BSODs happen more frequently when I use Chrome with a video game running in the background. Also, Chrome crashes and acts weird when a video game is also running. Sometimes I hear a loud buzzing sound from my speakers just before a BSOD.

I don't know if the following is related, but now I remember that about two years ago my RAM was acting up in some way and I tried running a single stick and the same thing happened. (3 beeps, switched to the other stick, etc.) I had 2x 4gb at that time which I upgraded to the 2x 8gb that I have now.

Does the low number of errors on the remaining stick mean it's the culprit of these issues? I don't know about this, but could something be "corrupting" my RAM sticks in any way? I find it somewhat unlikely that so many of my PC's RAM sticks have malfunctioned.

memory management isn't just ram, it can be caused by drivers or hdd perhaps

1. Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

2. Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone else with right software to read them will help you fix it

Here are the WhoCrashed reports. Also my PC is already creating minidumps. I have uploaded the contents of the minidump folder here: https://www.dropbox.com/sh/7g75n9zr96k7pso/AACyn6v9szz_9GToBD4a8aUpa?dl=0

On Wed 19/07/2017 19:20:31 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071917-4156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1C7 (0x0, 0xFFFFC689047B5000, 0x7F257B6C, 0x7FB98DAA)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 19/07/2017 19:20:31 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1C7 (0x0, 0xFFFFC689047B5000, 0x7F257B6C, 0x7FB98DAA)
Error: CUSTOM_ERROR
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 19/07/2017 17:59:11 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071917-4593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x41201, 0xFFFFBF0000A06120, 0x100000024D1E867, 0xFFFF818B6B2C5110)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 18/07/2017 15:02:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071817-3875-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF803B9AF229E)
Bugcheck code: 0xD1 (0xFFFF958C5771F1AC, 0x2, 0x0, 0xFFFFF803B9AF229E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 18/07/2017 13:44:52 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071817-6281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x50 (0xFFFFC4853CBDD3D1, 0x0, 0xFFFFF803D770E750, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

And these are my BlueScreenViewer reports. (This one shows more dumps for some reason)

071917-4156-01.dmp 19/07/2017 19:20:31 0x000001c7 00000000`00000000 ffffc689`047b5000 00000000`7f257b6c 00000000`7fb98daa ntoskrnl.exe ntoskrnl.exe+16c4c0 x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071917-4156-01.dmp 4 15 15063 576,948 19/07/2017 19:20:55
071917-4593-01.dmp 19/07/2017 17:59:11 MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 ffffbf00`00a06120 01000000`24d1e867 ffff818b`6b2c5110 ntoskrnl.exe ntoskrnl.exe+16c4c0 x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071917-4593-01.dmp 4 15 15063 525,900 19/07/2017 17:59:39
071817-3875-01.dmp 18/07/2017 15:02:54 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 ffff958c`5771f1ac 00000000`00000002 00000000`00000000 fffff803`b9af229e dxgmms2.sys dxgmms2.sys+2229e x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071817-3875-01.dmp 4 15 15063 680,204 18/07/2017 15:03:19
071817-6281-01.dmp 18/07/2017 13:44:52 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffc485`3cbdd3d1 00000000`00000000 fffff803`d770e750 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+16c4c0 x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071817-6281-01.dmp 4 15 15063 563,356 18/07/2017 13:45:20
071717-4343-01.dmp 17/07/2017 16:18:05 IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffd780`80c98642 00000000`00000002 00000000`00000000 fffff801`768eb823 ntoskrnl.exe ntoskrnl.exe+16c4c0 x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071717-4343-01.dmp 4 15 15063 585,316 17/07/2017 16:18:31
071517-4468-01.dmp 15/07/2017 19:17:38 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff803`1be570b8 ffff9600`2fbcf9a8 ffff9600`2fbcf1f0 dxgmms2.sys dxgmms2.sys+655ed x64 dxgmms2.sys+670b8 C:\WINDOWS\Minidump\071517-4468-01.dmp 4 15 15063 680,564 15/07/2017 19:18:03
071517-4765-01.dmp 15/07/2017 18:51:16 0x00000154 ffff8c01`b76a6000 ffffd181`729286e0 00000000`00000001 00000000`00000000 hal.dll hal.dll+253d x64 ntoskrnl.exe+16c4c0 C:\WINDOWS\Minidump\071517-4765-01.dmp 4 15 15063 649,916 15/07/2017 18:51:43
071217-5484-01.dmp 12/07/2017 23:08:37 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff808`4be03e4e ffffcf80`ea6b4d88 ffffcf80`ea6b45d0 nvlddmkm.sys nvlddmkm.sys+2eef1b x64 nvlddmkm.sys+2b3e4e C:\WINDOWS\Minidump\071217-5484-01.dmp 4 15 15063 680,668 12/07/2017 23:09:13
071017-2625-01.dmp 10/07/2017 23:20:11 DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00002000 fffff80c`cad99154 00000000`00000000 00000000`54435349 ISCTD64.sys ISCTD64.sys+9154 x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\071017-2625-01.dmp 4 15 15063 431,404 10/07/2017 23:23:00
070917-4734-01.dmp 09/07/2017 23:22:04 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffd881`469851a0 00000000`00000000 fffff808`4daeb548 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+16c3f0 x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\070917-4734-01.dmp 4 15 15063 686,060 09/07/2017 23:22:31
070917-4546-01.dmp 09/07/2017 23:12:41 CRITICAL_PROCESS_DIED 0x000000ef ffff8505`582e47c0 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+16c3f0 x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\070917-4546-01.dmp 4 15 15063 510,844 09/07/2017 23:13:11
070717-4390-01.dmp 07/07/2017 21:59:35 MEMORY_MANAGEMENT 0x0000001a 00000000`00061941 fffff67b`00962000 00000000`00000009 ffffe581`9d337fc0 hal.dll hal.dll+253d x64 ntoskrnl.exe+16c3f0 C:\WINDOWS\Minidump\070717-4390-01.dmp 4 15 15063 572,220 07/07/2017 22:00:02
062617-5859-01.dmp 26/06/2017 01:37:26 DRIVER_POWER_STATE_FAILURE 0x1000009f 00000000`00000004 00000000`0000012c ffffb207`71444040 fffff801`bb454910 ntoskrnl.exe ntoskrnl.exe+171226 x64 ntoskrnl.exe+171226 C:\WINDOWS\Minidump\062617-5859-01.dmp 4 15 15063 922,852 26/06/2017 01:37:57

One of those errors is a clue, the IRQ error blaming Direct X.

and blue screen view shows: nvlddmkm.sys which is an even bigger clue and answers a question I was going to ask next (what GPU do you have).

Do you have latest Nvidia drivers? If so, they might be cause as they aren't the best version released so far.

try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html
If you don't have the latest drivers, give them a go... if you do already, run ddu and instead of installing them again, run windows update and use the windows drivers.

Memory management can be caused by drivers, its not automatically RAM. Lets see if fixing GPU drivers is all you need. Otherwise, do step 2 or since you use BSV, just go to c/windows/minidump and upload the ones you already have...

One of those errors is a clue, the IRQ error blaming Direct X.

and blue screen view shows: nvlddmkm.sys which is an even bigger clue and answers a question I was going to ask next (what GPU do you have).

Do you have latest Nvidia drivers? If so, they might be cause as they aren't the best version released so far.

try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html
If you don't have the latest drivers, give them a go... if you do already, run ddu and instead of installing them again, run windows update and use the windows drivers.

Memory management can be caused by drivers, its not automatically RAM. Lets see if fixing GPU drivers is all you need. Otherwise, do step 2 or since you use BSV, just go to c/windows/minidump and upload the ones you already have...

Sorry I forgot to mention that I've already tried reinstalling graphics drivers twice with DDU (and formatted the PC from scratch too). My GPU is GTX1060. I've tried running the games with lower settings. I used FurMark to stress test the GPU and it didn't trigger anything even after I left it running for 50 minutes. Also neither the CPU nor the GPU are overheating. I had created a previous thread in which I mentioned all this and I was told by two users that this is most likely a RAM issue and that I should test it out using memtest86. I have uploaded the contents of my minidump folder here: https://www.dropbox.com/sh/7g75n9zr96k7pso/AACyn6v9szz_9GToBD4a8aUpa?dl=0

 

[Neur0nauT]

Have you tried using the RAM in the alternate RAM slots, i.e. slot 2 & 4 if you have them? Just to rule out that it is not a fault on the motherboards RAM slots. Also, did you test each RAM module individually with Memtest?

The reason you probably notice the BSODs during Chrome use is because it utilises such a big chunk of RAM with multiple extensions and pages open, and with a game running also... they are both probably fighting for memory usage.

I think it is safe to say you can narrow it down to either faulty RAM stick(s) or else faulty RAM slots/Motherboard.

You mentioned getting similar issues with previous RAM? If this is on the the same motherboard, then it could be killing RAM modules on you.

If you get similar results testing on all 4 slots with different RAM sticks, then the motherboard's Northbridge Memory Controller might at fault. If you touch the Northbridge heatsink after a time, and it is very hot, this could indicate an issue. You can locate the NB heatsink by referring to your mobo manual. If it's overheating, it might need more Thermal paste due to it drying up. This could be what is killing your RAM. This is also true if you are running overclocks on your RAM.

It is more likely to be faulty RAM modules, but just worth baring in mind if you've already replaced RAM on this motherboard due to failure in the past.

 

[CloudPhoenix]

Have you tried using the RAM in the alternate RAM slots, i.e. slot 2 & 4 if you have them? Just to rule out that it is not a fault on the motherboards RAM slots. Also, did you test each RAM module individually with Memtest?

The reason you probably notice the BSODs during Chrome use is because it utilises such a big chunk of RAM with multiple extensions and pages open, and with a game running also... they are both probably fighting for memory usage.

I think it is safe to say you can narrow it down to either faulty RAM stick(s) or else faulty RAM slots/Motherboard.

You mentioned getting similar issues with previous RAM? If this is on the the same motherboard, then it could be killing RAM modules on you.

If you get similar results testing on all 4 slots with different RAM sticks, then the motherboard's Northbridge Memory Controller might at fault. If you touch the Northbridge heatsink after a time, and it is very hot, this could indicate an issue. You can locate the NB heatsink by referring to your mobo manual. If it's overheating, it might need more Thermal paste due to it drying up. This could be what is killing your RAM. This is also true if you are running overclocks on your RAM.

It is more likely to be faulty RAM modules, but just worth baring in mind if you've already replaced RAM on this motherboard due to failure in the past.

Yes I have 4 RAM slots, I'll give different slots a try then.

I have tried testing both sticks both at once with Memtest and then a single stick. (The single stick only returned 8 errors) I can't test the other stick as the display doesn't even power on when it's the only one attached.

Yes, I had previous issues with two other RAM sticks on the same motherboard. I'll definitely check out the Northbridge heatsink as you said.

Thanks!