I didn't try but will do, also run some memory tests to confirmDid you check/swap the flash drive which you used to setup windows ?. Just try changing the flash drive and also try using it on a different usb port to install windows.
Do the memtest86 on default 2133/2400MHz first. If it fails you have a bad memory module. If not then use XMP profiles to test the same.I didn't try but will do, also run some memory tests to confirm
I did made a small change in the BIOS and selected XMP1 profile for 3000Mhz, where as XMP was on 3200Mhz (currently using XPG 3200 kit)
"I can rule out motherboard slots issue as I've also tested same hardware with another Asrock b550 board and got errors".Sure I'll try with another stick and see if there is an error.
Didn't run any test as this is a new kit also the motherboard is new as well. Infact everything is new leaving processor/gpu which I bought second hand.
I can rule out motherboard slots issue as I've also tested same hardware with another Asrock b550 board and got errors, upto now I was thinking all these errors were due to SMPS but that's changed as well.
How to get these details from minidump files?==================================================
Dump File : 031321-2968-01.dmp
Crash Time : 13-03-2021 16:33:21
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000240
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff802`3d65900a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5210
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.18362.1440 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5210
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031321-2968-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 19041
Dump File Size : 799,804
Dump File Time : 13-03-2021 16:33:51
==================================================
This is the latest error report, I've installed totally new windows and as expected it crashed giving this error
I am getting following BSOD anyone help.
So it might just be that you're experiencing issues with XMP which is fine since it's not always guaranteed to work at XMP with all configurations. You can always manually tune your RAM to 3000Mhz I think it would work at that and then maybe if you're feeling adventurous enough you can tune the timings.Tried memtest86 without XMP profile and got No error for first pass, though I had to stop the test for next 3 passes as I needed my PC for work. Will run full scan when I have couple of free hours to let it run without disturbance.
from options/select save the report as textI am getting following BSOD anyone help.
How to get these details from minidump files?
I haven't tried running PC without XMP yet but will try to see if there are crashes. I haven't done any OC so will be new for me but I can learn provided there is time for researchSo it might just be that you're experiencing issues with XMP which is fine since it's not always guaranteed to work at XMP with all configurations. You can always manually tune your RAM to 3000Mhz I think it would work at that and then maybe if you're feeling adventurous enough you can tune the timings.
I think its better to post here as we have similar issues.You should start a new thread, and not hijack anyone else's thread, which is already running long.
thanks got it.from options/select save the report as text
XMP is OC. Just that don't have to do it manually but settings/values are saved in the RAM itself as profiles. That's what extra you pay for when buying anything higher than 2133/2400Mhz.I haven't tried running PC without XMP yet but will try to see if there are crashes. I haven't done any OC so will be new for me but I can learn provided there is time for research
Thanks, that much I know but what I meant was that I haven't OC's anything manually before so if I need to use full potential of these RAMs then i will have to manually find the sweet spotXMP is OC. Just that don't have to do it manually but settings/values are saved in the RAM itself as profiles. That's what extra you pay for when buying anything higher than 2133/2400Mhz.
A factory overclock profile which is not guaranteed to work xD
Good thing there are many videos on YT. The gist is that first you need to set a frequency and see if that's fine, ideally if 3200Mhz doesn't work try 3000Mhz if memtest86 passes then if you want you can tune the timings.Thanks, that much I know but what I meant was that I haven't OC's anything manually before so if I need to use full potential of these RAMs then i will have to manually find the sweet spot
Did you try some other CPU? Ryzen 3000 series supports 3200 MHz out of the box. If it is crashing/hanging. The CPU memory controller might be causing trouble since you have already made sure slots and ram are not an issue.Thanks, that much I know but what I meant was that I haven't OC's anything manually before so if I need to use full potential of these RAMs then i will have to manually find the sweet spot
Do you know for a fact that your SSD is good? You can test that SSD on a known set of good hardware. I've had BSODs due to faulty HDD in the past too.The same set of hardware works perfectly fine when i use my other HD where as all these errors pop up when i try new SSD (NVMe or SATA), I am working on the same PC with same CPU and RAMs since morning and no crashes what so ever. Now that makes me believe that it might be Windows thats causing those errors but at this point in time I i just don't know whats the problem
Yes its good for sure, I've sent it for RMA and got a new one as replacement also have new NVMe SSDDo you know for a fact that your SSD is good? You can test that SSD on a known set of good hardware. I've had BSODs due to faulty HDD in the past too.
Lots of questions to ask. Did you rule out that the RAM is not faulty? How long does the system stay on before crash? Is there any particular event that causes the crash (e.g. opening a game or browser etc?The same set of hardware works perfectly fine when i use my other HD where as all these errors pop up when i try new SSD (NVMe or SATA), I am working on the same PC with same CPU and RAMs since morning and no crashes what so ever. Now that makes me believe that it might be Windows thats causing those errors but at this point in time I i just don't know whats the problem