Csgo randomly shutting down

tomatentros

Prominent
Jul 25, 2017
10
0
510
Got myself a brand new pc. after a week of problems (new chipset drivers) wont work. finaly got that fixed..

the next problem occours.

when i run csgo, it just randomly shuts it self down, back to the windows homescreen.

no errors, nothing..

pc setup
asus z270P
Intel I7 7700k
MSI gtx 1080 8gb
crucial balastix 16gb ddr4 2400mhz
3 screens (1 benq 1 samsung both 24inch and a lg 19inch)
corsair strafe RGB
razer deathadder

allready tried, cl_disablehtmlmotd 1, video setting_memlevel 0, deleted csgo.exe, changed the multicore rendering and verified game integrity

hope you guys can help me... cant even play 5 minutes of deathmatch =\
 

tomatentros

Prominent
Jul 25, 2017
10
0
510
the steam solutions have allready been tried.. dindt work..

have tried player unknown battle ground, but i get a instand BSOD.. (i can post the whocrashed reports) (will try H1Z1 soon)

PSU is a Cooler Master Silent Pro M700
 
Reseat the video card by pulling it out of the PCIE slot then put it back in. This makes sure of good connection. Try with only 1 stick of RAM and swap to the other and test again. Make sure you have the latest 0810 motherboard bios.
https://www.asus.com/us/Motherboards/PRIME-Z270-P/HelpDesk_Download/

Test with just 1 monitor to make sure its not a the windows 10 3 monitor issue.
 

tomatentros

Prominent
Jul 25, 2017
10
0
510
while running prime95 pc showed BSOD this is the whocrashed report:

On Wed 26-7-2017 16:43:25 your computer crashed
crash dump file: C:\Windows\Minidump\072617-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803582F141A, 0xFFFFCF015E7AF920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 26-7-2017 16:43:25 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: 0x3B (0xC0000005, 0xFFFFF803582F141A, 0xFFFFCF015E7AF920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
 
The dump says a windows service crashed which must have been caused by another program. Probably a driver associated to your motherboard chipset. Here is a few thing to try:

CheckSystem Log in Event Viewer for error messages that might identify the device or driver that caused the error.
Try disabling memory caching of the BIOS.
Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer. Memtest64 if they have none. https://www.techpowerup.com/memtest64/
Make sure the latest Service Pack is installed.
Try installing the latest chipset drivers for the Z270. https://downloadcenter.intel.com/product/98089/Intel-Z270-Chipset
 

tomatentros

Prominent
Jul 25, 2017
10
0
510
did a memtest64 test. and this came out:
1151.843: Starting loop 6
1151.890: Stuck Address Test...
1158.547: Random Data Test...
1166.156: Move Data Test...
1168.625: Bitpattern Test...
1276.922: Error at F3FFFC0
1276.953: Error at F3FFFC1
1276.968: Error at F3FFFC2
1276.968: Error at F3FFFC3
1276.968: Error at F3FFFC4
1276.968: Error at F3FFFC5
1276.968: Error at F3FFFC6
1276.984: Error at F3FFFC7
1276.984: Error at F3FFFC8
1276.984: Error at F3FFFC9
1276.984: Error at F3FFFCA
1277.000: Error at F3FFFCB
1277.015: Error at F3FFFCC
1277.015: Error at F3FFFCD
1277.015: Error at F3FFFCE
1277.015: Error at F3FFFCF
1277.015: Error at F3FFFD0
1277.015: Error at F3FFFD1
1277.031: Error at F3FFFD2
1277.031: Error at F3FFFD3
1277.031: Error at F3FFFD4
1277.031: Error at F3FFFD5
1277.031: Error at F3FFFD6
1277.031: Error at F3FFFD7
1277.031: Error at F3FFFD8
1277.031: Error at F3FFFD9
1277.047: Error at F3FFFDA
1277.047: Error at F3FFFDB
1277.047: Error at F3FFFDC
1277.047: Error at F3FFFDD
1277.047: Error at F3FFFDE
1277.047: Error at F3FFFDF
1277.062: Error at F3FFFE0
1277.062: Error at F3FFFE1
1277.062: Error at F3FFFE2
1277.062: Error at F3FFFE3
1277.078: Error at F3FFFE4
1277.078: Error at F3FFFE5
1277.078: Error at F3FFFE6
1277.078: Error at F3FFFE7
1277.078: Error at F3FFFE8
1277.093: Error at F3FFFE9
1277.093: Error at F3FFFEA
1277.093: Error at F3FFFEB
1277.093: Error at F3FFFEC
1277.093: Error at F3FFFED
1277.093: Error at F3FFFEE
1277.093: Error at F3FFFEF
1277.109: Error at F3FFFF0
1277.109: Error at F3FFFF1
1277.109: Error at F3FFFF2
1277.109: Error at F3FFFF3
1277.109: Error at F3FFFF4
1277.125: Error at F3FFFF5
1277.125: Error at F3FFFF6
1277.125: Error at F3FFFF7
1277.140: Error at F3FFFF8
1277.140: Error at F3FFFF9
1277.140: Error at F3FFFFA
1277.156: Error at F3FFFFB
1277.156: Error at F3FFFFC
1277.156: Error at F3FFFFD
1277.156: Error at F3FFFFE
1277.156: Error at F3FFFFF
1374.218: Starting loop 7

first 5 loops nothing happend and so was 7 and 8


tried a new test and this came out:

0.000: Detecting usable memory (16329 MB theoretical max)...
3.219: 7552 MB Test starting on 8 CPUs...
3.219: Allocating memory...
8.032: Memory locking failed (might be reserved by other apps/kernel)
8.516: Test finished with no errors detected
 

tomatentros

Prominent
Jul 25, 2017
10
0
510
could i be a ram module? every time i push it to the max it bluescreens..

On Thu 27-7-2017 17:08:39 your computer crashed
crash dump file: C:\Windows\Minidump\072717-4312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x3F, 0x3034F, 0xF77276ED, 0xF772772D)
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 Thu 27-7-2017 17:08:39 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: 0x1A (0x3F, 0x3034F, 0xF77276ED, 0xF772772D)
Error: MEMORY_MANAGEMENT
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.
 

tomatentros

Prominent
Jul 25, 2017
10
0
510
got the new ram installed..
still got blue screens..

On Sat 29-7-2017 19:44:14 your computer crashed
crash dump file: C:\Windows\Minidump\072917-3671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x18 (0x0, 0xFFFFC581FE2AC920, 0x2, 0xFFFFC581FF14D8FF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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 29-7-2017 19:44:14 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: 0x18 (0x0, 0xFFFFC581FE2AC920, 0x2, 0xFFFFC581FF14D8FF)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Check the RAM again and if still shows errors try a single stick. Then swap to the other stick. You may have a bad DIMM slot. You have to try the second bank if your motherboard allows. If the DIMM's are bad tho your probably going to have to RMA the motherboard.
 

tomatentros

Prominent
Jul 25, 2017
10
0
510
Brought my pc back to the part deliverer for research..

Turns out the cpu was broken... they replaced it and are now testing.

Hoping for good news so we can close this topic =)