Skip to content

[CS 1.6] fatal error: file read failure #1660

InmanInman opened this Issue Feb 13, 2013 · 3 comments

2 participants


I try to connect to this server, and it gives me a file read failure, then my CS closes/crashes

server data in the screenshot

Processor Information:
Vendor: GenuineIntel
Speed: 1701 Mhz
4 logical processors
2 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported

Network Information:
Network Speed:

Operating System Version:
Linux Mint 14 Nadia (64 bit)
Kernel Name: Linux
Kernel Version: 3.5.0-17-generic
X Server vendor: The X.Org Foundation
X Server release: 11300000

Video Card:
Driver: Intel Open Source Technology Center Mesa DRI Intel(R) Ivybridge Mobile x86/MMX/SSE2

Driver Version:  3.0 Mesa 9.0
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID:  0x8086
DeviceID:  0x166
Number of Monitors:  1
Number of Logical Video Cards:  1
Primary Display Resolution:  1600 x 900
Desktop Resolution: 1600 x 900
Primary Display Size: 12.17" x 6.85"  (13.94" diag)
                                        30.9cm x 17.4cm  (35.4cm diag)
Primary VRAM Not Detected

Sound card:
Audio device: Intel PantherPoint HDMI

RAM: 3655 Mb

UI Language: English
Microphone: Not set
Total Hard Disk Space Available: 236630 Mb
Largest Free Hard Disk Block: 167100 Mb

Installed software:

Recent Failure Reports:
Tue Feb 12 21:14:04 2013 GMT: file ''/tmp/dumps/assert_20130212221400_1.dmp'', upload yes: ''CrashID=bp-36c92141-b797-4542-8e58-8fcb12130212''

@alfred-valve alfred-valve was assigned Feb 13, 2013

I cannot reproduce the problem, I can connect to that server just fine. Note that it looks like a hacked server and it only running bots, so god knows what code it is actually running.


that's weird, it wasn't showing any bots in the bots tab.

It does seem to work now, so it might have been the map that was crashing my counter strike?


Could be, if you can find out how to reproduce it please update this bug and reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.