exception error

[nc]innova]

sorry for bumpage but. are ppl still getting these. cus if they are i think i found the problem.

Most ISP (internet service providers(the ppl that connect you to the net)) give user dynamic IP's this means every now and then your ip will change. i was thinking, if your playing halo as this happens, what would halo do. Your old ip that it is connecting too wouldnt be there anymore. and you would suddenly be another player who isnt supposed to be there. so bam, error. might not be but hey. if we can get someone who has a static ip to stay there for hours. maybe we will find out

[Sod-No_Fear]

im looking it up

[Sod-No_Fear]

im looking it up to

[Sod-No_Fear]

thank me
SYMPTOMS
Windows reports a random "Fatal Exception 0x has occurred at xxxx:xxxxxxx" error message even though your previous version of Windows or Windows for Workgroups did not.
CAUSE
A common cause for this error messages is faulty physical memory (RAM) on the computer. The following are reasons why your previous version of Windows may appear to run smoothly while Windows may report a random "Fatal Exception 0x has occurred at xxxx:xxxxxxx" error message:
• All operating systems use memory differently. In Windows 3.1, the "bad" memory may be used for holding rarely used data. In Windows, the "bad" memory is used for holding frequently run program information.
• Windows 3.1 contains comparatively little 32-bit code. Windows uses much more 32-bit code. Furthermore, there are subtle differences between the way memory is accessed if it is being accessed for code or if it being accessed for data. Because Windows runs much more 32-bit code, these subtle errors show up more often.

In particular, all the 32-bit code in Windows 3.1 resides in one place: at the low-end of physical memory. If the first 4 megabytes (MB) of memory can handle 32-bit code, Windows 3.1 works without errors. This is true even if the topmost physical memory cannot run 32-bit code because Windows 3.1 does not run 32-bit code outside the first 4 MB of RAM.

Windows runs 32-bit code in all portions of memory. Therefore, when Windows runs 32-bit code in a section of RAM that cannot run 32-bit code well, you may receive "Fatal Exception Error 0x:xxxxxxxx" error messages.
• Windows interacts with hardware differently than previous versions of Windows. This is due partly to Plug and Play and partly to new drivers that take advantage of the additional capabilities of interface adapters. These features may uncover anomalies in the hardware that never appeared in previous versions of Windows because earlier versions did not attempt to exploit these features.
• Many new computers do not have memory chips that perform parity checking; therefore, you may have been encountering parity errors in Windows 3.1 without realizing it because the errors were in relatively harmless sections of memory. For example, in a Microsoft Word for Windows document, the word "the" is changed to "tie."

RESOLUTION
To resolve these errors, it is often necessary to replace the RAM and/or system board (motherboard). In some circumstances it may be possible to alter CMOS settings, such as Memory Wait States, to run Windows successfully. In other cases, disabling the motherboard L2 cache allows Windows to run. For information about how to edit CMOS settings, please view your computer documentation or contact your hardware manufacturer.

For additional information about how to identify if your issue is faulty RAM, click the article numbers below to view the articles in the Microsoft Knowledge Base:
181862 (http://support.microsoft.com/kb/181862/EN-US/) Specifying Amount of RAM Available to Windows Using MaxPhysPage
134503 (http://support.microsoft.com/kb/134503/EN-US/) Parity Error Messages May Indicate Bad Memory
Note that you may want to restart Windows in Safe mode to see if the errors persist. If they do not, the problem may be a software or driver problem, in which case the information above may not apply. For additional information about how to troubleshoot fatal exception errors, click the article numbers below to view the articles in the Microsoft Knowledge Base:
192926 (http://support.microsoft.com/kb/192926/EN-US/) How to Perform Clean-Boot Troubleshooting for Windows 98
156126 (http://support.microsoft.com/kb/156126/EN-US/) Troubleshooting Windows 95 Using Safe Mode
MORE INFORMATION
Fatal exception errors are similar to EMM386 exception errors. For example, fatal exception error 0C is generally equivalent to EMM386 exception error 12 or a stack fault.

--------------------------------------------------------------------------------

APPLIES TO
• Microsoft Windows Millennium Edition
• Microsoft Windows 98 Second Edition
• Microsoft Windows 98 Standard Edition
• Microsoft Windows 95

Read these to see if you have these ...

Keywords: kberrmsg kbfatalexerr0e kbhardware kbprb kbfatalexerr0d kbdiskmemory KB138788


Did this content help you?
Yes
No
Maybe
Please select one option based on your first choice:
I'm very satisfied
I think it will help, but I haven't tried it yet
It is helpful, but I need more information
It is helpful, but hard to understand
Seemed relevant in search results, but didn't help me
The information is wrong
The page contains one or more broken links
i would like to thank me and my co-helpers

[Sod-No_Fear]

innovacious said:

sorry for bumpage but. are ppl still getting these. cus if they are i think i found the problem.

Most ISP (internet service providers(the ppl that connect you to the net)) give user dynamic IP's this means every now and then your ip will change. i was thinking, if your playing halo as this happens, what would halo do. Your old ip that it is connecting too wouldnt be there anymore. and you would suddenly be another player who isnt supposed to be there. so bam, error. might not be but hey. if we can get someone who has a static ip to stay there for hours. maybe we will find out

no it fracking doesn't hers the problem
look at my 2 thread on this page

[{§}V3NOm{§}]

holy crap dude major triple/quad post there man you better watch the rules or else the admin are really gonig to take care of you... you really need to read the #rules# or else you wont me able to post here..and if you ask me your a major #noob#

[nc]innova]

and what you have posted is not correct either no faer, there is no FATAL error, theres an exception error, it has nothing to do with hardware. its something happeing in game that halo dosnt like and dosnt have an error handler for.

and you cant "look it up" an exception error is shown if ANYTHING goes wrong in halo that it cannot handle, so there are hundreds of different errors that happen and then give the same error box.

edit: and ive just realised. what youve said basically mens everyone on this forum needs new ram and or a new motherboard.... after seeing that, didnt you think it may be wrong?

[{§}V3NOm{§}]

innovacious said:

edit: and ive just realised. what youve said basically mens everyone on this forum needs new ram and or a new motherboard.... after seeing that, didnt you think it may be wrong?

oh no im not buying nothing new for my computer i dont even have money to buy a new one..and ya nc]innova you are correct there are many exception errors escecially when we messed around with HMT if you remember (might be a slight #offtopic# sorry if i am )

[©Slingshot]

nofear said:

im looking it up

Hey will you please go to the Rules section and READ THEM!!

What is with the four posts in a row.......

Are you asking to be banned from this forum...

Well you are certainly going the right way about it!

[cs]ÆRÔ©]

I looked up the messege on google, and all it would say in everything i clicked on that the exception thing was a bug in the software.

That's Microsoft for ya

wondering if mac users have the same problem.

[nc]innova]

thats what i said it is. all software has error handlers, halo has some, like when two ppl join with the same name, it changes one to shadow to stop any errors. it dosnt have handlers for everything though, like, if someone in the server was already called shadow. bam, halo dont know what to do, exception error

[cs]ÆRÔ©]

exactly, so officially there are no wasy to predict or prevent these things from happening, just a nother dumb microsoft thing...

[Chicken Noodle]

i know what cuases the errors, an error is caused wen u overload the mod... like u say a sniper holds a clip round of 100 and say that ammo held is like 10 lol, also if u do too much, u know something virtually impossible, something unallowable, like wen it says under projectile ammo per shot for a sniper rifle and u put 2, thats unacceptable and causes an error, well thats wat it usually is when it happens to me, then wen i go back and correct it it works just fine, otherwise im clueless also

[nc]innova]

errors like what your saying will happen as soon as the map loads, this happens after playing if for hours

[lol]

Yea, and if that was the problem, then everyone would have exception errors all of the time. Even us Mac users. We have never had an exception error(That I know of). Skelito modded the rocket hog to fire 3 modded rockets at the same time. But we hog-a-pault all of the time so why are there no exception errors for it? Because it's something else.

and P.S. Try not to bump nearly month-old threads. Just wanted to say that.