PC crashing

[Pixelfie]

For the past 2 weeks my PC keeps crashing and I'm not sure why. Sometimes it just freezes, sometimes it gives a black screen and sometimes it reboots. I've tried DDU, and ran some stability tests (Memtest86, Prime95 & 3DMark), all seems good. I've also tried disabling XMP. Thermals are fine too (CPU max 68c under load, GPU max 72c). It doesn't happen that often (maybe 2x a week), so it's pretty difficult to check stability.

 

This is what eventviewer says:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000109 (0xa39fe7df1268d6ba, 0xb3b6f46564e72271, 0xfffff803074cc000, 0x0000000000000001). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: f2a191db-1627-4bcd-b3a0-a7a11ba5294f.

 

i5-10400F

Palit RTX 2060 Dual

2x8gb HyperX Fury RGB 3200

Crucial MX500

Be Quiet! System Power 9 600w

Asrock B460M Pro4

Intel AX200 desktop kit

Windows 10 21H1

[Radium_Angel]

11 minutes ago, Pixelfie said:

A dump was saved in: C:\WINDOWS\MEMORY.DMP

Upload that file, and any other .dmp files you find, here, I can deconstruct them and see what's happening.

[Pixelfie]

9 minutes ago, Radium_Angel said:

Upload that file, and any other .dmp files you find, here, I can deconstruct them and see what's happening.

When I upload it to anything it says this

I've tried taking ownership of the file but it doesn't seem to work.

 

 

 

Edit: after copying it to the desktop I can now upload it. https://drive.google.com/file/d/1XNWoTb-RipeErpUJyimC8iFu-1aYEOcD/view

[Radium_Angel]

5 hours ago, Pixelfie said:

When I upload it to anything it says this

I've tried taking ownership of the file but it doesn't seem to work.

 

 

 

Edit: after copying it to the desktop I can now upload it. https://drive.google.com/file/d/1XNWoTb-RipeErpUJyimC8iFu-1aYEOcD/view

Ok, these are complete memory dumps which is fine, but google how to enable mini dumps, those are a tad more useful

[Radium_Angel]

Ok, here are the relevant parts of the dump. I'll post my thoughts afterwards.

___

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

BUGCHECK_CODE:  109

BUGCHECK_P1: a39fe7df1268d6ba

BUGCHECK_P2: b3b6f46564e72271

BUGCHECK_P3: fffff803074cc000

BUGCHECK_P4: 1

MEMORY_CORRUPTOR:  ONE_BIT
PROCESS_NAME:  csrss.exe

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

 

____

Ok, from a single crash dump it's difficult to say with certainty what is at fault, but it looks like we have a memory issue.

Now you say you've tested your RAM with memtest86, how long did you let it run for?

 

Aside from XMP (which seems to cause more issues that it solves) have you changed any RAM timings in the BIOS?

Is your BIOS up to date? Are your drivers up to date?

 

[Pixelfie]

2 hours ago, Radium_Angel said:

Ok, here are the relevant parts of the dump. I'll post my thoughts afterwards.

___

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

BUGCHECK_CODE:  109

BUGCHECK_P1: a39fe7df1268d6ba

BUGCHECK_P2: b3b6f46564e72271

BUGCHECK_P3: fffff803074cc000

BUGCHECK_P4: 1

MEMORY_CORRUPTOR:  ONE_BIT
PROCESS_NAME:  csrss.exe

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

 

____

Ok, from a single crash dump it's difficult to say with certainty what is at fault, but it looks like we have a memory issue.

Now you say you've tested your RAM with memtest86, how long did you let it run for?

 

Aside from XMP (which seems to cause more issues that it solves) have you changed any RAM timings in the BIOS?

Is your BIOS up to date? Are your drivers up to date?

 

I ran it at night, so about 8 hours

[Radium_Angel]

21 minutes ago, Pixelfie said:

I ran it at night, so about 8 hours

And the rest of my questions?

[Pixelfie]

13 minutes ago, Radium_Angel said:

And the rest of my questions?

Everything up to date. I did change the RAM timings, but it's been stable for 3 months before crashing so I don't know if that's the cause. Will set them a bit higher, maybe it will help but I can't do any test as it just happens randomly (usually 2x a week)

[Pixelfie]

On 7/4/2021 at 8:54 PM, Radium_Angel said:

Ok, here are the relevant parts of the dump. I'll post my thoughts afterwards.

___

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

BUGCHECK_CODE:  109

BUGCHECK_P1: a39fe7df1268d6ba

BUGCHECK_P2: b3b6f46564e72271

BUGCHECK_P3: fffff803074cc000

BUGCHECK_P4: 1

MEMORY_CORRUPTOR:  ONE_BIT
PROCESS_NAME:  csrss.exe

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

 

____

Ok, from a single crash dump it's difficult to say with certainty what is at fault, but it looks like we have a memory issue.

Now you say you've tested your RAM with memtest86, how long did you let it run for?

 

Aside from XMP (which seems to cause more issues that it solves) have you changed any RAM timings in the BIOS?

Is your BIOS up to date? Are your drivers up to date?

 

Still hasn't crashed after a week, so it's probably unstable timings. Thanks for your help!