detect.dll has Stopped Working

Post here if you encounter any problems or bugs with the software.
GoodNPlenty
Posts: 1
Joined: 2013.05.15. 20:34

detect.dll has Stopped Working

Post by GoodNPlenty »

When I first logon to Windows on my HP EliteBook 8560p Notebook I get a "detect.dll has stopped working" error dialog. I did a search and did not see this issue mentioned, I don't have this issue on my desktop system.

Code: Select all

Problem signature: 
  Problem Event Name:	BEX
  Application Name:	detect.dll
  Application Version:	0.0.0.0
  Application Timestamp:	2a425e19
  Fault Module Name:	StackHash_e98d
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	00000000
  Exception Offset:	00000000
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	e98d
  Additional Information 2:	e98dfca8bcf81bc1740adb135579ad53
  Additional Information 3:	6eab
  Additional Information 4:	6eabdd9e0dc94904be3b39a1c0583635
Image
User avatar
hdsentinel
Site Admin
Posts: 3019
Joined: 2008.07.27. 17:00
Location: Hungary
Contact:

Re: detect.dll has Stopped Working

Post by hdsentinel »

Thanks for your message, your attention and the information - and excuse me for the troubles.

The issue is related that some detection function(s) used in this external module does not work, probably because some Windows file(s) or features may not responding properly.
The detect.dll is not really critical in the operation of Hard Disk Sentinel - so the software can run without the detected information.

If you prefer, you may try to

- download and try the latest beta version (4.30.4) available from the Download page (or directly from http://www.hdsentinel.com/beta4/hdsenti ... up4304.zip ) as it has an improved detect.dll which "tolerates" better the problems of Windows

- simply delete detect.dll file - to prevent problems

In any ways, I'd recommend to use Report -> Send test report to developer option. This would help to check the situation with more details and verify what can be wrong with Windows on this system, what may cause that the detect.dll stopped (waits for response which never provided by Windows).
Post Reply