Jump to content
krieser

Have You Seen This Error Message Before?

Recommended Posts

Hey folks! Does anyone know what this message might mean? I got an error like this today, after WinXP Pro locked up and I had to shut off the power to reboot. I've never seen anything like it before and google couldn't turn up anything useful in english. It seems to come up before the OS even starts to load, so this may be more appropriate in the hardware section (although I blame MS for everything).

 

TRAP 0000006 ======EXCEPTION======

 

tr=0028 cr0=80000011 c2=00000000 cr3=00039000

gdt limit=03FF base=0003F000 idt limit=07FF base=0003F400

 

cs:eip=0008:8016500C ss:esp=0010:005FBF4 errcode=0000

flags=00010097 Cy NoZr IntDis Down TrapDis

 

eax=0005FC99 cbx=0005FFD8 eox=0000000A edx=004164D2

ds=0010 es=0010

 

edi=0005FD3A esi=0005FFFC ebp=0005FE1F er0=80000011

fs=0030 gs=0000

 

From the message, I ctrl-alt-del'd and WinXP ran CHKDSK on two partitions. Any thoughts? :)

Share this post


Link to post
Share on other sites

It actually may not be the exact message I got. I wrote down about half the message to research later, and then said 'screw it' and rebooted. I found exerpt in another forum and it looks identical, but the forum didn't really seem to provide any useful feedback. I'm a little worried it's hard disk related since the drive kicked in before windows locked up...

 

Thanks in advance!! :)

Share this post


Link to post
Share on other sites

found this on google.

 

 

THE BLACK SCREEN OF DEATH!

 

TRAP 00000006 ===================== EXCEPTION

================================

 

 

tr=0028 cr0=00000011 cr2=00000000 cr3=000000000

gdt limit=03FF base=00017000 idt limit=07FF base=00017400

 

cd:eip=0008:412AC1B7 ss:esp=0010:00061FEB errcode=0000

flags=00010013 Cy NoZr IntDis Down TrapDis

eax=023EE94A ebx=00401280 ecx=0000FE18 edx=534D0040 ds=0010 es=0010

edi=00461643 esi=00051D68 ebp=000609E8 cr0=00000011 fs=0030 gs=0000

 

I have not the faintest idea as to what all this means but I have a feeling

that the "Cy NoZr Int Did Down TrapDis" bit might be telling me that the

problem lies in the hard disk (though I'm probably talking through my

heatsink and fan!).

 

To solve the problem, take the following steps: -

 

Set the Bios to boot from CD-ROM

 

Place the XP CD-ROM in the drive.

 

Boot the PC and when prompted tell it to boot from the CD.

 

You are asked if you want to install Windows or go into Repair mode (Console

Mode) - choose the install option.

 

The procedure then detects that you already have Windows XP install and asks

you if you want a new installation or if you want to repair the existing

installation. Choose the latter option - REPAIR THE EXISTING INSTALLATION.

 

Then you just sit back for half-an-hour. You may get occasional prompts

regarding drivers for hardware installed or updated since the original

installation and if you have those drivers on the hard disk you can do them

at that point or later on as you prefer.

 

This will fix the installation but you will then need to apply any Service

Packs

and ensure that you are fully up-to-date via Windows Update.

 

The end result is a fully fixed installation that look and works exactly as

it did before.

 

During the process a reinstallation of Windows takes place although all the

installed applications and data seem properly to be registered afterwards

and nothing has been found to be missing.

 

This problem has now occurred to me several times on two different PCs so

the repair feature on the XP CD is worth its weight in gold.

 

I'm pretty convinced that, for whatever reason, the boot sector plus some

other stuff (that prevents FIXBOOT and.or FIXMBR from working) is being

trashed but, whatever the reason, this solution has worked every time.

Share this post


Link to post
Share on other sites

Thanks TCH-Mike!!! Thumbs Up

I did read this, but have not had a chance to try it. I wanted to backup some data first (which I haven't done it like 8 months). I'm getting CHKDSK running every boot on a partition on my second hard disk. Kind of weird when there's nothing on it except the files winxp put there during partitioning... :)

Share this post


Link to post
Share on other sites

Had similiar problem late last night when I installed a refurb MB, trying to find out what the hell is going on.

 

My first though was HDD, without the drive connected received the same error.

I looked on the web and found something about over clocking.

 

At the time I did not think of it, I installed my old processor which is 1.1 ghz and the screen showed 1.4ghz.

 

I changed the clock speed from 133 to 100 and when I restarted the screen showed 1.1ghz which no problems.

 

Hope this helps.. ;)

 

Richard

Share this post


Link to post
Share on other sites
At the time I did not think of it, I installed my old processor which is 1.1 ghz and the screen showed 1.4ghz.

 

I changed the clock speed from 133 to 100 and when I restarted the screen showed 1.1ghz which no problems.

Yes, having the motherboard run at the same FSB speed that the processor is expecting is a good thing! ;)

Share this post


Link to post
Share on other sites

i hope this forum solve my problem, i have similar problem with trap 0000006 exception.

the problem is that i cannot even boot to my installation disk, it restart automatically

and the problem turns over and over again. please i need help.

Share this post


Link to post
Share on other sites

Hello

I stumbled accross this forum looking for the answer to this very same problem I had.

Yesterday I purchased this Barebone Kit - Gigabyte MA785GM-US2H Mobo, AMD Athlon 64 X2 6000+ CPU, Corsair 1024MB DDR2 RAM, WD Caviar Blue HD, Gigabyte GZPH2A30 Mid-Tower Case, Ultra LS500 500W PSU.

I assembled everything and slapped in my xp64Bit cd to which i thought i had the sata driver slipstreamed on the disk.

 

It turned out the driver was not slipstreamed and after a failed install i had the very same issue....Trap 00000006 Exception.

Its now 8 am and iv'e been working on this since 4 am this morning and is finally working.

 

This is what I did.

First i jumpered out the CMOS (look in the manual 4 how to) to reset to factory defaults.

Then i went and SET OPTOMIZED DEFAULTS within the BIOS and TADA! i temporarily installed a Floppy disk drive to incorporate the required SATA drivers for the MOBO.

 

It's all good now.

 

My first post :dance:

 

 

i hope this forum solve my problem, i have similar problem with trap 0000006 exception.

the problem is that i cannot even boot to my installation disk, it restart automatically

and the problem turns over and over again. please i need help.

Share this post


Link to post
Share on other sites

This is normally how to fix istall problems.

But as the previous poster also said,you CANNOT get to the point of a repair, it simply Cycles over and over and over and over.

 

My problem was doing a install without the required sATA driver and a incorrect MOBO setting.

During the text-mode phase of the setup process, Windows pauses briefly and prompts you to press F6. This option is displayed in the status line and lets you use an OEM mass storage controller driver. The F6 option is provided strictly as a means to install OEM drivers for mass storage controllers only. This is required to let the installation of the operating system continue. Microsoft does not support using F6 to install any device driver other than mass storage controller drivers.

 

You have to be quick on the trigger to press F6 to install the drivers. The pause is in fact brief.

 

 

 

found this on google.

 

 

THE BLACK SCREEN OF DEATH!

 

TRAP 00000006 ===================== EXCEPTION

================================

 

 

tr=0028 cr0=00000011 cr2=00000000 cr3=000000000

gdt limit=03FF base=00017000 idt limit=07FF base=00017400

 

cd:eip=0008:412AC1B7 ss:esp=0010:00061FEB errcode=0000

flags=00010013 Cy NoZr IntDis Down TrapDis

eax=023EE94A ebx=00401280 ecx=0000FE18 edx=534D0040 ds=0010 es=0010

edi=00461643 esi=00051D68 ebp=000609E8 cr0=00000011 fs=0030 gs=0000

 

I have not the faintest idea as to what all this means but I have a feeling

that the "Cy NoZr Int Did Down TrapDis" bit might be telling me that the

problem lies in the hard disk (though I'm probably talking through my

heatsink and fan!).

 

To solve the problem, take the following steps: -

 

Set the Bios to boot from CD-ROM

 

Place the XP CD-ROM in the drive.

 

Boot the PC and when prompted tell it to boot from the CD.

 

You are asked if you want to install Windows or go into Repair mode (Console

Mode) - choose the install option.

 

The procedure then detects that you already have Windows XP install and asks

you if you want a new installation or if you want to repair the existing

installation. Choose the latter option - REPAIR THE EXISTING INSTALLATION.

 

Then you just sit back for half-an-hour. You may get occasional prompts

regarding drivers for hardware installed or updated since the original

installation and if you have those drivers on the hard disk you can do them

at that point or later on as you prefer.

 

This will fix the installation but you will then need to apply any Service

Packs

and ensure that you are fully up-to-date via Windows Update.

 

The end result is a fully fixed installation that look and works exactly as

it did before.

 

During the process a reinstallation of Windows takes place although all the

installed applications and data seem properly to be registered afterwards

and nothing has been found to be missing.

 

This problem has now occurred to me several times on two different PCs so

the repair feature on the XP CD is worth its weight in gold.

 

I'm pretty convinced that, for whatever reason, the boot sector plus some

other stuff (that prevents FIXBOOT and.or FIXMBR from working) is being

trashed but, whatever the reason, this solution has worked every time.

Share this post


Link to post
Share on other sites

Hi,

 

Sorry for bumping up this old topic, but I've got the same problem except it's happening right after I try to boot the Windows XP install cd from the drive. I can't start my old windows installation because there is something wrong with it and it keeps restarting the computer.

 

Any idea?

 

Thanks

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×