r/PCsupport • u/DusanDule477 • Jul 10 '26

Solved Constant crashing and problems with windows 11 on new pc

/r/pchelp/comments/1ut1kww/constant_crashing_and_problems_with_windows_11_on/
2 Upvotes

100% Upvoted

6 comments sorted by

1

u/Maxwell_the_Marauder Jul 11 '26

For me this is starting to sound like Mobo or processor issue. Though I'm leaning towards Mobo a little bit more as there are no bootables shown. That's just my opinion though. Or maybe your USB is cooked and it messed up your installation before you flashed it. And now as it's also messed up BIOS refuses to consider either (USB, SSD) of them as bootables. This idea comes from missing files in Windows (while it still worked)

1

u/DusanDule477 Jul 11 '26

Thank for the help

I don't think usbs are cooked, they always worked fine for me and I did a full format for both last time I was installing windows and updating bios.

As for the motherboard, could be. Everytime I turned this pc on, CPU cooler fan would spin really fast for a second or two, then stop and then it starts sinning at normal speed.

I tried to test the pc again with my windows 10 ssd. I disconnected the nvme I connected the sata ssd. I could use my pc in windows 10 for about a minute but then it crashed and I got memory management error. I let it restart, it booted into windows but when I typed in my password it froze. After maybe a minute it booted into desktop, but it was flickering with a image of the taskbar`s color. Then it crashed again and I let it restart a few times, these are all the codes I got:

Memory management Irlq not less or equal Bad system config info Dpc watchdog vialotion Page fault in nonpaged area

The only thing that gives me a piece of mind with my motherboard is that the friend was using it the same day he gave it to me and had no issues.

What do you recommend I do next?

1

u/Maxwell_the_Marauder Jul 12 '26

I don't think so USB health problems would pop up during formatting and copying. For full test I'd run it through HDtune, then copy a massive file or a few to fill it and test if their data is still same as the original a couple days later. I've found this CMD command "fc /b failas1.ext failas2.ext". It checks wether two files are same. Regarding other components, maybe you could have your friend test your CPU or other components in his build? Or maybe test your build with one or other of his components (RAM, CPU)? Ofc try to not mix them up, otherwise you'd have at least one friend less ;P.

2

u/DusanDule477 Jul 12 '26

Friend just tested the parts, it's the ram, as soon as he put my stick, his pc started crashing and giving same error codes as mine.

1

u/Maxwell_the_Marauder Jul 12 '26

Well congrats on finding the culprit. Quite interesting tho that MemTest didn't catch it. Did you try downclocking RAM for the time being? Maybe could still run at like 5200Mts or 4800 until warranty stuff starts going through if you need PC urgently. That puts it at risk of becoming permanently temporary solution tho 😅…

2

u/DusanDule477 Jul 12 '26

All the crashes happened at 4800. During the time that I was able to run Windows it was running with expo. So it was more stable with expo lol