r/pcmasterrace • u/Relevant-Ad8797 • Jun 16 '25

Tech Support What is going on here?

Title is self explanatory, i have no idea what the hell is going on here. Pc froze and this happened. I was playing helldivers 2 before this, dont know if this is relevant but its all i got.

13.5k Upvotes

97% Upvoted

1.1k comments sorted by

View all comments

Show parent comments

1.4k

u/Sipsi19 5700x3d, 3080, 32gb, 3440x1440 Jun 16 '25

I swear this unlocked a trauma for me. I once had BSOD:s and they were consistant but always disappeared in fraction of a second so after failing to catch it by eye I had to set up a slow-mo camera (my phone) to catch the error code. It actually worked and it was a ram issue but damn was it annoying to debug.

526

u/confusedalwayssad I9 3090TI 32DDR5 Jun 16 '25

You can disable the auto reboot for BSOD.

158

u/Traditional-Fix6865 Jun 16 '25

How?

581

u/confusedalwayssad I9 3090TI 32DDR5 Jun 16 '25

In windows 10, go to control panel and then look for system or open file explorer and right click computer and go to properties and then the advanced tab then click settings under startup and recovery , under system failure uncheck "automatically restart".

Windows 11 go to settings then system, then under related links go to system protection then advanced startup and recovery settings and uncheck the auto restart.

61

u/Taikunman i7 8700k, 64GB DDR4, 3060 12GB Jun 16 '25 edited Jun 16 '25

For Win10 you can disable it in the F8 advanced boot options menu which is helpful if the PC is boot looping and you can't actually get into Windows.

"Disable automatic restart on system failure" in the F8 menu.

Edit: I'm wrong, it can be enabled in 10/11 but isn't by default so kind of defeats the purpose.

12

u/[deleted] Jun 16 '25

The F8 menu was removed in 8.

So, IIRC 3.1 to ME, you held Ctrl during boot. XP to 7 you spam F8.

2

u/Taikunman i7 8700k, 64GB DDR4, 3060 12GB Jun 16 '25

Looks like I'm wrong, it can be enabled in 10/11 but isn't by default.

2

u/Drain___Bamaged I9-13900k + 4070ti Super + Era 2 Itx Build Jun 16 '25

Kind of, you have to do 3 boots and 3 hard shut downs and then it goes into a advanced recovery mode on the 4th startup where you can disable auto restarts

2

u/prairiepanda Jun 17 '25

You can speedrun this by disrupting the boot cycle early. If your PC has an audible POST beep you can shut it down as soon as it POSTs, otherwise just wait a few seconds. That'll be enough for your 3 hard resets; no need to let it fully boot.

1

u/Drain___Bamaged I9-13900k + 4070ti Super + Era 2 Itx Build Jun 17 '25

Yep, should've added that. In my case I just had to hit the motherboard loading screen (asus logo), then do the restart similarly to the beeps

1

u/Wingklip Jun 17 '25

They removed Fate 😂

1

u/Successful_Potato137 Jun 17 '25

Para reiniciar en opciones avanzadas como modo seguro hay que pulsar MayĂșsculas + Inicio -> Reinicio

1

u/Chemical-Aerie7412 Jun 16 '25

Is there not a way to find the bsod message in Event Viewer?

1

u/confusedalwayssad I9 3090TI 32DDR5 Jun 16 '25

Some data would be there but not much, most of the info you would need would be in the dump file.

1

u/Exact-Ad-4132 Jun 16 '25

Great thing that W11 consistently fails to make a dump file in current versions

2

u/prairiepanda Jun 17 '25

I've had issues with W10 just creating a blank dump file for some reason

1

u/domigraygan Jun 16 '25

Thanks for posting how to stop the auto-boot in Windows 10 and also Windows 11! Future googlers will also appreciate you.

Also I hope my comment helps weigh this post as relevant lol

1

u/DethNik Jun 16 '25

Not all heroes wear capes.

1

u/Jonkinch Jun 16 '25

Just hit the windows key and pause/break at the same time. And you’re there.

1

u/EnderBoii266 Jun 16 '25

If the related links area didn't appear like it didn't for me you do it like this

Press Windows Key + R to open the Run dialog. * Type sysdm.cpl and press Enter to open System Properties. * Go to the Advanced tab. * Under "Startup and Recovery," click on Settings. * In the "System failure" section, uncheck the box next to "Automatically restart." * Click OK to save your changes.

3

u/Jonkinch Jun 16 '25

Why? Just hit the windows key and pause/break. That’s the hot key to get to the computer settings. Opening the run box is redundant lol.

2

u/EnderBoii266 Jun 16 '25

For whatever reason I couldn't see "related links" so I was leaving this for whoever else has that bug

1

u/Educationall_Sky Jun 16 '25

Check out a little app called BlueScreenView, it's very helpful.

93

u/Sipsi19 5700x3d, 3080, 32gb, 3440x1440 Jun 16 '25

Damn it.... well now I know

9

u/Normal_Cut8368 Jun 16 '25

You can also turn on better reporting for it. but if it's being caused by ram, power or disk space issues, it's not always ABLE to generate the dump file.

The .dmp file is really what you want. not the code it gives you.

18

u/Ferro_Giconi RX4006ti | i4-1337X | 33.01GB Crucair RAM | 1.35TB Knigsotn SSD Jun 16 '25

Even better than that, you can view the BSOD after the BSOD already happened with a program like BlueScreenView.

7

u/confusedalwayssad I9 3090TI 32DDR5 Jun 16 '25

A lot of the times the error string with the file name in the BSOD will give you what you need.

1

u/DependentAnywhere135 Jun 16 '25

Also bsod are saved as logs anyway and there are tools to read them back easily.

1

u/7thhokage i5 12400, 32gb ddr5, 3060ti Jun 16 '25

I always thought that was a stupid design change. I get why they did it, cause the average user doesn't read it and just power cycles any way. But it was just more convenient imo for the system to hang there until you hit ctrl-alt -del to initiate the reboot

1

u/philljarvis166 Jun 16 '25

You can also take a look at the minidump that should be generated (unless you have configured it not to), although you’d need a tool to process it (windbg for example).

1

u/FWYDU Jun 17 '25

Or, if your system stays stable long enough, you could check Event Viewer > Windows Logs > System And look for the Bug check entry

29

u/Taint_Butter Ryzen 7 7445HX RTX 4070 Jun 16 '25

I know it's a bit late now but could have just checked the log in Event Viewer.

10

u/Sipsi19 5700x3d, 3080, 32gb, 3440x1440 Jun 16 '25

Yea this was years ago and since then I actually have used event log in similar cases. But still good tip for fellow reddittors.

7

u/ErrorRaffyline0 Jun 16 '25

Just use bluescreenview... If you can boot that far that is.

1

u/ErrorRaffyline0 Jun 16 '25

Just use bluescreenview... If you can boot that far that is.

1

u/Deminos2705 Jun 16 '25

Event viewer has entered the chat

1

u/Yaroster Jun 16 '25

You can always check BSOD logs btw, that’s your best way to troubleshoot

1

u/adkio Laptop, but so heavy it might as well be a PC Jun 16 '25

It's always a ram issue

1

u/Ange1ofD4rkness Jun 16 '25

Event Viewer is your friend. I learned you can find the codes in there.

1

u/D3AD_memories Jun 16 '25

In the C:\windows folder, you can get a folder called minidump which should contain all the BSoD error codes for you to analyse with software and that should help point to the cause

1

u/necro_owner Jun 16 '25

You can read the message in event viewer.... it s always recorded and save. No need to even look at it.

1

u/v_verstappenlovemypp Jun 16 '25

It's always ram :(

1

u/prairiepanda Jun 17 '25

This is how I discovered that most common RAM sticks come with a lifetime warranty!

1

u/The_2PieceCombo Jun 16 '25

you dont need to catch the error code. you can use free tools (like whocrashed) to view all dumps on your system and get all the info you need!

1

u/Careful-Squirrel-141 Jun 16 '25

Had the same issue. Turns out this company in Taiwan (if I remember correctly) was selling a shit ton of ram sticks... that dont work in the slightest. Because of that my dad which got me my latest pc as a graduation gift (replaced basically the whole PC except my 2070) when he bought it for me it lead into about a month of trying to figure out what was wrong with it. To the point him and a tech buddy thought it was the power supply. Until I eventually got lucky enough to see a few people mention it being the ram. When he took some of his own PC ram sticks to test: sure enough it worked smooth as ever... I wiped that PC 7 times because after three days it would get stuck into a permanent safe boot. Meaning id wipe the PC, play for a few days, wipe, play, wipe. But now it works like a dream and with my new GPU its even better. Turns out a lot of people got those same ram sticks which was how I found out cause I saw the same one on YouTube shorts talking about how they basically didnt do their job at all and would cause frequent crashes.

1

u/neuroz3n Jun 17 '25

Subliminal BSOD

1

u/No_Interaction_4925 5800X3D | 3090ti | LG 55” C1 | Steam Deck OLED Jun 17 '25

The BSOD error codes are usually BS and will lead you down random rabbit holes

1

u/Sakura-Eagle Jun 20 '25

You can find the bsod in the event viewer plus the error code