BSOD after installing new CPU

[kurtkrys]

So, this is my first time ever posting anything like this, and I'm below average when it comes to knowing tech, so please bare with me. I replaced my AMD Athlon X4 760k to a X4 870k, ever since I have changed my cpu, there would be a BSOD when the pc is on for about 10 minutes or maybe even up to 30 minutes. For the first few days of me replacing my cpu, I wasn't able to update any of my drivers especially my gpu drivers as my pc would have a BSOD whenever the update is gonna be extracted, but a few days later after that, it suddenly was able to update it, and I thought I was good to go, so I also updated my Windows, after all of those updates, my pc would still BSOD. I did notice one thing though, this may be an important information, or maybe not, but I noticed that it would not have a BSOD whenever I have my game on, which is Valorant (I have not tested my other games yet), even if I play like 5 games, (which is maybe 4 hours?), it would not have a BSOD unless I close Valorant, then for maybe about 10 minutes, it would have a BSOD. I have already reset my CMOS (I removed my CMOS battery and waited more than 10 mins before I put it back in), I have the latest version of bios. I have downloaded DriverEasy and updated everything that needs to be updated. I'm starting to think that my cpu is the problem, I just want experts like you people to tell me any problem you may think it is. I'm open and ready to do any of your demands (I'm sorry for using "demands", I cannot think of another word to use), that you think may help me.(Side note: English isn't my first language, I'm sorry if my grammar isn't perfect.) 

 

ANOTHER NOTE: I would not receive any BSOD when I put my old cpu back which is my X4 760k     

Edited April 21, 2021 by kurtkrys

[Radium_Angel]

Are you sure the CPU is good?

Are you sure the BIOS of your system is updated to support the CPU?

[kurtkrys]

Just now, Radium_Angel said:

Are you sure the CPU is good?

Are you sure the BIOS of your system is updated to support the CPU?

1.) I'm not sure if the CPU is good, but I think it performs well because my frames on Valorant is much more better than my last CPU.

2.) I'm not a person who is very good a tech, so how can I possibly check if my CPU is compatible with my BIOS?

[Beerzerker]

40 minutes ago, kurtkrys said:

1.) I'm not sure if the CPU is good, but I think it performs well because my frames on Valorant is much more better than my last CPU.

2.) I'm not a person who is very good a tech, so how can I possibly check if my CPU is compatible with my BIOS?

If the chip is working in the board it's probrably compatable with your BIOS.
I've ran CPUs in boards that report it as "Unknown" yet it would still run fine and I'm talking about some heavily OC'ed stuff too.

When you swapped CPUs are you still using the settings the other chip was running with?
One thing could be the CPU you've got may need a small bump in voltage to stabilize it or perhaps a touch more RAM voltage to help it along. No two chips will behave in the exact same way so make sure if you've done some previous tweaking AND trying to run it with the same exact settings, be ready to do a little more for this one.

Mind you it shoudn't be a massive difference, just enough like, for example going from 1.35v's (Old chip) to 1.37-1.40v's (New chip) to stabilize it.

 

[kurtkrys]

4 minutes ago, Beerzerker said:

If the chip is working in the board it's probrably compatable with your BIOS.
I've ran CPUs in boards that report it as "Unknown" yet it would still run fine and I'm talking about some heavily OC'ed stuff too.

When you swapped CPUs are you still using the settings the other chip was running with?
One thing could be the CPU you've got may need a small bump in voltage to stabilize it or perhaps a touch more RAM voltage to help it along. No two chips will behave in the exact same way so make sure if you've done some previous tweaking AND trying to run it with the same exact settings, be ready to do a little more for this one.

Mind you it shoudn't be a massive difference, just enough like, for example going from 1.35v's (Old chip) to 1.37-1.40v's (New chip) to stabilize it.

 

What settings should I change or how do I change the settings for my CPU? I haven't really though about that because when even before my old CPU (X4 760k), I had another old cpu/apu which is the A4-4000. I will try to do what you have told me, thank you.

[Radium_Angel]

1 hour ago, kurtkrys said:

1.) I'm not sure if the CPU is good, but I think it performs well because my frames on Valorant is much more better than my last CPU.

2.) I'm not a person who is very good a tech, so how can I possibly check if my CPU is compatible with my BIOS?

In general, O'd update the BIOS, just to be on the safe side (unless the BIOS is already at the latest)

The other option, is to find all the crash dump files, upload them here, and I'll look into them and see what's going on.

[Beerzerker]

Noted it's saying "IRQ not less or equal" which is generally a RAM voltage issue, being it's not getting quite enough to be fully stable.

A small bump in RAM voltage usually works to get rid of that problem.

[kurtkrys]

1.) As I was about to type that when I bumped up my RAM voltage and there were no signs of any BSOD, it suddenly happened.

2.) I also forgot to tell you all that the most common error I get is "Kernel Security Check Failure"

Also, I forgot the part where you said that my CPU may also need a small bump in voltage, so I may try that as well.

 

(WndDbg)

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffee07535fda60, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffee07535fd9b8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8093

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 8896

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

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

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

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    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


BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffee07535fda60

BUGCHECK_P3: ffffee07535fd9b8

BUGCHECK_P4: 0

TRAP_FRAME:  ffffee07535fda60 -- (.trap 0xffffee07535fda60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff97033a03bed8 rbx=0000000000000000 rcx=0000000000000003
rdx=ffff97033a03be30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80267c1be53 rsp=ffffee07535fdbf0 rbp=ffffee07535fded0
 r8=ffff970333183a98  r9=ffff97033a03be30 r10=fffff80267c1be30
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
FLTMGR!FltpRemoveMessageWaiter+0x23:
fffff802`67c1be53 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffffee07535fd9b8 -- (.exr 0xffffee07535fd9b8)
ExceptionAddress: fffff80267c1be53 (FLTMGR!FltpRemoveMessageWaiter+0x0000000000000023)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  TiWorker.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
ffffee07`535fd738 fffff802`69a07b69     : 00000000`00000139 00000000`00000003 ffffee07`535fda60 ffffee07`535fd9b8 : nt!KeBugCheckEx
ffffee07`535fd740 fffff802`69a07f90     : 00000000`00000000 fffff802`69848727 ffff9703`40f99010 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffffee07`535fd880 fffff802`69a06323     : ffff9703`3e494b10 fffff802`69861553 ffff9703`40f99010 00000000`00000001 : nt!KiFastFailDispatch+0xd0
ffffee07`535fda60 fffff802`67c1be53     : ffffee07`535fded0 fffff802`00000000 ffff9703`00000000 ffff9703`3389bc01 : nt!KiRaiseSecurityCheckFailure+0x323
ffffee07`535fdbf0 fffff802`698fb760     : ffff9703`3d78a580 ffffee07`535fdd10 00000000`00000000 fffff802`67c3a060 : FLTMGR!FltpRemoveMessageWaiter+0x23
ffffee07`535fdc20 fffff802`67c1ac47     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IoCsqRemoveNextIrp+0x60
ffffee07`535fdc50 fffff802`6db30eda     : ffff9703`3389ba20 ffffee07`535fded0 ffff8304`ad128890 ffffffff`0000045c : FLTMGR!FltSendMessage+0x1e7
ffffee07`535fddb0 fffff802`6db3048d     : ffff8304`9c809790 ffff8304`9c809790 00000000`00000000 ffff8304`c11bb7c0 : WdFilter!MpDoScanFile+0xa1e
ffffee07`535fdf00 fffff802`6db2537a     : 00000000`00000000 ffff9703`3fe7c7e8 00000000`00000000 00000000`00000003 : WdFilter!MpScanFile+0xa49
ffffee07`535fdfc0 fffff802`6db265ac     : 00000000`00000001 fffff802`6db14000 00000000`00000000 ffff9703`00000000 : WdFilter!MpAmPostCreate+0x1002
ffffee07`535fe150 fffff802`67c15747     : ffff9703`3fe7c700 00000000`00000000 ffff9703`00000000 fffff802`00000000 : WdFilter!MpPostCreate+0x3cc
ffffee07`535fe1d0 fffff802`67c15018     : ffff9703`3fe7c700 fffff802`67c49b00 00000000`00000000 00000000`00000000 : FLTMGR!FltpPerformPostCallbacksWorker+0x347
ffffee07`535fe2a0 fffff802`67c16d62     : ffffee07`535f9000 ffffee07`535ff000 00000000`00000000 fffff802`67c2d440 : FLTMGR!FltpPassThroughCompletionWorker+0xf8
ffffee07`535fe340 fffff802`67c4bbd4     : ffffee07`535fe3f0 ffff9703`42179248 ffff9703`339efd00 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x322
ffffee07`535fe3b0 fffff802`69852f55     : 00000000`00000000 ffff9703`339f9860 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x324
ffffee07`535fe460 fffff802`69854544     : 00000000`00000003 ffff9703`3fb93b20 ffff9703`6d4e6f49 fffff802`69854173 : nt!IofCallDriver+0x55
ffffee07`535fe4a0 fffff802`69bfefad     : ffffee07`535fe760 ffff9703`339f9860 ffff9703`42179288 00000000`00000000 : nt!IoCallDriverWithTracing+0x34
ffffee07`535fe4f0 fffff802`69c2797e     : ffff9703`339f9860 00000000`00000098 ffff9703`48adb4e0 ffff9703`48adb401 : nt!IopParseDevice+0x117d
ffffee07`535fe660 fffff802`69beb27a     : ffff9703`48adb400 ffffee07`535fe8c8 ffff9703`00000040 ffff9703`32eaf400 : nt!ObpLookupObjectName+0x3fe
ffffee07`535fe830 fffff802`69c6d5af     : ffffffff`00000000 000000c3`f057d908 00000000`00000000 00000000`00000001 : nt!ObOpenObjectByNameEx+0x1fa
ffffee07`535fe960 fffff802`69c6d189     : 000000c3`f057d950 00000000`00000000 000000c3`f057d908 000000c3`f057d968 : nt!IopCreateFile+0x40f
ffffee07`535fea00 fffff802`69a075b5     : 00000000`00012a0c 000000c3`f057d3b8 00000000`00000000 00000000`00000000 : nt!NtCreateFile+0x79
ffffee07`535fea90 00007ffb`ccfad6b4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000c3`f057d368 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ccfad6b4


SYMBOL_NAME:  WdFilter!MpDoScanFile+a1e

MODULE_NAME: WdFilter

IMAGE_NAME:  WdFilter.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  a1e

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_WdFilter!MpDoScanFile

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2d28e9ed-655f-493f-f80c-96004c07c8ab}

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

[Beerzerker]

Yes, a bump in CPU voltage could do it.
Can't do any harm to try it.

[kurtkrys]

56 minutes ago, Beerzerker said:

Yes, a bump in CPU voltage could do it.
Can't do any harm to try it.

So, after hours of research and checking, I wasn't able to find an option or a tutorial on how to adjust my CPU Voltage.

My motherboard is a MSI A58m-E33 | msi click bios 4

 

What can I do?

 

EDIT: I know this is irrelevant but my "hours" of research is just an exaggeration

[Radium_Angel]

2 hours ago, kurtkrys said:

So, after hours of research and checking, I wasn't able to find an option or a tutorial on how to adjust my CPU Voltage.

My motherboard is a MSI A58m-E33 | msi click bios 4

 

What can I do?

 

EDIT: I know this is irrelevant but my "hours" of research is just an exaggeration

Upload the crash dump files, as files here, so that I can download them and deconstruct them please. 

[kurtkrys]

6 hours ago, Radium_Angel said:

Upload the crash dump files, as files here, so that I can download them and deconstruct them please. 

My bad, If there's anything missing, I'll reply ASAP

Dump files.zip

[Radium_Angel]

1 hour ago, kurtkrys said:

My bad, If there's anything missing, I'll reply ASAP

Dump files.zip 22 B · 0 downloads

The folder is empty....

[kurtkrys]

8 minutes ago, Radium_Angel said:

The folder is empty....

I'm genuinely sorry for the inconvenience, here is the updated folder

Dump files.zip

[Radium_Angel]

1 hour ago, kurtkrys said:

I'm genuinely sorry for the inconvenience, here is the updated folder

Dump files.zip 612.93 kB · 0 downloads

No worries Mate!

I'm going to look  them over, post the relevant parts from each crash dump, and my thoughts at the end.

Give me 20 or so minutes

[Radium_Angel]

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffb3829146f0f0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffb3829146f048, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb3829146f0f0

BUGCHECK_P3: ffffb3829146f048

BUGCHECK_P4: 0
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

PROCESS_NAME:  chrome.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

___

(same at the first one, except the crash occured at:)

PROCESS_NAME:  System
___

(ditto of the aboce, ecept:)

PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.925_none_e76d4f6f260a6
___

 

 

Ok, it's pretty clear you have a very badly mis-behaving driver.

https://techgenix.com/kernel-security-check/

This gets tricky to solve.

Start here:

https://www.memtest86.com/

Just to make sure your RAM is good. I'm 99% certain it is, but test anyway.

then:

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

 

What (if any) AntiVirus software are you running?

 

[kurtkrys]

23 hours ago, Radium_Angel said:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffb3829146f0f0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffb3829146f048, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb3829146f0f0

BUGCHECK_P3: ffffb3829146f048

BUGCHECK_P4: 0
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

PROCESS_NAME:  chrome.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

___

(same at the first one, except the crash occured at:)

PROCESS_NAME:  System
___

(ditto of the aboce, ecept:)

PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.925_none_e76d4f6f260a6
___

 

 

Ok, it's pretty clear you have a very badly mis-behaving driver.

https://techgenix.com/kernel-security-check/

This gets tricky to solve.

Start here:

https://www.memtest86.com/

Just to make sure your RAM is good. I'm 99% certain it is, but test anyway.

then:

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

 

What (if any) AntiVirus software are you running?

 

Sorry for the late reply! Too much schoolwork I had to finish, anyways, I appreciate your help and I'm gonna start doing the things you have told me, I'm replying even though I haven't done it yet to let you know that I'm at the process of doing it, thank you

[kurtkrys]

On 4/23/2021 at 5:27 AM, Radium_Angel said:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffb3829146f0f0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffb3829146f048, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb3829146f0f0

BUGCHECK_P3: ffffb3829146f048

BUGCHECK_P4: 0
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

PROCESS_NAME:  chrome.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

___

(same at the first one, except the crash occured at:)

PROCESS_NAME:  System
___

(ditto of the aboce, ecept:)

PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.925_none_e76d4f6f260a6
___

 

 

Ok, it's pretty clear you have a very badly mis-behaving driver.

https://techgenix.com/kernel-security-check/

This gets tricky to solve.

Start here:

https://www.memtest86.com/

Just to make sure your RAM is good. I'm 99% certain it is, but test anyway.

then:

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

 

What (if any) AntiVirus software are you running?

 

(I'm not really using any AntiVirus software)

 

UPDATE:

I cannot try the memtest as I do not have my flash drive with me atm, but I did manage to try and use the driver verifier. My pc failed to boot twice due to the bluescreens, and here is the crash dump file

042421-31765-01.dmp

[Radium_Angel]

Ok, give me a minute to look it over.

[Radium_Angel]

Found it!

(I think)

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff80316fd9250, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 00000000656e6f4e, Pool Tag (if provided).
 

IMAGE_NAME:  vgk.sys

 

https://www.reddit.com/r/ValorantTechSupport/comments/kfxy9a/vgksys_bsod/

 

Happening to a lot of folks....

[kurtkrys]

3 hours ago, Radium_Angel said:

Found it!

(I think)

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff80316fd9250, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 00000000656e6f4e, Pool Tag (if provided).
 

IMAGE_NAME:  vgk.sys

 

https://www.reddit.com/r/ValorantTechSupport/comments/kfxy9a/vgksys_bsod/

 

Happening to a lot of folks....

This makes A LOT of sense. Valorant's anti cheat system is so strict, it has kernel-level access. I might uninstall it and see what's going to happen. Thank you!!