2

It's been some time now I'm getting BSOD and reboots (generally message is critical process died). It seemed to appear after I moved house or after I move my computer. I kinda "resolved it" by placing my PC horizontally. Not a good resolve since I have the problem once again.

It generally appears while playing games, not youtube or netflix for example.

When it reboots, sometimes it goes directly to BIOS configuration and the boot options don't seem to recognize the SSD my OS (Windows 10) is installed on (the only disk in the computer). That's how I started guessing that maybe the problem comes from the SSD. SSD is samsung evo 970, it's a NVMe M.2 SSD.

I tried applying a slight pressure on the SSD and it reproduced the issue. Applying slight pressures on other parts of the motherboard rarely reproduce it but sometime does. The thing is, I don't know if I should change the SSD or if the motherboard is the issue. Maybe it's only the NVMe M.2 connector but there is only one on the motherboard so I can't cross check. Maybe it's another part of the motherboard. Maybe it's a software problem since it happens without me having to apply pressure on any hardware part (even if it reproduces the issue). My guess was that when the fans of the motherboards are running fast, for example in games) it created vibrations creating the problem (similar to when I touch the SSD).

I can't get any minidump when it happens, BSOD stay stuck at 0% collecting information. Having a minidump would help me though...

So here are my two questions :

  1. How can I have minidumps, how can I get the information collection unstuck ?
  2. What do you think the problem can come from ?

Thanks ! FYI the computer has less than a year old so maybe I can have some pieces exchanged still... But still I'd like some advices before asking for it.

EDIT :

Here are my performance and Startup and Recovery setting for minidumps :

Virtual Memory is auto : 34816MB (I have 32Go of RAM) System and recovery : Dump File : %SystemRoot%\MEMORY.DMP Complete memory dump.

I installed whocrashed and I have the crash test dump. Is it possible that if it comes from the SSD, the minidum can simply not be written on it ?

EDIT 2 : I ran Prime95 today for 5 hours. With an open case. After 30mn, CPU was at 76°C (generally run around 50°C) and SSD 61°C, after 5 hours CPU was at 85°C and SSD 58°C.

I'll try with a closed case tomorrow.

I'll also try a GPU stress test with closed case. SSD is just next to the GPU fans so I guess maybe the hot air from the GPU heats the SSD.

EDIT 18/08/2020

Yesterday it ran ok for hours of gaming, no problem. At one moment for a totally unrelated thing, I plugged one cable on the motherboard, not far from the SSD. When I tried booting the computer, it went directly on bios menu, SSD was unrecognized. I touched the SSD to see if it was well seated. Afterwards, PC booted but after some minutes, it crashed with BSOD Kernel Data Inpage. Tried Prime95, it crashed instant. SSD was really hot, 72°C (Samsung advises max 70°C for this model).

I shut the PC down. I booted it this morning and now Prime95 make it crash after a few tens of minutes. SSD runs around 65 to 70°C temperature real quick. My conclusions for now is that I a parts seating issue (Some of the screws aren't there...) (that's why PC start crashing after I move it or if I touch the motherboard around the SSD) and a heat problem (which seem to only happen after I touch the motherboard but maybe both are related ? ).

Maybe it's just I damaged the card because of the lack of some screws...

I just reset windows to be sure there is no software issue.

Improve this question
10
  • System has to be configured for minidumps from within Windows, can you boot into windows at all?
    – Moab
    Commented Aug 16, 2020 at 17:50
  • Yes I can. Everything is running fine sometimes for 1 or 2 hours before a BSOD happens again. I edited my post with my "minidump configuration".
    – JadenBZH
    Commented Aug 16, 2020 at 17:59
  • Have you cleaned the contacts? Presumably it's a 'hardware fit' drive rather than using an SATA cable, but if it isn't, clean all the contacts [can of contact cleaner $£€ 6 on ebay] change the SATA cable, make sure it has no pressure on it when in situ with casings closed. Bad contacts or cable will have you running in circles chasing your tail, every BSOD with a different apparent cause.
    – Tetsujin
    Commented Aug 16, 2020 at 18:11
  • 1
    Yep, it's not a SATA cable, it's an M.2 port. I haven't cleaned the contacts, I guess I'll try when I'll be a bit more sure it comes from the SSD.
    – JadenBZH
    Commented Aug 16, 2020 at 18:20
  • That is a full dump, configure it for a minidump, they are easier to read.
    – Moab
    Commented Aug 16, 2020 at 20:01

2 Answers 2

Reset to default
1

I had exactly the same problem, except that the bluescreens appeared the other way around - they would only appear when doing mundane browsing, and not when gaming.

For me the issue would appear in periods of my life when I moved around a lot, then gradually disappear afterwards. This year however, one of the BSOD's must've corrupted some Windows files, as it stopped booting altogether. Unfortunately no repair tools worked, so I made a backup.

After reinstalling Windows and reseating the SSD the issue seems to be fixed as well.

(My laptop is a Y520)

Improve this answer
3
  • I am not sure if that is going to help anyone
    – Rohit Gupta
    Commented Sep 8, 2022 at 21:11
  • @RohitGupta Perhaps not, but I felt a contribution to a 2-year old post with no upvotes causes little harm, and might make it easier for people with a similar problem to find this post (I had to search for hours upon hours). Either way, I'm new here, so if you consider it irrelevant I will delete it.
    – winnie33
    Commented Sep 10, 2022 at 8:41
  • No, its not my site. Its ours.:-)
    – Rohit Gupta
    Commented Sep 10, 2022 at 8:49
0

Unseating and reseating the SSD fixed the issue.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .