Pending OP Response Continuous BSOD

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Welcome to our Community
Wanting to join the rest of our members? Feel free to sign up today.
Sign up
Hello, sorry for the delay in my response but i was away from home in these days. In the next few days i will update the threads if more BSOD happens.
 
Hello, unfortunately i still experience BSODs. I am currently not overclocking my pc, i disabled any oc profile i could find as an attempt to make the pc more stable
 

Attachments

Please run the lastest version of the PCHF log tool. Post the new PCHF .txt log as well as the dump files.(right click run as administrator)
 

Attachments

Download the attached batch file right click run as admin.
This will disable un-needed scheduled task.

I'll need the new PCHF.txt and the latest dump files to go further.
 

Attachments

Also, there are a lot of memory errors, now that you have tried with no overclocking:

Your ram is set to 2399MHz

32,0GB Dual-Channel Unknown @ 2399MHz (40-40-40-77)



Change it manually to 4800 in bios

1727317484254.webp
 
Please run the lastest version of the PCHF log tool. Post the new PCHF .txt log as well as the dump files.(right click run as administrator)
i can't download it since windows defender signals a trojan virus in one of the files inside. It deletes it automatically so fast i cannot allow it to be spared.
I ran the disable_tasks script and will set the ram freq to 4800 manually. Attacched you can find the most recent dumps
 

Attachments

Your issues are not driver related per se but are instead down to Windows or the drive that Windows lives on not working properly.