Forum Home
Press F1
 
Thread ID: 131262 2013-04-30 03:45:00 Win 8 Defender Problem. linw (53) Press F1
Post ID Timestamp Content User
1339050 2013-04-30 03:45:00 For a week, now, my Defender has been scanning at startup and often at other times (as we speak, it is hammering the disk for the second time in 30 min). CPU for Antimalware is 30ish%. The disk noise is driving me nuts.

The system error log shows Defender stopping unexpectedly with error 7031. This error is posted when the disk hammering stops.

Windows update history shows Defn updates failing from 21 Apr to 28 Apr incl but updates were successful 29 and 30 Apr. Wonder what got these going again?

The Defender window shows the last scan was at the scheduled time of 4:22 am. So it is not seeing these rogue scans - probably because they don't terminate properly.

Google hasn't been helpful for this one but will keep looking. Wonder if I have a database corruption of some sort?

Anyone else seen this? Any ideas?

BTW, no other A/V progs installed
linw (53)
1339051 2013-04-30 04:08:00 It looks like you can get error 7031, if you installed another AV program, then uninstalled it. But, one of its services are still in services. But like you said no other AV programs were installed Speedy Gonzales (78)
1339052 2013-04-30 04:23:00 If the updates have failed earlier on they may be causing a problem, even though it says the latest are Ok try downloading them manually and installing.

Download Links: www.microsoft.com
wainuitech (129)
1339053 2013-05-03 22:06:00 The problem seems to have gone away - hopefully! I messed with stopping startups and seemed to have got a setup that worked then I added back the startups and it still works. I also ran sfc /scannow and it found some problems that it fixed but that didn't fix the Defender problem.

I have had no Defender crashes, or repeated scanning, for a couple of days, now, so can only assume later updates or database changes, or a wind change have fixed it.

Here's hoping!

Thanks for input, guys.
linw (53)
1339054 2013-05-04 21:13:00 Spoke too soon - problem is back. Back to more time consuming troubleshooting. linw (53)
1