Windows 10: Windows 10 multiple BSODs

Had lots of trouble with this computer before and it ran fine after posting on sevenforums. Upgraded to Windows 10 about a month ago and been running great ever since. Now it has decided to start blue screening again.

:)

 

Windows 10 pro (Avgntflt.sys) - BSOD

I got lots of BSOD since avira install on my windows 10 pro (Avgntflt.sys) and always while shuting down.

Uninstall AVIRA: NO MORE BSOD !

Eddy

 

BSOD ntoskrnl.exe

've been having multiple BSOD since then, here are all the dump files and system info.

Meanwhile I managed to upgade to Win 10 Pro feature 1607 and still getting all kind of BSOD regarding the same ntoskrnl.exe

https://goo.gl/mtd5sX

 

Please fill out System Specs for tenforums:

See here: System Specs - Fill in at Ten Forums

Dumps show different Microsoft files causing the BSODs which typically means something e3lse is the real cause.

fileinfo.sys
ntkrnlmp.exe
FLTMGR.SYS

Overclocking:
If you are overclocking, set all the hardware components to their defaults.

Test your RAM modules for possible errors.
MemTest86+ - Test RAM
Run memtest86+ for at least 8 consecutive passes.

If it starts showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

Stress test the Graphics Card using Furmark.
FurMark - GPU Stress Test
Take a Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.
Prime95 - Stress Test Your CPU
It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Lastly, If over clocking is the cause of the problem, then post here: PC Custom Builds and Overclocking to get help with over clocking.

If not, try running with Driver Verifier to see if that shakes out a defective driver:

Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

 

Sorry, I was updating my previous post while you were filling out your System Specs.

Please re-read my previous post.

 

Driver verifier seemed to do the trick. I've attached the new package of data with the dump file made by the driver verifier.

 

The latest dump indicates scpvbus.sys has a problem.

Code: Product: Scp Virtual Bus Driver Company: Scarlet.Crush Productions Description: Scp Virtual Bus Driver Version: 1.0.0.103[/quote] Driver is old, Sun May 05 17:31:26 2013.

I think this has something to do with a Playstation. Needs to be removed or updated.