my system keeps crushing while gaming

deni.cool1 · Sep 20, 2017

my rig is:
cpu: ryzen 1600 stock clock
gpu: evga 1070 sc
motherboard: MSI - A320M GRENADE Micro ATX
ram: corsair 16gb 2400
hdd: westren digital 1TB 72000rpm
ssd: kingstone 120 gb
psu: 500w (zm-500-LE)

CSGO- freezes, makes the screen darker and then its normal for a couple of minutes and again or i play normally, very random.
THE WITCHER 3- freezes and just shows the last frame and the game just playing in the background.
PUBG- a lot of crashes and small freezes.

its a new build that i built a month ago, im getting a lot of problems especially while im gaming.
and when im trying to watch a YouTube video most of the time it will fail or will freeze will show some green crap and then play the video.

i tried to streestest with 3DMARK and the its just crashes in the first seconds of the test (fire strike) and its says that the test was cancelled by the user but i didn't touch anything and its giving me score 0 .
https://imgur.com/a/lssCW (for proof)

please help its so annoying to buy this rig and getting those problems.
thanks in advance.

Sedivy · Sep 20, 2017

Are you running any overclocks on the gpu itself? Or just running at whatever you got it at?
First, get HWMonitor and check your temps when you start playing, for both cpu and gpu.

deni.cool1 · Sep 20, 2017

Sedivy :

nope, no overclocks on the cpu and none on the gpu.
starting temps are around 40 (hot room)

Sedivy · Sep 20, 2017

That's pretty hot for an idle. What is it when you open a game? And that was the gpu temp right? Not cpu?

deni.cool1 · Sep 20, 2017

Sedivy :

the 40 is for both but the gpu stays cooler then the cpu (im using the stock cooler btw) and when im in a game its around 50, its rare to see it at 60

Sedivy · Sep 20, 2017

That's not bad at all. Ok, try opening up the event viewer in windows and look for critical errors around the time of the crash +/- a minute. Post the event ID here, and the description.

Darkvillain · Sep 20, 2017

Your GPU could be dying already, sometimes you get faulty parts when building, if you can, I would try contacting support and expressing your problems with the system to them.

deni.cool1 · Sep 20, 2017

Sedivy :

+ System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 5

Level 1

Task 63

Opcode 0

Keywords 0x8000400000000002

- TimeCreated

[ SystemTime] 2017-09-20T16:19:02.372773200Z

EventRecordID 5238

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer DESKTOP-4023BRL

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI true

well that just happened

deni.cool1 · Sep 20, 2017

Darkvillain :

well shit, thanks tho didn't want to think about it lol

deni.cool1 · Sep 20, 2017

Log Name: Application
Source: Windows Error Reporting
Date: 20/09/2017 20:09:34
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-4023BRL
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffd18ab69a04a0
P3: fffff802572ae0bc
P4: 0
P5: 25cc
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170920-2009.dmp
\\?\C:\Windows\Temp\WER-3031265-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B41.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B51.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B62.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_825a710477afa2dbf341ad6263b3781650b048_00000000_cab_0bb24ca9

Analysis symbol:
Rechecking for solution: 0
Report ID: 3f846d83-740e-4447-80ee-0d630221ee95
Report Status: 2049
Hashed bucket:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-09-20T17:09:34.668078300Z" />
<EventRecordID>2789</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-4023BRL</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>LiveKernelEvent</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>141</Data>
<Data>ffffd18ab69a04a0</Data>
<Data>fffff802572ae0bc</Data>
<Data>0</Data>
<Data>25cc</Data>
<Data>10_0_15063</Data>
<Data>0_0</Data>
<Data>768_1</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170920-2009.dmp
\\?\C:\Windows\Temp\WER-3031265-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B41.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B51.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B62.tmp.txt</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_825a710477afa2dbf341ad6263b3781650b048_00000000_cab_0bb24ca9</Data>
<Data>
</Data>
<Data>0</Data>
<Data>3f846d83-740e-4447-80ee-0d630221ee95</Data>
<Data>2049</Data>
<Data>
</Data>
</EventData>
</Event>

one more crash

Darkvillain · Sep 20, 2017

I am pretty sure it is a GPU problem, not the greatest at log files, but your symptoms would relfect that, are you sure your mobo has enough power to cover all components though? Just curious if it could be a power problem. If so, then I would recommend trying to get a replacement from whoever you purchased from.

Sedivy · Sep 20, 2017

Yeah the dreaded 41(63) is a hardware error but it's not clear which piece of hardware unfortunately. If you have any overclocks, take them off. Here's what microsoft has to say about it:
https://social.technet.microsoft.com/Forums/windows/en-us/308cbcb3-46ce-4f74-85f9-d87ce4cef0d6/kernel-power-event-id-41-task-category-63-spontaneous-improper-shutdowns-and-reboots?forum=w7itproperf

In your case it translates to few things. After you reset things to basic clocks, try re-seating your ram, try different slots a1/b1 vs a2/b2 and so on. Try a single stick. See if it helps.

Then try pulling out your gpu and putting it into another system. You already know 3DMark will freeze it but it could be memory, it could be the gpu itself but it could also be the psu dying, and therefore choking the most power hungry component in your system first, when you load it up (gpu).

PSU you can test yourself if you've got a multimeter (scroll down to second part):
http://www.wikihow.com/Check-a-Power-Supply
but generally people just take it into a repair shop for someone to test it for them.

You can also always the simplest parts on your end. Meaning use DDU to completely uninstall your drivers, and reinstall them. Update your BIOS if you can, but follow manufacturer's instructions carefully. Doing it wrong can brick your board so take care during this process.

Darkvillain · Sep 20, 2017

Sedivy just presented you the bible of these problems. I would recommend going through what he has recommended here.

deni.cool1 · Sep 22, 2017

Sedivy :

Yeah the dreaded 41(63) is a hardware error but it's not clear which piece of hardware unfortunately. If you have any overclocks, take them off. Here's what microsoft has to say about it:
https://social.technet.microsoft.com/Forums/windows/en-us/308cbcb3-46ce-4f74-85f9-d87ce4cef0d6/kernel-power-event-id-41-task-category-63-spontaneous-improper-shutdowns-and-reboots?forum=w7itproperf

In your case it translates to few things. After you reset things to basic clocks, try re-seating your ram, try different slots a1/b1 vs a2/b2 and so on. Try a single stick. See if it helps.

Then try pulling out your gpu and putting it into another system. You already know 3DMark will freeze it but it could be memory, it could be the gpu itself but it could also be the psu dying, and therefore choking the most power hungry component in your system first, when you load it up (gpu).

PSU you can test yourself if you've got a multimeter (scroll down to second part):
http://www.wikihow.com/Check-a-Power-Supply
but generally people just take it into a repair shop for someone to test it for them.

You can also always the simplest parts on your end. Meaning use DDU to completely uninstall your drivers, and reinstall them. Update your BIOS if you can, but follow manufacturer's instructions carefully. Doing it wrong can brick your board so take care during this process.

i used the DDU program but no positive changes trying to convince my friend to give me his PC for testing.
and i cant play with the ram cause i bought a mother board with only 2 ram slots and everything is up to date
thanks for the psu testing thing lol

deni.cool1 · Sep 22, 2017

Darkvillain :

i will make sure to go through it, thanks for the help before

Sedivy · Sep 22, 2017

If you can't play with different memory slots, try taking out one stick and see if there's any difference in stability.

Search

my system keeps crushing while gaming

deni.cool1

Prominent

Sedivy

Sedivy

Estimable

deni.cool1

Prominent

Sedivy

Estimable

deni.cool1

Prominent

Sedivy

Estimable

Darkvillain

Honorable

deni.cool1

Prominent

deni.cool1

Prominent

deni.cool1

Prominent

Darkvillain

Honorable

Sedivy

Estimable

Darkvillain

Honorable

deni.cool1

Prominent

deni.cool1

Prominent

Sedivy

Estimable

TRENDING THREADS

Latest posts

Moderators online

Share this page