Game crashing computer on start-up

[Pyropup55]

I need some help please. I recently rebuilt my pc, did a fresh install of windows (x3 times so far trying to fix this issue. The first error I would get was a BSOD with the error "unexpected_kernal_mode_trap" and my pc would reboot. I've run chkdsk and a few other win commands, rolled back to win version 23h2. Now I can at least get in game, but after about 5 - 10 seconds, it crashes my pc with no shown error message. I've uninstalled, verified files numerous times. The game is on an ssd with plenty of space on it. I just want to be able to play scum again, I was almost at 2,000 hours into it.

PC Specs:
CPU - AMD 9800x3d
GPU - RTX 3080 ftw3
RAM - 64 g DDR5
1200W PSU
10 TB storage (all ssds)

Scum is the only game I can't play. Everything else installed runs flawlessly.

[marktkm]

I'm not overly familiar with Windows 11, but that sounds like a rather low level error. Is anything being written to the 'Crashes folder?

C:\Users\%Username%\AppData\Local\SCUM\Saved

If so you might want to upload it to somewhere like google drive so the devs can have a look. If there's nothing there due to the re-installations you could let it crash a few times to generate the file.

You might also find some information following the basic blue screen steps from Microsoft:

https://support.microsoft.com/en-US/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6

[Pyropup55]

Originally posted by marktkm:

I'm not overly familiar with Windows 11, but that sounds like a rather low level error. Is anything being written to the 'Crashes folder?

C:\Users\%Username%\AppData\Local\SCUM\Saved

If so you might want to upload it to somewhere like google drive so the devs can have a look. If there's nothing there due to the re-installations you could let it crash a few times to generate the file.

You might also find some information following the basic blue screen steps from Microsoft:

https://support.microsoft.com/en-US/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6

As of right now, I think I've gotten the bsod taken care of, I'll check for crash logs and see if there's anything in there. Thanks.

[Deathwhisper]

Hello :),

The best thing to do with a BSOD is to consult the Windows logs to find out what caused the crash.

BSODs can have a wide variety of possible causes, which makes it more difficult to identify the exact cause. Therefore, the Windows logs are the best option.

You can find a description of how to do this here [www.howtogeek.com].

[xKiCkx]

Originally posted by Deathwhisper:

Hello :),

The best thing to do with a BSOD is to consult the Windows logs to find out what caused the crash.

BSODs can have a wide variety of possible causes, which makes it more difficult to identify the exact cause. Therefore, the Windows logs are the best option.

You can find a description of how to do this here [www.howtogeek.com].

That would be best to check, also just curious, what changes did you make to take care of the BSOD?

[Pyropup55]

Originally posted by xKiCkx:

Originally posted by Deathwhisper:

Hello :),

The best thing to do with a BSOD is to consult the Windows logs to find out what caused the crash.

BSODs can have a wide variety of possible causes, which makes it more difficult to identify the exact cause. Therefore, the Windows logs are the best option.

You can find a description of how to do this here [www.howtogeek.com].

That would be best to check, also just curious, what changes did you make to take care of the BSOD?

Well I thought the BSOD was gone. I took a look at the minidump when it BSODed again trying to launch Scum. It looks like it's all pointing to EasyAntiCheat. This is what the minidump file said.
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffc681b7de1e70
Arg3: ffffe80803c30fe0
Arg4: fffff8067bc2ec41

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 593

Key : Analysis.Elapsed.mSec
Value: 1428

Key : Analysis.IO.Other.Mb
Value: 20

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 31

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007f

Key : Bugcheck.Code.TargetModel
Value: 0x1000007f

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x7f_8_EasyAntiCheat_EOS!unknown_function

Key : Failure.Hash
Value: {9d5b0e91-8976-ce0a-e55f-fa940c7a1997}


BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffc681b7de1e70

BUGCHECK_P3: ffffe80803c30fe0

BUGCHECK_P4: fffff8067bc2ec41

FILE_IN_CAB: 012725-15828-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

FAULTING_THREAD: ffffd80a15a79080

STACK_OVERFLOW: Stack Limit: ffffe80803c31000. Use (kF) and (!stackusage) to investigate stack usage.

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe808`03c30fe0 fffff806`7bc2e768 : fffff806`7ba00000 fffff806`7bc2da5f ffffe808`03c31670 fffff806`7bad33a0 : nt!RtlpUnwindPrologue+0x111
ffffe808`03c310b0 fffff806`7bc2db17 : 00000000`00000000 ffffe808`03c32b00 fffff806`7bc2da5f fffff806`7bad33a0 : nt!RtlpxVirtualUnwind+0x108
ffffe808`03c31170 fffff806`7bdd171b : fffff806`e07a9c64 ffffe808`00000001 ffffe808`03c32b00 ffffe808`03c38000 : nt!RtlUnwindEx+0x1f7
ffffe808`03c318a0 fffff806`7be205b2 : ffffe808`03c328c8 ffffe808`03c31ea0 ffffe808`03c32800 fffff806`e010c5b9 : nt!_C_specific_handler+0xeb
ffffe808`03c31910 fffff806`7bc2cc93 : 00000000`0010000b ffffe808`03c328c8 fffff806`e010c5b9 fffff806`df481478 : nt!RtlpExecuteHandlerForException+0x12
ffffe808`03c31940 fffff806`7bd1817e : ffffffff`ffffffff ffffe808`03c32970 ffffe808`03c32970 ffffe808`03c320e0 : nt!RtlDispatchException+0x2f3
ffffe808`03c320b0 fffff806`7be2af7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1ae
ffffe808`03c32790 fffff806`7be22442 : fd6a6777`fabb8e29 f818856b`f7ee88c3 fb31563e`f2909f6f ffffffff`9dab9d05 : nt!KiExceptionDispatch+0x13c
ffffe808`03c32970 fffff806`e010c5b9 : 00000000`00000000 00000000`00000000 0000ffff`f8067be1 00000050`00000000 : nt!KiDivideErrorFault+0x342
ffffe808`03c32b00 00000000`00000000 : 00000000`00000000 0000ffff`f8067be1 00000050`00000000 000001ff`00000000 : EasyAntiCheat_EOS+0xe8c5b9


SYMBOL_NAME: EasyAntiCheat_EOS+e8c5b9

MODULE_NAME: EasyAntiCheat_EOS

IMAGE_NAME: EasyAntiCheat_EOS.sys

STACK_COMMAND: .process /r /p 0xffffd809ec9cd040; .thread 0xffffd80a15a79080 ; kb

BUCKET_ID_FUNC_OFFSET: e8c5b9

FAILURE_BUCKET_ID: 0x7f_8_EasyAntiCheat_EOS!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9d5b0e91-8976-ce0a-e55f-fa940c7a1997}

Followup: MachineOwner

[xKiCkx]

I'm not to sure what exactly might be causing this issue, when did the issue start to happen? Is this something that recently started to happen and was there any updates on the windows that might of caused it?

[Pyropup55]

Originally posted by xKiCkx:

I'm not to sure what exactly might be causing this issue, when did the issue start to happen? Is this something that recently started to happen and was there any updates on the windows that might of caused it?

It started when I built my new pc. Previously the game ran flawlessly. I upgraded everything, minus the gpu. When I first launched the game, it worked fine. Windows updated, then that's when it started. I reverted back to the previous version because I was seeing a lot of people were having issues with easy anticheat and the latest windows update 24h2. I was able to launch the game, ran fine for about 10 mins. Then the next day is when all the BSOD started happening again.

[Pyropup55]

It looks like it's any game with EAC right now. I tried installing Sea of Thieves which uses EAC and had the exact same issue

[xKiCkx]

Huh, not sure what exactly is the reason for this, we didn't have any threads beside this one about the BSOD issue with EAC, I know that some older versions had that issue, perhaps it would be good to deinstall it from the PC manually and remove all residue files and see if pulling it again with SCUM will help in that case.

[Pyropup55]

Originally posted by xKiCkx:

Huh, not sure what exactly is the reason for this, we didn't have any threads beside this one about the BSOD issue with EAC, I know that some older versions had that issue, perhaps it would be good to deinstall it from the PC manually and remove all residue files and see if pulling it again with SCUM will help in that case.

I'll give it a shot, it sucks, I haven't been able to play in almost a month lol

[xKiCkx]

Originally posted by Pyropup55:

Originally posted by xKiCkx:

Huh, not sure what exactly is the reason for this, we didn't have any threads beside this one about the BSOD issue with EAC, I know that some older versions had that issue, perhaps it would be good to deinstall it from the PC manually and remove all residue files and see if pulling it again with SCUM will help in that case.

I'll give it a shot, it sucks, I haven't been able to play in almost a month lol

Hope it will work out

[Pyropup55]

Well I couldn't get it figured out at all, ended wiping and going back to windows 10, and it's been flawless.

[xKiCkx]

Originally posted by Pyropup55:

Well I couldn't get it figured out at all, ended wiping and going back to windows 10, and it's been flawless.

So win11 has caused the issues here?

[Pyropup55]

Originally posted by xKiCkx:

Originally posted by Pyropup55:

Well I couldn't get it figured out at all, ended wiping and going back to windows 10, and it's been flawless.

So win11 has caused the issues here?

Sorry I didn't see the notification. I believe it had to do with something left over from 24h2 update, even though I rolled it back, I think something was left behind. I installed win 10 and the game played fine, installed win 11 23h2 and the game has been running great as well.

[xKiCkx]

Originally posted by Pyropup55:

Originally posted by xKiCkx:

So win11 has caused the issues here?

Sorry I didn't see the notification. I believe it had to do with something left over from 24h2 update, even though I rolled it back, I think something was left behind. I installed win 10 and the game played fine, installed win 11 23h2 and the game has been running great as well.

Thank you for letting us know :)