@Wonko the Sane COOL DOWN MAN... its different topic realted to boot livexp bootsdi.img on laptop giving STOP error 0xEA , nothing to do with this topic.
this topic is i can NOT run bootsdi.img of livexp and that topic is i CAN run livexp bootsdi.img on laptop but BSOD STOP error 0xEA ..just want to know how to workout the BSOD STOP error 0xEA on laptop.
see post http://reboot.pro/to...od-7b/?p=178424 and this http://reboot.pro/to...od-7b/?p=178545
i hope now you got my point....and will work out for that topic not this ..
That topic is "LiveXP - BSOD 7B".
This topic is "Live xp and BootSDI",
You fail to see how you needlessly hijacked a thread (BTW started by another user in need of help/assistance) about a BSOD 0x0000007b and CORRECTLY tiltled "LiveXP - BSOD 7B" by posting your request for help on an altogether different issue, first the integration of DriversPack and later for yet another issue, the BSOD STOP error 0xEA on your laptop.
The general idea of a board topic is that it remains - if possible - ON topic, and it is expected that non-newbies understand this basic concept and tries his/her best to not hijack a topic, particularly if he/she isn't the topic starter.
You also fail to see how on a board you do not ask for help "ad personam" and how the EXACT, ACCURATE, EXHAUSTIVE informations that you are asked to provide in order to be helped, besides making more probable that someone can actually help you (and allow these good intentioned members to do so as fast and with the least effort possible) are useful (or will become useful) to other people that may have the same or similar issues, i.e. through helping you an idea, a workaround or a solution might become of use for something or someone else.
If you prefer, by omitting informations or providing vague or confusing ones, not only you reduce the probabilities that someone will take the added time to get such info from you, but you are making a damage to the whole board ( I could have personally spent the time I lost to explain over and over these same basic concepts into something more useful or helping someone else), contribute to "hide" a hopefully found solution or workaround from search results into an exceptionally long thread largely occupied by the attempts to get the information from you or dedicated to a completely different issue from what the topic title says and - before or later - such attitude will result in other members simply failing to reply to your questions and/or stop assisting you.
There is - as always - an alternative which is providing you with some vague, confusing or absurd information/advice, so that you will also lose a lot of time in attempting to interpret them, and attempt to implement them, as it happens on a number of technical boards, example
To solve the 0xEA error you should limit externally the kernel linkage to the framebuffer.
A co-driver may help with it, but only if you have less than 3 Gb of Ram, otherwise the user-space helper may connect to RIng 0, especially if you have noframe set in the BIOS.
UEFI is different.