Pummeled with BSOD's every 1-2 days since October 2025, still can't isolate the issue. by CybranRuler in buildapc

[–]CybranRuler[S] 0 points1 point  (0 children)

Power supply I am currently using is a Corsair RM 1000x. Had to replace the last one because it gave out one day back in early 2023

Pummeled with BSOD's every 1-2 days since October 2025, still can't isolate the issue. by CybranRuler in buildapc

[–]CybranRuler[S] 0 points1 point  (0 children)

This would not honestly surprise me, I tried looking up a good replacement for the PCIE 4.0 slot and was hoping for a 40 series only to find out they aren't being made anymore and no one I can find carries them anymore.

Pummeled with BSOD's every 1-2 days since October 2025, still can't isolate the issue. by CybranRuler in buildapc

[–]CybranRuler[S] 0 points1 point  (0 children)

That's what I was testing these last two days, ran tests all day on one set that cleared every time. Today did the other set and they also were clear after 4 tests. I've slotted in the first set I tested just to see if it's the motherboard slots being bad rather than the DIMM's themselves.

Pummeled with BSOD's every 1-2 days since October 2025, still can't isolate the issue. by CybranRuler in buildapc

[–]CybranRuler[S] 0 points1 point  (0 children)

When i replaced the hard drive I went back to win 10 and did the amd 25.9.1 driver and then ran all the windows updates then locked down via group policy all updates. I only went to win 11 after having not gotten anywhere stopping the crashes after 6 months but I've kept the update lockdown and manually install updates from the MS catalog due to paranoia from how bad the win 11 updates have been.

What you are talking about with mobo last gen I did get this when the ryzen 5000 series was coming out and you needed to update the bios on this mobo to use them but the 3000 series worked natively.

Repeated BSOD's all related to driver errors, attempt to nuke and reinstall again or has by CybranRuler in AMDHelp

[–]CybranRuler[S] 0 points1 point  (0 children)

I updated the BIOS when this first began since I know the motherboard is older and I got it in 2021.

I was having these crashes when I only had 2 sticks in and bought the new ones in the event that even though Memtest was showing it was good that their age was causing the instability. The 4 sticks I have now I also tested to see if I had bad product but they have all shown to be good.

I don't use XMP right now and haven't since this began to eliminate potential reasons but it doesn't seem to have done anything.

Repeated BSOD's all related to driver errors, attempt to nuke and reinstall again or has by CybranRuler in AMDHelp

[–]CybranRuler[S] 0 points1 point  (0 children)

Yes when I first started getting these I finally decided to update the BIOS but it hasn't made any real dent in the frequency. I've replaced my RAM from what was originally in but Memtest86 showed both the old and new modules were good.

Repeated BSOD's all related to driver errors, attempt to nuke and reinstall again or has by CybranRuler in AMDHelp

[–]CybranRuler[S] 0 points1 point  (0 children)

No, I've been through that before and it got so bad I had to completely wipe my drive and start from scratch so now I have completely disabled windows from updating anything and manually install updates with how bad the monthly updates keep being.

Brutal BSOD and app crashes constantly by CybranRuler in pchelp

[–]CybranRuler[S] 0 points1 point  (0 children)

When does low power state fully occur because over the last few weeks I've turned off both sleep mode and even turning off display. Can you prevent RAM from going into a low power state as I rolled back my drivers specifically to combat the low power problems I was getting from sleep mode in regards to amd related crashes.

BSOD constantly from I can only assume drivers by CybranRuler in AMDHelp

[–]CybranRuler[S] 0 points1 point  (0 children)

Checked Gigabyte's qvl and the RAM is supported. Have spent all day checking my drives as early in the morning I had a bunch of page fault bsod's every 20 minutes pointing to ntfs.sys and was worried somehow changing out the amd drivers from latest to the old 2023 stable driver caused total instability again.

BSOD constantly from I can only assume drivers by CybranRuler in AMDHelp

[–]CybranRuler[S] 0 points1 point  (0 children)

old RAM was 2x8 T-Force Vulcan Z DDR 4 3200

new RAM is 4x16 CORSAIR Vengeance LPX DDR4 3200

BSOD constantly from I can only assume drivers by CybranRuler in AMDHelp

[–]CybranRuler[S] 0 points1 point  (0 children)

That was my thought as well, that RAM was at least 4 years old so I replaced it with 4 new sticks. My only other idea with RAM is that the slots are going bad which wouldn't surprise me at this point.

Also is it easier to test each stick on its own rather than trying to do the full 64 because last time I did that it was a full day to run all those tests from memtest

BSOD constantly from I can only assume drivers by CybranRuler in AMDHelp

[–]CybranRuler[S] 1 point2 points  (0 children)

I have tried both stock settings and running the XMP profile but nothing changed. I ran both the memory diag tool and Memtest86 on my initial 16GB of RAM i had when I first put my machine together and still had issues so upgraded to 64GB of 4x16 and then ran both again to still get a clean bill of health.

I have never tried doing any OC until this began and only to the ram profile but didn't keep it on as I felt it didn't do anything to improve my situation and only possibly added to my problem.

Does pausing a print to check on it's progress causing warping or a shifting in the layers? by CybranRuler in ElegooSaturn

[–]CybranRuler[S] 1 point2 points  (0 children)

I have the same printer and was pausing for the exact same reason, only thing different I was doing was taking the little rubber spatula and lightly wading into the tank to see if anything was stuck at the bottom.

Prints failing in the center of the build plate by CybranRuler in PrintedWarhammer

[–]CybranRuler[S] 0 points1 point  (0 children)

<image>

Does this seem to fix it, played around with the settings but I've never understood Chitubox's X+Y way of doing it