|
|
|
Problems Starting Up Windows
Showing all messages in thread #1167072057 Windows XP Annoyances Discussion Forum
The following are all of the messages in this thread (6 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
|
Problems Starting Up Windows
Monday, December 25, 2006 at 10:40 am Posted by D. Jones
(4 messages posted)
when i turn on my computer it goes through the normal set up checking drives and
just before the windows startup screen shows up i get a black screen that says:
trap00000002 exception
tr=0028 cr0=80000011 cr2=00000000 cr3= 00039000 gdt limit=03ff base=0003f000
idt limit=07ff base=0003f400
cs:eip=0008:00407283 ss:esp=0010:0005f85c
errcode=0000 flags=00000016 nocy nozr intdis down trapdis eax=00008000 ebx=00008000
ecx=00001f3d edx=004480000 ds=0010 es=0010 edi=80e7b30c esi=0048030c ebp=0005f878
cr0=80000011 fs=0030 gs=0000
I have been workin with computers for a while and i have never seen an error like
this before. Could someone please help me with this matter
Thanks,
D. Jones
[Reply or follow-up to this message]
| |
re: Problems Starting Up Windows
Monday, December 25, 2006 at 11:13 am Posted by Blue
(115 messages posted)
Trap" is an assembly instruction. It probably means that sometime when your OS was
starting up, something went terribly terribly wrong (ie, something that Windows wasn't
designed to handle) and now the OS doesn't know what to do. So it does the only thing
it can do...it fails and displays a lot of vital things like CPU registers, CPU flags,
etc... This is the garbage that you're seeing below the Trap Exception. As for
fixing this, I'm afraid there's not a lot that can be done. The debugging symbols
might be of use to someone who's working on the Windows OS itself and trying to debug
a problem like this, but from an end user point of view there's not a whole lot you
can do other than reinstall. If you have data you need to back up from the windows
partition, you can boot your computer with a Linux LiveCD and access your files that
way (email them to yourself? Upload them to some sort of other storage facility?).
http://support.microsoft.com/kb/150314
[Reply or follow-up to this message]
|
re: Problems Starting Up Windows
Monday, December 25, 2006 at 11:19 am Posted by Rich Kurtz
(12246 messages posted)
This is almost always caused by defective memory (RAM). Memory will fail between
power cycles. No rhyme or reason, just happens.
Open your computer and see what kind of memory is installed. If there are two sticks
of ram, remove one and see if you can boot. If you get the same error, put it back
and remove the other then boot again. Replace the defective one.
Be very careful when working inside the case. Always touch bare metal to discharge
any static electricity before doing anythin in there.
If there is only one stick of memory, download and run memtest86 for a couple
hours (or more), see if it finds any memory errors. Usually avialable as a diskette
image of a bootable CD image.
http://www.memtest86.com/
[Reply or follow-up to this message]
|
re: Problems Starting Up Windows
Thursday, December 28, 2006 at 9:27 pm Posted by D. Jones
(4 messages posted)
I've removed my hard drive from the computer and attached it to another computer,
so that I can salvage the saved files i needed, when I put the drive back into the
computer and i try to boot it up i get a blank screen the monitor is workin fine
but nothin comes on the screen but the monitor testing.
thanks for all your help
On Monday, December 25, 2006 at 11:13 am, Blue wrote:
>Trap" is an assembly instruction. It probably means that sometime when your OS was
>starting up, something went terribly terribly wrong (ie, something that Windows
wasn't
>designed to handle) and now the OS doesn't know what to do. So it does the only
thing
>it can do...it fails and displays a lot of vital things like CPU registers, CPU
flags,
>etc... This is the garbage that you're seeing below the Trap Exception. As for
>fixing this, I'm afraid there's not a lot that can be done. The debugging symbols
>might be of use to someone who's working on the Windows OS itself and trying to
debug
>a problem like this, but from an end user point of view there's not a whole lot
you
>can do other than reinstall. If you have data you need to back up from the windows
>partition, you can boot your computer with a Linux LiveCD and access your files
that
>way (email them to yourself? Upload them to some sort of other storage facility?).
>
>
>
>
>
>http://support.microsoft.com/kb/150314
[Reply or follow-up to this message]
|
re: Problems Starting Up Windows
Thursday, December 28, 2006 at 9:32 pm Posted by D. Jones
(4 messages posted)
I have tried the memory swapping thing out and the computer is still doing the same
thing plus now when you boot up the computer the screen only shows the monitor testing
and nothing else. I have been lookin at it since earlier this week and every now
and then the screen will come on with no problem but the majority of the time it
will just do the monitor testing thing. Thanks for all your help
On Monday, December 25, 2006 at 11:19 am, Rich Kurtz wrote:
>This is almost always caused by defective memory (RAM). Memory will fail between
>power cycles. No rhyme or reason, just happens.
>
>Open your computer and see what kind of memory is installed. If there are two sticks
>of ram, remove one and see if you can boot. If you get the same error, put it back
>and remove the other then boot again. Replace the defective one.
>
Be very careful when working inside the case. Always touch bare metal to discharge
>any static electricity before doing anythin in there.
> If there is only one stick of memory, download and run memtest86 for a couple
>hours (or more), see if it finds any memory errors. Usually avialable as a diskette
>image of a bootable CD image.
>
>http://www.memtest86.com/
[Reply or follow-up to this message]
|
re: Problems Starting Up Windows
Friday, December 29, 2006 at 5:30 am Posted by Rich Kurtz
(12246 messages posted)
Sounds like something is not connected right or is not firmly seated. Check everything
again, cables, cards, memory, CPU. Make sure they are all firmly plugged in.
[Reply or follow-up to this message]
| |
| |
Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
| |
Return to the Windows XP Discussion Forum
|
|
|
|