Welcome to Crashland

MGhostX

Reputable
Jan 30, 2017
36
0
4,530
well i did all stress test for my gpu, cpu, and ram for a while no crash but i cant play cs go, overwatch, bf3, bf4,gta v, pes 2k17 start the game and crash bsod
specs
amd a8 5500 > max temp doing stress 40c idle 30c
gtx 670 > max temp doing the test furmark, kombustor, unigine 60c idle 27-35c
psu thermaltake tp 750w
ram corsair vengance 8gb 1600mhz dd3
mobo f2a55-M

the only games can i play are Dayz, League of legends, chivalry medial warfare, planetside 2, doom, far cry primal, re7

thanks for watching my thread, hope can help me

what already did
reinstall os
reinstall several drivers off nvidia page /i use ddu/

Sorry for my english im not an american
 

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360
Get the program called Bluescreenviewx64 It will analyze your dumps, and will tell you what is failing. I'm willing to bet a dozen donuts that it's a Graphics driver causing your issue seeing as the stress tests themselves work fine.
 

MGhostX

Reputable
Jan 30, 2017
36
0
4,530


i use who crashed an this what appears
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 3/10/2017 12:01:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\031017-20703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xA97, 0x1703C4E0, 0xFFFFD7810E992000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 3/10/2017 12:01:12 PM 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: 0x12B (0xFFFFFFFFC00002C4, 0xA97, 0x1703C4E0, 0xFFFFD7810E992000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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 3/9/2017 10:56:19 AM your computer crashed
crash dump file: C:\Windows\Minidump\030917-24765-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x157B4C)
Bugcheck code: 0x116 (0xFFFFDD055A895010, 0xFFFFF80C757A7B4C, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_e9418cd4947d9b45\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 376.33
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.33
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 376.33 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR
 

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360
Prime is great for CPU related stuff. You want to stress the RAM in all sorts of weird and wonderful ways.
"Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test). "
 

MGhostX

Reputable
Jan 30, 2017
36
0
4,530


so i did the memtest 40 mins 4/4 task error 0 so what can i do know? i did all the test posible
 

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360
Have you run HD diagnostics as well?
Scan your windows system files to make sure they are all good
Drop to an administrative command prompt and type
sfc /scannow /offbootdir=d:\ /offwindir=d:\windows --> Press enter
Let the SFC utility scan your windows core system files for corruption.
 

MGhostX

Reputable
Jan 30, 2017
36
0
4,530


on my way to do that ill update soon ! thanks for ur time
 

MGhostX

Reputable
Jan 30, 2017
36
0
4,530


i got a error says
C:\Windows\system32>sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

Windows Resource Protection could not start the repair service.
 

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360


Are you running in Safe Mode? It doesn't work well in Safe Mode. Are you able to determine what is stoping the repair service from starting?
 

MGhostX

Reputable
Jan 30, 2017
36
0
4,530


no errors so far well i got a kernel power id 41 error in event viewer

 

MGhostX

Reputable
Jan 30, 2017
36
0
4,530


my psu is enough for that or not? hwmonitor
Voltage 0 3.33 Volts [0xD0] (+3.3V)
Voltage 1 0.87 Volts [0x6D] (CPU VCORE)
Voltage 2 2.42 Volts [0x97] (DRAM)
Voltage 3 1.25 Volts [0x9C] (VIN3)
Voltage 4 1.47 Volts [0xB8] (VIN4)
Voltage 5 1.38 Volts [0xAC] (VIN5)
Voltage 6 1.31 Volts [0xA4] (VIN6)
Voltage 7 3.39 Volts [0xD4] (VSB3V)
Voltage 8 3.20 Volts [0xC8] (VBAT)
Voltage 9 5.16 Volts [0xD7] (5VSB)
 

MGhostX

Reputable
Jan 30, 2017
36
0
4,530


i did no errors so far