A couple more occurred today (see attached). Also the computer restarted once without blue screen and had a long continuous beep on post. It did this once on a bluescreen restart as well. According to Gigabyte for AWARD BIOS this means a bad memory install. All sticks are being detected, so I'm going to clean the connectors, dust the slots, and reseat the memory.
Hmm, You do have graphics driver references again.
However we'll try removing Avast first because that appears that be causing problems.
Can you replace it with Microsoft Security Essentials and Malwarebytes.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8e002f649bc, 1, fffff80002fba2f2, 5} Unable to load image aswMonFlt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswMonFlt.sys *** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys Could not read faulting driver name Probably caused by : aswMonFlt.sys ( aswMonFlt+2475 )
Microsoft Security Essentials | Protect against viruses, spyware, and other malware
https://www.malwarebytes.org/
When you install malwarebytes make sure you uncheck the tick box that says "Free trial of Malwarebytes pro".
That also didn't help. Latest attached. I also tried cleaning the memory and slots better. I swapped the memory slots as well. The last three crashes are new, but only the latest two are post-removing avast! and installing Microsoft security Essentials.
You appear to have a graphics display crash. Please run a stress test on your graphics card using furmark by following these instructions.
Video Card - Stress Test with Furmark
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff880045d6e26, fffff88003c426a8, fffff88003c41f00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
It made it through two half hour tests without problem. It leveled off at around 85 degrees and 81 degrees during the two tests. Oddly enough the first test was run with MSI Afterburner on and underclocking the factory overclocked card to 820 MHz (level recommended by some users experiencing problems with this card). The second was with the default settings.
Windows action center reported that I may have RAM problems and recommended a memory test. Despite running one previously (both Memtest 86+ and the Windows RAM utility) I obliged.It reported no errors. Now it is reporting that I need to troubleshoot a problem with a device or driver, but opening that issue does not download a solution (my internet connection is working).
I have noticed drivers on rare occasions cause memory issues, I would recommend running Driver Verifier for at least 24 hours. Follow these instructions.
Driver Verifier - Enable and Disable
Several crashes this evening, four blue screens. After starting driver verifier I played Diablo III for a bit (just let it sit on character select), then Guild Wars 2 for a bit (just let it sit in the game). That crashed the system once after a little bit, then it didn't post BIOS and gave one continuous beep (Gigabyte Award BIOS says this means memory not correctly installed) before restarting and posting the BIOS. Tried Guild Wars 2 again, didn't even load before crashing, same loud continuous beep. It restarted and posted then got stuck on "Loading OS...", so I manually restarted. It went to a black screen and auto-restarted. Finally, it made it to windows. At Windows I ran Furmark, it passed. Ran Guild Wars 2, crashed. Loaded to the desktop, ran Furmark. Didn't crash. Ran Diablo III and played it for a bit, didn't crash. Ran Guild Wars 2, played it for a bit, didn't crash. Turned off driver verifier, as I thought your instructions were conditional on getting crashes. After doing so started running the BSOD information gathering script and composing this message. The computer blue screened and restarted while doing so. Got to the desktop reread your instructions and realized you weren't conditional about the driver verifier running for 24 hours, turned it on again. Ran the BSOD gathering script and wrote this message. See attached.
I don't want to give the impression this just happens during Guild Wars 2. Tonight happened to be a special night for GW 2, but I've had repeat restarts playing Diablo III before. It's also restarted from the desktop or Google Chrome a handful of times as well. Before you told me to run Furmark I had ran Furmark a few weeks ago and one of my attempts caused a restart, but others didn't
It looks like a faulty graphics card. However there is one bugcheck that caught my eye, this is the bad pool caller which identified the root cause as MPfilter.sys. I would run your Anti Virus to scan for viruses, then download and run malwarebytes.
malwarebytes.org
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 109b, 0, fffffa8009aced10} Unable to load image MpFilter.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for MpFilter.sys *** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys GetPointerFromAddress: unable to read from fffff80003106100 Probably caused by : MpFilter.sys ( MpFilter+145a7 )
Virus scan and malware bytes reported no problems. I filled out an RMA for the card. Will let you know if I get a new one and if the problem is fixed. If I get a new card should I wipe the drivers and go with the most current ones?
Yes you should wipe the old drivers off and install the latest certified/recommended for your card.
Quote