Blue screen(0x0000013a) after being disconnected from steam for steam maintenance.

[Abaddon-9]

Fair warning Im not knowledgeable with computers and my friend built this one for me. Ironically that friend just shipped out for boot camp TODAY(I even played with him day before yesterday) so he cant help me.

Was playing Destiny 2, had a video through firefox running in the background. Suddenly the video paused(I could rewind and it would play up to the same spot it froze at), I checked my connection and it was fine. Went back to destiny and it was still running but Ctrl+alt+del wasnt coming up and only did after I closed firefox. Destiny then kicked me back to title and said I needed to be signed into steam so I checked steam which said there was no connection. I hit retry and it closed and didnt come back up. Looked online to find they where doing maintenance but by that point my computer was starting to not respond. Tried clicking on taskbar to restart and that wasnt coming up(has happened before but reset always fixed it), finally the option came up and I hit reset.

It said there were apps still running and I clicked to end them and restart. From there it went briefly into its thinking wheel before giving me the blue screen and then shutting down to restart.. Did some looking around found it was error code 0x0000013a which has given me all sorts of unhelpful results. Watched a video on how to fix such error codes. Turns out theres no memory.dmp to run through WinDBG and minidump is empty. So all other sources are saying to do things that Ive already tried or to use apps that find nothing or are sketchy and rated in the 1.2 stars in reviews with all sorts of redflags. This all happened at the time steam went down for maintenance and disconnected me. My computer has acted buggy in the past. I have Comodo and Ccleaner though with games like Destiny 2 or Multiverses I was told to set Comodo to silent to reduce stress on the computer.
Some sites are saying its either using the wrong dump or that there is a corrupted dump.

EDIT: Forgot to mention after restarting I tried to launch destiny 2 and it had me verify/validate(cant recall which) all files in game. Closed and tried verifying files through steam and that took just as long but I figured that cleared that up, nope. It still insisted on verifying in game so I sat through that and Destiny 2 is running again.

Win10
Drivers up to date

Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz 3.79 GHz

8.00gb RAM

In device manager it has an exclamation mark over "Other Devices" with "Base system device", "PCI data acquisition and signal processing", "PCI memory controller" and "SM Bus controller" inside all having the exclamation mark. Says there is no drivers installed for them. Trying to update it says there is no driver in the computer for that.

Was this just a bug caused by steam and nothing to worry about or should I take it a repair place as I have no clue how to fix it or what to fix. Is it a simple bug or a hardware fix?

Should I avoid using my computer till I can take it in for repairs?

Im also seeing a few other people had similar problems after maintenance but no mention of a bluescreen though.

[ReBoot]

Upload the crash dump for someone to analyze.

[Abaddon-9]

Автор сообщения: ReBoot

Upload the crash dump for someone to analyze.

I searched " C:\WINDOWS\MEMORY.DMP " in "My PC" and in "Local drive C:" and both brought up nothing.

I go to Minidump and its empty.

I scroll down looking for anything saying "Memory" and no folders or files show up.

From event viewer looking at its general info it reads:
"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000013a (0x0000000000000011, 0xffff95018d402100, 0xffff9501a21dc710, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 934624f4-e54c-4b12-99fd-dc9b1aaf4cf9."

[ReBoot]

Don't search! Open this folder and get the file from there.

[Abaddon-9]

Автор сообщения: ReBoot

Don't search! Open this folder and get the file from there.

you mean the memory dump folder in Drive C? Because that doesnt exist apparently...

Of the "M" folders I have Microsoft dot net, Media, Migration, Minidump(empty) and Modem logs. Thats all that shows up in local disk C windows folder.

[ReBoot]

You said, a dump was saved in C:\WINDOWS\MEMORY.DMP. That makes a file named memory.dmp in the Windows folder. A FILE memory.dmp, NOT a FOLDER.

[Abaddon-9]

Автор сообщения: ReBoot

You said, a dump was saved in C:\WINDOWS\MEMORY.DMP. That makes a file named memory.dmp in the Windows folder. A FILE memory.dmp, NOT a FOLDER.

and how do I find and open that?

Tried opening it with WinDBG and it says the file does not exist. I also checked for any files with that name and nothing. I tried putting it into Run/ and again "file does not exist".

There is no file or folder with that name in the windows folder.

[ReBoot]

How to find: you open Explorer and go there.
How to open: I suggested you to upload it, not to open it. You're of course free to open it with WinDbg yourself, but given your trouble to navigate the file system, I doubt you'll find WinDbg self-explanatory. So do yourself a davor and upload it.

[Abaddon-9]

Автор сообщения: ReBoot

How to find: you open Explorer and go there.
How to open: I suggested you to upload it, not to open it. You're of course free to open it with WinDbg yourself, but given your trouble to navigate the file system, I doubt you'll find WinDbg self-explanatory. So do yourself a davor and upload it.

I would if I could dude, I really would if I could. All the explorer brings up is relevant Web searches. I dont know where you would want me to upload it but at the moment I cant even find it. It shows up in event viewer and that seems to be it.

Ive tried copy and pasting it exactly in WinDBG, in the task bar explorer, in Run and keep getting "file does not exist".
Im not trying to be difficult, Im sharing all that I know and can find.

[ReBoot]

DO NOT SEARCH! Just browse. Open the folder. DO NOT SEARCH! As for where to upload, OneDrive, Dropbox, something like that.

You can browse folders without searching.

[Abaddon-9]

Автор сообщения: ReBoot

DO NOT SEARCH! Just browse. Open the folder. DO NOT SEARCH! As for where to upload, OneDrive, Dropbox, something like that.

right, as in scrolling through the windows folder in drive C. I did that and its not there.
Theres NVcontainer recovery. Ill take a screenshot and try to upload that.

[Abaddon-9]

Автор сообщения: ReBoot

DO NOT SEARCH! Just browse. Open the folder. DO NOT SEARCH! As for where to upload, OneDrive, Dropbox, something like that.

You can browse folders without searching.

https://www.dropbox.com/s/vf7hfpbz2w5xpw5/Untitled.jpg?dl=0

https://www.dropbox.com/s/kfwiz6yhf0x23if/Untitled2.jpg?dl=0

https://www.dropbox.com/s/4t649fiii022km8/Untitled3.jpg?dl=0

Thats what Im seeing.

Also this:
https://www.dropbox.com/s/xv1ghv8bnl54dwu/Untitled4.jpg?dl=0

[Crazy Tiger]

The memory.dmp doesn't always get saved. Minidumps usually do get saved, the Minidump folder really is empty?

The error code can be related to hardware and driver issues. More often than not it's a bad driver, but it could mean some troubleshooting to rule out things can be required. But for that it's indeed good to have a minidump at least to check what caused it.

[Abaddon-9]

Автор сообщения: Crazy Tiger

The memory.dmp doesn't always get saved. Minidumps usually do get saved, the Minidump folder really is empty?

The error code can be related to hardware and driver issues. More often than not it's a bad driver, but it could mean some troubleshooting to rule out things can be required. But for that it's indeed good to have a minidump at least to check what caused it.

Minidump is empty
https://www.dropbox.com/s/7f7m01tf91347pw/Untitled5.jpg?dl=0

[Abaddon-9]

Automatic memory dump was already on.

https://www.dropbox.com/s/y677m8b6dvfyiyj/fsf.jpg?dl=0

[Abaddon-9]

Автор сообщения: Crazy Tiger

The memory.dmp doesn't always get saved. Minidumps usually do get saved, the Minidump folder really is empty?

The error code can be related to hardware and driver issues. More often than not it's a bad driver, but it could mean some troubleshooting to rule out things can be required. But for that it's indeed good to have a minidump at least to check what caused it.

Theres also this though I dont know if its relevant:
https://www.dropbox.com/s/1ouwj5wy9vkt2wf/sgfsdfsf.jpg?dl=0