What's new
Carbonite

South Africa's Top Online Tech Classifieds!
Register a free account today to become a member! (No Under 18's)
Home of C.U.D.

Constant BSOD, I've run out of ideas, need tech shop in Cape Town

XMP will work with AMD?
In general, yes. You might even notice it won't necessarily even be called XMP in BIOS, it may be called DOCP or something similar. But in practice it's still XMP.

Sometimes, XMP won't be stable for RAM not on your mobo's QVL list. However this issue is more rare on more recent Ryzen chips, it affected mainly first and second gen. And in general enabling XMP will be much more stable than just changing the RAM speed alone.

If I were you I would:

0. Don't open your new RAM when it arrives.
1. Reset BIOS to complete stock and leave it stock for now.
2. Ideally reinstall Windows. If your RAM has been unstable for ages your whole installation could be corrupt, causing issues even if you get your RAM stable.
3. With BIOS still stock, run P95 large FFTs for at least 8 hours or until you see an error. If you see any errors at stock BIOS and fresh Windows, you can pretty much give up on that RAM in that system. (Doesn't mean the RAM is necessarily faulty though, just incompatible).
4. If no errors, enable XMP on the RAM - no other BIOS changes! - and repeat step 3. If no errors, keep the RAM and return the new RAM unopened. If errors, I'd then try the new RAM from step 3 onwards.

AMD has EXPO.

Same, same but different.
Only from Ryzen 7000 and the 600-series chipsets though, I think? Before that you basically just used XMP RAM in your AMD system.
 
Reading through this thread is bringing back PTSD.

When i purchased and built my Ryzen 5000 series system I also got a Corsair Ram kit (3600Mhz two 2x8gb kits) that was not on my motherboards QVL list. System only ran stableish with XMP disabled but then was super unstable with XMP. RMA'D the two kits and supplier tested them indivdually and they were fine but together a disaster. Got a 4x8gb Kingston kit that was was on my mobo's QVL list and the system has been running stable ever since with XMP enabled.

Will definately always check motherboard QVL going forward.
 
@Shiizzo did the new SSD etc help ? Best way to tell will be to enable verifier again.
 
Excuse the lack of updates. PC was stable until Sunday night, where it had a BSOD. Did not have time to troubleshoot or change parts then, or last night. Yesterday I started the PC up, logged in, and it had a BSOD (literally did nothing on the PC, just logged in). Won't have time to troubleshoot or change parts until Friday.
 
Update: Installed new M.2 SSD, with fresh install of Windows 11. Will be monitoring now.

RAM is unchanged, PSU is unchanged.

Side note: How do I get rid of interference in my PC speakers? They make a doof doof doof noise constantly, unless something is playing, then it goes away.
 
Excuse the lack of updates. PC was stable until Sunday night, where it had a BSOD. Did not have time to troubleshoot or change parts then, or last night. Yesterday I started the PC up, logged in, and it had a BSOD (literally did nothing on the PC, just logged in). Won't have time to troubleshoot or change parts until Friday.
i had a similar issue with a laptop of mine.... BSOD for no apparent reason.. Everything was fine, installed an SSD and installed Windows 10 and from there constant BSOD with WHAE UNCORRECTABLE ERROR. Went back to windows 8.1 same thing, changed back to spinny disk, BSOD,could log on and if i leave it on windows desktop it's fine.. if i as much as look at it to want to do something...BSOD. mind you there was nothing installed on the either drives...just plain windows...

I thought of taking it to an exorcist and get some garlic and holy water, but i don't have that kind of money, and i used all the garlic in that evening's supper....so now it's a paperweight in my laptop bag.
 
Side note: How do I get rid of interference in my PC speakers? They make a doof doof doof noise constantly, unless something is playing, then it goes away.
Disregard. Interference was from cables that crossed each other...
 
Update: Switched on XMP on my 3600 RAM last night. PC still up since then, no BSOD.
Could it be the SSD was bad, even though it showed 80%+ status?
 
Yup. It was mentioned many times.
I would give this a go: How to Fix IRQL_NOT_LESS_OR_EQUAL Errors in Windows 10. Worked for me ounce. 90% sure this is storage or memory or mobo (dimm slots).
By the sounds of it drive errors were leading to increasing corruption of the windows drivers and services. Following the link above would have probably fixed it, if only temporarily. Exact same thing happened to me in the past. Glad you sorted it out.
 
Update: Switched on XMP on my 3600 RAM last night. PC still up since then, no BSOD.
Could it be the SSD was bad, even though it showed 80%+ status?
It was your RAM speed bud. Like I said before you can't just increase the RAM clock speed without adjusting the timings. You have to use XMP, or manually adjust the timings, if you increase RAM speed above 2133.
 
Update: Played some WoWS yesterday, and the game crashed. BSOD at 5AM this morning. PC just froze up on me a few minutes ago.
Turned down speed on RAM to 3200 from 3600. Will monitor today, and play a game after work to see if it crashes again.
 
Update: Played some WoWS yesterday, and the game crashed. BSOD at 5AM this morning. PC just froze up on me a few minutes ago.
Turned down speed on RAM to 3200 from 3600. Will monitor today, and play a game after work to see if it crashes again.
Is this with the new ram kit?
 
Yes. Anything below 100% is not good.
SSD health software usually reports SSD health as a percentage of how many TBW are left. E.g. if your drive is rated for 100TBW then as soon as you've written 1TB to the drive the health will show 99%. A 100TBW drive with 20TB written would show 80% health, at which point you would hardly expect it to be failing.

People often exceed the TBW value on SSDs and they still work fine.

So no, anything less than 100% is not automatically bad.
 
SSD health software usually reports SSD health as a percentage of how many TBW are left. E.g. if your drive is rated for 100TBW then as soon as you've written 1TB to the drive the health will show 99%. A 100TBW drive with 20TB written would show 80% health, at which point you would hardly expect it to be failing.

People often exceed the TBW value on SSDs and they still work fine.

So no, anything less than 100% is not automatically bad.
Not saying you're wrong but I disagree (If I understand what your saying + reading the SSD app correctly).

My SSD is rated for 300TBW. Currenty 9.3TB written. Drive health shows as 100% in Crystal disk info and HDSentinal.

My comprehension of what you're saying, is that my drive should be around 97% ?
 
Excuse the lack of updates. PC was stable until Sunday night, where it had a BSOD. Did not have time to troubleshoot or change parts then, or last night. Yesterday I started the PC up, logged in, and it had a BSOD (literally did nothing on the PC, just logged in). Won't have time to troubleshoot or change parts until Friday.

Was it cooler weather during the time it was running? Crashed under load after that? Sounds like PSU to me... Buy a new second hand one off carb and when it tests all ok then sell it again after
 
Not saying you're wrong but I disagree (If I understand what your saying + reading the SSD app correctly).

My SSD is rated for 300TBW. Currenty 9.3TB written. Drive health shows as 100% in Crystal disk info and HDSentinal.

My comprehension of what you're saying, is that my drive should be around 97% ?
HD Sentinel reports two values, Performance and Health. Performance checks various states on the drive while Health is a direct readout of % TBW remaining (it even says so in the description of how health is determined).

HWINFO reports drive remaining life in the same way as HD Sentinel.

CrystalDiskInfo I'm not sure of their exact methodology, but on my drive it's reporting the exact same value as the other two (which is % of TBW left). So I assume it's the same.

If your drive is at 3% TBW but reporting 100% health then it's reporting its stats to the apps differently to most drives.

Most drives, with all these apps, health = % of TBW remaining.

It's also the reason people ask people selling used SSDs to post the health reports, to get an idea of how many TB the drive has written. It's rare to see a used SSD with 100% health because they all tend to have had some writes in their lives. And why people are perfectly happy buying used drives with 90% or even 80% health.
 
Is this with the new ram kit?
This is not with 3200 RAM kit I bought most recently that is on the QVL list for my mobo. This was with the 3600 RAM that was in the PC the whole time, that is not on the QVL list for my mobo.

Played a few games of WoWS, and the game didn't crash. This is with the RAM running at 3200 instead of 3600. No BSOD since dropping speed on RAM.
 
Not saying you're wrong but I disagree (If I understand what your saying + reading the SSD app correctly).

My SSD is rated for 300TBW. Currenty 9.3TB written. Drive health shows as 100% in Crystal disk info and HDSentinal.

My comprehension of what you're saying, is that my drive should be around 97% ?

Depends on how the software interprets the drive stats, also 9.3 of 300 is about 3% which is generally within the over provisioning buffer set by manufacturers, samsung set their over provisioning at around 9% in which case the ssd health is theoretically 109% but you can only access 100% of it. So if the software can read the over provisioned section, you need to write up to that % of extra space before your drive health starts decreasing from 100% according to the raw values, if it doesn't have access to it then it only reports on the user accessible portion.
 
Thank you for the insight and knowledge @goldfritter & @Switch :) Very valuable to me. I'll digest it better over the weekend :) Might run some tests on my various SATA & M.2 SSD's to better improve my know-how here. Thanx again :)
 
Fuck me. These BSODs are so so regular now man.

Got a few recently. All different reasons.
Nephew getting random shut downs as well.
Another person I know also has BSODs.

Pretty sure it's shit software from NVIDIA or Microsoft. Or ram stick chips are just not being built like they used to. Seen so so many lately it's crazy.
 
Fuck me. These BSODs are so so regular now man.

Got a few recently. All different reasons.
Nephew getting random shut downs as well.
Another person I know also has BSODs.

Pretty sure it's shit software from NVIDIA or Microsoft. Or ram stick chips are just not being built like they used to. Seen so so many lately it's crazy.
I've also seen more of a trend of more BSOD's and no-display issues on desktops in the last 2-3months (here on Carbs and with clients / friends).

I suspect MS, specifically W11 (no real evidence why Win11 over W10, just a bit of a pattern forming, I think).
 
I've also seen more of a trend of more BSOD's and no-display issues on desktops in the last 2-3months (here on Carbs and with clients / friends).

I suspect MS, specifically W11 (no real evidence why Win11 over W10, just a bit of a pattern forming, I think).
100% agree on Windows 11. And every update seems worse and worse. Maybe TPM? Dunno.
 
This is not with 3200 RAM kit I bought most recently that is on the QVL list for my mobo. This was with the 3600 RAM that was in the PC the whole time, that is not on the QVL list for my mobo.

Played a few games of WoWS, and the game didn't crash. This is with the RAM running at 3200 instead of 3600. No BSOD since dropping speed on RAM.
Technically the Ryzen 3600 is only rated to run the RAM at 3200MHz. Normally they're fine to run a bit faster... But perhaps your particular CPU is just more picky.
 
Update: Two BSOD's yesterday. Today I have swapped in the 3200mHz RAM I bought recently that is on the QVL list for my mobo. Will continue to monitor.
 
Update: Two BSOD's yesterday. Today I have swapped in the 3200mHz RAM I bought recently that is on the QVL list for my mobo. Will continue to monitor.
When you put in the new RAM I strongly suggest a clean install of Windows with the BIOS at completely stock (XMP off). If your Windows install became corrupt over time due to unstable RAM (which is quite likely) you may continue to get BSODs even if your RAM is stable.
 
Sigh...
BSOD (hypervisor error) after installing new 3200 RAM on QVL list. I'll do the windows reinstall, but I'm going back to Windows 10.

I just got everything reinstalled!
 

Users who are viewing this thread

Latest posts

Back
Top Bottom