This article is from a FAQ concerning SCO operating
systems. While some of the information may be applicable to any OS,
or any Unix or Linux OS, it may be specific to SCO Xenix, Open
Desktop or Openserver.
There is lots of Linux, Mac OS X and general Unix info elsewhere on
this site: Search this site is the best
way to find anything.
This is an ancient post with little relevance to modern systems.
What causes a kernel trap 0x00000008 ?
That's the Double Panic- the kernel panics while panicing.
It can be caused by corrupt driver code, but is more likely to be bad ram (or bad CPU, motherboard- anything that causes a bad instruction to get to the cpu).

Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
How can I fix this error? (0x00000008) and I have another problem: 0x006fac78. What could be? What can I do to fix this error?
Thanks a lot.
Mon Aug 1 19:48:04 2005: 914 anonymous
I'm also running into this issue. I'm getting the following error message;
The instruction at "0x635ed461" referenced memory at "0x00000008". The memory could not be "written".
followed by;
The instruction at "0x63638176" referenced memory at "0x00000130". The memory could not be "read".
Any suggestions?
SBR24@msn.com
Mon Aug 1 20:18:22 2005: 915 TonyLawrence
There's no magic: it's either bad hardware or a bad driver. If nothing has changed in the OS and it has sprung up, it is almost certainly hardware. See the advice at http://aplawrence.com/Unixart/trape.html
Sat Oct 23 22:27:45 2010: 9059 anonymous
Problem caused by .net framework, when an application that use .net 1.1 version use too much memory...BUM
LOOK AT http://support.microsoft.com/kb/830724
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar