#sometimes laggy and slow restart and then Blue Screen

1 messages · Page 1 of 1 (latest)

robust helm
#

Hi, I have a problem, sometimes when I restart my PC, it takes a very long time to restart and the wheel under the ASrock logo spins terribly laggy, then I get a BSOD and the PC restarts and goes back to the OS without a problem, I can solve the problem in the meantime by restarting the PC with a physical button on the case but that's not the best solution, I've reset the cmos, run memory diagnostics, update OS disk firmware, updated the BIOS, even reinstalled windows cleanly, but it didn't help. i have r5 7600 32gb ram and 7800xt thanks for your help.

Screenshot_2024-10-04_231140.png Snimek_obrazovky_2024-10-04_233112.png
#

BSOD is kernel-power and precedes it volmgr

robust helm
#

Can someone help me?

fluid rune
#

@robust helm The volmgr one, does it say that it was unable to create a dump file?

#

If yes, could you check if any of the crashes have been able to create one? Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

#

If you don't have any dump files, screenshot the Details tab of the Kernel-Power Event 41 crash.

robust helm
robust helm
fluid rune
#

Upload it

robust helm
#

where? here?

robust helm
fluid rune
#

I'm the one downloading something from you.

#

How could that infect your PC?

robust helm
#

here it is @fluid rune

robust helm
fluid rune
#

I was looking at the dump file.

#

This was just a memory error. Memory doesn't have to mean RAM, but it's usually the main suspect. Because of the page file storage can look like memory, the memory controller is in the CPU and if this has issues it can look like memory.

#

Because of the errors creating dump files, storage is higher up as a suspect.

#

Open Event Viewer and go to Windows logs → System.

#

On the right hand side, select Filter Current Log. In the Event Sources dropdown menu, select "WHEA-logger".

#

If you have any WHEA events, highlight them (4-5 newest ones if you have lots), right click and save. Upload the .evtx file here.

robust helm
fluid rune
#

@robust helm Ok. Debugging from just one dump file can also be inaccurate. We don't know if that crash was the same as everything else.

#

But just from that one, I would say it's storage, RAM or the CPU.

#

I know you've ran memory diagnostics, but they just aren't that reliable with DDR4 and newer.

#

You are running EXPO so it might be that as well. 6000 isn't crazy fast, but if you get unlucky with the CPU it might be too much for it.

#

You are on the newest BIOS which is good.

fluid rune
robust helm
robust helm
fluid rune
#

We tried all sorts of memory testers when we noticed DDR4 being missed a lot.

#

Even Google's tool that they use on their servers.

#

We took a known faulty kit and ran it through all of them, and none of them reliably found errors.

#

When I say "we", I am on a different server dedicated to tech support.

#

Not having a tool to test RAM was a pain in the ass so we looked hard.

robust helm
fluid rune
#

Set the speed to 5200MT/s. If you crash, use one stick at a time.

#

Check the manual for which slot to use.

#

If it crashes with either stick, the CPU would be my next suspect.

#

Though I would also like more dump files.