another one of those BSOD

[tuggray]

Hi, i just returned to rust after a bit of a hiatus.
basicly tweaked the game down a bit to make it run decent FPS and happy with the gameplay how it feels everything.
been live streaming my play and it's going all good then BAM! BSOD system crash minidump says easyanticheat.sys to blame.
[QUOTE]Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Swanny\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03660000 PsLoadedModuleList = 0xfffff800`038a3890
Debug session time: Sat Nov 14 00:56:36.846 2015 (UTC + 0:00)
System Uptime: 0 days 1:08:34.985
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........

************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800036671e4, fffff8800929fcb0, 0}

*** ERROR: Module load completed but symbols could not be loaded for EasyAntiCheat.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully q

[Myrothas]

try a different power supply

[eac knubbe]

Could you upload the memory.dmp and the latest file in C:\Windows\Minidump\ to e.g. [url]http://speedyshare.com/?[/url] Thanks!

Also could you screenshot the output of running 'bcdedit' in command-line as Administrator?

[tuggray]

how do i get the bcdedit?

[editline]14th November 2015[/editline]

[QUOTE=Myrothas;49115447]try a different power supply[/QUOTE]

not a power supply issue trust me it's been running twin gpus no problem, i recently swaped out both 6870s for a single r9 270x 4gb just for star citizen and that runs fine.

[url]https://drive.google.com/file/d/0Bx0eQRbk5aPWYlJhbmdsX3ZlTWc/view[/url]
bdcedit here

[URL]http://speedy.sh/fxSFN/MEMORY.DMP[/URL]
[URL="http://speedy.sh/vXMXQ/111415-27112-01.dmp"]http://speedy.sh/vXMXQ/111415-27112-01.dmp[/URL]
[URL="http://speedy.sh/Qa9ap/111415-29702-01.dmp"]http://speedy.sh/Qa9ap/111415-29702-01.dmp[/URL]
memory dumps here

since all BSOD i've had are the last 3 days during rust gameplay (Only BSOD i've had in a very long time)

[tuggray]

Any luck?

[eac knubbe]

Thanks! We will check these out and see what's going on.

The last 2 links seem to have been deleted, could you re-upload these?

Also can you upload the screenshot of bcdedit to speedy.sh as well? The drive.google.com link is asking for authorization.