BSOD before Windows loads - Diagnosing / Dead RAM?

Swi1ch

Swi1ch

Swi1ch

Associate
Joined
19 Nov 2008
Posts
1,581
5900x
MSI B570S Tomahawk Max
Teamgroup ProDark 8PACK 32GB
3080TI
Corsair RM1000x

Started getting BSODs in August 2024. At the time I put the machine aside and I've only just gotten around to sorting it. On first power on it BSOD'd as soon as Windows loaded. I wiped the drives entirely and did a fresh install of W11. I then ran a bunch of OCCT tests, memtest86 passes, and some 3DMark for good measure - everything seemed to be fine. That was two weeks ago and it's been running great at everything (general work stuff, 3D modelling, gaming) up until this morning.

I had a BSOD an hour or so after power on. After the restart it instantly BSOD'd again after logging into Windows, and then after that it BSOD's before I can even get to the login screen. The BSOD codes seem to imply that the RAM may be at fault:
IRQL_NOT_LESS_OR_EQUAL (0XA) - ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA (0X50)
KMODE_EXCEPTION_NOT_HANDLED (0X1C) - ACP.sys

I tried running with a single stick in slot 2 to see if one of them has died. Stick 1 would boot but BSODs before Windows login, stick 2 would not POST. Putting both sticks in would then boot but instant BSOD. On a second test run I can't get either stick in any slot to POST.

Is this sufficiently conclusive to call it the RAM at fault? I could do with being reasonably sure as I have lifetime warranty with OCUK on these sticks, but I'm a little concerned that with both sticks not working it may indicate something else at fault, and now I can't even boot the machine I can't run anymore tests.
 
Swi1ch said:
5900x
MSI B570S Tomahawk Max
Teamgroup ProDark 8PACK 32GB
3080TI
Corsair RM1000x

Started getting BSODs in August 2024. At the time I put the machine aside and I've only just gotten around to sorting it. On first power on it BSOD'd as soon as Windows loaded. I wiped the drives entirely and did a fresh install of W11. I then ran a bunch of OCCT tests, memtest86 passes, and some 3DMark for good measure - everything seemed to be fine. That was two weeks ago and it's been running great at everything (general work stuff, 3D modelling, gaming) up until this morning.

I had a BSOD an hour or so after power on. After the restart it instantly BSOD'd again after logging into Windows, and then after that it BSOD's before I can even get to the login screen. The BSOD codes seem to imply that the RAM may be at fault:
IRQL_NOT_LESS_OR_EQUAL (0XA) - ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA (0X50)
KMODE_EXCEPTION_NOT_HANDLED (0X1C) - ACP.sys

I tried running with a single stick in slot 2 to see if one of them has died. Stick 1 would boot but BSODs before Windows login, stick 2 would not POST. Putting both sticks in would then boot but instant BSOD. On a second test run I can't get either stick in any slot to POST.

Is this sufficiently conclusive to call it the RAM at fault? I could do with being reasonably sure as I have lifetime warranty with OCUK on these sticks, but I'm a little concerned that with both sticks not working it may indicate something else at fault, and now I can't even boot the machine I can't run anymore tests.
Click to expand...
 
A few things I would try.

- Clear CMOS, remove the battery, disconnect from mains then hold power button down for 30 seconds to discharge any remaining power.
- Disable fast boot in Windows.

If this system has been sitting aside for over a year do you have another system you have been using? Could you swap the ram from another system? (if you have 1)

Have you tried the ram in slots 3/4 (if your motherboard has 4 x dimm slots) was unable to find the model posted as something else came out)

Only other thing is it could be the motherboard causing the issues or the CPU? Could try re seating the CPU and while at it checking pins etc.
 
I'll have a go at clearing the CMOS tomorrow. I can't disable fast boot in Windows as I can't get to Windows, or the BIOS.

I do have a system in use aside from this, but it's been ropey at best for a long time and I'm taking a don't break what ain't broke approach, so I'm loathe to touch it. I think I can borrow some DDR4 to test with instead.

I tried all of the dimm slots with no change.

I've manged to get access to a similar motherboard I can use for testing, I hope to give that a go over the weekend.

It's possible that it's the CPU but that seems extraordinariliy unlikely - that would make it the second time that this CPU has failed in this machine.
 
You must log in or register to reply here.
Back
Top Bottom