Windows 7 stops at windows logo/'windows is starting' screen

December 12, 2018 at 02:23:26
Specs: Windows 10
A few weeks ago I first got an error message when booting up my computer stating that the CMOS battery may need replacing. This message disappeared for a while after I accepted the default bios settings.

More recently the message reappeared so I replaced the battery. After starting the machine the hardware was scanned but the machine failed to boot. All text on the scanning was in white apart from four comments in green beside my hard drives, of which I have four, stating non-raid disk for each. The text scrolled on to state that all four hard disks were controlled by the RAID BIOS. It also said AHCI BIOS was installed. The final thing to occur was a beep with accompanied blue highlighted text stating F1: Boot.

After much deliberation (as I have a significant amount of data on the drives which I need to access) I pressed F1 to boot the machine. this appeared to run okay but then seized up on the windows starting/windows logo screen. I am now in a position of uncertainty.

My HP Z800 workstation specification is as follows:
Intel Xeon Quad Core Processers
NVidia Quadro 6000 video card
96GB RAM
1 x Hitachi 2TB HDD - c-drive
2 x WD 4TB HDD mirrored (RAID)
1 x WD 4TB HDD

I have removed my c-drive and been able to copy data to another drive using a caddy and USB connection, but the WD 4TB drives are not identified by my laptop using the same method.

Obviously I'd like to get my workstation working again, but a must is without compromising my data on the other drives. At a bare minimum I need to access my data. Please can anybody offer some advice on this matter? I'm more of an IT user than technician.

Many thanks in advance.

message edited by m7281


See More: Windows 7 stops at windows logo/windows is starting screen

Reply ↓  Report •

#1
December 12, 2018 at 02:28:46
have you tried booting into safe mode? there should be an option for that in the bios

i5-6600K[delid]@4.7GHz/4.2GHz@1.408v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2666MHz@1.35v | MSI Armor RX 570 4GB@1415Mhz core@1.2v/1920MHz


Reply ↓  Report •

#2
December 12, 2018 at 02:49:19
Thanks for the reply. I've not been given a choice to do that.

The only things I can do during the stages when text appear are:
CTRL+S to configure device
CTRL+I to enter configuration utility
F1: Boot


Reply ↓  Report •

#3
December 12, 2018 at 02:54:12
Weird, there should be an F10 option according to Hp:
https://support.hp.com/rs-en/docume...

i5-6600K[delid]@4.7GHz/4.2GHz@1.408v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2666MHz@1.35v | MSI Armor RX 570 4GB@1415Mhz core@1.2v/1920MHz


Reply ↓  Report •

Related Solutions

#4
December 12, 2018 at 20:40:37
After replacing the CMOS battery you would first need to enter the BIOS set up and reset it to defaults save and exit and then go back into the BIOS and manually set everything properly. This includes time, date, CPU, RAM, SATA/RAID, Primary Graphics, bootable drives, boot order, and more.

Since your drives were set up in a RAID array then you are going to have to reset it the same way for them to be detected properly. If an IT technician set up your workstation and you are not familiar with the exact set up, you may need them back to reset it for you. I am not very experienced with RAID but others may pop by to expand on this if needed.

You have to be a little bit crazy to keep you from going insane.


Reply ↓  Report •

#5
December 13, 2018 at 03:46:01
Thanks for the reply Fingers. I've not had a chance to try starting the machine since your or hidde663's responses. Hopefully I'll get a chance this evening to see if an F10 option appears.

I setup my workstation myself after buying it from my old employer. Windows was pre-loaded and the drives all within their spaces in the case.

At setup I ran the Intel iata_enu driver so windows could see all 4TB of the WD drives. All I did for the RAID setup was within windows, setting two of the drives to mirror each other:
https://www.howtogeek.com/howto/179...

If it's of any help there is a line in the startup text which states:
Intel(R) Matrix Storage Manager option ROM v8.6.0.1007 ICH10R/D0 wRAID5


Reply ↓  Report •

#6
December 13, 2018 at 08:19:26
I wonder if drives that are not set up as RAID should be plugged
into the RAID connectors, or if they need to be plugged into the
non-RAID connectors. Especially the drive with Windows.

-- Jeff, in Minneapolis


Reply ↓  Report •

#7
December 13, 2018 at 20:29:36
Your SATA ports need to be set up as RAID for the ones that have been set up that way before and not RAID for those that are not. This was probably set up this way prior as a work station so you will need to reset these in the BIOS set up as well as making sure all else is optimized.

You have to be a little bit crazy to keep you from going insane.


Reply ↓  Report •

#8
December 14, 2018 at 21:13:17
For safety, I would take out the mirror drive(s). If for some reason the setup does not recognize the current RAID setup it could starting (auto or manual) to format the drives with a new RAID setup.

To get to Safe Mode boot, try the following:
When you see the win 10 logo appear, reset the PC immediately with reset button or power off.
On the next boot repeat until you get the windows boot menu. Select safe boot from there.

Is the machine loaded with an Enterprise Windows version?


Reply ↓  Report •

#9
December 15, 2018 at 06:16:10
Just to clarify, you would take out the large WD drives and then try to boot in safe mode before replacing if all boots up okay?

The workstation is running Windows 7.


Reply ↓  Report •

#10
December 15, 2018 at 21:58:52
With mirror drives I mean one of the 2 drives in RAID.
But you could disconnect all peripherals not needed to boot and try to get windows going.

Reply ↓  Report •

#11
December 16, 2018 at 15:30:33
Safest is to disconnect all drives except the one with Windows,
and plug that drive into a non-RAID port on the motherboard.
When Windows is working without problems, then add the other
dirves, first any non-RAID drives, then the RAID array if you
want one.

-- Jeff, in Minneapolis


Reply ↓  Report •

#12
January 11, 2019 at 04:27:14
Hi all.

I've finally committed some time to look into my problem. I took the advice and removed all of the large WD drives (two mirrored and one not - all dynamic discs), and tried to boot windows.

At first it went smoothly, opening the login screen and I manged to get into windows. It seemed stable for about a minute when I opened the device manager to see what was detected. Please note I did not click on any option other than viewing properties. My screens then started to pixelate and the system closed down, with the fans continuing to run on the workstation tower.

Upon trying to start up again I heard a series of beeps and the primary screen displayed a dancing psychedelic mix of colours. The next time I tried starting up I could hear four rapid beeps. After looking at the HP support website this translates to "Flashing failed (checksum error, corrupted image etc.)".

Is anyone able to advise what next steps I should take. I'm really hoping that if I can get windows starting and stable, the Intel raid controller would detect the drives when I later plug them in.

Many thanks in anticipation.


Reply ↓  Report •

#13
January 11, 2019 at 14:31:17
Try unplugging all drives including Windows drive. Boot into BIOS set up and look around for a while navigating to different parts. If it crashes then it is certainly hardware related. Look at the temps and the voltages and make sure they all make sense, The temps need to be 20C to maybe 50C at idle (though 50C is high for idle it certainly will run) and the primary voltages (12V, 5V, 3.3V) all need to be within 5% of their nominal values. If they are not then we need to investigate these. Voltages outside of the 5% limit will mean you will need to replace the power supply with a new and better one. High temps need to be dealt with right away.
If it does not have any issues in BIOS after a while and the temps and voltages are stable then run Memtest86 via a bootable CD or flash drive and boot to it. Let it run all of its tests at least once through. No errors are acceptable in memory. replace in matched pairs as necessary. One thing you can do is to clean the contacts on the memory with a clean, soft pencil eraser, wipe clean and then pop them into and out of the sockets 4 or 5 times to burnish the sockets as well. Retest with Memtest86 to see if it helped.
If the memory also tests good then you will need to boot it to a Live Linux Disk (CD, DVD, or Flash Drive) and run it off the memory only with no drives present. If it works then shut down and install a data drive only and reboot to Linux and see if you can mount the disk and access the files. If you can do this then it is more likely your Windows installation or disk itself.
Report back with results for more suggestions.

You have to be a little bit crazy to keep you from going insane.


Reply ↓  Report •

#14
January 13, 2019 at 16:40:50
It sounds like overheating or some modules on the motherboard become unstable.
If you have the ability, check the power voltages are OK. Is the CPU cooler (still) properly mounted?
Otherwise I'm afraid you have a major motherboard or CPU breakdown.

From experience, I had a motherboard where one of the large chips became very hot and created the same behavior as you described; if cold it started up and after a minute shut off. it could not be started again until the system cooled off completely


Reply ↓  Report •

Ask Question