[SOLVED] Random BSOD's that have been happening for while ?

[Certix18]

Good night everyone. Im posting this here because I dont know what else to do.

I built a PC last year and since then I'm having constant BSODs which happen completely at random. Sometimes it can go a whole day without getting one. Other times I can get one after another, with only ten minutes of usages between them.

The codes also differ most of times, with the more common being:
IRQL_NOT_LESS_OR_EQUAL
DRIVER_IRQL_NOT_LESS_OR_EQUAL

I leave with you the last dump debug I did:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff80296cec831, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80296cec831, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2000

Key : Analysis.Elapsed.mSec
Value: 2940

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key : Bugcheck.Code.TargetModel
Value: 0xd1

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: AV_CODE_AV_BAD_IP_nt!KiPageFault

Key : Failure.Hash
Value: {73cd60cc-83fa-6b76-df08-1961c31d7403}


BUGCHECK_CODE: d1

BUGCHECK_P1: fffff80296cec831

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80296cec831

FILE_IN_CAB: 060724-31453-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

READ_ADDRESS: fffff8030a31c4a8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff80296cec831

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff803057aa7f0 -- (.trap 0xfffff803057aa7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000383331b619 rbx=0000000000000000 rcx=fffff80304562180
rdx=fffff8030a34c700 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80296cec831 rsp=fffff803057aa988 rbp=fffff803057aaa90
r8=fffff803057aaaf0 r9=0000000000000000 r10=0000fffff8030993
r11=fffff80304565d80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
fffff802`96cec831 ?? ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
fffff802`96cec831 ?? ???

STACK_TEXT:
fffff803`057aa6a8 fffff803`09a2ff29 : 00000000`0000000a fffff802`96cec831 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
fffff803`057aa6b0 fffff803`09a2b389 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff803`057aa7f0 fffff802`96cec831 : fffff803`0985ffc4 fffff78b`40003158 00000000`00989680 00000000`00000000 : nt!KiPageFault+0x489
fffff803`057aa988 fffff803`0985ffc4 : fffff78b`40003158 00000000`00989680 00000000`00000000 fffff803`04569c08 : 0xfffff802`96cec831
fffff803`057aa990 fffff803`09a1efee : 00000000`00000000 fffff803`04562180 fffff803`0a34c700 ffffa309`fd2ec080 : nt!KiRetireDpcList+0x1b4
fffff803`057aac40 00000000`00000000 : fffff803`057ab000 fffff803`057a5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: nt!KiPageFault+489

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3672

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 489

FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}

Followup: MachineOwner

Please, someone help me reallize wtf is going on with this PC. I have been dealing with all this for quite a while.

Thanks

 

[Colif]

What are specs of the PC?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

Dump files can show us more than the report shows.

 

[TheHerald]

What do you do when these bsods happen? Gaming? Just browsing the web?

If you have your cpu undervolted return to stock and try

 

[Certix18]

What do you do when these bsods happen? Gaming? Just browsing the web?

If you have your cpu undervolted return to stock and try

Just on normal usage. Like... I can be just navigating on the Internet and get an BSOD out nowhere.

I bought a new Power Source to replace the older one, but still I keep getting them.

I dont know how to check if my CPU is getting undervoltage, so I would find helpful If you could explain me how to.

What are specs of the PC?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

Dump files can show us more than the report shows.

System Specs:

CPU: AMD Ryzen 5 4200
Motherboard: Gigabyte B450m DSH3 WiFi
VGU: Nvidia GeForce GTX 1650
Ram: 24gb, in three modules of 8gb
SO: Windows 11

I dont know if that is enough. If not, tell me what else do you need.

About the memory dumps...

https://drive.google.com/file/d/1GXf-tA06Of8chYHAoHhzzpk75s4Pb19j/view?usp=sharing

Here you have the last five ones.

Thanks for answering.

 

[Dark Lord of Tech]

Power supply make and model?

 

[Certix18]

Power supply make and model?

Corsair RM750e Gold Modular

 

[bicy]

As you can see, the Bug check already says it all. If we look at the root cause, we can safely say that the cause is an invalid memory access.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff80296cec831, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80296cec831, address which referenced memory

0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 2 (DISPATCH_LEVEL)

Address with the invalid memory access looks like a normal/valid address. Everything looks normal.

0: kd> !pte fffff80296cec831
                                           VA fffff80296cec831
PXE at FFFFD5EAF57ABF80    PPE at FFFFD5EAF57F0050    PDE at FFFFD5EAFE00A5B0    PTE at FFFFD5FC014B6760
contains 000000063E20C063  contains 0000000000000000
pfn 63e20c    ---DA--KWEV  contains 0000000000000000
not valid

This is because the address is still in the pagefile. Windows cannot paging addresses in case of high IRQL. As a result we have the bug check you see.

0xfffff803057aa7e8 : 0xfffff80309a2b389 : nt!KiPageFault+0x489
0xfffff803057aa830 : 0xfffff8030a34c700 : nt!KiInitialThread
0xfffff803057aa858 : 0xfffff8030986d745 : nt!KiProcessExpiredTimerList+0x2a5
Unable to load image aswVmm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswVmm.sys
0xfffff803057aa970 : 0xfffff803057aa988 : 0xfffff8030985ffc4 : nt!KiRetireDpcList+0x1b4
0xfffff803057aa988 : 0xfffff8030985ffc4 : nt!KiRetireDpcList+0x1b4
0xfffff803057aaa60 : 0xfffff8030a34c700 : nt!KiInitialThread
0xfffff803057aaaa8 : 0xfffff80309a22bec : nt!KiDpcInterrupt+0x34c
0xfffff803057aac38 : 0xfffff80309a1efee : nt!KiIdleLoop+0x9e
0xfffff803057aac50 : 0xfffff8030a34c700 : nt!KiInitialThread

From what I see in this file and many others, the cause is Avast's security suite. I would say to get rid of this AV software.

The problem may be independent of this. Of the other files, this one caught my eye:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000047, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8052351fe10, address which referenced memory

The cause of the error is AVAST, but this time the system crashed when accessing an invalid address.

0: kd> KnL
 # Child-SP          RetAddr               Call Site
00 fffff805`21a992c8 fffff805`2362ff29     nt!KeBugCheckEx
01 fffff805`21a992d0 fffff805`2362b389     nt!KiBugCheckDispatch+0x69
02 fffff805`21a99410 fffff805`2351fe10     nt!KiPageFault+0x489
03 fffff805`21a995a8 fffff805`2869e1e8     nt!PsGetCurrentProcess
04 fffff805`21a995b0 fffff805`4c289aaf     aswVmm+0xe1e8
05 fffff805`21a995b8 fffff805`20816180     amdppm!AcpiCStatePreselect+0x7f
06 fffff805`21a995c0 ffff840b`63afec80     0xfffff805`20816180
07 fffff805`21a995c8 fffff805`4c2815d1     0xffff840b`63afec80
08 fffff805`21a995d0 fffff805`2347751f     amdppm!SnapEnergyCountersAndTimestamp+0x91
09 fffff805`21a99600 fffff805`23476a0b     nt!PpmIdleExecuteTransition+0xaaf << A change related to CPU's power plans.
0a fffff805`21a99a50 fffff805`2361efa4     nt!PoIdle+0x68b << The system is idle.
0b fffff805`21a99c40 00000000`00000000     nt!KiIdleLoop+0x54

But the difference is that before Avast crashes, the system makes a change to the CPU's power plans. Avast may be the victim here, the problem seems to me to be with the CPU power management.

0xfffff80521a99408 : 0xfffff8052362b389 : nt!KiPageFault+0x489
0xfffff80521a99428 : 0xfffff805235560c9 : nt!KiCancelClockTimer+0x55
0xfffff80521a99500 : 0xfffff80523570d50 : nt!HalpApicX2WriteRegister
0xfffff80521a99508 : 0xfffff805235481fc : nt!HalpApicTimerStop+0x1c
0xfffff80521a99518 : 0xfffff80523475b57 : nt!KeQueryInterruptTimePrecise+0x57
0xfffff80521a99548 : 0xfffff8054c283c4b : amdppm!ReadGenAddr+0x1f
0xfffff80521a99578 : 0xfffff8052351fe10 : nt!PsGetCurrentProcess
0xfffff80521a995b0 : 0xfffff8054c289ab0 : amdppm!C2Idle 
0xfffff80521a995c8 : 0xfffff8054c2815d1 : amdppm!SnapEnergyCountersAndTimestamp+0x91
0xfffff80521a995f8 : 0xfffff8052347751f : nt!PpmIdleExecuteTransition+0xaaf
0xfffff80521a99a30 : 0xfffff80523f259b0 : nt!KiProcessorIndexToNumberMappingTable
0xfffff80521a99a48 : 0xfffff80523476a0b : nt!PoIdle+0x68b
0xfffff80521a99a60 : 0xfffff80523f4c700 : nt!KiInitialThread
0xfffff80521a99c38 : 0xfffff8052361efa4 : nt!KiIdleLoop+0x54
0xfffff80521a99c48 : 0xfffff80523f4c700 : nt!KiInitialThread

The system goes to C2 idle state, then these crashes... It suggests there may be a problem with the C-STATE.

You have to uninstall Avast and turn off the CBS setting in BIOS

 

[Certix18]

As you can see, the Bug check already says it all. If we look at the root cause, we can safely say that the cause is an invalid memory access.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff80296cec831, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80296cec831, address which referenced memory

0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 2 (DISPATCH_LEVEL)

But as you can see, the address with the invalid memory access looks like a normal/valid address. Everything looks normal.

0: kd> !pte fffff80296cec831
                                           VA fffff80296cec831
PXE at FFFFD5EAF57ABF80    PPE at FFFFD5EAF57F0050    PDE at FFFFD5EAFE00A5B0    PTE at FFFFD5FC014B6760
contains 000000063E20C063  contains 0000000000000000
pfn 63e20c    ---DA--KWEV  contains 0000000000000000
not valid

This is because the address is still in the pagefile. Windows cannot page addresses in case of high IRQL. As a result we have the bug check you see.

0xfffff803057aa7e8 : 0xfffff80309a2b389 : nt!KiPageFault+0x489
0xfffff803057aa830 : 0xfffff8030a34c700 : nt!KiInitialThread
0xfffff803057aa858 : 0xfffff8030986d745 : nt!KiProcessExpiredTimerList+0x2a5
Unable to load image aswVmm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswVmm.sys
0xfffff803057aa970 : 0xfffff803057aa988 : 0xfffff8030985ffc4 : nt!KiRetireDpcList+0x1b4
0xfffff803057aa988 : 0xfffff8030985ffc4 : nt!KiRetireDpcList+0x1b4
0xfffff803057aaa60 : 0xfffff8030a34c700 : nt!KiInitialThread
0xfffff803057aaaa8 : 0xfffff80309a22bec : nt!KiDpcInterrupt+0x34c
0xfffff803057aac38 : 0xfffff80309a1efee : nt!KiIdleLoop+0x9e
0xfffff803057aac50 : 0xfffff8030a34c700 : nt!KiInitialThread

From what I see in this file and many others, the cause is Avast's security suite. I would say to get rid of this AV software.

The problem may be independent of this. Of the other files, this one caught my eye:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000047, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8052351fe10, address which referenced memory

The cause of the error is AVAST, but this time the system crashed when accessing an invalid address.

0: kd> KnL
 # Child-SP          RetAddr               Call Site
00 fffff805`21a992c8 fffff805`2362ff29     nt!KeBugCheckEx
01 fffff805`21a992d0 fffff805`2362b389     nt!KiBugCheckDispatch+0x69
02 fffff805`21a99410 fffff805`2351fe10     nt!KiPageFault+0x489
03 fffff805`21a995a8 fffff805`2869e1e8     nt!PsGetCurrentProcess
04 fffff805`21a995b0 fffff805`4c289aaf     aswVmm+0xe1e8
05 fffff805`21a995b8 fffff805`20816180     amdppm!AcpiCStatePreselect+0x7f
06 fffff805`21a995c0 ffff840b`63afec80     0xfffff805`20816180
07 fffff805`21a995c8 fffff805`4c2815d1     0xffff840b`63afec80
08 fffff805`21a995d0 fffff805`2347751f     amdppm!SnapEnergyCountersAndTimestamp+0x91
09 fffff805`21a99600 fffff805`23476a0b     nt!PpmIdleExecuteTransition+0xaaf << A change related to CPU's power plans.
0a fffff805`21a99a50 fffff805`2361efa4     nt!PoIdle+0x68b << The system is idle.
0b fffff805`21a99c40 00000000`00000000     nt!KiIdleLoop+0x54

But the difference is that before Avast crashes, the system makes a change to the CPU's power plans. Avast may be the victim here, the problem seems to me to be with the CPU power management.

0xfffff80521a99408 : 0xfffff8052362b389 : nt!KiPageFault+0x489
0xfffff80521a99428 : 0xfffff805235560c9 : nt!KiCancelClockTimer+0x55
0xfffff80521a99500 : 0xfffff80523570d50 : nt!HalpApicX2WriteRegister
0xfffff80521a99508 : 0xfffff805235481fc : nt!HalpApicTimerStop+0x1c
0xfffff80521a99518 : 0xfffff80523475b57 : nt!KeQueryInterruptTimePrecise+0x57
0xfffff80521a99548 : 0xfffff8054c283c4b : amdppm!ReadGenAddr+0x1f
0xfffff80521a99578 : 0xfffff8052351fe10 : nt!PsGetCurrentProcess
0xfffff80521a995b0 : 0xfffff8054c289ab0 : amdppm!C2Idle 
0xfffff80521a995c8 : 0xfffff8054c2815d1 : amdppm!SnapEnergyCountersAndTimestamp+0x91
0xfffff80521a995f8 : 0xfffff8052347751f : nt!PpmIdleExecuteTransition+0xaaf
0xfffff80521a99a30 : 0xfffff80523f259b0 : nt!KiProcessorIndexToNumberMappingTable
0xfffff80521a99a48 : 0xfffff80523476a0b : nt!PoIdle+0x68b
0xfffff80521a99a60 : 0xfffff80523f4c700 : nt!KiInitialThread
0xfffff80521a99c38 : 0xfffff8052361efa4 : nt!KiIdleLoop+0x54
0xfffff80521a99c48 : 0xfffff80523f4c700 : nt!KiInitialThread

The system goes to C2 idle state, then these crashes... It suggests there may be a problem with the C-STATE.

You have to uninstall Avast and turn off the CBS setting in BIOS

Thanks for the Reply, man.

Now... could you explain my how to change that setting. I entered the BIOS and tried to look for it, but I wasn´t sure what to disable exactly, so I choose no not touch anything so to avoid further damage.

I would really apreciate if you could give me a brief explanation.

 

[bicy]

you should look for the core performance boost setting in the BIOS.

 

[Certix18]

**UPDATE**

So, I did what you guys told me, but the BSOD keep on happening on random.

Here is the new batch of Minidumps...

https://drive.google.com/file/d/1dZ2Ne8SiPU2m4S5ybXnIzsRV0VQOrunu/view?usp=sharing

I hope you can help me to fix this.

Thanks.

 

[bicy]

So, the same error's again. Are you sure you did everything you were told to do?

 rsp : 0xfffff8071e640318 : 0xfffff8071fe2ff29 : nt!KiBugCheckDispatch+0x69
0xfffff8071e640318 : 0xfffff8071fe2ff29 : nt!KiBugCheckDispatch+0x69
0xfffff8071e640328 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
0xfffff8071e640340 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
Unable to load image aswVmm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswVmm.sys
0xfffff8071e640418 : 0xfffff8071fc75083 : nt!KeQueryPerformanceCounter+0xc3
0xfffff8071e640458 : 0xfffff8071fe2b389 : nt!KiPageFault+0x489
0xfffff8071e640460 : 0xfffff8071e6404f0 :  Trap @ fffff8071e640460
0xfffff8071e640530 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
0xfffff8071e640548 : 0xfffff80732893c4b : amdppm!ReadGenAddr+0x1f
0xfffff8071e640578 : 0xfffff80732899b37 : amdppm!C2Idle+0x87
0xfffff8071e640588 : 0xfffff8071fc75083 : nt!KeQueryPerformanceCounter+0xc3
0xfffff8071e6405a8 : 0xfffff8073289c265 : amdppm!LpiIdleExecute+0xb5
0xfffff8071e6405b0 : 0xfffff80732899ab0 : amdppm!C2Idle
0xfffff8071e6405c8 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
0xfffff8071e6405e0 : 0xfffff8071e6405f8 : 0xfffff8071fc76ea5 : nt!PpmIdleExecuteTransition+0x435
0xfffff8071e6405f8 : 0xfffff8071fc76ea5 : nt!PpmIdleExecuteTransition+0x435
0xfffff8071e640a48 : 0xfffff8071fc76a0b : nt!PoIdle+0x68b
0xfffff8071e640a60 : 0xfffff8072074c700 : nt!KiInitialThread
0xfffff8071e640c38 : 0xfffff8071fe1efa4 : nt!KiIdleLoop+0x54
0xfffff8071e640c48 : 0xfffff8072074c700 : nt!KiInitialThread

 

[Certix18]

So, the same error's again. Are you sure you did everything you were told to do?

 rsp : 0xfffff8071e640318 : 0xfffff8071fe2ff29 : nt!KiBugCheckDispatch+0x69
0xfffff8071e640318 : 0xfffff8071fe2ff29 : nt!KiBugCheckDispatch+0x69
0xfffff8071e640328 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
0xfffff8071e640340 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
Unable to load image aswVmm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswVmm.sys
0xfffff8071e640418 : 0xfffff8071fc75083 : nt!KeQueryPerformanceCounter+0xc3
0xfffff8071e640458 : 0xfffff8071fe2b389 : nt!KiPageFault+0x489
0xfffff8071e640460 : 0xfffff8071e6404f0 :  Trap @ fffff8071e640460
0xfffff8071e640530 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
0xfffff8071e640548 : 0xfffff80732893c4b : amdppm!ReadGenAddr+0x1f
0xfffff8071e640578 : 0xfffff80732899b37 : amdppm!C2Idle+0x87
0xfffff8071e640588 : 0xfffff8071fc75083 : nt!KeQueryPerformanceCounter+0xc3
0xfffff8071e6405a8 : 0xfffff8073289c265 : amdppm!LpiIdleExecute+0xb5
0xfffff8071e6405b0 : 0xfffff80732899ab0 : amdppm!C2Idle
0xfffff8071e6405c8 : 0xfffff8071fbd1f80 : "nt!_guard_fids_table <PERF> (nt+0x1d1f80)"
0xfffff8071e6405e0 : 0xfffff8071e6405f8 : 0xfffff8071fc76ea5 : nt!PpmIdleExecuteTransition+0x435
0xfffff8071e6405f8 : 0xfffff8071fc76ea5 : nt!PpmIdleExecuteTransition+0x435
0xfffff8071e640a48 : 0xfffff8071fc76a0b : nt!PoIdle+0x68b
0xfffff8071e640a60 : 0xfffff8072074c700 : nt!KiInitialThread
0xfffff8071e640c38 : 0xfffff8071fe1efa4 : nt!KiIdleLoop+0x54
0xfffff8071e640c48 : 0xfffff8072074c700 : nt!KiInitialThread

Yes. I Unninstalled the Avast AV and also turned off that setting you told me to.

 

[Colif]

if you got bsod after removing Avast, I would try running this to make sure its removed everything - as last BSOD was caused by it still
https://www.avast.com/en-au/uninstall-utility#pc

 

[Certix18]

if you got bsod after removing Avast, I would try running this to make sure its removed everything - as last BSOD was caused by it still
https://www.avast.com/en-au/uninstall-utility#pc

I did use that aplication to unninstal Avast, but still got several BSOD after that.

Could it be a CPU Voltage Problem?

 

[bicy]

There is obviously a problem with the CPU. Restricting the power limit didn't seem to help.

 

[Certix18]

Final Report:

Guys... I waited a few days in order to check it worked, but I managed to fix the constant BSOD problem.

Aparently, it had to do with the Voltage the Motherboard was suppliying the CPU with. I managed to find how to increase it manually on the BIOS menu, and then tuned it up until (Around) 1,375V.

Its being 5 days of uninterrupted usage since then.

Again, thanks to all of you for answering my questions and helping.