i get a code=10000 error approximatly 30 mins after i start up mir on any server, a friend told me that it might be something to do with missing files. I have tried downloading mir 1.4 many times and each time its the same story. Im just wondering if anyone has the same problem and if so wots the cure?
code 10000
- Thread starter Rocusho123
- Start date
So there is absolutley nothing i can do to stop this? because i cant really play mir with it happening
there are many cures 1 of them disable hardware acceleration on your soundcard ,or just disable sound in mir
- Mar 27, 2003
- 1,195
- 0
- 213
*Moved to help* also its nothing to do with mir etc its just that you either need more ram or you have a slow computer etc just get more and i think it should be fine (i used to get it on my old comp but i dont get it now), also i think it varies on the server you play on eg if the servers really laggy you usually get it.
/Miles
/Miles
thx fr the help guys. Sadly i have a relativly new computer with 512 DDR RAM, just got a new graphics card and motherboard and i have XP. Ive been tweaking around with my graphics card, but nothing seems to have changed. Any more help or advice would be greatly appreciated.
Thanks
Thanks
Taken from legendofmir site
What is the infamous Code 10000 Error
According to the official FAQs, this error means "bad lag". In practice its meaning is much more complex. The code 10000 message is generated by the routine that checks the internal timers of the machine and compare them with those of the servers in order to find out if some kind of speed hack is installed. Lag can certainly cause this error (if makes data packets go out of sync) but, I have to remark, the code 10000 error is first of all an anti-cheat protection: as soon as the timing errors reach 3 milliseconds, the client closes the connection and shows the error message.
Why the code 10000 error is so common on nForce2 based motherboards
As already said, it's an error related to the internal timers of the PC. It has been initially found by some players (thank you FeelTheFear ) that by decreasing the clock speed of the FSB you could prevent the infamous code 10000 error from happen. Strangely enough it didn't seem a problem of stability, for example if you downclock the external frequency (the FSB is twice the value of the external frequency) from 166 to 133MHz, you don't improve the situation, but if you downclock it by 3/4 MHzs MIR is much more stable and the errors arise more rarely. The solution was found in a usually overlooked option included in some nForce2 chipsets (namely the ASUS models), called "FSB Spread spectrum" which, if disabled, solves the problem (thank you TheSeLecteR ).
What's the "FSB Spread spectrum" option for and why it is related to the code 10000 problem
Apparently this option seems just related to the EMI (Electromagnetic Interference) reduction system implemented on nForce2 motherboars. What it is interesting to discuss is the method used by the nForce2 chipset to acomplish this task: the Spead Spectrum option reduces the EMI by modulating the pulses of the clock so that a particular frequency is used only for short moments, i.e. the frequency is constantly and slightly changed. This option can cause malfunctions of timing-critical components and programs including the speed-hack check routines implemented in Mir.exe. For this reason it is recommended that you disable it!
Instructions to disable the FSB Spectrum option
This option can be disabled from the BIOS. Please, refer to the User's manual of your mainboard.
You might also need to flash the BIOS, but if you don't know how to do it, ask some more experienced friend for assistance: if something goes wrong while flashing the BIOS, your PC might not reboot.
What is the infamous Code 10000 Error
According to the official FAQs, this error means "bad lag". In practice its meaning is much more complex. The code 10000 message is generated by the routine that checks the internal timers of the machine and compare them with those of the servers in order to find out if some kind of speed hack is installed. Lag can certainly cause this error (if makes data packets go out of sync) but, I have to remark, the code 10000 error is first of all an anti-cheat protection: as soon as the timing errors reach 3 milliseconds, the client closes the connection and shows the error message.
Why the code 10000 error is so common on nForce2 based motherboards
As already said, it's an error related to the internal timers of the PC. It has been initially found by some players (thank you FeelTheFear ) that by decreasing the clock speed of the FSB you could prevent the infamous code 10000 error from happen. Strangely enough it didn't seem a problem of stability, for example if you downclock the external frequency (the FSB is twice the value of the external frequency) from 166 to 133MHz, you don't improve the situation, but if you downclock it by 3/4 MHzs MIR is much more stable and the errors arise more rarely. The solution was found in a usually overlooked option included in some nForce2 chipsets (namely the ASUS models), called "FSB Spread spectrum" which, if disabled, solves the problem (thank you TheSeLecteR ).
What's the "FSB Spread spectrum" option for and why it is related to the code 10000 problem
Apparently this option seems just related to the EMI (Electromagnetic Interference) reduction system implemented on nForce2 motherboars. What it is interesting to discuss is the method used by the nForce2 chipset to acomplish this task: the Spead Spectrum option reduces the EMI by modulating the pulses of the clock so that a particular frequency is used only for short moments, i.e. the frequency is constantly and slightly changed. This option can cause malfunctions of timing-critical components and programs including the speed-hack check routines implemented in Mir.exe. For this reason it is recommended that you disable it!
Instructions to disable the FSB Spectrum option
This option can be disabled from the BIOS. Please, refer to the User's manual of your mainboard.
You might also need to flash the BIOS, but if you don't know how to do it, ask some more experienced friend for assistance: if something goes wrong while flashing the BIOS, your PC might not reboot.