Rust
Rust > General Discussions > Topic Details
Kirito Jan 2, 2014 @ 5:04pm
Blue screen of Death
Well, when i play rust for some time, my computer go to "Blue Screen Of Death"..

PC :

8GB RAM (Just using 3,5...Windows 32 bits.)
GT 9800
AMD PHENOM x4 II.
< >
Showing 1-15 of 25 comments
Nick Jan 2, 2014 @ 5:05pm 
Your PC is probably overheating or has a hardware problem. Try opening it up and see if the fans are dusty. If they aren't and it still does that you likely have something else wrong and should get it serviced.
Gambles Jan 2, 2014 @ 5:05pm 
that sounds a lot like an overheating issue sir, I would check your temps while playing.

Edit: Damnit Nick Ninja'd me.
Last edited by Gambles; Jan 2, 2014 @ 5:06pm
Howard Jan 2, 2014 @ 5:13pm 
What's the file it mentions that causes the crash?
Kody Jan 2, 2014 @ 7:12pm 
I also got a BSOD recently while playing Rust. I was waiting for someone else to post about this problem just to see if it was an issue for anyone else. I have around 50 hours of play time in rust already and have not experienced a BSOD before the most recent patch....

My specs are very similiar to OP:
AMD Phenom x4 II BE
GTX 760
8GB RAM

my BCCODE was "F4" thought it didn't directly point to a file that caused the crash....

My temps are really good. My CPU is well below 55C and my GPU maybe hits 60 - 65 max.

Like i said, I have around 50 hours in rust already and only recently got this BSOD problem... happened twice lastnight... if anyone knows of any fixes please let us know!
Howard Jan 2, 2014 @ 8:18pm 
The most important part is the file that caused it. If I had to guess its probably some graphics driver ♥♥♥♥-up.
Kody Jan 2, 2014 @ 9:50pm 
my drivers are up to date... Any chance it could be a bug in the latest update that conflicts with our specific processors? the only thing mentioned in my BSOD is that a thread failed or something along those lines... no files mentioned at all... I started my rust up just now and it ran for around 20 mins or so and hit me with the BSOD again
Kody Jan 2, 2014 @ 10:27pm 
it's pointing to ntsokrnl.exe and labeled as a "CRITICAL_OBJECT_TERMINATION" if that helps anyone. I've read its a driver error? Is there anyway for me to tell which driver specifically?
Howard Jan 3, 2014 @ 1:07pm 
Okay well that really helps. For Kody, bsod's with ntoskrnl.exe are normally from third party software, probably Rust in this case. I don't know what Rust would be doing but try this:
Go to cmd and use the command SFC /SCANNOW. What this will do is it will basically inspect system files and if it finds any of them ♥♥♥♥ed up it will replace them. Check if it says it was unable to replace it or something else. After that, restart your PC and try playing Rust
Last edited by Howard; Jan 3, 2014 @ 1:17pm
Skuggan Jan 3, 2014 @ 1:24pm 
Originally posted by Kody:
it's pointing to ntsokrnl.exe and labeled as a "CRITICAL_OBJECT_TERMINATION" if that helps anyone. I've read its a driver error? Is there anyway for me to tell which driver specifically?

"CRITICAL_OBJECT_TERMINATION"
This is usually a software issue, however the game itself doesnt interfere with your OS-files in a way that could result in a BSOD, it could however trigger bugs in drivers or firmwares.
I would dig deeper in eventviewer to find a pattern of what is happening before the crash.

Do you use a SSD?
Look for a new firmware if that is the case.

When you install latest graphics drivers do you do a clean install or do you just install the new driver over the old one?
Always do a clean install.

Did you update anything else recently?
Try restoring your computer to a point before installing any updates, that includes updates from Microsoft.

Did you install new BIOS version when you got that graphics card?
Last edited by Skuggan; Jan 3, 2014 @ 1:27pm
Tacticus Winter Jan 3, 2014 @ 1:27pm 
Try reinstalling the game or running a PC scan, something may have ♥♥♥♥ed up a file or 2
Cika Jan 14, 2014 @ 9:01am 
this is ♥♥♥♥ed up, honestly...i could choose dayz but i didnt and now i already bought, cant rebuy -.- my game crashes after less than a minute when i join a server. ♥♥♥♥.
Howard Jan 15, 2014 @ 7:27pm 
Originally posted by Uajcika (Gadjiev):
this is ♥♥♥♥ed up, honestly...i could choose dayz but i didnt and now i already bought, cant rebuy -.- my game crashes after less than a minute when i join a server. ♥♥♥♥.
Did you try any of what was suggested?
dLP|.GaidenFocus Mar 9, 2014 @ 1:31pm 
I can tell you it is not a hardware issue. I have the same problem, no other game causes this.
Showiz Aug 2, 2014 @ 9:43am 
♥♥♥♥♥game ffs.
TheHalvinator Apr 30, 2015 @ 7:43pm 
I'm also experiencing crashes while playing Rust.
My heat never exceeds temps that would cause my system to shut down.
Only ever happens with Rust. I monitor with Open Hardware Monitor.

I run Diablo 3, Skyrim, and GTA 5 on max settings without issues.

i7-4770k
GTX 770
16 gigs Ram

I get a variety of blue screens stop codes. Can't remember a specific one. Had plenty of access violation crashes (0x00...05) and PFN list corrupt popped up once.

I've checked all my hardware and drivers. Everything was ok. Either Memtest86 or jelly bean extract gave me some nasty malware so I had to reinstall my entire OS. I intended to do it anyways. After which installing my OS and playing for a longer period of time with no issue, I finally blue screened again (frequent crashes before the blue screen).

Here's the mini dump from Windbg:

-------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff880053b0f33, fffff8800910af90, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+9f )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880053b0f33, Address of the instruction which caused the bugcheck
Arg3: fffff8800910af90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+9f
fffff880`053b0f33 8b5638 mov edx,dword ptr [rsi+38h]

CONTEXT: fffff8800910af90 -- (.cxr 0xfffff8800910af90;r)
rax=0000000000000000 rbx=fffffa800ec11000 rcx=fffffa800ec11000
rdx=fffff8a004e92db4 rsi=0cf2f440fffffa20 rdi=0000000000000000
rip=fffff880053b0f33 rsp=fffff8800910b960 rbp=fffff8a004ada000
r8=0000000000000000 r9=0000000000000000 r10=fffff880053a68d0
r11=0000000000060000 r12=0000000000000000 r13=0000000000000000
r14=fffff8a004e92db4 r15=00000000896c51f0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x9f:
fffff880`053b0f33 8b5638 mov edx,dword ptr [rsi+38h] ds:002b:0cf2f440`fffffa58=????????
Last set context:
rax=0000000000000000 rbx=fffffa800ec11000 rcx=fffffa800ec11000
rdx=fffff8a004e92db4 rsi=0cf2f440fffffa20 rdi=0000000000000000
rip=fffff880053b0f33 rsp=fffff8800910b960 rbp=fffff8a004ada000
r8=0000000000000000 r9=0000000000000000 r10=fffff880053a68d0
r11=0000000000060000 r12=0000000000000000 r13=0000000000000000
r14=fffff8a004e92db4 r15=00000000896c51f0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x9f:
fffff880`053b0f33 8b5638 mov edx,dword ptr [rsi+38h] ds:002b:0cf2f440`fffffa58=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: RustClient.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880053b0f33

STACK_TEXT:
fffff880`0910b960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x9f


FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+9f
fffff880`053b0f33 8b5638 mov edx,dword ptr [rsi+38h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+9f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

IMAGE_VERSION: 6.1.7600.16385

STACK_COMMAND: .cxr 0xfffff8800910af90 ; kb

FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+9f

BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+9f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x3b_dxgmms1!vidmm_global::begincpuaccess+9f

FAILURE_ID_HASH: {fcdf3689-2575-7ce6-921f-0f7ccca100f8}

Followup: MachineOwner
---------


*Hope this helps if the issues are related to software. Once again, only ever happens with Rust. Drivers were straight from Nvidia. Tried two different ones, same issue. New OS install. All hardware tests ran for max duration with no errors.
< >
Showing 1-15 of 25 comments
Per page: 15 30 50

Rust > General Discussions > Topic Details
Date Posted: Jan 2, 2014 @ 5:04pm
Posts: 25