This game can cause BSOD (Bluescreen)

[SJang]

I am having BSOD only when playing C:S2. Also checked the dump file with WinDBG, it happens like this.


SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff803a0863dcb, Address of the instruction which caused the BugCheck
Arg3: ffffb2092cb06080, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.



BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff803a0863dcb

BUGCHECK_P3: ffffb2092cb06080

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21800

CONTEXT: ffffb2092cb06080 -- (.cxr 0xffffb2092cb06080)
rax=000002519b0c0003 rbx=fffff80331e4fd00 rcx=00000216ed8c0004
rdx=ffffa10cf314fb20 rsi=0000000000000000 rdi=00000216ed8c0004
rip=fffff803a0863dcb rsp=ffffb2092cb06ad0 rbp=0000000000000000
r8=ffffa10cf314fb20 r9=0000000000000000 r10=fffff80331e4fd00
r11=00000216ed8c0004 r12=0000000000000000 r13=ffffa10cd323a500
r14=ffffa10cdcadbca0 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!ExpInterlockedPushEntrySList+0x1b:
fffff803`a0863dcb 4d8903 mov qword ptr [r11],r8 ds:002b:00000216`ed8c0004=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Cities2.exe

STACK_TEXT:
ffffb209`2cb06ad0 fffff803`a055e37c : fffff803`31e50580 fffff803`a058c4f5 ffffa10c`f3cb237c fffff803`a058eeb3 : nt!ExpInterlockedPushEntrySList+0x1b
ffffb209`2cb06ae0 fffff803`31e6ba18 : fffff803`31e50380 fffff803`31e6c414 00000000`00000210 ffff8d87`b68cedf0 : nt!ExFreeToNPagedLookasideList+0x4c
ffffb209`2cb06b20 fffff803`a0428a4e : 00000000`00000000 ffffa10c`dcadbca0 ffffa10c`d323a500 ffffa10c`f3cb2310 : FLTMGR!FltpCreateFileNameInformation+0x118
ffffb209`2cb06bb0 fffff803`31e6b837 : 00000000`00000000 ffffa10c`dee06b01 ffffa10c`f3cb2350 fffff803`a0425899 : nt!KeAbPostReleaseEx+0xae
ffffb209`2cb06bf0 fffff803`31e1e3b9 : ffffa10c`f3cb2310 ffffa10c`dcadb010 ffffa10c`dcadbca0 00000000`00000000 : FLTMGR!CreateTemporaryFileNameInformation+0x37
ffffb209`2cb06c50 fffff803`31e1c678 : 00000000`00000000 ffffa10c`f3cb2310 ffffb209`2cb06d90 00000000`00000000 : FLTMGR!HandleStreamListNotSupported+0x69
ffffb209`2cb06c90 fffff803`31e1db40 : ffffa10c`f34f5648 00000000`00000000 ffffa10c`dcadb010 00000000`00000000 : FLTMGR!FltpGetFileNameInformation+0x3d8
ffffb209`2cb06de0 fffff803`4fe3e275 : ffffa10c`f3cb2310 ffffa10c`00000102 00000000`00000000 ffffa10c`f34f5648 : FLTMGR!FltGetFileNameInformation+0x1c0
ffffb209`2cb06e70 fffff803`31e180a9 : ffffa10c`f34f5560 ffffa10c`90001018 ffffa10c`f34f5560 00000000`00000000 : wcifs!WcPreNetworkQueryOpen+0x95
ffffb209`2cb06ef0 fffff803`31e1946a : ffffb209`2cb07200 00000000`00000100 ffffa10c`d2e0a800 00000000`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x409
ffffb209`2cb070e0 fffff803`31e7b16a : ffffb209`2cb01000 00000000`00000000 00000000`00000000 00000000`00000000 : FLTMGR!FltpPassThroughFastIo+0xda
ffffb209`2cb071d0 fffff803`a0b93def : ffffa10c`d31e7b10 ffffb209`2cb077c0 00000000`d2ff0000 ffffa10c`f1df3aa0 : FLTMGR!FltpFastIoQueryOpen+0x16a
ffffb209`2cb07260 fffff803`a0cb733d : 00000000`00000000 ffff8d87`9c235745 00000000`00000000 ffffb209`2cb07910 : nt!IopQueryInformation+0x9f
ffffb209`2cb072d0 fffff803`a0a48ac9 : ffffa10c`f29d4aa0 ffff8d87`9c2357a0 ffff8d87`9c2357a0 ffffb209`2cb076a8 : nt!IopParseDevice+0x181dad
ffffb209`2cb07470 fffff803`a0a46a11 : ffffa10c`f07b3801 ffffb209`2cb076a8 ffffa10c`00000040 ffffa10c`c47c8b50 : nt!ObpLookupObjectName+0xdd9
ffffb209`2cb07620 fffff803`a0b5af22 : ffffa10c`00000000 ffffa10c`c47c8b50 00000000`00000001 00000000`00000001 : nt!ObOpenObjectByNameEx+0x201
ffffb209`2cb07770 fffff803`a086e755 : 00000000`5e0b0c0e ffffa10c`dc50c080 ffffa10c`dc50c080 000000c8`56afec30 : nt!NtQueryFullAttributesFile+0x1c2
ffffb209`2cb07a20 00007ffc`53f445e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000c8`56afe6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`53f445e4

[MaGicBush]

No the game didn't cause this.

[peterslee9]

Code reads

Post win update -
Display driver

>Update Win
>Verify CSII files lib

Reload game



And see, there they go again,
"this game can cause"
Uh, no.
A common win system refresh.

[Silencer]

c0000005 is related to the calls that return values from memory. It expects a certain value but is getting another due to a fault or error in transit.

Most cases this is tied to an unstable RAM kit or worse a weak or faulty memory controller.

[peterslee9]

Could be.
Unlikely.
BLACKBOX

[vfr]

It's very likely cased by RAM error. Very likely. I suggest you run a memory check utility.

[AIRwolf79]

Its nothing to do with your hardware mate. Its just a very poorly optimised game. Put together by a only 30 amateurs. You can spend thousands on new hardware and get the same results. I never have any issues like I do with cs2 on any other game.

[MaGicBush]

BSODs cannot be caused by games lmao. I wont buy this game as it seems horrible, but I also wont blindly accept a lie. This game did not cause that specific issue. My reasoning is 30 years in Tech support, and not once has a BSOD ever been caused by a game on any of my calls even when a CU gets irate thinking a game or some software caused it. It's always some hardware component failing or a driver issue.

[sams19]

Originally posted by MaGicBush:

BSODs cannot be caused by games lmao. I wont buy this game as it seems horrible, but I also wont blindly accept a lie. This game did not cause that specific issue. My reasoning is 30 years in Tech support, and not once has a BSOD ever been caused by a game on any of my calls even when a CU gets irate thinking a game or some software caused it. It's always some hardware component failing or a driver issue.

IDK what tech support you do but maybe you should find another field.

[ekin]

Originally posted by MaGicBush:

BSODs cannot be caused by games lmao.

Don't make ♥♥♥♥ up. A game can cause BSOD like any other software.

Originally posted by MaGicBush:

I wont buy this game as it seems horrible, but I also wont blindly accept a lie. This game did not cause that specific issue. My reasoning is 30 years in Tech support, and not once has a BSOD ever been caused by a game on any of my calls even when a CU gets irate thinking a game or some software caused it. It's always some hardware component failing or a driver issue.

It is true that BSOD might be caused by hardware or driver issues, but that is not necessarily always the case. I would expect better from "30 years of tech support."

The problem here is clearly a null pointer exception. The "mov qword ptr [r11],r8" instruction says store the value in r8 (register 8) into the memory address pointed by r11; however it seems that register 11 doesn't have a valid memory address; i.e. the value is zero.

This is a textbook software issue, and has NOTHING to do with memory.

[MaGicBush]

Originally posted by Awesomes007:

Originally posted by MaGicBush:

My reasoning is 30 years in Tech support

It's always some hardware component failing or a driver issue.

Hard pass on your anecdotal "evidence" and across the board absolutes.

https://stackoverflow.com/a/1588560

Cool. You do you. Any person in tech would agree with me however. I like how the people responding have private profiles. I don't give a ♥♥♥♥ what you all think on here. I know what I know from experience and a 4 year bachelor degree.

[ekin]

Originally posted by MaGicBush:

Originally posted by Awesomes007:

Hard pass on your anecdotal "evidence" and across the board absolutes.

https://stackoverflow.com/a/1588560

Cool. You do you. Any person in tech would agree with me however.

I am a computer engineer and I just wrote about how you are wrong. I even explained the error in detail.

[MaGicBush]

Originally posted by mehmeteking:

Originally posted by MaGicBush:

Cool. You do you. Any person in tech would agree with me however.

I am a computer engineer and I just wrote about how you are wrong. I even explained the error in detail.

No you did no such thing. The OP should run a memory test before jumping to any conclusions. If it's faulty memory it wont read/write correctly which could provide such an error. Hell a bad PSU could even cause that error if the voltages messed up at the wrong time as it tried to read/write.

I'd run a memtest, and check your PSU and MB before assuming it's software. There is no reason for a game developer to ever write code on the OS/driver layer so it's hardly ever just a software issue.

[ekin]

Originally posted by MaGicBush:

Originally posted by mehmeteking:

I am a computer engineer and I just wrote about how you are wrong. I even explained the error in detail.

No you did no such thing. The OP should run a memory test before jumping to any conclusions. If it's faulty memory it wont read/write correctly which could provide such an error. Hell a bad PSU could even cause that error if the voltages messed up at the wrong time as it tried to read/write.

I'd run a memtest, and check your PSU and MB before assuming it's software. There is no reason for a game to ever write code on the OS/driver layer so it's hardly ever just a software issue.

Wtf are you talking about? Did you not even read the message? The instruction being run doesn't even check any memory address because it can't. The REGISTER has invalid value (which is 0)... Dude, FFS... A memory fault would show up as a checksum error, not a f*ing null pointer in a register.

[MaGicBush]

Originally posted by mehmeteking:

Originally posted by MaGicBush:

No you did no such thing. The OP should run a memory test before jumping to any conclusions. If it's faulty memory it wont read/write correctly which could provide such an error. Hell a bad PSU could even cause that error if the voltages messed up at the wrong time as it tried to read/write.

I'd run a memtest, and check your PSU and MB before assuming it's software. There is no reason for a game to ever write code on the OS/driver layer so it's hardly ever just a software issue.

Wtf are you talking about? Did you not even read the message? The instruction being run doesn't even check any memory address because it can't. The REGISTER has invalid value (which is 0)... Dude, FFS... A memory fault would show up as a checksum error, not a f*ing null pointer in a register.

Come back when you actually have a degree or know what YOU are talking about lol.

[ekin]

Originally posted by MaGicBush:

Originally posted by mehmeteking:

Wtf are you talking about? Did you not even read the message? The instruction being run doesn't even check any memory address because it can't. The REGISTER has invalid value (which is 0)... Dude, FFS... A memory fault would show up as a checksum error, not a f*ing null pointer in a register.

Come back when you actually have a degree or know what YOU are talking about lol.

I AM a computer engineer since 2008, and been doing software engineering since then. Of course, us engineers don't do "tech support" so don't know what your diploma says but it is probably some IT stuff :)

I literally explained to you in very clear terms how the specific assembly instruction failed, and how it is not memory related. If you cannot understand it, then I suggest do everyone a favour and find another job.