** blue screen of death ** with kernel security check failure or irql_not_less_or_equal

[amir2927]

hi
according to my last topic
i have bsod every 7 8h after i turn on my pc
i tired new windows i tried bios reset i tries default ram speed and xmp enable i tried update windows i tried hard test i tried ayda46 ram and cpu full load test for 30 min
any help?
i tried any thing on google xd
but still have bsod every 7 or 8 hours some times even after 10 hours
with kernel security check failure or irql_not_less_or_equal

[Hellowpplz]

56 minutes ago, amir2927 said:

hi
according to my last topic
i have bsod every 7 8h after i turn on my pc
i tired new windows i tried bios reset i tries default ram speed and xmp enable i tried update windows i tried hard test i tried ayda46 ram and cpu full load test for 30 min
any help?
i tried any thing on google xd
but still have bsod every 7 or 8 hours some times even after 10 hours
with kernel security check failure or irql_not_less_or_equal

Use Memtest86 to test your ram. Or use the windows system file checker

1. Run command prompt as administrator

2. Type the following and press enter (in command prompt): DISM.exe /Online /Cleanup-image /Restorehealth

3. After it says "The operation completed successfully" type the following and press enter: sfc /scannow

 

[OddOod]

37 minutes ago, Hellowpplz said:

1. Run command prompt as administrator

 

This set of instructions is solid, but, as always, when running admin CMD stuff, do google a bit to make sure it's safe

Also, reseat your RAM

[amir2927]

52 minutes ago, Hellowpplz said:

Use Memtest86 to test your ram. Or use the windows system file checker

1. Run command prompt as administrator

2. Type the following and press enter (in command prompt): DISM.exe /Online /Cleanup-image /Restorehealth

3. After it says "The operation completed successfully" type the following and press enter: sfc /scannow

 

i did ram test before with ayda46 for 30 min
and

 

 

[amir2927]

15 minutes ago, OddOod said:

This set of instructions is solid, but, as always, when running admin CMD stuff, do google a bit to make sure it's safe

Also, reseat your RAM

i did reset my bios to default before
 

[OddOod]

On 5/7/2024 at 8:41 AM, amir2927 said:

did ram test

Still reseating RAM might help. 

 

It's possible this is going to end up being a dying mobo, but IRQL errors *tend* to be ram related

[amir2927]

58 minutes ago, OddOod said:

Still reseating RAM might help. 

 

It's possible this is going to end up being a dying mobo, but IRQL errors *tend* to be ram related

i tried ram test
i tried bios reset
i tries xmp
but now i reset to default and increese to 2666 hz
its stable for 10h and after that bsod !!
i just reset my pc every 5h i cant do anything to stop that

[amir2927]

1 hour ago, OddOod said:

Still reseating RAM might help. 

 

It's possible this is going to end up being a dying mobo, but IRQL errors *tend* to be ram related

what u mean dying mobo? you mean my motherboard gonna die and crash soon?

[OddOod]

21 hours ago, amir2927 said:

what u mean dying mobo? you mean my motherboard gonna die and crash soon?

potentially
But if you've already found a fix, that works

[OddOod]

21 hours ago, amir2927 said:

but now i reset to default and increase to 2666 hz

Though, that sounds like dying RAM. RAM's cheap right now, it wouldn't hurt to try a new kit.
And come to think of it, most RAM comes with lifetime warranty. You could ask about an RMA 

[amir2927]

19 hours ago, OddOod said:

Though, that sounds like dying RAM. RAM's cheap right now, it wouldn't hurt to try a new kit.
And come to think of it, most RAM comes with lifetime warranty. You could ask about an RMA 

but every thing was fine with that my previously windows version !!! after i update to new version windows 10 i got this problem!
should i change it to previously version again?

[OddOod]

You are potentially falling for one of the most common human logic traps: just because it happened after the upgrade doesn't mean that the upgrade borked it. 

You are absolutely free to try installing a fresh copy of W10, but it would surprise me if that fixed it