search

spiele / snappy-driver-installer

Automatically exported from code.google.com/p/snappy-driver-installer
0 stars 0 forks source link

SDI_R168 updating error #30

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I have a problem when downloading, updating driverpacks, I have each time the 
message: Snappy driver installer has stopped working!
I am with SDI_R168 on my Win8.1 x64 and without driverpacks (unpack 
SDI_R168.zip). Here is the log
Thanks

Original issue reported on code.google.com by Mateo.RO...@gmail.com on 17 Mar 2015 at 11:14

Attachments:

GoogleCodeExporter commented 9 years ago 
Here's a debug build. It should produce a file named backtrace.txt upon 
crashing. Attach it here.

Original comment by BadPointer0 on 17 Mar 2015 at 11:24

Attachments:

GoogleCodeExporter commented 9 years ago 

Same error with SDI_R169D but I can not find backtrace.txt in SDI_R169D 
(sub)folder, also searched in C:
I just tested also on a win7 x64 laptop with same issue, it start downloading 
in update folder then crash!

Original comment by Mateo.RO...@gmail.com on 17 Mar 2015 at 11:48

GoogleCodeExporter commented 9 years ago 
Make sure that backtrace.dll is in the same folder as the app.

backtrace.txt should be created in the same folder.

Original comment by BadPointer0 on 17 Mar 2015 at 11:56

GoogleCodeExporter commented 9 years ago 
Thanks for your quick replies
Yes backtrace.dll is in SDI_R169D root folder, next to SDI_R169D.exe 
(SDI_R169D.zip  unpack with 7-zip) but no backtrace.txt around after crash!

Original comment by Mateo.RO...@gmail.com on 17 Mar 2015 at 12:04

GoogleCodeExporter commented 9 years ago 
Let's test the torrent client.

1. Run runme.bat
2. Check if it's working fine.
3. Press Q to quit.

Original comment by BadPointer0 on 17 Mar 2015 at 12:12

Attachments:

GoogleCodeExporter commented 9 years ago 
I don't know if it can help.
Here is what I have if I click debug.

'SDI_R169D.exe': Loaded 'E:\_WinPE\Outils\Snappy Driver Installer 
SDI\SDI_R169D\SDI_R169D\SDI_R169D.exe', Binary was not built with debug 
information.
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\ntdll.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\kernel32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\KernelBase.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\advapi32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\msvcrt.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\sechost.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\sspicli.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\cryptbase.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\comdlg32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\shlwapi.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\gdi32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\user32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\lpk.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\usp10.dll'
'SDI_R169D.exe': Loaded 
'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7
601.18201_none_ec80f00e8593ece5\comctl32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\shell32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\msimg32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\newdev.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\uxtheme.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\setupapi.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\oleaut32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\ole32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\devobj.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\devrtl.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\ws2_32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\nsi.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\wsock32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\mswsock.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\imm32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\msctf.dll'
'SDI_R169D.exe': Loaded 'E:\_WinPE\Outils\Snappy Driver Installer 
SDI\SDI_R169D\SDI_R169D\backtrace.dll', Binary was not built with debug 
information.
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\imagehlp.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\dwmapi.dll'
'SDI_R169D.exe': Loaded 
'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.76
01.17514_none_41e6975e2bd6f2b2\comctl32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\clbcatq.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\cryptsp.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\rsaenh.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\RpcRtRemote.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\wship6.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\WSHTCPIP.DLL'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\IPHLPAPI.DLL'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\winnsi.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\dhcpcsvc6.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\dhcpcsvc.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\dnsapi.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\rasadhlp.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\FWPUCLNT.DLL'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\wintrust.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\crypt32.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\msasn1.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\ExplorerFrame.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\duser.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\dui70.dll'
'SDI_R169D.exe': Loaded 'C:\Windows\SysWOW64\actxprxy.dll'
The thread 'Win32 Thread' (0x1e6c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1de4) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x18f4) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x149c) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1cc8) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x11f8) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1e00) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1a34) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xb54) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1fe4) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1f34) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1a8c) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1e7c) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0xcbc) has exited with code 3 (0x3).
The thread 'Win32 Thread' (0x1ec4) has exited with code 3 (0x3).
The program '[7924] SDI_R169D.exe: Native' has exited with code 3 (0x3).

Original comment by Mateo.RO...@gmail.com on 17 Mar 2015 at 12:30

GoogleCodeExporter commented 9 years ago 
backtrace.dll is loaded succefully but it crashes inside a 3rd library called 
libtorrent. 

This is why asked you to test the simple torrent client(it's using libtorrent). 
If it's a libtorrent issue, we should forward this bugreport to the developer 
of libtorrent.

Original comment by BadPointer0 on 17 Mar 2015 at 12:44

GoogleCodeExporter commented 9 years ago 
I tested client_test.zip. same here when running runme.bat, it start 
downloading then crash.
Maybe useful, here is the copy of the cmdline: SDI_R168.exe /autoupdate

Original comment by Mateo.RO...@gmail.com on 17 Mar 2015 at 12:53

Attachments:

GoogleCodeExporter commented 9 years ago 
SDI_Debug.txt doesn't yeild any useful information.

It's definitly a libtorrent issue. I suggest filling a bugreport at 
http://www.libtorrent.org/. Arvid Norberg knows better how to troubleshoot his 
library. You can say that client_test.exe crashes on you and post a link to 
this bugreport.

My setup:
libtorrent 1.0.3
BOOST 1.57.0
GCC 4.8.1 (MinGW)
<link>static <runtime-link>static <threading>multi <boost>source 
<boost-link>static <optimization>space <deprecated-functions>off <rtti>off 
<geoip>off <asserts>production <debug-symbols>off <iconv>off <i2p>off <ipv6>off

Original comment by BadPointer0 on 17 Mar 2015 at 1:09

GoogleCodeExporter commented 9 years ago 
When you say: we should forward this bugreport to the developer of libtorrent.
Do I have to do something ? I do not know anything avout libtorrent.
Do you have enough information, test, to open a bugreport.
For now, I will use your torrent link to download driverpacks and continue my 
first tests with Snappy that seems really great.
Thanks BadPointer0

Original comment by Mateo.RO...@gmail.com on 17 Mar 2015 at 1:19

GoogleCodeExporter commented 9 years ago 
post crossing, I'll try to open a bugreport.
but execpt your client_test, I don't know more on libtorrent to compil, test.

Original comment by Mateo.RO...@gmail.com on 17 Mar 2015 at 1:22

GoogleCodeExporter commented 9 years ago 
If you want it fixed, you should do it because you're the one who's having the 
problem, so your assistance is required.

You don't have to compile it. He can compile a debug build for you.

Original comment by BadPointer0 on 17 Mar 2015 at 1:26

GoogleCodeExporter commented 9 years ago 
OK, I understand, Done here : 
http://code.google.com/p/libtorrent/issues/detail?id=725

Original comment by Mateo.RO...@gmail.com on 17 Mar 2015 at 1:37

GoogleCodeExporter commented 9 years ago 
Sorry BadPointer0, I tried again this morning after rebooting and no worries 
now, everything works fine.
However, I have not invented yesterday and I had the same problem on 2 
computers, my Win7 x64 and a very new laptop with Win8.1 x64.
As it works this morning, I tried on a 3rd PC, also successfully.
It remained a mystery to me (same PCs, same config, no network concern) !!!, 
but well, it works now.
Sorry again, keep us your good work and thanks a lot for your great SDI :)

Original comment by Mateo.RO...@gmail.com on 18 Mar 2015 at 8:44