exception error on boot

[Seifer]

Whenever I boot up my computer, right when windows is supposed to boot, I get an error message with white text on a black screen that says "EXCEPTION" and a bunch of other gibberish. I've installed Windows XP Pro, XP Pro SP1, 2000 Advanced Server, and 98SE. This happens to ALL of them. Now the weird thing is that it only does this when the computer has been off for a while, like more than 30 min. If I leave it running for about 3 min. and then boot windows, it will boot and the computer will work perfectly. So I don't know if it's a problem with windows, or a piece of my hardware, but it only seems to boot if the computer has been on and "warmed up" so to speak.

Specs:
Soyo KT333 Dragon Plus Mobo
256MB Kingston DDR PC2700
Maxtor 40GB ata/133 7200 rpm HDD
Athlon XP 1800
SB Audigy
Radeon 7000

 

[Nodsu]

That "exception" part is a very general decription and that bunch of other gibberish might actually be useful information.

This problem being time-related, I suggest you double-check the power management options in BIOS

 

[DigitAlex]

yeah very weird ...

I have same kind of "warming" thing with my monitor. When I turn it on, the 10 bottom most pixels are too low to be seen, in fact all the picture is 10 pixels lower than normal.
However 2/3 minutes later when the monitor has warmed up, the picture reaches its normal centered position ...
As if the vertical magnetic fields deviating the electrons were not at full power instantly ....

 

[Seifer]

I'll check the power management settings, and then copy down the error if it happens again and come back tomarrow.

Edit: so what options should I change in power managment?

 

[Justin]

Problems that "go away" after the machine has been on for X amount of time are often heat related issues. It is possible not all the contacts on one of your parts is firmly connected... and may be too weak to properly function - But after heating up for a few minutes the metal expands and makes a proper connection.

I would re-seat your RAM and video card, and then unplug and firmly replug all your components in.

 

[Seifer]

Well, I've come here because I've already tried it all. I've dissassembled the whole box and put it back together. Everything is secure in its place. I'm about to start buying new parts and swapping them until I find the problem.

 

[Mictlantecuhtli]

Originally posted by Seifer
I get an error message with white text on a black screen that says "EXCEPTION" and a bunch of other gibberish.

Could you post the "gibberish" here, please?

 

[Seifer]

Sure here ya go "smart computer guy"

TRAP 00000002 ======= EXCEPTION ===== tr=0028 cr0=800000011 cr2=000000000 cr3=00039000 gdt limit=03FF base= 0003F000 idt limit= 07FF base= 0003f400 cs: eip=0008:00406AD3 ss: esp=0010:0005FB28 errcode = 0000 flags=0000000016 NoCy NoZr IntDis Down TrapDis eax=00008000 ebx=00008000 ecx00000F3E ds=0010 es0010 edi=80B8E308 esi=00484308 ebp=0005FB44 cr0=80000011 fs=0030 gs=0000

 

[Tarkus]

Here's something I found....

The following is the actual message that is appearing on the Screen which is a back screen
as opposed to the usual dump screen which is blue


TRAP 00000002 ========= exception====

Er= 0028 cr0 = 80000011 cr2 = 00000000 cr3 = 00030000
gdt limit = 03FF base = 00036000 idt limit = 07FF
base= 0036400

cs:eip 0008 : 0031296e ss:esp = 0010:00060930
errcode= 0000
flags = 00010006 NoCy NoZr IntDis Down TrapDis

eax = 0004C000 ebx = 00000000 ecx = 00000578
edx = 00000000 ds = 0010 es = 0010

edi = 801F0E20 esi = 004AA20 ebp = 000609B8
cr0 = 000609B8 fs = 0030 gs = 0000



After trying out all things i finally went for a
fresh install but after installing a fresh copy the problem still continued. so obviously the problem
was with the hardware . i disabled ecc memory check in the setup and found that theerror stopped so now i have concluded that the problem was with the physical memory and going for a replacement .

 

[Mictlantecuhtli]

I found similar answers - trap 00000002 indicates errors in physical memory. It's possible that the memory module is somehow damaged so that after warming up a bit, thermal expansion makes it work again. I'd test the computer with different memory modules.

 

[Arkimedes00]

I had almost exact same issue

I had almost exactly the same issue with the trap 00000002 ========exception========= error. I scoped out the MS KB, and found that the problem is similar to problems with the NTLDR. I formatted my HD but to no avail, finally after swapping out my memory, I found that the problem was actually with the processor, after replacing it to a 2500 AMD Athlon XP, I havent had a problem with the system yet. I hope this helps.

-Ark

ps. I have the same MOBO too

 

[Mondo1287]

I've been dealing with this problem for over a year with a Soyo kt400 board running XP pro. I rarely reboot so its not a huge problem and I never could determine what was causing it. That machine has since been retired and I recently started using that board for some other things and started noticing strange boot errors from other operating systems. The problem definitly is because of the onboard highpoint hpt372 controller bios. None of the Soyo bios images have the updated hpt372 bios so you have to manually make your own bios image using cbrom. If you're not using the highpoint controller you should be able to just disable it in the bios and you'll be fine. If you are using it, download cbrom here

If you're using a differen't soyo board that uses the hpt372 controller this will still work just use the right soyo bios image for your board.

http://www.stormpages.com/crazyape/cbrom207.zip
(There are newer version but you need to use 2.07)

Get the release 9 bios from soyo (kvx42aa9.bin).

Get the 2.31 hpt372 drivers here http://www.biosmods.com/download/hpt/370raid_2.31.zip

The driver file contains a bios directory with a file bios372.231

Put cbrom.exe, bios372.231, and kvx42aa9.bin in the same directory and open a command prompt. Get to that directory and then run:

cbrom kvx42aa9.bin /pci bios372.231

Now flash the bios image and update your hpt372 windows drivers using the ones you downloaded.