In the past I’ve used three methods:
1) Looking at the error displayed on the BSOD seeing if it’s obvious (e.g. specific driver mentioned)
2) (relatively complex) running the crash dump made during the BSOD through the debugger windbg with the MS ‘symbols’, but in the past it made it easier to diagnose certain errors the BSOD on it’s own couldn’t e.g. mentioning a driver.
3) Going through other troubleshooting options e.g. ram test/memtest, software/driver updates, checking/replacing cable connections, unplugging hardware, etc.
I’d link to a guide for windbg, but I haven’t found an ‘easy’ one since some mention an older method where you install the Windows SDK, which isn’t really necessary now as it’s on the Windows store.
Is the BSOD repeatedly happening or is it a ‘one off‘ fluke’?