Hey, I experienced a BSOD and from the crash dump generated by windows 10 and the cause seems to be factorio!
Code: Select all
2: 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: fffff8040aeb4ec9, Address of the instruction which caused the BugCheck
Arg3: fffff2853c291d80, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 31523
Key : Analysis.IO.Other.Mb
Value: 6
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 32
Key : Analysis.Init.CPU.mSec
Value: 718
Key : Analysis.Init.Elapsed.mSec
Value: 32990
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.DumpHeader
Value: 0x3b
Key : Bugcheck.Code.Register
Value: 0x3b
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
FILE_IN_CAB: 031723-11031-01.dmp
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff8040aeb4ec9
BUGCHECK_P3: fffff2853c291d80
BUGCHECK_P4: 0
CONTEXT: fffff2853c291d80 -- (.cxr 0xfffff2853c291d80)
rax=00000000000000b4 rbx=00000026b96f4dc0 rcx=00000026b96f5000
rdx=fffff8040a800000 rsi=0000000000000001 rdi=0000000000000040
rip=fffff8040aeb4ec9 rsp=fffff2853c292780 rbp=fffff2853c292b80
r8=0000000000000003 r9=0000000000000000 r10=0000000000000000
r11=fffff2853c292ab8 r12=0000000000000001 r13=0000000000000004
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
nt!ExpQuerySystemInformation+0x189:
fffff804`0aeb4ec9 0000 add byte ptr [rax],al ds:002b:00000000`000000b4=??
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: factorio.exe
MISALIGNED_IP:
nt!ExpQuerySystemInformation+189
fffff804`0aeb4ec9 0000 add byte ptr [rax],al
STACK_TEXT:
fffff285`3c292780 fffff804`0aeb4bf7 : ffff4f94`c696d6dc 00000000`00000000 ffff4f94`c696d6dc 00000000`00000001 : nt!ExpQuerySystemInformation+0x189
fffff285`3c292ac0 fffff804`0ac0d8f8 : ffffaf89`d7ae0000 0000015b`23ef5d74 00000000`00000020 00000000`00000000 : nt!NtQuerySystemInformation+0x37
fffff285`3c292b00 00007fff`3af6d784 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000026`b96f4d88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`3af6d784
SYMBOL_NAME: nt!ExpQuerySystemInformation+189
IMAGE_VERSION: 10.0.19041.2728
STACK_COMMAND: .cxr 0xfffff2853c291d80 ; kb
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD.sys
FAILURE_BUCKET_ID: IP_MISALIGNED_AuthenticAMD.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {716d112a-8330-4bbb-160c-ec98297019d2}
Followup: MachineOwner
Sorry that I didn't mention it in my original post but I did that as people who had had the same BSOD error code said that it could be the source and/or updating outdated drivers could fix it. As such I have already checked all of my drivers and have made sure to be up to date with all of them! As I said in my previous reply I will run memtest during the night and also most likely reset my CMOS while at it I will make sure to check every cable and make sure that nothing has a loose connection. Tho thanks for pointing out that the application might be unlikely to be the true source of it and it might simply be something which "triggers" the error causing the crashFuryoftheStars wrote: Fri Mar 17, 2023 4:58 pm Make sure Windows and all drivers are fully up to date, too. BSODs are typically not the application itself, but rather something in the underlying OS or drivers that it was depending on.
The process name isn't the cause, just whatever process the code that faulted was running under. What you actually want is the image name:ArrowFX wrote: Fri Mar 17, 2023 12:59 pm Hey, I experienced a BSOD and from the crash dump generated by windows 10 and the cause seems to be factorio!
That's what specifically caused the BSOD. It's an AMD driver, either graphics or chipset. Could be a bad driver, could be memory corruption.IMAGE_NAME: AuthenticAMD.sys
lyvgbfh wrote: Sat Mar 18, 2023 6:54 am Your dump seems to indicate memory corruption. Can you make sure any overclock and especially XMP are disabled in your BIOS? It may also be prudent to run memtest overnight.
Seems to be caused by memory corruption as memtest failed. Thanks for all the help!Silari wrote: Fri Mar 17, 2023 11:37 pmThe process name isn't the cause, just whatever process the code that faulted was running under. What you actually want is the image name:ArrowFX wrote: Fri Mar 17, 2023 12:59 pm Hey, I experienced a BSOD and from the crash dump generated by windows 10 and the cause seems to be factorio!
That's what specifically caused the BSOD. It's an AMD driver, either graphics or chipset. Could be a bad driver, could be memory corruption.IMAGE_NAME: AuthenticAMD.sys
