Jump to content

Blue Screen - Only with 7 days to die


Recommended Posts



Is there know issue for BSOD for 7 days to die. I never have BSOD in any game and only when playing with 7DTD I get this behaviour.

I already did SFCSCAN and Memory test and no issues at all. All drivers are updated.


Also the de@%$# seems to point out to 7 days to die. The de@%$# of the windows I get this:

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel de@%$# is available get the stack backtrace.
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80419a1a4e8, address which referenced memory

Debugging Details:


    Key  : Analysis.CPU.mSec
    Value: 4812

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4873

    Key  : Analysis.Init.CPU.mSec
    Value: 749

    Key  : Analysis.Init.Elapsed.mSec
    Value: 11824

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1





BUGCHECK_P4: fffff80419a1a4e8

WRITE_ADDRESS:  0000000000000000 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME:  7DaysToDie.exe

TRAP_FRAME:  ffff94067017f500 -- (.trap 0xffff94067017f500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffc700cade1ac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80419a1a4e8 rsp=ffff94067017f690 rbp=0000000000000001
 r8=00000000000000e0  r9=0000000000000fff r10=000000000000000b
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
fffff804`19a1a4e8 f08120fffffbff  lock and dword ptr [rax],0FFFBFFFFh ds:00000000`00000000=????????
Resetting default scope

ffff9406`7017f3b8 fffff804`19a09169     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff9406`7017f3c0 fffff804`19a05469     : ffffc700`ca900180 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9406`7017f500 fffff804`19a1a4e8     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
ffff9406`7017f690 fffff804`1980c690     : ffffc700`0000000b 00000000`ffffffff 00000000`00000000 ffffc700`cade1ac0 : nt!KiSelectReadyThread+0x20ce48
ffff9406`7017f720 fffff804`1980be9f     : ffff950f`0000000a 00000000`00000009 ffff9406`7017f8e0 00000000`00000000 : nt!KiSwapThread+0x220
ffff9406`7017f7d0 fffff804`1980b743     : ffff950f`00000000 fffff804`00000000 00000000`00000000 ffff950f`65dcf1c0 : nt!KiCommitThreadWait+0x14f
ffff9406`7017f870 fffff804`19bf7551     : ffff950f`672593e0 00000000`00000006 00000000`00000001 ffff950f`00000001 : nt!KeWaitForSingleObject+0x233
ffff9406`7017f960 fffff804`19bf75fa     : ffff950f`65dcf080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObWaitForSingleObject+0x91
ffff9406`7017f9c0 fffff804`19a08bb5     : ffff950f`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6a
ffff9406`7017fa00 00007ff8`e828cea4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000089`76cffa58 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`e828cea4

SYMBOL_NAME:  nt!KiSelectReadyThread+20ce48


IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .thread ; .cxr ; kb


FAILURE_BUCKET_ID:  AV_nt!KiSelectReadyThread

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release


OSNAME:  Windows 10

FAILURE_ID_HASH:  {5fdc59e9-e30c-ea39-69b0-0e6a90df3a23}

Followup:     MachineOwner


Edited by SylenThunder (see edit history)
Link to comment
Share on other sites

the guys here will need far more info then a picked thru log (they need to see the ENTIRE log as its other parts in it are vital pieces to the puzzle).

also, BSOD usually is caused from hardware strain/defects or improper settings that cause strain on system and this is where they will ask questions and offer suggestions.

help them to help you, there is a banner above in every thread that leads to how and what is needed.

good luck

QA Tester-unholyjoe

Edited by unholyjoe (see edit history)
Link to comment
Share on other sites

That error is specific to memory. Highly unlikely but it could be an anti virus thing.


More likely is something with the memory modules, I know you said you've run memtest but running that once usually doesn't net any results (usually they don't show errors in 2/3 times). But, from ram tinkering experiences, when you have a bad frequency/timing on your ram this is one of the bsods that can show up. And as Joe said the truncated logs show nothing there.


Yes this may happen with 7 days but this game is intensive, this one will find issues since it stresses/uses more and more frequently system resources (and believe it or not CSGO is good at finding bad overclocks/ram timing configurations for some reason). 


Do you have XMP enabled in the bios? Any other ram frequency/timing settings? 


Try Prime95, use either blend or check custom, uncheck FFT's in place and set the max ram to like 85% of your total ram. Let that run for a few hours. 

Link to comment
Share on other sites

Blue Screen is a PC issue, not a game client issue.  As Jugg pointed out, it does indicate a memory issue. Could be something as simple as bad timing. (very common, even on pre-built PC's)


But it could also be something else, like the Power Supply unit going bad, and this is just where the error ended up.


Also I fixed your post.  That was a mess.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...