PDA

View Full Version : TRAP 00000006


Rob
January 10th 04, 11:41 AM
Can anyone help with this error message recieved when I
tried to boot up?

TRAP 00000006 EXCEPTION tr=0028 cr0=80000011 cr2=00000000
cr3=00039000 gdt limit=03ff base=8003f00 idt limit=07ff
base=8003f400 cs:eip=0008:80530b85 ss:esp=0010:000600d0
errcode=0000 flags=00010087 CyNoZr IntDis Down TrapDis
eax=00000000 ebx=80087000 ecx:8003f028 edx=80042000
ds=0010 es=0010 edi=8003f000 esi=ffdff000 ebp=000600d8
cr0=80000011 fs=0030 gs=0000

Also this isn't the only error I've been receiving.
Usually it only happens when I boot my computer up after
a couple of hours of being switched off (i.e. the
morning) Sometimes get a ntoskrnl.exe missing or corrupt
error.
I've re-installed windows (several times) and re-
formatted my hdd (several times).

Any suggestions greatly apreciated.

BTW: I'm running Windows XP, Intel 2.4Ghz, Western
Digital 80Gb Hdd (7200SE), 256 (DDR333)

Malke
January 10th 04, 04:41 PM
Rob wrote:

> Can anyone help with this error message recieved when I
> tried to boot up?
>
> TRAP 00000006 EXCEPTION tr=0028 cr0=80000011 cr2=00000000
> cr3=00039000 gdt limit=03ff base=8003f00 idt limit=07ff
> base=8003f400 cs:eip=0008:80530b85 ss:esp=0010:000600d0
> errcode=0000 flags=00010087 CyNoZr IntDis Down TrapDis
> eax=00000000 ebx=80087000 ecx:8003f028 edx=80042000
> ds=0010 es=0010 edi=8003f000 esi=ffdff000 ebp=000600d8
> cr0=80000011 fs=0030 gs=0000
>
> Also this isn't the only error I've been receiving.
> Usually it only happens when I boot my computer up after
> a couple of hours of being switched off (i.e. the
> morning) Sometimes get a ntoskrnl.exe missing or corrupt
> error.
> I've re-installed windows (several times) and re-
> formatted my hdd (several times).
>
> Any suggestions greatly apreciated.
>
> BTW: I'm running Windows XP, Intel 2.4Ghz, Western
> Digital 80Gb Hdd (7200SE), 256 (DDR333)

I Googled for "TRAP 00000006 EXCEPTION" and got links implying that the
ntldr file is corrupted. However, since you've formatted and
reinstalled several times, I'd look to faulty hardware as the cause. Do
a hard drive diagnosis with a utility downloaded from the drive mftr.'s
website. If the drive is OK, then test RAM with Memtest86
(www.memtest86.c0m), but I'm going to guess there's something wrong
with your hard drive.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

Google