C
Customcrust
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fd65dfd28d643, Reserved
Arg2: b3b6e2e44fa71ee9, Reserved
Arg3: fffff8003aeffde0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 5
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-6QMMSG6
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 5
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 109
BUGCHECK_P1: a39fd65dfd28d643
BUGCHECK_P2: b3b6e2e44fa71ee9
BUGCHECK_P3: fffff8003aeffde0
BUGCHECK_P4: 1
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
STACK_TEXT:
ffffd08f`96724e98 00000000`00000000 : 00000000`00000109 a39fd65d`fd28d643 b3b6e2e4`4fa71ee9 fffff800`3aeffde0 : nt!KeBugCheckEx
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8003af000e0-fffff8003af000e3 4 bytes - nt!EtwpGetAutoLoggerLevelKwFilter+300
[ 24 28 01 e8:90 22 84 11 ]
fffff8003af000e7 - nt!EtwpGetAutoLoggerLevelKwFilter+307 (+0x07)
[ ff:df ]
5 errors : !nt (fffff8003af000e0-fffff8003af000e7)
SYMBOL_NAME: nt!EtwpGetAutoLoggerLevelKwFilter+0
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.836
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 0
FAILURE_BUCKET_ID: 0x109_1_nt!EtwpGetAutoLoggerLevelKwFilter
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5d3bc76c-14e4-e42f-b94d-f0702ecccd0b}
Followup: MachineOwner
---------
Here is the dump analysis for the most recent crash. Happens at any state of operation, if computer is sitting idle or running a program. If there is anyone who can help it would be much appreciated. New PC build.
just based of a little bit of reading similar problems i have tried:
updating all drivers. have updated chipset drivers. havent updated bios yet. have disabled c-states in bios.
EDIT: BIOS has been updated
ASUS x570 prime mobo
2x corsair vengeance rgb pro 16gb 3200mhz RAM
amd ryzen 7 3700x
h100i rgb platinum cpu cooler
zotac gtx 2060 super amp extreme
boots from crucial m.2 1tb ssd
650W silverstone PSU
Continue reading...
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fd65dfd28d643, Reserved
Arg2: b3b6e2e44fa71ee9, Reserved
Arg3: fffff8003aeffde0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 5
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-6QMMSG6
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 5
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 109
BUGCHECK_P1: a39fd65dfd28d643
BUGCHECK_P2: b3b6e2e44fa71ee9
BUGCHECK_P3: fffff8003aeffde0
BUGCHECK_P4: 1
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
STACK_TEXT:
ffffd08f`96724e98 00000000`00000000 : 00000000`00000109 a39fd65d`fd28d643 b3b6e2e4`4fa71ee9 fffff800`3aeffde0 : nt!KeBugCheckEx
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8003af000e0-fffff8003af000e3 4 bytes - nt!EtwpGetAutoLoggerLevelKwFilter+300
[ 24 28 01 e8:90 22 84 11 ]
fffff8003af000e7 - nt!EtwpGetAutoLoggerLevelKwFilter+307 (+0x07)
[ ff:df ]
5 errors : !nt (fffff8003af000e0-fffff8003af000e7)
SYMBOL_NAME: nt!EtwpGetAutoLoggerLevelKwFilter+0
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.836
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 0
FAILURE_BUCKET_ID: 0x109_1_nt!EtwpGetAutoLoggerLevelKwFilter
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5d3bc76c-14e4-e42f-b94d-f0702ecccd0b}
Followup: MachineOwner
---------
Here is the dump analysis for the most recent crash. Happens at any state of operation, if computer is sitting idle or running a program. If there is anyone who can help it would be much appreciated. New PC build.
just based of a little bit of reading similar problems i have tried:
updating all drivers. have updated chipset drivers. havent updated bios yet. have disabled c-states in bios.
EDIT: BIOS has been updated
ASUS x570 prime mobo
2x corsair vengeance rgb pro 16gb 3200mhz RAM
amd ryzen 7 3700x
h100i rgb platinum cpu cooler
zotac gtx 2060 super amp extreme
boots from crucial m.2 1tb ssd
650W silverstone PSU
Continue reading...