Question My PC keeps BSODing alot. Help?

Nov 19, 2020
13
0
10
0
So after I Cleaned my pc out of its filth and dust with air I swapped out the ram sticks from 2x4gb 2666mhz corsair vengeance lpx to 2x8gb 2666mhz corsair vengeance lpx. But I started to encounter many BSOD's about 5 days after on boot up. The first BSOD's I got whilst launching my pc were all "ATTEMPTED_TO_WRITE_READONLY_MEMORY"
Then the next after a few of those a few days later I get a "KMODE_EXCEPTION_NOT_HANDLED" with what failed as dxgkrnl.sys . I also got "BAD_POOL_CALLLER". After bad pool thing I decided to factory reset my pc if it was buggy software as this time it had occurred whilst gaming. Then I got a few days later "MEMORY_MANAGEMENT" then whilst booting up "Recovery Error code: 0xc0000428". Then a "SYSTEM_SERVICE_EXCEPTION" whilst gaming. These happened multiple times whilst gaming over the past week with "CRITICAL_STRUCTURE_CORRUPTION" too. This morning I got "ATTEMPTED_TO_WRITE_READONLY_MEMORY" again and like 8 hours later after booting up my pc after getting home I get "CRITICAL_STRUCTURE_CORRUPTION" again after about 5 minutes of usage on my pc. I don't know what the issue is or how to fix it.
My pc is:
AMD Ryzen 5 2600 Six-Core Processor
EVGA RTX2060 XC 6gb
ASUS EX-A320M-GAMING motherboard
2x8gb Corsair Vengeance LPX 2666mhz ddr4
WD Green 240GB M.2 2280 SATA 3D NAND SSD/Solid State Drive
Seagate BarraCuda 1TB 3.5" SATA III Desktop HDD/Hard Drive
Corsair VS550
yeah thats it really idk what is wrong with my pc all i know is that it is bsod alot
 

shivababbli

Honorable
Apr 16, 2015
736
9
11,165
71
I did the 1gb test first to see what happens then once that hit 100% I did a few other 2gb tests and none came back with errors, although near the end my pc black screened for 5 seconds but came back to normal Do I keep running these or is my ram clear from the mess?
Did you check with passmark memtest
 
Nov 19, 2020
13
0
10
0
Did you check with passmark memtest
I havent done the passmark memtest yet as I havent had time but while booting my pc went into winre for some reason so i checked where it said a logifle was placed and it said this at the bottom of it:
Root cause found:
---------------------------
Boot critical file d:\windows\system32\ntoskrnl.exe is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x57
Time taken = 1703 ms

---------------------------
---------------------------
is this an issue thats ram aswell or is it something else?
 
Nov 19, 2020
13
0
10
0
***
  • *
  • Bugcheck Analysis * 11/16/20
  • *
***

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff8c8abb7bb0b0, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff80633475eff, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name
*** WARNING: Unable to verify checksum for win32k.sys

BUGCHECK_CODE: 50

BUGCHECK_P1: ffff8c8abb7bb0b0

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80633475eff

BUGCHECK_P4: 2

PROCESS_NAME: System

SYMBOL_NAME: nt!RtlDeleteNoSplay+4f

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: AV_INVALID_nt!RtlDeleteNoSplay

FAILURE_ID_HASH: {59bc1287-1489-a801-1af8-c2d45de5ce4f}

Followup: MachineOwner
---------

***
  • *
  • Bugcheck Analysis * 11/17/20
  • *
***

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

Debugging Details:
------------------


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8032eb3de5e

BUGCHECK_P3: fffffc031a04a070

BUGCHECK_P4: 0

PROCESS_NAME: MsMpEng.exe

SYMBOL_NAME: Ntfs!NtfsFindPrefixHashEntry+1ee

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

FAILURE_BUCKET_ID: 0x3B_c0000005_Ntfs!NtfsFindPrefixHashEntry

FAILURE_ID_HASH: {fd51bba6-3a1c-9f2a-cb88-7eed4d844386}

Followup: MachineOwner
---------

***
  • *
  • Bugcheck Analysis * 11/19/20 (7am)
  • *
***

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: a3a008642918d552, Reserved
Arg2: b3b714ea7b971de6, Reserved
Arg3: fffff806582b06e0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

BUGCHECK_CODE: 109

BUGCHECK_P1: a3a008642918d552

BUGCHECK_P2: b3b714ea7b971de6

BUGCHECK_P3: fffff806582b06e0

BUGCHECK_P4: 1

PROCESS_NAME: System

SYMBOL_NAME: nt!HalpTimerConvertAuxiliaryCounterToPerformanceCounter+0

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: 0x109_1_nt!HalpTimerConvertAuxiliaryCounterToPerformanceCounter

FAILURE_ID_HASH: {b79d61bd-39ee-db76-20d9-65328a524e8b}

Followup: MachineOwner
---------

***
  • *
  • Bugcheck Analysis * 11/19/20 (4pm)
  • *
***

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffe6a523bace88, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: fffff48f6e98e8d0, (reserved)
Arg4: 000000000000000a, (reserved)

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

BUGCHECK_CODE: be

BUGCHECK_P1: ffffe6a523bace88

BUGCHECK_P2: 8a00000000200121

BUGCHECK_P3: fffff48f6e98e8d0

BUGCHECK_P4: a

PROCESS_NAME: System

SYMBOL_NAME: nt!MiRaisedIrqlFault+1bf460

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: 0xBE_nt!MiRaisedIrqlFault

FAILURE_ID_HASH: {1c5b4d11-09e0-def3-d2d0-70a11d69b92d}

Followup: MachineOwner
---------


These are the 4 minidumps i have since after factory reset
 
Nov 19, 2020
13
0
10
0
It definitely is your ram
Summary
Report Date2020-11-21 16:43:15
Generated byMemTest86 V8.4 Free (64-bit)
ResultPASS
System Information
EFI Specifications2.60
System
ManufacturerSystem manufacturer
Product NameSystem Product Name
VersionSystem Version
Serial NumberSystem Serial Number
BIOS
VendorAmerican Megatrends Inc.
Version5602
Release Date07/14/2020
Baseboard
ManufacturerASUSTeK COMPUTER INC.
Product NameEX-A320M-GAMING
VersionRev X.0x
Serial Number181140080100289
CPU TypeAMD Ryzen 5 2600 Six-Core
CPU Clock3414 MHz [Turbo: 3916.4 MHz]
# Logical Processors12
L1 Cache12 x 96K (86973 MB/s)
L2 Cache12 x 512K (73021 MB/s)
L3 Cache1 x 16384K (30398 MB/s)
Memory16332M (16288 MB/s)
DIMM Slot #08GB DDR4 XMP PC4-21300
Corsair / CMK16GX4M2A2666C16
16-18-18-35 / 2666 MHz / 1.200V
DIMM Slot #18GB DDR4 XMP PC4-21300
Corsair / CMK16GX4M2A2666C16
16-18-18-35 / 2666 MHz / 1.200V
Result summary
Test Start Time2020-11-21 13:23:12
Elapsed Time3:18:27
Memory Range Tested0x0 - 41F380000 (16883MB)
CPU Selection ModeParallel (All CPUs)
ECC PollingEnabled
# Tests Passed48/48 (100%)
Test# Tests PassedErrors
Test 0 [Address test, walking ones, 1 CPU]4/4 (100%)0
Test 1 [Address test, own address, 1 CPU]4/4 (100%)0
Test 2 [Address test, own address]4/4 (100%)0
Test 3 [Moving inversions, ones & zeroes]4/4 (100%)0
Test 4 [Moving inversions, 8-bit pattern]4/4 (100%)0
Test 5 [Moving inversions, random pattern]4/4 (100%)0
Test 6 [Block move, 64-byte blocks]4/4 (100%)0
Test 7 [Moving inversions, 32-bit pattern]4/4 (100%)0
Test 8 [Random number sequence]4/4 (100%)0
Test 9 [Modulo 20, ones & zeros]4/4 (100%)0
Test 10 [Bit fade test, 2 patterns, 1 CPU]4/4 (100%)0
Test 13 [Hammer test]4/4 (100%)0

thats my memtest86 thing, no errors. What could be causing my Bsod?
 
Nov 19, 2020
13
0
10
0
I was just thinking the memtest result says you have ram in slots 0 and 1. Are you sure that is the correct way to install 2 dimms for your motherboard? I think it is more usual to install in slots 0 and 2 or 1 and 3
They are in A1 and B1, but my uncle said for me to put them in A2 and B2 as he did more digging and found the manual for the asus motherboard, The image there shows A1 B1 doesn't it?
 

ASK THE COMMUNITY

TRENDING THREADS