Tweet
Everytime I try to play Albion online I get BSODs, no other game has this problem, when I first started playing it there was no issues at all, then one day BSODs started, according to research on the subject I updated all my drivers then everything was working again. Today I try to play and the BSODs have started again, as soon as I launch the ngame and its doing the Easy Anti Cheat" check is where it always crashes, I checked my drivers and theyre still up to date, I also uninstalled the game and reinstalled it, the BSODs still happen. I did a memtest and my RAM is fine. I also ran Whocrashed and this is what was found:
System Information (local)
Computer name: NEWNAMEK
Windows version: Windows 10, 10.0, version 2009, build: 19044
Windows dir: C:\Windows
Hardware: ASUS, ASUSTeK COMPUTER INC., ROG STRIX Z590-E GAMING WIFI
CPU: GenuineIntel 11th Gen Intel(R) Coreâ„¢ i9-11900K @ 3.50GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 68556591104 bytes (63.8GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 2/21/2022 11:06:17 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x139 (0x1D, 0xFFFF940FE7585F40, 0xFFFF940FE7585E98, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 11:06:17 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xD039)
Bugcheck code: 0x139 (0x1D, 0xFFFF940FE7585F40, 0xFFFF940FE7585E98, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\ntfs.sys
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT File System Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It’s suggested that you run CHKDSK.
On Mon 2/21/2022 10:30:00 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x4A (0x7FF81AE6CE54, 0x2, 0x0, 0xFFFFFC84C37D7440)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 10:13:05 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8030A28ADC0, 0xFFFFF8030DC54920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 10:09:14 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-7968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80378E8ADC0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 10:03:52 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80343E8A270, 0xFFFFAC8020EE2920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
System Information (local)
Computer name: NEWNAMEK
Windows version: Windows 10, 10.0, version 2009, build: 19044
Windows dir: C:\Windows
Hardware: ASUS, ASUSTeK COMPUTER INC., ROG STRIX Z590-E GAMING WIFI
CPU: GenuineIntel 11th Gen Intel(R) Coreâ„¢ i9-11900K @ 3.50GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 68556591104 bytes (63.8GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 2/21/2022 11:06:17 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x139 (0x1D, 0xFFFF940FE7585F40, 0xFFFF940FE7585E98, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 11:06:17 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xD039)
Bugcheck code: 0x139 (0x1D, 0xFFFF940FE7585F40, 0xFFFF940FE7585E98, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\ntfs.sys
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT File System Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It’s suggested that you run CHKDSK.
On Mon 2/21/2022 10:30:00 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x4A (0x7FF81AE6CE54, 0x2, 0x0, 0xFFFFFC84C37D7440)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 10:13:05 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8030A28ADC0, 0xFFFFF8030DC54920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 10:09:14 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-7968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80378E8ADC0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/21/2022 10:03:52 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022122-6765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F73B0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80343E8A270, 0xFFFFAC8020EE2920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Comment