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 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).
Got something to add? Send me email.
640K ought to be enough for anybody. (Bill Gates)
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 (link)
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 (link)
------------------------
Printer Friendly Version
Have you tried Searching this site?
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.
Contact us
Printer Friendly Version