Not booting TRAP FFFFFFFF EXCEPTION

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Ok, so I accidentally kicked the computer, (stupid, i know) and this black
screen with white text appeared with that as the header. Then there is what I
am assuming was a register dump, almost all of which contained either 4 or 8
'F' characters. The others were 'gdt limit=03FF base=00017000 idt limit=07FF
base=00017400'
'ss:esp=FFFF:00000017 errcode=0000' and that is all that contained anything
other then 'F'. I have tried rewriting the MBR and such as well as a recovery
from the XP disc but nothing works. Also tried just the one hard drive by
itself in a seperate box, but that didn't work either. I would like to know
if anyone can tell me if there is a chance of recovering the windows install,
or if the physical drive has crapped out and needs replacing, or anything
inbetween. If its fixable, please explain. I am fairly competent for a home
user, but not a rocket scientist.
THANK YOU
 
computerulz said:
Ok, so I accidentally kicked the computer, (stupid, i know) and this
black screen with white text appeared with that as the header. Then
there is what I am assuming was a register dump, almost all of which
contained either 4 or 8 'F' characters. The others were 'gdt
limit=03FF base=00017000 idt limit=07FF base=00017400'
'ss:esp=FFFF:00000017 errcode=0000' and that is all that contained
anything other then 'F'. I have tried rewriting the MBR and such as
well as a recovery from the XP disc but nothing works. Also tried just
the one hard drive by itself in a seperate box, but that didn't work
either. I would like to know if anyone can tell me if there is a
chance of recovering the windows install, or if the physical drive has
crapped out and needs replacing, or anything inbetween. If its
fixable, please explain. I am fairly competent for a home user, but
not a rocket scientist. THANK YOU
Click to expand...

Your post is a bit jumbled, but if I have this correctly:

1. You kicked the computer.
2. Your hard drive no longer works.
3. You put the hard drive in a different computer and it - what? Wasn't
shown in the BIOS? What error messages did you get? I wouldn't expect
it to be able to boot XP on different equipment but it should show up
in the BIOS.
4. Did you try a different, known-working hard drive in the original
computer? If not you need to do this to determine if you also damaged
the motherboard.
5. Have you run a diagnostic utility on the suspect hard drive? Get one
from the drive mftr.'s website and do a thorough test.

Try and give the details clearly - use numbered points as above. Tell us
exactly what happens when you put the original hard drive in the
original pc and what happens when you put that drive in the second pc.
Quote error messages exactly. Tell us the answer to #4 and #5 above.

Then we'll be able to give you more focused help.

Malke
 
1) I can see the HDD in my bios
2) I can boot onto another HDD on the same IDE cable in my computer (however
my RAID 0 SATA drives will not boot)
3)I can read some files on the original/dead HDD when booted into my other
OS (obviously I haven't tried all of the 70000+ files)
4) The file system is NTFS, (both partitions) which unfortunately rules out
editing from a linux boot.
5)I have now run a full physical disk scan, (which supposedly scanned all
platters) which found no errors. (Not one from the manufacturers site yet, as
it recommends a backup first.)
6) FYI the drive is a 120GB Western Digital PATA drive, partitioned into
approx 20GB (C: drive) and 100GB (D: drive)
7) When the computer boots, the BIOS does its thing, passes control to the
HDD or should have, and it is then that I get the same exception screen as i
got instantly after kicking it.
8) What follows is the error, as closely formatted to the original as
possible.
TRAP FFFFFFFF ==============EXCEPTION=====================


tr=FFFF cr0=FFFFFFFF cr2=FFFFFFFF cr3=FFFFFFFF
gdt limit=03FF base 00017000 idt limit=07FF base=00017400
cs:eip=FFFF:FFFFFFFF ss:esp=FFFF:00000017 errcode=0000

flags=FFFFFFFF CyZr IntEnUp TrapEn
eax=FFFFFFFF ebx=FFFFFFFF ecx=FFFFFFFF edx=FFFFFFFF ds=FFFF es=FFFF
edi=FFFFFFFF esi=FFFFFFFF epb=FFFFFFFF cr0=FFFFFFFF fs=FFFF gs=FFFF

That is pretty much all I can tell you right now, I may attempt a backup
tonight, then a scan, but otherwise let me know if you need any more
information.
Thanks for the quick response:)
 
computerulz wrote:

See my comments inline:
1) I can see the HDD in my bios
Click to expand...
This is good. To make sure the original drive is fine, boot with
Knoppix. If it runs fine with Knoppix, you can't edit files but you can
get your data off and either burn to cd-r or use a usb thumbdrive. Let
me know if you want to do this and need more details about it.
2) I can boot onto another HDD on the same IDE cable in my computer
(however my RAID 0 SATA drives will not boot)
Click to expand...
This is good because it does show that the IDE connection on the
motherboard is OK. You never mentioned any RAID 0 SATA drives in your
first post. From which drive are you booting Windows? If XP is
installed on the PATA drive, what have the SATA drives got to do with
this?
3)I can read some files on the original/dead HDD when booted into my
other OS (obviously I haven't tried all of the 70000+ files)
Click to expand...
You also didn't mention that you were dual-booting. I assume since you
mention Linux that you are running some Linux distro as the "other OS".
If this is the case, you don't need Knoppix. Just boot into whatever
distro you're running and get your data off the drive.
4) The file system is NTFS, (both partitions) which unfortunately
rules out editing from a linux boot.
Click to expand...
No, you shouldn't edit NTFS from Linux. You could make a Bart's PE if
you need to edit files on XP, but I'm not convinced that will be useful
anyway.
5)I have now run a full physical disk scan, (which supposedly scanned
all platters) which found no errors. (Not one from the manufacturers
site yet, as it recommends a backup first.)
Click to expand...
So back up your data as suggested above and then get the Western Digital
drive diagnostic and run it. The thorough test will not write to the
drive.
6) FYI the drive is a 120GB Western Digital PATA drive, partitioned
into approx 20GB (C: drive) and 100GB (D: drive)
7) When the computer boots, the BIOS does its thing, passes control to
the HDD or should have, and it is then that I get the same exception
screen as i got instantly after kicking it.
8) What follows is the error, as closely formatted to the original as
possible.
TRAP FFFFFFFF ==============EXCEPTION=====================
Click to expand...
(snip rest of error message)

Basically, get your data off, test the drive with Western Digital's
tools, and if the drive tests OK you may want to run a motherboard test
or two. Otherwise, format the drive and clean-install Windows to see
what happens. Or throw in another drive and clean-install Windows to
see if it runs well.

Don't forget to reseat all RAM and hardware cards, too.

Malke
 
Back
Top