Startup Problem

L

Laen

My Dell Dimension 9150 running Win XP will not Boot Up?

The Windows XP logo appears on screen, but hangs there for sometime before a Blue screen appears with message " problem detected and windows has been shutdown to prevent damage to PC" and screen freezes with this message.

I have tried to boot up in Safe Mode, but get no response!

I have reformatted hard drive and reinstalled Win XP and SP3 and a few drivers and this seemed to cure problem and installed some software but after a few days when switched on my PC reproduced all the the symptoms of previous problem??

What is my problem?,can you help?
 
I can't download any files let alone unzip if my PC is crashed and I can only get a blue screen?!

I could download and unzip on another PC but then I still have the problem of getting it onto my blue screen PC.....windows does not boot either normally or safe mode!
 
Stop code. 0x00000001 (0x00000018,0x00000002,0x00000000,0xBA66B261)

1 aster.sys Address BA66B261 bSe BA6SC000 DateStamp 426d0c8c

NB. The B preceding 261 maybe another letter or No.?

Does this help?
 
DRIVER_IRQL_NOT_LESS_OR_EQUAL

do you have sata drives??

see the two links below:

http://www.dell.com/support/article/us/en/19/SLN130053/EN

http://www.dell.com/support/article/us/en/19/SLN86272/en?c=us&s=dhs&cs=19&l=en

"iastor.sys" is the driver for SATA and/or RAID.
Click to expand...

from here

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

you might be able to get into bios and change the drive to achi ide vs sata.

is there any data on the drive??

if not then I suggest that you get your sata drivers, compatible with xp, and slipstream them into your install disk with nlite. as xp cannot be installed on sata drives without controllers.
 
Thank you, ..very interesting.I only have one HD and that is a SATA drive, where my XP OS must have been.
I will study you link info and see what I am able to do.
 
I have previously successfully installed XP, therefore controllers must be present.....However after installing the situation of blue screen returns after a few days?
 
Usually a driver shouldn't crash by itself. You can never completely exclude this, but the driver should be tested good enough for this.
Either it crashes because the hardware doesn't work as it should (because it's broken)
OR there are two drivers shooting each other down (e.g. one is badly written and reads the ram reserved by another one and windows says "fu" and turns off with a bluescreen).
BSView (suggested by Elizabeth) could give you the information about the second driver.
If you cannot execute bsview on your own system, you could try to trnasfer the memorydumps to another one. They are usually stored in "C:\WINDOWS\Minidump\*.dmp". (As far as I know BSView can only analyze minidumps, not total dumps stored in "C:\WINDOWS\MEMORY.DMP" (only the latest dump).)

If it's really iastor.sys and that's really the sata controller driver, then disabling it and enabling ide-simulation (turning off AHCI) could really avoid the problem. But if it's another driver shooting down your iastor.sys, then maybe your "poor" driver will just shoot down the next driver using thess ram adresses.

The case that it needs a few days after re-install makes me think of a driver shipped by an update?

What do you mean with "I have tried to boot up in Safe Mode, but get no response!"?
Don't you manage to get to the safe mode selection? Does it freeze during safe mode boot?
 
I am able to obtain the safe mode option screen, but when I select safe mode I get a full screen list of single line comment (maybe error messages) about a whole load of drivers!?
 
sm5.jpg


safe mode starts with this and goes on to load, this page is usually up for approx 1 or 2 minutes

http://pcsupport.about.com/od/fixtheproblem/ss/safemodexp.htm

steps to get to safe mode, with pictures at above website. :)
 
Last edited:
reply no. 2:

what is the drive listed as in the BIOS??

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

courtesy of Jose Ibarra:

Make a note of what the current settings are before making any changes so you can change them back if things get worse.

After you make the changes, save them and see how things look now.

If you find the mode is set to RAID/SATA mode, change the mode to IDE.

If you find the mode is set to SATA, change the mode to IDE.

If you find the mode is set to SATA, disable SATA mode.

If you find the mode is set to AHCI, change the mode to ATA.

If you find the mode is set to AHCI Emulation Mode, change the mode to IDE Emulation.

If you find the mode is set to SATA, disable SATA mode and/or change the mode to ATA.

If you find the mode is set to SATA Native Mode, disable SATA Native Mode.

If you find the mode is set to RAID/Autodetect AHCI, change the mode to Combination.

If you find the mode is set to RAID Auto/AHCI, change it to RAID Auto/ATA

The WWW says this works on some Dells: "I had to set my SATA Operation to ATA instead of AHCI"

After making the adjustments, ACCEPT and SAVE the changes, and restart the system and see if it will now boot on the Recovery Console CD.

Here are some additional ideas about changing the BIOS to recognize the SATA drive to boot from CD:

http://www.mydigitallife.info/commo...install-unable-to-detect-sata-harddisk-drive/
 
reply no 3: as an assist to Rhino's post:

How To Find Drivers For An Unrecognized Device

1. Open Device Manager (Control Panel>System>Hardware>Device Manager)
2. The hardware whose drivers are missing will appear as Unknown device, so it's easier to locate the device.
3. Right click on the unknown device and click on Properties.
4. Under the Properties window click on Details tab and select Device Instance Id from the drop down box.
5. You should see a code similar to this

PCI\VEN_8086&DEV_27DC&SUBSYS_30868086
&REV_01\4&1E46F438&0&40F0

6. The portion of the code highlighted in RED is the Vendor ID and the portion highlighted in GREEN is the Device ID. In this example:

Vendor ID = 8086
Device ID = 27DC

7. Once you have obtained both the IDs, proceed to PCI Database. There you can either search for the vendor from the vendor ID or directly get information about the device along with the vendor name by searching with the device ID.

8. Then from there you can go directly to the hardware manufactureres website and get the driver.
 
You must log in or register to reply here.
Back
Top