Windows 10 BSOD 'Kernel Panic'

Tends to BSOD on log out or when away from computer for a while. The time's I've seen it it said 'Kernel Panic'. This last time happened while I wasn't at the computer, so I ran the tool and I'm attaching it here.DAYTON-PC-Sat_03_12_2016_102356_86.zip

Hello TKFM and welcome to 10blog!

Please perform these steps:

1. Click the Startbutton.
2. Type "command" in the search box... DO NOThit ENTERyet!
3. While holding CTRL-Shifton your keyboard, hit ENTER.
4. You will be prompted with a permission dialog box.
5. Click Yes.
6. A black box will open with a blinking cursor.
7. Type "sfc /scannow" and hit ENTER.
8. System File Checker will begin scanning for Error 0x139 and other system file problems (be patient - the system scan may take a while).
9. Follow the on-screen commands.

1. Click the Startbutton.
2. Type "command" in the search box... DO NOThit ENTERyet!
3. While holding CTRL-Shifton your keyboard, hit ENTER.
4. You will be prompted with a permission dialog box.
5. Click Yes.
6. A black box will open with a blinking cursor.
7. Type "chkdsk /f /r" and hit ENTER.
8. "chkdsk" will begin scanning for hard disk corruption that could be causing 0x139 STOP errors.
9. Follow the on-screen commands.

MemTest86+ - Test RAM

Cheers, Boris

Well, both sfc and chkdsk look liked they fixed some things (based on the logs). Running memtest overnight only yeilded like 3 passes, but those all passed. I'll keep running it at night to see if anything comes up. Thanks for your help.

Yeah but remember to run it for at least 8 passes, to be really sure there aren't any errors!

Well, I do have some memory errors and the BSOD is persisting. I'm trying to catch the error again so that I can see it it is the DIMs or the slots that are bad, as described in the link.

Well I'm retracting my statement about the memory error, I must have caused it while I was messing with the settings of the program.

I ran the memtest w/o stopping for 12 complete passes (in almost 60 hours) and it never threw an error. At the very least, this isn't a debuggable solution b/c if it was a legit memory error earlier, I have no idea if it was the slot or the dim and all I would be able to do is replace practically everything. Therefore, I would say that it's unlikely that memory errors are the source of my frequent BSOD experience.

Would the logs from sfc and chkdsk be any help to further pursuing the source of my BSOD? I could upload those.

I've not heard the phrase Kernel Panic since I was using Unix (*many* years ago!).
Could you be running something Unix/Linux related?

There would be a BIOS update, but I'm not sure if it would fix the issue.

Would the logs from sfc and chkdsk be any help to further pursuing the source of my BSOD? I could upload those.

Depends on if SFC cannot fix something and if chkdsk has done something

Included are "updated" BSOD logs and the results from the tests. Both sfc and chkdsk found stuff to do.

• DAYTON-PC-Tue_03_15_2016__94657_32.zip (1.06 MB, 4 views)
• Response.zip (430.2 KB, 4 views)