PDA

View Full Version : fun w/ win 8



Theoras
2014-07-07, 08:09
Windows 8 monitor reports the following:
Spybot - Search & Destroy has stopped working properly.

Support for this product is community-based, providing solutions to common problems through an online user forum. Typically, this type of support lets you search the postings of other users for solutions, or ask the group a question if a solution to your problem is not immediately available.

No additional information is available.
Not sure how to fix a problem with out knowing exactly what is wrong

Zenobia
2014-07-08, 04:16
Which version of Spybot do you have? :)
Anything related to Spybot listed in Event Viewer?To open Event Viewer,click Winkey +w,then type in ev,and you should see View Event Logs.

Theoras
2014-07-08, 08:28
I have spybot 1.6.2

I was able to find the following errors in the event log:

Error 7/3/2014 12:39:37 PM SideBySide 63 None
Activation context generation failed for "c:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Error 6/30/2014 12:53:09 AM SideBySide 63 None
Activation context generation failed for "c:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Error 6/28/2014 1:31:20 PM Application Hang 1002 (101)
The program SpybotSD.exe version 1.6.2.46 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: d30

Error 6/25/2014 9:25:02 PM Application Error 1000 (100)
Faulting application name: TeaTimer.exe, version: 1.6.4.26, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ac2f
Exception code: 0xc000041d
Fault offset: 0x00014b32
Faulting process id: 0x13b4
Faulting application start time: 0x01cf90d50b1948f4
Faulting application path: C:\Program Files (x86)\Spybot - Search & Destroy\TeaTimer.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: d6dc5363-fce9-11e3-be7d-74d02bad9c8d
Faulting package full name:
Faulting package-relative application ID:

Error 6/25/2014 9:24:34 PM Application Error 1000 (100)
Faulting application name: TeaTimer.exe, version: 1.6.4.26, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ac2f
Exception code: 0x0eedfade
Fault offset: 0x00014b32
Faulting process id: 0x13b4
Faulting application start time: 0x01cf90d50b1948f4
Faulting application path: C:\Program Files (x86)\Spybot - Search & Destroy\TeaTimer.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: c5f6ec1e-fce9-11e3-be7d-74d02bad9c8d
Faulting package full name:
Faulting package-relative application ID:

Zenobia
2014-07-08, 19:40
Ok,thanks. :)
Those are from June,and one from July,so probably not (totally) related to the not working message.

I'm on Windows 7,so I'm not totally familiar with Windows 8.

Windows 8 monitor reports the following:
Spybot - Search & Destroy has stopped working properly.
Is that message coming from Action Center,or Reliability Monitor?

Theoras
2014-07-09, 00:54
The action center.

Zenobia
2014-07-09, 05:45
If you wouldn't mind,could you give me a screenshot of your action center,it'll be easier to look around then:
https://answers.syr.edu/display/os/Taking+Screenshots+on+Windows+8+-+Using+the+Snipping+Tool+and+keyboard+shortcuts
Most of the action center page,if at all possible.Sort of like this:
http://www.eightforums.com/attachments/tutorials/2034d1316685801-automatic-maintenance-change-maintenance-settings-windows-8-settings.jpg
Probably can't attach it here,the file would be too large.You could post an image of it on imgur,and give me the link here. :)
http://imgur.com/

Theoras
2014-07-09, 15:42
Interestingly, I restarted the system and it appears to be working, but still has this flagged from the 27th.

11679

Zenobia
2014-07-09, 22:43
That's way too small to read.I tried making it larger,and it looked like it was written in Sanskrit. :D:
http://awesomelyluvvie.com/wp-content/uploads/2010/11/magnify-far.gif

Try clicking View Reliability history,then at the bottom,click View All Problem Reports.There may be a section listed there for Spybot and/or Teatimer.
If everything listed there is mostly all the same,it might just simply say Spybot Search & Destroy,then under Summary have listed,Stopped Working,then doubleclick that text.It should open to a page with more info,highlight the info written in the box with your mouse,then rightclick,select Copy,then Paste it here.
Here's an example from mine:

Description
Faulting Application Path: C:\Program Files (x86)\Spybot - Search & Destroy 2\SDTray.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: SDTray.exe
Application Version: 2.3.39.129
Application Timestamp: 535a51a2
Fault Module Name: rtl150.bpl
Fault Module Version: 15.0.3953.35171
Fault Module Timestamp: 4cca139f
Exception Code: c0000005
Exception Offset: 0000a116
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional Information 1: 547d
Additional Information 2: 547d549622873cd400a72a94353baf17
Additional Information 3: e52d
Additional Information 4: e52d8c8e68547a0b7f60dd8fec4767b2

Extra information about the problem
Bucket ID: 219400798

Whatever is in there is probably related to this message in your event viewer,but I want to see if there is any more info listed in the Problem Reports:

Error 6/28/2014 1:31:20 PM Application Hang 1002 (101)
The program SpybotSD.exe version 1.6.2.46 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: d30

Theoras
2014-07-10, 23:17
Looks like my recent restart has resolved what ever the issue is. The error is not appearing in the action center, so I don't quite know what happened. If it happens again, I'll grab as much info as I can and go from there.

Zenobia
2014-07-11, 03:06
Ok. :)
..........