Windows 10: Random BSOD's every 45 min or so, usually while playing games

If you don't have a hardware problem, then I suspect there is some program or driver that is not compatible with Windows 10 or in conflict with some other program. That is what I suspect. Maybe it was AVG, but only time will tell that. If you get another BSOD, upload the DM Log and I'll look at it until @axe0 gets free from the other stuff he has going on. He is incredibly busy right now and I couldn't do what he is doing. I am just trying to help him out a little until things slow down for him. The only thing I know to do at this point is when the dump files identify a program, uninstall it until we find which one is causing the problem. I do know that many of the AV programs have had problems with Windows 10 until they re-write the programs. Most, but not all, have done that. So, let's see what happens.

 

Alright, I'll keep everyone posted, in the meantime do you know of another good AV program I could use? I installed AVG because I heard good things from reviewers but since thats not an option...

 

Windows 10 has built in Windows Defender, which is much improved over previous versions. I say that just to say you are not unprotected. But, let's just wait a while and see if AVG was your problem. Once we get this sorted out, you can try and reinstall AVG and give it another try. Once it is stable, if you reinstall AVG and begin having BSODs again, you will know what it is and what to do. I would suggest just running with Windows Defender right now. We know that it does not cause problems.

 

Heya all, so another BSOD happened, memory_management. Thing is when I rebooted, my start button and search bar weren't working, I'd click on them and nothing would happen. After some online searching I ran sfc /scannow. I got this result:

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

The DM Log is also attatched, any idea where to go from here?

 

Try using the AVG uninstall utility to make sure all of it is removed AVG | Download tools and utilities.

Then enable Driver Verifier. There is always the chance you may have to reinstall, but every effort is made to avoid that. Make sure you create a restore point before starting. You can also create a system image to an external source too.

*YouTube video player [/i]

 

Well got one crash so far with driver verifier running, start button and search still not working. Here's the log.

 

I'm still looking at it, but it is not very forthcoming. It just seems to me that throughout this entire thread we have always zeroed in on Hard Drive, Memory and Graphics cards. Even if you have already please run these again. Run full scans with each.

Scan with Kaspersky TDSSKiller:
http://support.kaspersky.com/viruses...on/5350#block1
Anti-rootkit utility TDSSKiller
ESET online scanner:
Free Virus Scan | Online Virus Scan from ESET
Free Online Virus Scanner | ESET
Superantispyware
SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
Malwarebytes
Free Anti-Malware & Malware Removal
When installing, uncheck the start trial real time scanning and just use it as an on demand scanner

 

Code: MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041793, The subtype of the bugcheck. Arg2: fffff680ec51c400 Arg3: 0000000000000005 Arg4: 0000000000000004 Debugging Details:[/quote]

 

Yea, I dropped AVG for not respecting my exceptions, went to Avast!, got a BSOD with it in Windows 7, got rid of it. Been using MSE/Windows Defender since then, supplemented with Malwarebytes.

 

Alright, well I'm fairly sure the computer crashed 2 times, maybe more, while it was running over the 24 hours with driver verifier. Should I turn off driver verifier now? The DM log for the crashes is attached, I'm running the antivirus scans now.

 

Alright well, Eset scanner won't complete without crashing, even after disabling driver verifier, this happened before too when you asked me to run these tests initially. Malwarebytes and Kapersky returned no threats, superantispyware however returned some adware tracking cookies as usual, not sure if those are the cause because every time I run superantispyware its just adware tracking cookies it detects. The DM log for the crashes is attached.

 

OK, still not having a lot of luck. To answer your question, turn Driver Verifier off, as I think you did. Here are what the dump files say.

Code: Use !analyze -v to get detailed debugging information. BugCheck A, {8008080, 2, 1, fffff802ab96c959} Probably caused by : memory_corruption ( nt!MiClearFilePointer+3d ) Followup: MachineOwner[/quote] The rest were

Code: KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: ffffd000208a5800, Address of the trap frame for the exception that caused the bugcheck Arg3: ffffd000208a5758, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details:[/quote] try this. Go to your motherboard's web site (http://www.asrock.com/mb/Intel/Z97%2...oad&os=Win1064) and download your Windows 10 drivers to a USB drive and keep them. Install your Lan driver.

If you still crash, uninstall all of your Nvidia graphics drivers making sure to uninstall the graphics driver last. It will tell you to restart. Don't restart, shut down instead. Unplug the PSU, hold the start button down for about 30 seconds. Completely remove the graphics card from the computer. Attach the monitor to the on board graphics. Be sure to use the same type cable or change the input method on your monitor so it will know which type signal to look for. Plug the PSU back in and start up the computer. It should load a graphics driver for the on board graphics. Run it that way for a while and see how it does. That should tell us once and for all whether the graphics card is your problem.

In the meantime upload the DM Log if you get a BSOD. I know this is frustrating to you. But, trust me, it is frustrating to me too. But, the dump files are not making things easy. There are only indications in the dump files other than the memory corruption. Some are pointing to problems with the Network driver, memory, Graphics and hard drive. When you get problems like that, it usually points to bad memory. But, let's try to eliminate the Network and Graphics problems first if we can. As it seems to me right now, we can't run many of the tests because it keeps crashing while running them.