Windows 10: BSOD: While running Firefox and file sharing in the background

Hello,

I was running Firefox and browsing the web, whilst also having a few programs running in the background, when all of a sudden my system flashed a BSOD (System_Thread_Exception_Not_Handled) and I had to restart. I have only ever gotten a BSOD after upgrading to Windows 10 and never experienced such issues in Windows 7, so I suspect a bad driver may be the cause. However, I was downloading files with my file sharing program (qbittorrent) and I think that could have also played a part as well.

I have had BSOD's in the past (Memory managemnt) and usually just ignore them, but I would like to finally solve this issue before it gets in the way of important work. When I examined the BSOD with BlueScreenView by Nirsofit, it said ntoskrnl.exe and FLTMGR.SYS were the prime culprits.

Any and all help will be very appreciated; Thanks!

Attachment 120961

:)

 

BSOD UNEXPECTED_STORE_EXCEPTION

Ok, this Bsod occurred while i'm chatting in Discord with Firefox and a VM working in the background and sometime the programs freezzed and from nowhere my pc bsod

 

Win10 BSOD Kernel_Security_error atikmdag.sys Video timing error ? Driver issue?

Got another BSOD so I updated the file and am posting another link with the additional error. This BSOD said the problem was:

irql_not_less_or_equal

And it occurred when trying to watch Netflix on Firefox.

Link:

Gamble6x-BSOD-Filesv2.zip

 

There seem to be problems doing the analysis because of bad symbols in the operating system files.

I suggest you run a system file check and see if any of them need repairing.

 

I got a response: "Windows Resource Protection did not find any integrity violations." I have zipped up my CBS.log file according to the command in the link you've provided.

Attachment 121053

 

In that case Microsoft may not have loaded the symbols yet for your version of windows. Did you update recently on the Insider program? You may have to wait a few days before I can do a proper analysis.

 

I'm not using a insider version of Windows. I'm using an updated Windows 10 anniversary edition (Version 1607, 14393.726) Also, what do you mean by "bad symbols"?

 

Yes, you are on a more recent version than I have. It was only released via the Catalogue. It will probably be available via windows update after tomorrow (Patch Tuesday).

The symbols are provided by Microsoft to allow debugging of the crashes. In your case, it is just that MS have not yet loaded the symbols for this latest version of Windows so that I am unable to debug your crash files properly. I should have said missing symbols not bad symbols.