Random BSODs everyday, help

Question

Hi, I got my new pc and installed w10 from official Microsoft page but I'm constantly getting random blue screens and I don't know why, I got almost all blue screens, IRQL_NOT_LESS_OR_EQUAL, ATTEMPTED_WRITE_TO_READONLY_MEMORY_SITE, KERNEL_SECURITY_CHECK_FAILURE, UNEXPECTED_KERNEL_MODE_TRAP and others.

Things I already did:

_Ran sfc/scannow

_Ran DISM check thing

_Ran Memory diagnostic tool

And everything was fine, also my hardware is NEW, like, NEW, from factory.

Please help I don't know what to do anymore.

Also my drivers are all updated and the OS is updated with windows update.

I also opened the MEMORY.DMP doc with WinDbg and this is that it said when clicked "!analyze -v"

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: ffffe57906774768, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: ffff87021dc97860, (reserved)
Arg4: 000000000000000a, (reserved)

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3015

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3053

    Key  : Analysis.Init.CPU.mSec
    Value: 1452

    Key  : Analysis.Init.Elapsed.mSec
    Value: 11748

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 93

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xbe

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xbe

    Key  : Bugcheck.Code.Register
    Value: 0xbe

    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:  MEMORY.DMP

BUGCHECK_CODE:  be

BUGCHECK_P1: ffffe57906774768

BUGCHECK_P2: 8a00000000200121

BUGCHECK_P3: ffff87021dc97860

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  ffff87021dc97860 -- (.trap 0xffff87021dc97860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe30000000000 rbx=0000000000000000 rcx=ffff87021dc97a10
rdx=0000000ffffffad6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80772883840 rsp=ffff87021dc979f0 rbp=fffff80773250b80
 r8=0000003000000000  r9=ffffe60000007030 r10=0000000fffffffff
r11=fffffff000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiEmptyDecayClusterTimers+0x150:
fffff807`72883840 f0480fba6e183f  lock bts qword ptr [rsi+18h],3Fh ds:00000000`00000018=????????????????
Resetting default scope

STACK_TEXT:  
ffff8702`1dc97668 fffff807`72a771a4     : 00000000`000000be ffffe579`06774768 8a000000`00200121 ffff8702`1dc97860 : nt!KeBugCheckEx
ffff8702`1dc97670 fffff807`72839acf     : 8a000000`00200121 00000000`00000003 ffff8702`1dc978e0 00000000`00000000 : nt!MiRaisedIrqlFault+0x142d18
ffff8702`1dc976c0 fffff807`72a0715e     : 00000000`0000000f fffff807`72844d7c ffffe3ca`8b196de8 ffff9d01`d0dd7180 : nt!MmAccessFault+0x4ef
ffff8702`1dc97860 fffff807`72883840     : 00000000`00000002 ffffe300`06776520 ffffe600`0000818a ffffe600`0000818a : nt!KiPageFault+0x35e
ffff8702`1dc979f0 fffff807`72883f65     : fffff807`00000003 fffff807`73250b80 00000000`00000000 ffffc083`0ea4b010 : nt!MiEmptyDecayClusterTimers+0x150
ffff8702`1dc97a60 fffff807`729b6f57     : 00000000`00000007 00000000`00000007 00000000`ffffffff ffff9d01`d0ca3180 : nt!MiWorkingSetManager+0x85
ffff8702`1dc97b20 fffff807`72871d25     : ffffc083`0ebac080 00000000`00000080 fffff807`729b6e00 1b76085e`39db3335 : nt!KeBalanceSetManager+0x157
ffff8702`1dc97c10 fffff807`72a00628     : ffff9d01`d0ca3180 ffffc083`0ebac080 fffff807`72871cd0 d38b4800`037df7e8 : nt!PspSystemThreadStartup+0x55
ffff8702`1dc97c60 00000000`00000000     : ffff8702`1dc98000 ffff8702`1dc92000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  nt!MiRaisedIrqlFault+142d18

MODULE_NAME: nt

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  142d18

FAILURE_BUCKET_ID:  AV_nt!MiRaisedIrqlFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3b24175f-7f5b-9c9f-8aaf-822c248bf0f5}

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

Answer 1

Hi LePon,

Driver Verifier indicates the chipset device driver is causing the crashes.

Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

Answer 2

Hi LePon,

Your minidump files just indicate memory (RAM) corruption no specific driver is listed

To try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

https://answers.microsoft.com/en-us/windows/for...

---

Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

Upon restart, press 4 to enter Safe Mode

Open Command Prompt as Administrator and run these two commands, then restart your PC.

verifier /reset

verifier /bootmode resetonbootfail

Answer 3

No, I installed it, I did buy all parts by myself

Answer 4

Hi LePon,

I am Dave, I will help you with this.

There is nothing specific listed in that printout, please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.

Answer 5

Was not win10 pre-installed by the PC maker?

Visit that makers support to update both bios and ALL drivers