Steam fails to respond

Ask your support questions in here

Moderator: Moderator Team

Post Reply
User avatar
Fraizeraust
Posts: 234
Joined: Thu Jan 05, 2017 11:46 am
Location: Italy
Contact:

Steam fails to respond

Post by Fraizeraust »

As the title implies, after the successful installation of Steam from Applications manager, Steam simply outputs no screen at all and the Task Manager reports the application as "not responding". To make things more oddly, Task Manager reports that Steam is "Running" and vice versa at the same time. Furthermore after letting Steam opened for a few minutes, Steam closes itself and I can't even open it anymore.

The affected ReactOS builds are 0.4.5 (Stable) and 0.5-SVN (r75429 trunk revision). I did fill a JIRA report of this issue, CORE-12660, but looks like nobody seemed to take a look at this.
a.k.a. GeoB99 -- ReactOS Kernel developer -- My Wiki page
middings
Posts: 1073
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Steam fails to respond

Post by middings »

Thank you for making a JIRA report about ReactOS's problems with Steam that you observed. And thank you for being patient. The developers work on what the developers choose to work on. This is the nature of a volunteer project such as ReactOS. I regret that your JIRA issue hasn't received any attention since you reported your difficulty with Steam.

All I can suggest is to report that r75429 also fails to operate with Steam. Put your remarks in a new comment in the JIRA issue that you created earlier, CORE-12660. Describe any differences between the failure you discovered in the earlier revision and this most recent revision that you tried. An update to the issue is useful now because six months and many revisions have passed since you first reported the issue. New information added to a JIRA issue is added to a log seen by the developers. (A note to all JIRA users: Even tiny updates cause a new log entry. Most people do not realize that this happens. Multiple updates to correct or re-word small things are annoying to see in the log. Some developers even get updates by e-mail, they greatly dislike 'JIRA spam'. Try to make your comments and additions to JIRA correct before submitting them.)

Some of the developers have been working on implementing networking features that ReactOS still lacks. There is yet much more to be done. Perhaps this work will eventually resolve the difficulty with Steam that you reported.

If no developer takes an interest in your JIRA issue at this time, please continue to be patient.
Last edited by middings on Sat Jul 29, 2017 10:47 pm, edited 1 time in total.
User avatar
Fraizeraust
Posts: 234
Joined: Thu Jan 05, 2017 11:46 am
Location: Italy
Contact:

Re: Steam fails to respond

Post by Fraizeraust »

Makes me wonder why I posted this topic yet no recent updates for my JIRA report have been committed. Sorry about that, middings! Hopefully the new information I gave today on that JIRA is helpful otherwise please let me note!

*EDIT*: A guy named Mark wants me to translate the crash addresses to functions with log2lines. I installed RosBE for Linux and ran it flawlessly but no such command like log2lines can be found. He says it should be somewhere in ReactOS/host-tools but I don't have that folder! I read the wiki articles and nothing helps me at all. I'm confused. :(
a.k.a. GeoB99 -- ReactOS Kernel developer -- My Wiki page
middings
Posts: 1073
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Steam fails to respond

Post by middings »

See also the Support forum topic "Steam Stuck Connecting to account" that was started in May 2017.

Edit (July 30, 2017; 8:40 AM GMT):
Fraizeraust wrote:A guy named Mark wants me to translate the crash addresses to functions with log2lines. I installed RosBE for Linux and ran it flawlessly but no such command like log2lines can be found. He says it should be somewhere in ReactOS/host-tools but I don't have that folder! I read the wiki articles and nothing helps me at all. I'm confused..
Perhaps Mark forgot what is present in a new, clean installation of RosBE (the ReactOS Build Environment) and what might be created by RosBE later. A ReactOS/host-tools folder path is not created when RosBE is installed. This path and its contents are created when RosBE builds ReactOS from source. You could not be expected to know that.

However, you have installed RosBE and log2lines is a RosBE tool. RosBE has its own copy of log2lines in the RosBE/bin directory. Start RosBE then enter log2lines at RosBE's command prompt. You should get a screenful of usage information.

Oldman has written some instructions for log2lines. They helped me the first time I used log2lines. Oldman put his instructions on his private ReactOS Wiki page, here: https://www.reactos.org/wiki/User:Oldma ... _log2lines.
User avatar
Fraizeraust
Posts: 234
Joined: Thu Jan 05, 2017 11:46 am
Location: Italy
Contact:

Re: Steam fails to respond

Post by Fraizeraust »

@middings: Thank you for being patient at helping my unfortunate case as well as answering my PM!
middings wrote:However, you have installed RosBE and log2lines is a RosBE tool. RosBE has its own copy of log2lines in the RosBE/bin directory. Start RosBE then enter log2lines at RosBE's command prompt. You should get a screenful of usage information.
As I already explained to Mark Jansen about log2lines, he further asked me if log2lines DOES actually exist through RosBE/bin directory path. I answered him with "No" as the ls command doesn't say anything about log2lines' existence. Here I post an example of how RosBE binaries look like in an image.

http://imgur.com/a/ARRJW

According to Mark, I must build ReactOS with RosBE in order to get host-tools thus log2lines. Oldman's wiki says I must get Tortoise SVN to proceed with the building operation however Tortoise SVN isn't available for Linux ecosystems. RabbitVCS seems to be a great alternative for Tortoise SVN though but ReactOS' Wiki hasn't a documented page for implementing a SVN alternative for Linux.

I apologise if this seems to be quite a waste of time for you (and for everyone else?) but I really want to get this thing done and sending the required information to developers so they can fix the issue easily.
a.k.a. GeoB99 -- ReactOS Kernel developer -- My Wiki page
oldman
Posts: 1179
Joined: Sun Dec 20, 2009 1:23 pm

Re: Steam fails to respond

Post by oldman »

Fraizeraust wrote:
middings wrote:However, you have installed RosBE and log2lines is a RosBE tool. RosBE has its own copy of log2lines in the RosBE/bin directory. Start RosBE then enter log2lines at RosBE's command prompt. You should get a screen full of usage information.
As I already explained to Mark Jansen about log2lines, he further asked me if log2lines DOES actually exist through RosBE/bin directory path. I answered him with "No" as the ls command doesn't say anything about log2lines' existence. Here I post an example of how RosBE binaries look like in an image.
I have spent some frustrating hours over this weekend trying to get the information as to where to find log2lines in Linux, but I cannot find it. Linux comes with it's own version of log to lines, I wonder if RosBE does not come with it for Unix systems for that reason, or else I have not got a fully installed RosBE! log2lines superseded raddr2line, which I think is the Unix name.

Edit: just read the post by middings » 29 Jul 2017 20:56. So it is not there until you compile ReactOS!
Fraizeraust wrote: According to Mark, I must build ReactOS with RosBE in order to get host-tools thus log2lines. Oldman's wiki says I must get Tortoise SVN to proceed with the building operation however Tortoise SVN isn't available for Linux ecosystems. RabbitVCS seems to be a great alternative for Tortoise SVN though but ReactOS' Wiki hasn't a documented page for implementing a SVN alternative for Linux.
I apologise if this seems to be quite a waste of time for you (and for everyone else?) but I really want to get this thing done and sending the required information to developers so they can fix the issue easily.
There is a quick way around all this, that is to post your debug log here (use the Code button) with the actual revision number of ReactOS that you got it from, along with the JIRA CORE number. Then I, or someone else can down load it and run it through log2lines and post it in your JIRA report!
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
User avatar
Fraizeraust
Posts: 234
Joined: Thu Jan 05, 2017 11:46 am
Location: Italy
Contact:

Re: Steam fails to respond

Post by Fraizeraust »

Oh, sure! Here you go.

Code: Select all

fixme:(dll/win32/shell32/shlexec.cpp:1804) flags ignored: 0x00004000
err:(dll/win32/comctl32/commctrl.c:1954) GdiAlphaBlend failed: 2
(sdk/lib/rtl/actctx.c:2355) unknown attr xmlns:asmv3=urn:schemas-microsoft-com:asm.v3
(sdk/lib/rtl/actctx.c:2447) unknown element asmv3:application
(sdk/lib/rtl/actctx.c:2447) unknown element ms_compatibility:compatibility
(ntoskrnl/mm/ARM3/virtual.c:4506) Virtual allocation base above User Space
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/loader.c:384) LoadLibraryExW(C:\Program Files\Steam\crashhandler.dll) failing with status c0000135
(dll/win32/kernel32/client/loader.c:384) LoadLibraryExW(C:\Program Files\Steam\crashhandler.dll) failing with status c0000135
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
fixme:(dll/win32/winhttp/session.c:1329) no support on this platform
fixme:(dll/win32/winhttp/session.c:1367) discovery via DHCP not supported
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
TCP operation failed: 0xc0000128 (-12)
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
(sdk/lib/rtl/actctx.c:2355) unknown attr xmlns:asmv3=urn:schemas-microsoft-com:asm.v3
(sdk/lib/rtl/actctx.c:2447) unknown element asmv3:application
(sdk/lib/rtl/actctx.c:2447) unknown element ms_compatibility:compatibility
TCP operation failed: 0xc0000128 (-12)
(ntoskrnl/mm/ARM3/virtual.c:4506) Virtual allocation base above User Space
net.cpp (262) : Fatal Assertion Failed: PlatformSocketsInit failed, error [no name available] (10022)
net.cpp (262) : Fatal assert failed: net.cpp, line 262.  Application exiting.

[NFS41_NP][aglo] GetNetCaps 1
[NFS41_NP][aglo] GetNetCaps 2
[NFS41_NP][aglo] GetNetCaps 11
[NFS41_NP][aglo] GetNetCaps 6
C:\Program Files\Steam\crashhandler.dll
C:\Program Files\Steam\steamerrorreporter.exe
C:\Program Files\Steam\steamerrorreporter.exe
Starting minidump reporter process
(ntoskrnl/mm/ARM3/virtual.c:4506) Virtual allocation base above User Space
[NFS41_NP][aglo] GetNetCaps 1
[NFS41_NP][aglo] GetNetCaps 2
[NFS41_NP][aglo] GetNetCaps 11
[NFS41_NP][aglo] GetNetCaps 6
SteamErrorReporter process started
TCP operation failed: 0xc0000128 (-12)
Uploaded dump (out-of-process): C:\Program Files\Steam\dumps\assert_steam.exe_20170730174158_1.dmp
SteamErrorReporter process shutting down
I actually generated this debug log on a new revision trunk of ReactOS, r75458 (version 0.5-SVN) and build 20170730. The version of Oracle Virtualbox that I use for testing is 5.1.24 and the type CD ISO of that revision build is bootcd-dbg. The JIRA number is CORE-12660 as usual. If you can post here the new log created by log2lines it'd be very appreciated! :D
a.k.a. GeoB99 -- ReactOS Kernel developer -- My Wiki page
oldman
Posts: 1179
Joined: Sun Dec 20, 2009 1:23 pm

Re: Steam fails to respond

Post by oldman »

Have you posted the correct file? I cannot see where it as broken into the debugger, there is no backtrace, either! log2lines just created a copy, without adding anything!
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
User avatar
Fraizeraust
Posts: 234
Joined: Thu Jan 05, 2017 11:46 am
Location: Italy
Contact:

Re: Steam fails to respond

Post by Fraizeraust »

That because Steam doesn't actually crash the whole ReactOS so it did not enter in the debugger mode. Thought that these information from the log were enough for log2lines to produce a new log. I guess that's my mistake then?

No worries, I made a new log, with backtrace! Hopefully it's correct.

Code: Select all

fixme:(dll/win32/shell32/shlexec.cpp:1804) flags ignored: 0x00004000
(sdk/lib/rtl/actctx.c:2355) unknown attr xmlns:asmv3=urn:schemas-microsoft-com:asm.v3
(sdk/lib/rtl/actctx.c:2447) unknown element asmv3:application
(sdk/lib/rtl/actctx.c:2447) unknown element ms_compatibility:compatibility
(ntoskrnl/mm/ARM3/virtual.c:4506) Virtual allocation base above User Space
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/loader.c:384) LoadLibraryExW(C:\Program Files\Steam\crashhandler.dll) failing with status c0000135
(dll/win32/kernel32/client/loader.c:384) LoadLibraryExW(C:\Program Files\Steam\crashhandler.dll) failing with status c0000135
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
fixme:(dll/win32/winhttp/session.c:1329) no support on this platform
fixme:(dll/win32/winhttp/session.c:1367) discovery via DHCP not supported
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
TCP operation failed: 0xc0000128 (-12)
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
(dll/win32/kernel32/client/version.c:134) VerifyVersionInfo -- Version mismatch
err:(dll/win32/msafd/misc/dllmain.c:2813) Setting send buf to 12eb20 is not implemented yet
err:(dll/win32/msafd/misc/dllmain.c:2859) MSAFD: Set unknown optname 1002
WARNING:  WSHIoctl at dll/win32/wshtcpip/wshtcpip.c:366 is UNIMPLEMENTED!
(dll/win32/wshtcpip/wshtcpip.c:368) Ioctl: Unknown IOCTL code: -1744830460
(dll/win32/wshtcpip/wshtcpip.c:694) Set: SO_KEEPALIVE not yet supported
net.cpp (1828) : Assertion Failed: Unable to set default socket options, error 10022
err:(dll/win32/msafd/misc/dllmain.c:1973) Async Connect UNIMPLEMENTED!
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
(sdk/lib/rtl/actctx.c:2355) unknown attr xmlns:asmv3=urn:schemas-microsoft-com:asm.v3
(sdk/lib/rtl/actctx.c:2447) unknown element asmv3:application
(sdk/lib/rtl/actctx.c:2447) unknown element ms_compatibility:compatibility
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
TCP operation failed: 0xc0000128 (-12)
(ntoskrnl/mm/ARM3/virtual.c:4506) Virtual allocation base above User Space
net.cpp (262) : Fatal Assertion Failed: PlatformSocketsInit failed, error [no name available] (10022)
net.cpp (262) : Fatal assert failed: net.cpp, line 262.  Application exiting.

[NFS41_NP][aglo] GetNetCaps 1
[NFS41_NP][aglo] GetNetCaps 2
[NFS41_NP][aglo] GetNetCaps 11
[NFS41_NP][aglo] GetNetCaps 6
C:\Program Files\Steam\crashhandler.dll
C:\Program Files\Steam\steamerrorreporter.exe
C:\Program Files\Steam\steamerrorreporter.exe
Starting minidump reporter process
(ntoskrnl/mm/ARM3/virtual.c:4506) Virtual allocation base above User Space
[NFS41_NP][aglo] GetNetCaps 1
[NFS41_NP][aglo] GetNetCaps 2
[NFS41_NP][aglo] GetNetCaps 11
[NFS41_NP][aglo] GetNetCaps 6
SteamErrorReporter process started
TCP operation failed: 0xc0000128 (-12)
Uploaded dump (out-of-process): C:\Program Files\Steam\dumps\assert_steam.exe_20170730202630_1.dmp
SteamErrorReporter process shutting down

Entered debugger on embedded INT3 at 0x0008:0x80946734.
kdb:> bt
Eip:
<NTOSKRNL.EXE:146735 (:0 (RtlpBreakWithStatusInstruction))>
Frames:
<NTOSKRNL.EXE:125b5b (sdk/include/crt/mingw32/intrin_x86.h:94 (KiInterruptDispatch))>
<NTOSKRNL.EXE:125f7e (ntoskrnl/ke/i386/irqobj.c:315 (KiInterruptTemplateHandler))>
<NTOSKRNL.EXE:1ead13 (:0 (P0BootStackData))>
<HAL.DLL:9745 (:0 (HalProcessorIdle))>
<NTOSKRNL.EXE:1002e6 (ntoskrnl/po/power.c:383 (PopIdle0))>
<NTOSKRNL.EXE:127139 (ntoskrnl/ke/i386/thrdini.c:317 (KiIdleLoop))>
<NTOSKRNL.EXE:184ee8 (ntoskrnl/ke/i386/kiinit.c:682 (KiSystemStartupBootStack))>
<0000000e>
Couldn't access memory at 0x0000EB20!
kdb:> 
a.k.a. GeoB99 -- ReactOS Kernel developer -- My Wiki page
oldman
Posts: 1179
Joined: Sun Dec 20, 2009 1:23 pm

Re: Steam fails to respond

Post by oldman »

Sorry, but if ReactOS does not break into the debugger by itself, then it is of no use forcing it to break into the debugger with Alt+k. It is of no help whatsoever to the developers!

I have run it through log2lines, with the same outcome as before!
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
User avatar
Fraizeraust
Posts: 234
Joined: Thu Jan 05, 2017 11:46 am
Location: Italy
Contact:

Re: Steam fails to respond

Post by Fraizeraust »

That means there is no hope for me to translate all the crash addresses at all. Since Steam basically doesn't break up ReactOS into debugger I have no idea how can I make it so to track the culprit necessary for log2lines. Welp, I'm out...
a.k.a. GeoB99 -- ReactOS Kernel developer -- My Wiki page
oldman
Posts: 1179
Joined: Sun Dec 20, 2009 1:23 pm

Re: Steam fails to respond

Post by oldman »

Fraizeraust wrote:That means there is no hope for me to translate all the crash addresses at all. Since Steam basically doesn't break up ReactOS into debugger I have no idea how can I make it so to track the culprit necessary for log2lines. Welp, I'm out...
Not yet, there is something else that I want you to try!

Start ReactOS in debug mode, and just before you start Steam, do this.
Press Tab + k then Enter, to break into the debugger.
Then type set condition * first always then Enter.
Then type cont then Enter.
Now start Steam, if it breaks into the debugger, then type bt then Enter.
When it comes back to the prompt, type cont then Enter.
Keep typing bt and cont, as above, every time it breaks into the debugger.
When it as stopped breaking into the debugger, save the debug log and post it in your JIRA ISSUE, state that you have 'set condition * first always' in this report.
I can down load it from JIRA and run it through log2lines, but please use the same 75458 revision.

Please read this https://reactos.org/wiki/User:Oldman#Ge ... backtrace:


If it does not break into the debugger, then there is nothing more I can tell you to try, you will have to wait for any request from a developer.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
User avatar
Fraizeraust
Posts: 234
Joined: Thu Jan 05, 2017 11:46 am
Location: Italy
Contact:

Re: Steam fails to respond

Post by Fraizeraust »

I did every step and Steam still doesn't want to break ReactOS onto debugger mode. This is what I can say. I thank you and middings for trying at helping me nevertheless, it was a pleasure!
a.k.a. GeoB99 -- ReactOS Kernel developer -- My Wiki page
MadWolf
Posts: 688
Joined: Sat Dec 31, 2005 4:19 am
Contact:

Re: Steam fails to respond

Post by MadWolf »

hi
i did have an idea run Dependency Walker to generate a log http://www.dependencywalker.com/ but there looks like there is a regression or bug https://jira.reactos.org/browse/CORE-12052
Post Reply

Who is online

Users browsing this forum: No registered users and 17 guests