New PC win 10 constant crashes in-game

[AndiElse96]

I build a PC last weekend, and i keep getting bsod... Its not always the same but quite often MEMORY_MANAGEMENT.

I checked the cables, exchanged the RAM, repositioned the RAM, removed harddrives... i have no idea what to do. It only happens after a few minutes into a game of XCOM, CSGO, Dishonerd, so i assume it has something to do with the graphics card... I added the Minidumps in the post.

My Sytem:
CPU: i5 6600k @3,50 GHz
GPU: Nvidea GTX 970 4 GB
PSU: Be quit! 630W
Storage: Samsung 250 GB SSD
Toshiba 3GB HDD
RAM: Kingston 2x8GB

Minidump-files: http://www57.zippyshare.com/v/juHRdeN2/file.html

 

[turkey3_scratch]

Run a memory test. This can be done from the Windows control panel, then administrative tools, and memory test.

 

[AndiElse96]

you mean MEMTEST? memtest says my RAm is okay after a few hours

 

[turkey3_scratch]

It could possibly be the power supply. I would try replacing that, PSU problems can cause BSODs. That PSU is okay.

 

[13thmonkey]

does it do it with each of the single sticks of memory on their own. Because a few hours is not long for a memory test.

 

[AndiElse96]

i just bought everthing last week, would suck if it is broken... so you think a different PSU could work? why does it mostly crash when i play a game?

i just got 2 BSOD with the message: SYSTEM_SERVICE_EXCEPTION, i think it was because i was installing something

 

[turkey3_scratch]

When you play a game there is higher load on the PSU.

 

[AndiElse96]

but 630W should be enough, or?

 

[AndiElse96]

is there a way to test it?

 

[turkey3_scratch]

It's not about watts, it's about the quality of the PSU. Voltage regulation for instance. The power supply is supposed to send out 12V of electricity on the 12V rail, and sometimes lower quality power supplies have bad voltage regulation and don't deliver a close enough voltage.

 

[13thmonkey]

picking out the PSU as being the faulty component with no actual evidence or discounting every single other component is an exercise in futility and generating shipping charges for RMAs. Get back to the basics, test each stick of ram individually for a LONG time, I'd be wanting to see 8+ hours on each stick. then we start talking about what else might be wrong.

 

[13thmonkey]

It's not about watts, it's about the quality of the PSU. Voltage regulation for instance. The power supply is supposed to send out 12V of electricity on the 12V rail, and sometimes lower quality power supplies have bad voltage regulation and don't deliver a close enough voltage.

Be Quiet are ok.

 

[13thmonkey]

is there a way to test it?

No, only to test that it turns on, and you know that. The only test is to try another one, that's last resort.

 

[13thmonkey]

The dumps strongly hint at a memory error (use whocrashed to have a look).
Have you installed the mobo drivers?

 

[AndiElse96]

oh, i forgot to mention my mainboard is ASRck Z170M Pro4S. Could that cause problems?

 

[turkey3_scratch]

Probably not. I think we can cross out the graphics card since the BSOD says "memory management" unless it is referring to vRAM. I recommend you post your memory dumps on the Windows forums where experts read them.

 

[AndiElse96]

WhoCrashed says to all Crahses most likly caused by a faulty driver... is there a way to easily deinstall and reinstall all drinvers?

 

[turkey3_scratch]

If you installed the 970 driver from Nvidia's website, I don't see how it could be faulty IMO.

 

[13thmonkey]

did you install the mobo drivers? or are we going to just randomly suggest components?

 

[johnbl]

looked at a few more of the bugchecks and they show single bit memory corruptions.
files are being corrupted when they are loaded into memory.

if the problems don't go away with driver updates, I would be looking at the primary and memory secondary timings and confirm they are correct in BIOS. Then run memtest86 on each stick and confirm all work as expected.
I would also confirm the voltage to the memory is set correctly. (or run it at a slower speed)
PC4-17000, 1.2V, CAS Supported: 9 11 12 13 14 15 16




--
i looked at three of the bugcheck they were all in memory management but related to how data was copied from virtual memory to physical ram. Look for a driver problem. Also, 3 looked like they were modified in the debugger one of the files was the microsoft storage driver. (why i suggested the sfc and dism to repair and malware/virus scan to find cause of modified files)
-----------
update the drivers for the motherboard, then run the dism command below and reboot. Be sure to run a malwarebytes scan
and a virus scan. if you don't find a virus infecting your storage driver then run tests on your drive.
if you get another bugcheck provide a updated memory dump.

-------------------

3 of your microsoft files did not look correct in the debugger,
start cmd.exe as an admin and run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth

run a malwarebytes scan.
------------
new audio driver release on 10/8/2015
update all the drivers for your motherboard. remove the 2011 AsrAppCharger.sys driver.

http://www.asrock.com/mb/Intel/Z170M%20Pro4S/?cat=Download&os=Win1064

old driver installed remove
\SystemRoot\system32\DRIVERS\AsrAppCharger.sys Tue May 10 01:28:46 2011

machine info:
BIOS Version P1.40
BIOS Starting Address Segment f000
BIOS Release Date 08/13/2015
BIOS Version P1.40
BIOS Starting Address Segment f000
BIOS Release Date 08/13/2015

Manufacturer ASRock
Product Z170M Pro4S


Processor Manufacturer Intel(R) Corporation
Processor ID e3060500fffbebbf
Processor Version Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 5000MHz
Current Speed 3500MHz

memory:
Speed 2133MHz
Manufacturer Kingston
Serial Number
Asset Tag Number
Part Number 9905598-009.A00G

 

[AndiElse96]

i ran dism.exe and sfc.exe. both had some errors, here are the logs: http://www78.zippyshare.com/v/IYmSERZd/file.html

malwarebyttes and firewall fpound nothing. In the bios everything is set to auto.

removed AppCharger

 

[13thmonkey]

have you run memtest on each memory stick in turn?