Question Rust random BSOD on sick computer

Jan 4, 2020
1
0
10
0
I desperately need someones help.

I'm a full-time streamer and these random every hour or every 15m or every 2 hour BSOD are killing me!

Randomly while in game my rust will just cause my entire computer to go into a BSOD. It has never happened with any other game but only Rust.. I desperately need to get this fixed as I'm loosing viewers each time I crash. Specs and Mini dumps will be posted below! I even tried resetting/reformating my entire computer and still am getting BSODs randomly in the game. It can be 2 hours without one, then one every 15m for an hour, it's horrible.

I've also downloaded and bought the pro version of Driver Easy and updated all drivers correctly from that program. I've done a memtest and it came back with no issues. I've ran /sfc scannow with also no issues.

Specs and MiniDump info:


Operating System Microsoft Windows 10 Home (64-bit)
Memory 32 GB
Processor Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
Motherboard ASRock - Z390 Phantom Gaming 4-CB
Video Cards NVIDIA GeForce RTX 2070
Memory
Type DDR4
Size 32768 MBytes
Timings
DRAM Frequency 1199.8 MHz
FSB:DRAM --
CAS# Latency(CL) 16 clocks
RAS# to CAS# Delay(tRCD) 16 clocks
RAS# Precharge(tRP) 16 clocks
Cycle Time(rRAS) 39 clocks
Bank Cycle Time(tRC) --
Command Rate(CR) 2 clocks


MINIDUMP Analysis


***
  • *
  • Bugcheck Analysis *
  • *
***

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa00503bcc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 0

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-VQS2OCF

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 0

Key : Analysis.Memory.CommitPeak.Mb
Value: 42

Key : Analysis.System
Value: CreateObject

Key : WER.CorruptModuleList
Value: 1

Key : WHEA.MCiStatus.Code
Value: 0xb200000000030005

Key : WHEA.MCiStatus.McaError
Value: 0x0005

Key : WHEA.MCiStatus.ModelError
Value: 0x0003

Key : WHEA.MCiStatus.Reserved
Value: 0x00000000


ADDITIONAL_XML: 1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa00503bcc028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffe5811dee2d78 fffff8027dfa4fe8 : 0000000000000124 0000000000000000 ffffa00503bcc028 00000000b2000000 : 0xfffff8027e1c14e0
ffffe581
1dee2d80 0000000000000124 : 0000000000000000 ffffa00503bcc028 00000000b2000000 0000000000030005 : 0xfffff8027dfa4fe8
ffffe5811dee2d88 0000000000000000 : ffffa00503bcc028 00000000b2000000 0000000000030005 fffff8027e463ce0 : 0x124


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BANK0_MSCOD0003_MCACOD0005_PCC_UC_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1873bcae-5777-f674-1761-09c9eea09dbd}
 
Last edited by a moderator:

Lutfij

Titan
Moderator
First off, welcome to the forums, newcomer!

Second, you shouldn't drop money into a third party app, that tells you if you're on the latest drivers or not. In fact there are known documented cases where third party apps have brought in unnecessary drivers or even the wrong BIOS version to knock the system out for good.

Third, which version of Windows 10 are you currently on and which BIOS version are you on for your motherboard?

Fourth, You should ideally list your specs to your build like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
 

ASK THE COMMUNITY