When i turn on my PC, I am asked to choose from options such as safe mode,
last known settings that worked, start windows normally, etc. However when i
choose ANY of these options, as the XP splash screen appears, a blue STOP
screen flashes up quickly, before the system reboots. I have tired numerous
things:
- loaded failsafe / optimised bios settings
- used the hard disk in another computer (booted perfectly)
- checked all conections in the pc
- tried booting from xp install cd to repair but still reboots
Any ideas?
Thanks

ben <(E-Mail Removed)> wrote:

>When i turn on my PC, I am asked to choose from options such as safe mode,
>last known settings that worked, start windows normally, etc. However when i
>choose ANY of these options, as the XP splash screen appears, a blue STOP
>screen flashes up quickly, before the system reboots. I have tired numerous
>things:
>- loaded failsafe / optimised bios settings
>- used the hard disk in another computer (booted perfectly)
>- checked all conections in the pc
>- tried booting from xp install cd to repair but still reboots
>Any ideas?
>Thanks

Suspect a hardware fault in the computer.

When you tried the drive in another computer were you able to boot all
the way to the desktop? If you can do so, even in Safe Mode, then you
can check out the cause of the boot failures. Right-click on "My
Computer" and select Manage. Expand the Event Viewer category to show
all 3 subcategories and then browse through each of them looking for
red-flagged error records that correspond to the date and time of your
failed startups.

Also open Control Panel - System - Advanced and click on the Settings
button in the Startup and Recovery (bottom) section. In the Startup
and Recovery window click on the checkbox for "automatically restart"
to clear it then click on Apply and OK as needed to exit. Shut down
the computer and return the hard drive to the original machine. Now
when you start it up the BSOD should remain on the screen and you can
see the complete error message.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

> Suspect a hardware fault in the computer.
>
> When you tried the drive in another computer were you able to boot all
> the way to the desktop? If you can do so, even in Safe Mode, then you
> can check out the cause of the boot failures. Right-click on "My
> Computer" and select Manage. Expand the Event Viewer category to show
> all 3 subcategories and then browse through each of them looking for
> red-flagged error records that correspond to the date and time of your
> failed startups.
>
> Also open Control Panel - System - Advanced and click on the Settings
> button in the Startup and Recovery (bottom) section. In the Startup
> and Recovery window click on the checkbox for "automatically restart"
> to clear it then click on Apply and OK as needed to exit. Shut down
> the computer and return the hard drive to the original machine. Now
> when you start it up the BSOD should remain on the screen and you can
> see the complete error message.
>
> Good luck
>
>
> Ron Martell Duncan B.C. Canada
> --
> Microsoft MVP
> On-Line Help Computer Service
> http://onlinehelp.bc.ca
>
> "The reason computer chips are so small is computers don't eat much."
>

Hi. Thanks for the advice. The windows event log did not pick up of the
crashes at all. I stopped the automatic restarts and now can read the blue
screen. It is:

IRQL_NOT_LESS_OR_EQUAL
and
"*** STOP: 0x0000000A (0x00000020 0x00000020, 0x00000000, 0x804FB38A)

I have recently installed a wireless PCI card, but i remeoved it as soon as
the crashes began. Also, the fact that the hard disk boots in a machine with
the same PCI card suggests to me that it is harmless?
Thanks in advance.

Merry Christmas!
Ben

ben <(E-Mail Removed)> wrote:

>
>Hi. Thanks for the advice. The windows event log did not pick up of the
>crashes at all. I stopped the automatic restarts and now can read the blue
>screen. It is:
>
>IRQL_NOT_LESS_OR_EQUAL
>and
>"*** STOP: 0x0000000A (0x00000020 0x00000020, 0x00000000, 0x804FB38A)
>
>I have recently installed a wireless PCI card, but i remeoved it as soon as
>the crashes began. Also, the fact that the hard disk boots in a machine with
>the same PCI card suggests to me that it is harmless?
>Thanks in advance.
>
>Merry Christmas!
>Ben

Go to MVP Jim Eshelman's STOP errors web page at
http://www.aumha.org/win5/kbestop.htm and click on the "0A: IRQL Not
Less/Equal" link in the left side column.

Good luck



Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

Thanks, the link has given me some pointers and things to try . . .one
problem is that when i choose safe mode with command promt, i get another
blue screen. I can even get into command promt.

Just to clarify:

BOOT WINDOWS-> 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

SAFE MODE -> 0x00000024
WITH COMMAND
PROMPT

I have disabled everything I can in the BIOS settings. In terms of hardware,
I have my motherboard (with onbhoard sound and video), CD drive, hard disk.
That is all. I recently installed a wireless PCI card, which I removed as
soon as the problem began. I built the machine myself, and it has been
working fine until a week ater installing the wireless PCI card. I cannot
start windows, and cannot get into command promt. All solutions i have found
so far require me to be in windows or dos, so I am realy stuck.

Thanks in advance.

This most definitely looks like bad or flakey RAM.

RAM can go bad, and there can be a discrepancy between the SPD timings and
the timings set in your BIOS that can cause these errors.

Might be worth checking into.

Bobby

"ben" <(E-Mail Removed)> wrote in message
news:2A9A7FBC-5B7F-4FD5-995C-(E-Mail Removed)...
> Just to clarify:
>
> BOOT WINDOWS-> 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
>
> SAFE MODE -> 0x00000024
> WITH COMMAND
> PROMPT
>
> I have disabled everything I can in the BIOS settings. In terms of
> hardware,
> I have my motherboard (with onbhoard sound and video), CD drive, hard
> disk.
> That is all. I recently installed a wireless PCI card, which I removed as
> soon as the problem began. I built the machine myself, and it has been
> working fine until a week ater installing the wireless PCI card. I cannot
> start windows, and cannot get into command promt. All solutions i have
> found
> so far require me to be in windows or dos, so I am realy stuck.
>
> Thanks in advance.

Listen people, get memtest86 from the net. I think this is the link (good
old google!!)

http://www.memtest86.com/

This willl prove for certain if your memory is faulty(or near enough as the
program needs to go somewhere)

cheers


"NoNoBadDog!" <mypants_bjsledgeATpixi.com> wrote in message
news:(E-Mail Removed)...
> This most definitely looks like bad or flakey RAM.
>
> RAM can go bad, and there can be a discrepancy between the SPD timings and
> the timings set in your BIOS that can cause these errors.
>
> Might be worth checking into.
>
> Bobby
>
> "ben" <(E-Mail Removed)> wrote in message
> news:2A9A7FBC-5B7F-4FD5-995C-(E-Mail Removed)...
>> Just to clarify:
>>
>> BOOT WINDOWS-> 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
>>
>> SAFE MODE -> 0x00000024
>> WITH COMMAND
>> PROMPT
>>
>> I have disabled everything I can in the BIOS settings. In terms of
>> hardware,
>> I have my motherboard (with onbhoard sound and video), CD drive, hard
>> disk.
>> That is all. I recently installed a wireless PCI card, which I removed as
>> soon as the problem began. I built the machine myself, and it has been
>> working fine until a week ater installing the wireless PCI card. I cannot
>> start windows, and cannot get into command promt. All solutions i have
>> found
>> so far require me to be in windows or dos, so I am realy stuck.
>>
>> Thanks in advance.
>
>