Computer crashes when gaming

RoadBlaster said:

All I got is this from the manual:

Attachment 286756

Does not state which slot to use for 1 stick so maybee just try in each slot to see if still crashes but can not say for certain ?

No luck.

yehonatans said:

I bought the PC more than 7 years ago and I have been replacing it's components piece by piece, the mobo and processor were the last original parts. After replacing them I also reinstalled windows (and all the drivers)

Thank for your input so far, temps, voltages etc. so far look good, unless I missed something, but how exactly did you reinstall OS?

For example:
1. Is disk partitioned as GPT or MBR?
2. Is BIOS running in legacy or UEFI mode?
3. Are Windows 10 features turned on in BIOS? (secure boot, Windows 10 WHQL etc..)
4. are there legacy functions enabled in BIOS?
5. have you checked disk and file system for errors or performed slow format?

Let me know if you need help determining these things out, next step is to share event logs:

Please follow bellow steps to share event logs:

1. Right click on Windows button and click on "Windows PowerShell (Admin)"
2. copy/paste all of the bellow code at once and right click into console then hit enter

Code:

Get-EventLog -LogName System -EntryType Error | ? Source -ne DCOM |
select EventID, TimeGenerated, Source, Message | sort TimeGenerated -Descending | fl > C:\system.log

3. copy/paste all of the bellow code at once and right click into console then hit enter

Code:

Get-EventLog -LogName HardwareEvents -EntryType Error, Warning -Newest 200 -EA Ignore |
select EventID, TimeGenerated, Source, Message | sort TimeGenerated -Descending | fl > C:\hardware.log

4. copy/paste all of the bellow code at once and right click into console then hit enter

Code:

Get-EventLog -LogName system -Source user32 | select EventID, EntryType, TimeGenerated, Source, Message |
sort TimeGenerated -Descending | fl > C:\shutdown.log

5. copy/paste all of the bellow code at once and right click into console then hit enter

Code:

Get-WinEvent -LogName Setup | select Id, TimeCreated, LevelDisplayName, Message | fl > C:\setup.log

6. copy/paste all of the bellow code at once and right click into console then hit enter

Code:

Get-EventLog -LogName Application -EntryType Error, Warning |
select EventID, TimeGenerated, Source, Message | sort TimeGenerated -Descending | fl > C:\application.log

7. This will create 5 log files in your C drive
8. Zip up those 5 files and attach to your new reply

For more information about event log see:
https://support.microsoft.com/en-us/...rosoft-windows

You said to be reinstalling drivers after system installation, make sure the drivers you downloaded and installed are only those from motherboard site, GPU site or Windows update service and not other sites.

zebal said:

Thank for your input so far, temps, voltages etc. so far look good, unless I missed something, but how exactly did you reinstall OS?

Before I switched the CPU and Mobo I was still using Win7, I installed win 10 after switching using a usb.

zebal said:

1. Is disk partitioned as GPT or MBR?

GPT

zebal said:

2. Is BIOS running in legacy or UEFI mode?

UEFI

zebal said:

3. Are Windows 10 features turned on in BIOS? (secure boot, Windows 10 WHQL etc..)

I don't think so, how can I check.

zebal said:

4. are there legacy functions enabled in BIOS?

I don't know, if my BIOS is running UEFI shouldn't it mean that they aren't?

zebal said:

5. have you checked disk and file system for errors or performed slow format?

Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on C:

Stage 1: Examining basic file system structure ...
The attribute name offset for attribute of type 0x30
and instance tag 0x5 is incorrect.
30 00 00 00 00 01 00 00 00 00 00 08 00 00 05 00 0...............
e6 00 00 00 18 00 01 00 84 0c 00 00 00 00 01 00 ................
22 3a 8c b6 37 2a d6 01 00 05 ca 8d 93 23 d6 01 ":..7*.......#..
e2 c4 e5 77 37 2a d6 01 22 3a 8c b6 37 2a d6 01 ...w7*..":..7*..
00 10 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? ................
Found corrupt basic file structure for "\Windows\servicing\Packages\MIC78B~1.MUM <0x1,0x613ce>"
... repaired online.
436736 file records processed. File verification completed.
8855 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
6331 reparse records processed. Found an unneeded link ($FILE_NAME: "MIC78B~1.MUM") in index "$I30" of directory "\Windows\servicing\Packages <0x1,0xc84>"
... repaired online.
Found an unneeded link ($FILE_NAME: "Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~~10.0.18362.836.mum") in index "$I30" of directory "\Windows\servicing\Packages <0x1,0xc84>"
... repaired online.
591332 index entries processed. Index verification completed.

Found lost file "\Windows\servicing\Packages\MIC78B~1.MUM <0x1,0x613ce>"; requesting reconnection to index "$I30" of directory "\Windows\servicing\Packages <0x1,0xc84>"
... repaired online.

6331 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
77299 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and they were all fixed online.
No further action is required.

116558847 KB total disk space.
64372676 KB in 280790 files.
183592 KB in 77300 indexes.
509463 KB in use by the system.
65536 KB occupied by the log file.
51493116 KB available on disk.

4096 bytes in each allocation unit.
29139711 total allocation units on disk.
12873279 allocation units available on disk.

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


Stage 1: Examining basic file system structure ...
Deleting corrupt attribute record (0x30, "")
from file record segment 0x613CE.

Stage 2: Examining file name linkage ...
There is no NTFS file name attribute in file 0x613ce.
Correcting minor file name errors in file 613CE.
Unable to locate the file name attribute of index entry MIC78B~1.MUM
of index $I30 with parent 0xc84 in file 0x613ce.
Deleting index entry MIC78B~1.MUM in index $I30 of file C84.
Unable to locate the file name attribute of index entry Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~~10.0.18362.836.mum
of index $I30 with parent 0xc84 in file 0x613ce.
Deleting index entry Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~~10.0.18362.836.mum in index $I30 of file C84.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file MIC78B~1.MUM (613CE) into directory file C84.
Recovering orphaned file MIC78B~1.MUM (613CE) into directory file C84.
1 unindexed files recovered to original directory.

Stage 3: Examining security descriptors ...

Just did, this is the result.

Log files:
Logfiles.zip

The error code from system log are all due to Atheros wireless adapter, the meaning of error code is as follows:
I put red color because that makes errors related, other way around doesn't make much sense, and also we know windows installation is not clean or corrupt because disk/file system check failed.

Code:

PS C:\tools> .\err* 126
# for decimal 126 / hex 0x7e
  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED                            bugcodes.h
  NMERR_REMOTE_NOT_A_SERVER                                      netmon.h
  ERROR_MOD_NOT_FOUND                                            winerror.h
# The specified module could not be found.
# for hex 0x126 / decimal 294
  NETIO_INVALID_POOL_CALLER                                      bugcodes.h
  STATUS_FSFILTER_OP_COMPLETED_SUCCESSFULLY                      ntstatus.h
# A file system or file system filter driver has successfully
# completed an FsFilter operation.
# as an HRESULT: Severity: SUCCESS (0), FACILITY_NULL (0x0), Code 0x7e
# for decimal 126 / hex 0x7e
  ERROR_MOD_NOT_FOUND                                            winerror.h
# The specified module could not be found.
# 6 matches found for "126"

Either the missing module happens to be in bad drive sector, or installation is corrupt.

Errors from shutdown logs are mostly related to drive or file system errors:

Code:

PS C:\tools> .\err* 0x80020010
# for hex 0x80020010 / decimal -2147352560
  DISP_E_BADCALLEE                                               winerror.h
# Invalid callee.
# as an HRESULT: Severity: FAILURE (1), FACILITY_DISPATCH (0x2), Code 0x10
# for hex 0x10 / decimal 16
  ERROR_CURRENT_DIRECTORY                                        winerror.h
# The directory cannot be removed.
# 2 matches found for "0x80020010"

Code:

PS C:\tools> .\err* 0x500ff
# No results found for hex 0x500ff / decimal 327935
# anonymous HRESULT: Severity: SUCCESS (0), Facility 0x5, Code 0xff
# for hex 0xff / decimal 255
  BTH_ERROR_UNSPECIFIED                                          bthdef.h
  RESERVE_QUEUE_OVERFLOW                                         bugcodes.h
  NRC_PENDING                                                    nb30.h
# /* asynchronous command is not yet finished   */
  STATUS_ALREADY_COMPLETE                                        ntstatus.h
# The requested action was completed by an earlier operation.
  ERROR_EA_LIST_INCONSISTENT                                     winerror.h
# The extended attributes are inconsistent.
# 5 matches found for "0x500ff"

Code:

PS C:\tools> .\err* 0x80020003
# for hex 0x80020003 / decimal -2147352573
  DISP_E_MEMBERNOTFOUND                                          winerror.h
# Member not found.
# as an HRESULT: Severity: FAILURE (1), FACILITY_RPC_RUNTIME (0x2), Code 0x3
# for hex 0x3 / decimal 3
  STATUS_WAIT_3                                                  ntstatus.h
# as an HRESULT: Severity: FAILURE (1), FACILITY_DISPATCH (0x2), Code 0x3
  ERROR_PATH_NOT_FOUND                                           winerror.h
# The system cannot find the path specified.
# 3 matches found for "0x80020003"

And on top of that your drive checks have failed so the very first thing is to isolate drive or file system problems and then try reproducing problem.

What to do?

To *attempt* to fix the problem without system reinstall, (may not always succeed):

Following is a list of software one should avoid to prevent unexpected system behavior

1. Registry, disk or system cleaners
2. Driver download or updater tools
3. System tweak tools or system optimizers
4. Various malware/adware removal tools or scanners
5. Program/driver uninstallers
6. Browser extensions of questionable reputation
7. Various "fix" tools that claim to fix some problem

If you installed anything that matches the list above, please remove and reboot system.

Reinstall all network adapter drivers from valid sites first (manufacturer site or motherboard site)

Open command prompt as Administrator

Code:

CHKDSK /r

if asked to reboot, do it let it fix bad sectors

Once done run in following order as Administrator:

Code:

DISM.exe /Online /Cleanup-image /Restorehealth

Code:

sfc /scannow

reboot if needed, then reinstall ALL drivers from valid sites (manufacturer site or motherboard site)
Driver installation goes like this:
1. reinstall chipset driver
2. reboot system
3. reinstall the rest of drivers
4. reboot system

IMPORTANT:
If this doesn't solve the problem, your installed system is not suitable to self repair, you'll need new installation image to perform repair and start all over again, see bellow link how to repair installation using installation image:
https://support.microsoft.com/en-us/...rrupted-system

Here is where to get fresh Windows (installation image):
https://www.microsoft.com/en-us/soft...load/windows10

If this doesn't work, back up all your data onto external drive because this one should be wiped out and system fresh installed, (you can skip fixing things, and just do clean install of course)

Possible reasons for failure to restore using above steps is that Windows was installed over bad sectors or the drive generated new bad sectors since installation which contains important system files.

Before I switched the CPU and Mobo I was still using Win7, I installed win 10 after switching using a usb.

Sounds to me like upgrade from Windows 7 to Windows 10?
If the drive contains bad sectors it must be properly formatted before installing.

Here is where to get fresh Windows:
https://www.microsoft.com/en-us/soft...load/windows10

Bellow is a friendly tutorial how to do clean installation with automatic format:
Clean Install Windows 10
Tutorial screenshots may be out of date, IDK, but principle is the same.
Just make sure you install same edition of Windows.

This should work, if that does not work, to test disk further, slow format should be performed prior installation, I'm not sure if there is tutorial for this, let me know if you want to do it.

After installation is done:
1. Fully update Windows
2. Install all drivers from (motherboard site, or specific hardware site, not driver downloaders and not googling out drivers)
3. the order of driver installment and reboot order is described above, this is important because you are testing drive and system installation.

Are Windows 10 features turned on in BIOS? (secure boot, Windows 10 WHQL etc..)

I don't think so, how can I check.

Usually if these options are not visible in BIOS, there should be "Advanced" mode, that let's you set these.

And legacy functions in BIOS depend from one BIOS to another, if BIOS is in UEFI mode that's already a lot, for example
xhci hand off is legacy function and must be disabled separately. not needed for windows 10.

RoadBlaster said:

I would also say a Bios update would be best done after a fresh install or repair also..

If it resolves some specific problem then yes, in any case I would not do it until computer is completely stable and only BIOS remains and it fixes specific thing.

For example my BIOS is 2 years out of date, everything works just fine so I'm still not updating it.

You know the saying: "if it ain't broke, don't fix it"

zebal said:

reboot if needed, then reinstall ALL drivers from valid sites (manufacturer site or motherboard site)
Driver installation goes like this:
1. reinstall chipset driver
2. reboot system
3. reinstall the rest of drivers
4. reboot system

What do you mean by all drivers? (Besides GPU driver)

yehonatans said:

What do you mean by all drivers? (Besides GPU driver)

Once you're done with file system and disk repair as described before, we isolate file system and drive bad sector problems, drivers must be fresh installed after that to isolate them too.

Isolating means, ensuring file system and drivers (which are core to resolving this issue) are no longer problem, so that if another problem happens or this doesn't resolve the issue we'll know there is something else to look at, thus saving valuable troubleshooting time.

As noted previously drivers must be all signed and verified to prevent unexpected results, this means downloading them from these sites:
B450 AORUS M (rev. 1.0) | Motherboard - GIGABYTE Global
https://www.amd.com/en/support/graph.../radeon-rx-580

Your biggest problem with drivers is "Wireless adapter driver", I don't know which adapter you have, but this one should be reinstalled first to make network normal before downloading the rest.

If you want help with this then:

1. Click on Windows button
2. Type msinfo32 on your kyeboard
3. Right click on "System Information" and Run as Administrator
4. If asked for password enter your password and click OK
5. Click on: File -> Save...
6. Save the file to your desktop or to C:\ drive directly
8. Zip up the file and attach to your reply

To share driver signatures (to identify bad drivers)

1. Press Windows key
2. type sigverif
3. run "sigverif" as Administrator
4. click "start" button
5. when complete, click "Advanced" button
6. click "View log"
7. click anywhere in the log and press, CTRL + A then CTRL + C to copy contents
8. paste contents to new file, save it and attach to your new reply.

(Assuming wireless adapter was reinstalled and system rebooted)
For gigabyte site, please download all drivers only, not "Utility" or "Bios" for now.
For AMD site download "Adrenalin 2020 Edition 20.4.2 Recommended (WHQL)"

You would then start running downloaded installers to install downloaded drivers: in this order:
1. chipset driver
2. reboot
3. the rest of drivers
4. reboot

EDIT:
Note there are multiple same drivers on gigabyte site, you only need latest drivers for your OS build, no duplicates.