Windows XP is a pain in the /\R$3!!!
Have you ever had a PC reboot on you in the middle of an important backup? Well I have, and I'll tell you this, it's really starting to (CENSORED) me off...
Can anyone translate this MicroCrap jargon for me please?
Code:
BCCode : 1000008e BCP1 : C0000005 BCP2 : F953376D BCP3 : F4874B08
BCP4 : 00000000 OSVer : 5_1_2600 SP : 0_0 Product : 256_1
Ok, now I'm REALLY mad! Halfway through posting this bloody post, it decides to restart again... This is the first time I've had this problem, and I hate Bill Gates.
Quote:
"We are Microsoft of Borg. You will be assimissimissimissimiss.... The system has recovered from a fatal error, would you like to report this error to Microsoft?"
I hate Bill Gates. C'mon people, let's say it together! I HATE BILL GATES! I'm shutting my PC down now and will continue to post using my lovely friend here, My Sun Microsystems UltraSparc 2 Creator... God that felt good typing that...
Re: Windows XP is a pain in the /\R$3!!!
Quote:
Originally posted by esmerelda
Can anyone translate this MicroCrap jargon for me please?
Code:
BCCode : 1000008e BCP1 : C0000005 BCP2 : F953376D BCP3 : F4874B08
BCP4 : 00000000 OSVer : 5_1_2600 SP : 0_0 Product : 256_1
That 'microcrap' basically translates to a possible stack fault in the hex address printed above. All aspects of any program go onto what is called a stack. Like so...
| ITEM 5 |
| ITEM 4 |
| ITEM 3 |
| ITEM 2 |
| ITEM 1 |
----------
Now....
The only way item 1 (or segment 0) can be removed (pop) from the data stack is to remove all the items above.. which is where a segment/stack error can occur. It's commonly caused by bad coding from the vendor... not Microsoft (so don't hate Bill!)
When a segment error occurs, it's trying to pull an item from the stack which doesn't exist or cannot be accessed. It's very tricky to understand, so you really need to be a base developer to understand it. lol
The two common phrases are "Pop" & "Push" a data segment. They work in the same way as an array would in Pascal or VB.
As i have posted previously... the error screen you are refering to... is a default screen in WinXP, which tells the user EXACTLY what has crashed and why (if you understand the microcrap). It's NOT windows crashing !!!! Again... It's NOT windows crashing !!!!
The most common cause of the stack segment error, is basically an item has been pulled from the stack (removed) and then is reffered to l8er in the program. The only way to re-access that data segment, is to PUSH (put) that stack name back on.
IE.
ITEM 1 'Program then removes this'
mov item1 'ERROR...it doesn't exist anymore?????'
PUSH ITEM 1 'And now it's back, yeehee'
Sorry if this is a bit blinding, but you asked ! lol
If you are still strugling, feel free to gimmie a call.
Hope that helps u, although i cannot think how:confused:
Regards,
Paul.