BSODs at startup mystery - tl;dr + daily log

Associate
Joined
26 Oct 2020
Posts
7
tl;dr - get BSOD sometimes during startup. It's not Windows, drivers or storage drives. Happens even with RAM A-XMP profiles and Try It! Is there any usual cause? Or, save replacing every part, is it a lost cause and just live with it?

Full version + log - When I upgraded to new motherboard (Mortar Max), CPU (Ryzen 3600) and RAM (2 x 8 GB Corsair Vengeance LPX @ 3200 MHz), I started getting BSODs during startup (just after splash, before desktop) but it restarted itself so not a big deal. I figured it was due to driver conflict, so I got an SSD eventually and used that as a boot drive. But nope, still happening, even with the old drive disconnected.

My next check was the RAM. I haven't done MemTest but I've done Windows' memory test with default settings and it found nothing. I reinserted the RAM and have tried both A-XMP profiles (which seem to be identical anyway) and Memory Try It! but still get them. Only thing left to try is just manually setting RAM speed to the 3200 MHz it should be at (it defaults at 2133) and MemTest. Maybe update BIOS if there is one.

I even tried using an NVIDIA driver from before the BSODs.

PSU? Guessing not.
Motherboard? Sure hope not.
GPU memory being daft? Random guess.

I also got a couple of new things now, as seen in the log. Also, one more random oddity: Using VLC player, now when I pause I risk the video (not audio) getting garbled when I resume, which can be undone by clicking another time in the video.

Now the log. I upgraded in June but only got the SSD recently, so I started logging a few weeks ago. I think I started with A-XMP profile 2. I boot up every day. Enjoy:

4th oct - BSOD

6th - BSOD

7th - system thread exception not handled BSOD

8th - uninstall nvidia driver and install new driver

9 - system thread exception not handled BSOD
9 - HDD disconnected
9 - multiple restarts, no bsod

10 - memory_management BSOD but after boot

12 - HDD reconnected

14 - memory_management long after boot
14 - microsoft memory test clear, uninstall nvidia driver and reinstall March nvidia driver
14 - No BSOD but shuts down a few secs into boot
14 - HDD disconnected

15 - kernel_security_check_failure BSOD
15 - Reconnected hdd, reinserted RAM, change to a-xmp 1

20 - system_service_exception BSOD

21 - No BSOD but restarts like one again
21 - Change a-xmp to 2

22 - Black and hear a windows notification or 'device inserted' noise, after a couple minutes press power button (which usually does nothing but will turn off PC if it's screwing up) and screen goes orange and cursor can be moved. Another minute or 2, I turn off (holding power button)

22 - Boots with .dll error (realtek), then try open Firefox and supposedly .dll missing and XCOM missing. Jsut restart myself.

24 - kernel_security_check_failure BSOD
24 - turn off a-xmp altogether and use Memory try it!

25 - kernel BSOD
 
I got a new BSOD: video scheduler internal error

BSODs are a mystery never to be solved, but the word 'video' obviously jumps out. The only other video card I have is an 8800 GT, but there's no point getting that dusty thing out to check it's the card when I'd just put it back in anyway.

I've just played all of Watch Dogs Legion fine, it's still only coming up during boot. Even on days it doesn't happen, something funny like not being able to search in File Explorer happens and I have to restart anyway to fix it. But with an SSD now it's still not a big problem.
 
UPDATE: Updating the BIOS didn't seem to work (I got a BSOD but quite a while after booting), but keeping the RAM at default 2133MHz (rather than the 3200Mhz it should be on) hasn't got one in the past few days yet.
 
Question: How do you know this isn't Windows related? You say you got a new motherboard, but didn't mention anything about reinstalling Windows.

Honestly the first thing that came to mind is that you're running your 'previous' Windows installation on all-new hardware, and that's bound to cause issues
 
Question: How do you know this isn't Windows related? You say you got a new motherboard, but didn't mention anything about reinstalling Windows.

Honestly the first thing that came to mind is that you're running your 'previous' Windows installation on all-new hardware, and that's bound to cause issues

It's a new installation of Windows on the new SSD drive as the new boot drive.
 
Ah, okay!

I have only two thoughts:
1) Try running with a single RAM stick and seeing how that goes. If issue remains, change to the other and see how that works out.
2) If at all possible, try using a Linux distribution and see how that compares. Most will run off USB/CD so you can try leaving it running and poking around to see if you get any lockups

Sorry I can't think of much more right now, but I hope you get the issue sorted
 
Does this only happen on start-up after your PC has been shutdown? Does it run fine on restarts?

I had that happen to me and it turned out to be the PSU. Luckily I had one to hand to test out.
 
Does this only happen on start-up after your PC has been shutdown? Does it run fine on restarts?

I had that happen to me and it turned out to be the PSU. Luckily I had one to hand to test out.

Yeah, only seems to happen sometimes the first time I start it for the day. Never on restart or if I shut down and wait a bit.

It's not done it since I put the RAM speed back to 2133MHz. Someone's sending me RAM so I can see if it's that or not for sure.
 
sounds very much like its the RAM's fault here. I'd try identifying if its a particular stick.

I assume you've plugged them into the appropriate slots for your mobo? (manual should recommend which slots to be filled first)
 
Back
Top Bottom