Crashing after booting from hibernate

tomdsr said:

same issue

dalchina said:

Have you actually tried a RAM check? (Yes, I know it's new...)
And presumably you're not overclocking...?

I haven't done any overclocking apart from using the XMP on my RAM.

Actually, the 32GB kit that I'm using right now is not exactly new since it came from my 2nd system which stayed there for about 7+ months with no issues. It even had a system up time of 70+ days from the hibernation and shut downs with fast startup. Though with the 32GB kit on my 2nd system before, I had to do a manual OC so it was at 2933 MHz since XMP was a no go there.

So here's my plan of action: I'm gonna be free in the next couple of days so I would be able to speed up the testing process by hibernating the PC soon after it boots up and repeat the process (until it crashes).

1. Run my current RAM at JEDEC speed (2133).

2. Use my older 16GB Trident Z RGB kit and test between XMP and JEDEC.

3. Disconnect any other storage device so only the boot drive is present.

In each of those steps I'll test the hibernation. I'll report back my findings afterwards.

So slight change of plan...

Before doing any doing of those 1-3 things, I decided to disable and enable hibernation once more. Nothing else.

When I did the continuous hibernations, I finally got to do 15 hibernations and boot ups from it. That's the first time I reached double digits since getting this PC.

Now I'm wondering if this actually fixed the issue or maybe it could be time-based where the issue only appears when the system uptime goes on for longer. From what I noticed, the issue seemed to have happened when the uptime was >72 hours. I will do further monitoring.

And my computer crashed again. It does look like the length of system uptime has an influence on whether or not the issue will happen. I guess testing is gonna be slow if that is the case since I only did 2 successful hibernations since my previous post.

- - - Updated - - -

Another change of plan since I think this one would be easier to do for me. I got my Crucial P5 Plus 2 TB today, which was supposed to be used for game storage. But to help check my SSD's integrity, I decided to clone the contents of the MP600 to the P5 Plus.

I have turned off, then turned on the hibernation in my new boot drive in the P5 Plus to ensure nothing is carried over from the clone. And only that action. I will report my findings (once I crash again [hopefully not anymore]).

Been busy for a while so I was not able to post an update, but so far it seems things are doing better for my computer.

I have disabled XMP for the moment and it would appear that my computer is not crashing anymore after booting from hibernation. It's currently 11 days of up time, the longest it has been since getting this computer.

Never knew that hibernation was the way to find out the instability of my computer from the XMP. I might try updating the BIOS of my mobo and try checking the stability of the XMP again. Current BIOS is 7E06v14 (2023-01-09) and MSI has 7E06v15
(2023-03-24) as the latest one and it mentions better memory compatibility.

Full list of what I did since my last post:

-Returned to using the MP600 as my boot drive. No cloning from P5 Plus to MP600 was done so the SSD was pretty much how it was prior to installing the P5 Plus.

-Disabled XMP from the BIOS.

-Disabled then enabled hibernation again.

-And now using the desktop without hitches so far.

So this is probably my last update regarding this issue.

It would seem that I'm just unlucky with the XMP setting of my RAM. Either I don't use it or I have to do further RAM OC tweaking.

A BIOS update did not help with my issue. I would still get the crashing from hibernates.

For now, what I did is just set my RAM to 3200 MHz and I think it's a good enough compromise. It has been a stable experience. I'd probably consider buying a new bigger set in the future and hopefully that one would be a smoother experience.