Random BSOD and monitor doesn't turn off

Hello everyone. A little less than a month has passed and again, for no reason at all, the blue screens started again. I haven't installed anything since that moment, and I haven't touched any PC components either. Attaching SysnativeFileCollectionApp

You tend not to respond to Questions asked of you.  So we do not get a answer to important questions.  Make a larger effort to do so please.

Nor do you tell us if you have completed what we have asked of you,   Withdrawal of help could be warranted.

Ok, NEW ISSUE WRONG BIOS INSTALLED : Please explain why you are running BIOS Version :  F65  As there is NO Bios version F65 released for your Motherboard as per :

https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-1x/support#support-dl-bios

I told you there was a Bios Version F64 that was new and to update to that Re Post # 7  

Why would you update to F65 when the URL I provided in  Post # 7 had no F65 and had Bios Version F64 as was directed to install.

Read instructions carefully.  Confirm if do not understand.  By putting in the wrong Bios you could have made a Paper Weight.

This is what I mean not following directions, not informing us of doing things that have been asked.

So now you need to see if can Update your BIOS to Version : F66   Released : Mar 22, 2024

https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-1x/support#support-dl-bios  repeating BIOS URL

Update Drivers to correct Version as well and do not stick in Win11 Drivers until you are actually running Windows 11.

Going to look no further nor say more as there maybe issues.    Report Back later if the Bios helped

Edited by Pkshadow, 08 April 2024 - 05:30 PM.

Sorry, I don't quite understand what I didn't do. I have installed Trifecta Malwarebytes. I did everything you write. I made a mistake in the BIOS version, I apologize for that. I will install another BIOS version right away and keep you informed

You would have to be on the wrong website to install the WRONG BIOS that was not meant for your system.  Lucky it still works.

I have no idea what : Trifecta Malwarebytes means.  When google that you get people that are having Malware Removed. from Malwarebytes Forum.

Malwarebytes is just : Malwarebytes, it is made by Malwarebytes : https://www.google.com/search?client=firefox-b-d&q=Malwarebytes    Explain please : Trifecta Malwarebytes

 

 

In future it would be best to run Defender as your A/V and Firewall.   So will need to do this : https://www.howtogeek.com/230158/how-to-run-malwarebytes-alongside-another-antivirus/

 

A tool to bring out Defenders hidden controls : https://www.majorgeeks.com/files/details/configuredefender.html

Developer now works for MBAM so colours are changed and brings out hidden Firewall Controls : https://www.binisoft.org/wfc

Make a trifecta with MBAM Browser Guard : https://www.malwarebytes.com/browserguard

 

 

Sorry, I explained it the wrong way.  I did as you said here

Ah Ok. 

@ubuysa will need to look at your Dump Files in Post # 31

Taken as a group this still looks very much like a RAM problem. Did you ever actually test your RAM with Memtest86 as advise in post #10? If not please do so. As an alternative you can remove one RAM stick for a day or two - or until it BSODs again. Then swap RAM sticks and run on just the other for a day or two.

We need to be 100% certain that this is not simply bad RAM before we look elsewhere.

I checked the RAM twice using Memtest86. I'll run another check tonight. And then I will try to change the RAM sticks. The main problem is that the BSODs disappear as suddenly as they appear, so I will do these actions after the new BSOD appears

Change the ram.  At 3 pages of it is probably the ram.  A Conclusion/Decision should be made.  No get the ram,  no waiting around for another BSOD what is that about  !! 

I checked the RAM twice using Memtest86. I'll run another check tonight. And then I will try to change the RAM sticks. The main problem is that the BSODs disappear as suddenly as they appear, so I will do these actions after the new BSOD appears

Just remove one RAM stick for a few days, or until you gate a BSOD. Then swap sticks and run on just that for a few days, or until you get a BSOD.

• Does it BSOD on just one stick?
• Does it BSOD on both sticks on their own?
• Does it not BSOD with each stick on their own but does BSOD with them both inserted?
   

Edited by ubuysa, 10 April 2024 - 01:15 AM.

Hi, there have been no BSOD since I pulled out one RAM, is there any method to make sure that the problem is in the deleted RAM? Because it's hard to use a PC with 8GB of RAM. It is quite difficult to make a conclusion in a week because recently there was no BSOD for a month, although both RAM were inserted into the PC. Memtest86 showed no problems

Oh, I just saw that now I need to insert one and get the other

Edited by sh1k1, 18 April 2024 - 07:07 AM.

Run if for a month on one RAM stick then. Troubleshooting is often awkward and compromises have to be made, but unless you want to go out and buy new RAM now that's you're only option.