This crash interrupted by outputting the usual windows 7 error dialog, asking to send to microsoft.com or close the program ...
I closed the program/dialog because I'm sure that irfanview doesn't collaborate with microsoft ....
This copy/paste MIGHT be useful?
Problem signature:
Problem Event Name: BEX
Application Name: i_view32.exe
Application Version: 4.51.0.0
Application Timestamp: 5a952946
Fault Module Name: FaceDetect.dll
Fault Module Version: 1.0.0.0
Fault Module Timestamp: 514c0eea
Exception Offset: 0000c583
Exception Code: c0000409
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 1739
Additional Information 2: 1739ca20768186bd625a80cc43775c29
Additional Information 3: 63c8
Additional Information 4: 63c80c71995d98095ab53d17a704315b
Ok, before I start to report a detailed analysis on what might have caused this ... I'm going to give a "heads-up" to the possibility that my file(s) naming convention COULD very well have caused the program and\or the DLL software to incorrectly parse the file(s) that I supplied too it.
An example of the file name(s) which it was attempting to process was (the actual filename[s]that crashed with):
Carol Goldnerova@indexxx.com.jpg
Carol@sapphicerotica.com.jpg
I know that file naming like this in Linux won't cause it to choke on it, while most Windows have had a inherent file naming limitation, since the days of MSDOS, despite the fact that 32/64bit Win processing was supposed to fix that limitation.
So for the sake of first argument did this cause the crash?
I closed the program/dialog because I'm sure that irfanview doesn't collaborate with microsoft ....
This copy/paste MIGHT be useful?
Problem signature:
Problem Event Name: BEX
Application Name: i_view32.exe
Application Version: 4.51.0.0
Application Timestamp: 5a952946
Fault Module Name: FaceDetect.dll
Fault Module Version: 1.0.0.0
Fault Module Timestamp: 514c0eea
Exception Offset: 0000c583
Exception Code: c0000409
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 1739
Additional Information 2: 1739ca20768186bd625a80cc43775c29
Additional Information 3: 63c8
Additional Information 4: 63c80c71995d98095ab53d17a704315b
Ok, before I start to report a detailed analysis on what might have caused this ... I'm going to give a "heads-up" to the possibility that my file(s) naming convention COULD very well have caused the program and\or the DLL software to incorrectly parse the file(s) that I supplied too it.
An example of the file name(s) which it was attempting to process was (the actual filename[s]that crashed with):
Carol Goldnerova@indexxx.com.jpg
Carol@sapphicerotica.com.jpg
I know that file naming like this in Linux won't cause it to choke on it, while most Windows have had a inherent file naming limitation, since the days of MSDOS, despite the fact that 32/64bit Win processing was supposed to fix that limitation.
So for the sake of first argument did this cause the crash?
Comment