xp hangs in normal mode but not in safe mode

February 24, 2011 at 11:08:44
Specs: windows xp, intel pemtium mobile
I have change dmy laptop mainbord from china its a refubrished board but the seller has given me 45 days warranty, he says the board has been checked, xp setup hangs on 34% , i tried ghost image system it worked xp booted up but hanged again in 1 or 2 minutes , but it works fine in safe mode no problemss , is it a driver issue , hard disk issue , or mainboard problem?

See More: xp hangs in normal mode but not in safe mode

Report •


#1
February 24, 2011 at 13:57:52
You can't simply change motherboards out. Test with clean install of xp.

"The era of big government is over," said Clinton 1996


Report •

#2
February 24, 2011 at 14:32:06
When a computer is OK in safe mode but not normal mode it is very often a driver issue. If you didn't get all the XP drivers for the new board it will be trying to run on incorrect drivers.

You could try getting all the XP drivers to suit the new board but I agree that a clean install of XP is the best approach.

We all live on the same ball.


Report •

#3
February 24, 2011 at 20:45:51
Thanks for your reply , I have tried clean installtion of xp formatting the whole disk still same issue, how will i install drivers if the setup is freezing at 34 minutes left screen , can there be a problem with hard drive because thats the only thing i havent replaced yetotherwise i have tried all

Report •

Related Solutions

#4
February 24, 2011 at 21:20:13
"setup is freezing at 34 minutes left screen"

That indicates Windows is having problem detecting some hardware device properly.
It often then black screens eventually and restarts,running Setup from the beginning of the second stage again, it stalls at 3x minutes, black screens, over and over again.

Unplug everything you have plugged into the computer and try running Setup again.

If you don't have anything plugged when it does that....

Check your hard drive with the manufacturer's diagnostics.
See the latter part of response 1 in this:
http://www.computing.net/windows95/...

If you don't have a floppy drive, you can get a CD image diagnostic utility from most hard drive manufacturer's web sites, but obviously you would need to make a burned CD, preferably a CD-R for best compatibility, on another computer if you need to.

E.g.
Seagate's Seatools will test any brand of hard drive.
Do the long test.
http://www.seagate.com/ww/v/index.j...

The bootable Dos versions of SeaTools can be used even if Windows is not working properly.

If the hard drive itself tests okay, any data problems found can be fixed, one way or another

- if the hard drive itself tests okay, open up the laptop and check all connections of the mboard to other components


Report •

#5
February 24, 2011 at 22:33:28
I have checked already everything the disc is also ok by all diagnostics, there are no periphrals attached, i have removed the modem & wireles card also, i have tried swaping memory moduls ,I have changed dvd drive , how will i come to know on which device the setup is freezing ,i have checked the setuplog, setupapi.log, setupact.log how will i daignose the device which is malfunctioning

Report •

#6
February 24, 2011 at 23:37:26
" ....how will i daignose the device which is malfunctioning...."

I have no idea.

When this happens with a desktop computer the few times it has happened to me, removing all hardware not essential to running Setup has allowed Setup to complete successfully.
The only thing I have to suggest is as I said above -"....open up the laptop and check all connections of the mboard to other components".


Report •

#7
February 25, 2011 at 13:07:56
Sorry, I misread your post.

Yes, some issue with system. Driver or chipset driver or faulty ram or something.


Start with memtest. Then maybe get ultimate boot cd and use hard drive diags.

May have to slipstream to sp2 or sp3 and add in your motherboard's drivers. That may include everything that the OEM offers. Chipsets and nic's and sound may all have to be available at the install.

Be sure bios settings show disk's as what they should be. If larger than I think 137G you need SP2 in the xp disk.

Also set bios settings to failsafe or default. They may be too high or voltages wrong. Ram settings may be off too.

"The era of big government is over," said Clinton 1996


Report •

#8
February 26, 2011 at 06:31:47
there are no bios seeting in the laptop only video memory 64 & 128 thats all , I think so its the mianboard or some particular hardware i dont know.... how to find out the problem ? now i have changed the drive also but same problem , i tried xp sp3 but it hangs on installing network connection , internet is working fine by ethernet adapter in " safe mode networking" as as the laptop xp starts in normal mode within 2 minutes it freezes completely

Report •

#9
February 26, 2011 at 07:00:07
See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
http://www.computing.net/hardware/w...

For a laptop, or netbook, you must remove both its main battery and AC adapter before you do that.

For a brand name computer, see the Owner's or User's manual if you need to - how to remove or replace the ram is usually in that - it may already be in your installed programs. If you can't get into Windows, it may be on a disk that came with the computer, or you can go online and look at it or download it - it's in the downloads for your specific model.

Some ram manufacturer's modules do not strictly adhere to the JEDEC standards that most mboards bioses use to determine ram settings.
In that case, the ram settings in the bios Setup that the bios has automatically chosen may not be correct.
Check the ram settings in your bios - the ram voltage, and the ram timing numbers - those should be the same as for the specs for the modules themselves. Often the ram voltage and timing numbers are printed on the label on the modules.

If the voltage setting or timings settings in the bios are different from the specs for the ram, change them in the bios. The timing numbers must be as close as you can get to the same, or slower timings (higher numbers = slower) - you won't notice the difference the slower settings make.

If you have a mix of different modules
- don't mix ram that different voltages are specified for - the bios will force the ram to use the lowest voltage, if "by spd" or similar is used (default settings) - ram that a higher voltage is specified for is more likely to not work properly in that situation.
- the bios settings must be those for the slowest timing settings of all the modules, or slower (higher numbers = slower).

Test the ram

Microsoft's
Windows Memory Diagnostic:
http://oca.microsoft.com/en/windiag...

Windows Memory Diagnostic is limited to testing only the first 4 gigabytes (GB) of RAM.

It can be toggled (press T) to do a standard or a more comprehensive set of tests - use the default 6 test one first - if it passes one pass of that, use the latter one. A few of the tests in the latter set are intentionally slower.
If you don't have a floppy drive, see the Quick Start Information at that Microsoft link for how to make a bootable CD of the Windows Memory Diagnostic (you need Windiag.iso - you don't necessarily need to use the program they mention to add it to the CD).
............

Start - Run - type : cmd

Type: CHKDSK /F C:

Answer Yes to any questions

Restart the computer normally and let CHKDSK run.




Report •

#10
February 26, 2011 at 10:00:32
The memory modules which I am using have come with laptop itself both are identical and they worked fine on previous board Laptop is HP DV 4000 i.e 4307cl model I have replace mainboard because previous mainboard was dead , The board is working very fine in safe mode but not in normal .Setup hangs on 34 minutes , can processor be a problem because thats what i havent changed?

Report •

#11
February 26, 2011 at 11:09:53
It's possible that whatever killed your motherboard did some harm to the processor. If, for example, the damage was caused by a heat problem, the processor could well have sustained damage.

Please let us know if you found someone's advice to be helpful.


Report •

#12
February 26, 2011 at 11:25:41
"I have replace mainboard because previous mainboard was dead "

Motherboards DO NOT spontaneously go dead, unless they have been damaged by an external event, or unless some of the electrolytic capacitors on the mboard have failed.

HOW did the mboard get damaged if that applies?

Did someone drop the laptop or spill liquid on it?

Was it exposed to a power failure event while the AC adapter was plugged in ?

Some mboards develop this problem - electrolytic capacitors were installed on them that were not properly made, and they fail eventually - the mboard manufacturer didn't know they were improperly made at the time the mboard was made.

Open up your case and examine the mboard to see if you have bad capacitors, and/or other findable signs of mboard damage .

This was the original bad capacitor problem - has some example pictures.
History of why the exploding capacitors and which mboard makers were affected:
http://members.datafast.net.au/~dft...

What to look for, mboard symptoms, example pictures:
http://www.badcaps.net/pages.php?vid=5
Home page that site
- what the problem is caused by
- he says there are STILL bad capacitors on more recent mboards.
http://www.badcaps.net/

Pictures of blown capacitors, other components, power supplies, fried Athlon cpus, etc.:
http://www.halfdone.com/Personal/Jo...
...............

Did you wipe off and re-seat the ram ?

Dis you check the ram settings in the bios ?

Did you run ram diagnostics ?

Did you run CHKDSK /F C: ?

There may be a problem with something on the Windows installation that is trying to load when you boot normally that is not loaded when you boot into Safe mode. Running CHKDSK /F C:may fix that.
I don't know if CHKDSK will run before Windows loads when you boot into Safe mode - I don't recall ever trying that.

As far as I know, the fact that Setup stalls during the second stage at 3x minutes left can ONLY indicate you have a problem with Windows detecting hardware.

It's extremely unlikely that has anything to do with the cpu. Is it the same cpu that was used in the other mboard or did it come with the mboard or what ?

You could try booting and pressing F8 and selecting Enable boot logging which will attempt to boot Windows normally and make a log file of what loads while booting and you can examine that file for problems in Safe mode, but in my experience the log file often fails to be made.

You could try booting and pressing F8 and selecting Enable VGA mode - that loads Windows completely normally except it uses the same default VGA video drivers that Safe mode does. If that works fine,it's probably the video adapter on the mboard that is the hardware problem.


Report •

#13
February 26, 2011 at 14:27:58
Have you looked in Device Manager to see if any errors are showing?

Are the vents and CPU heat sinks clean?

We all live on the same ball.


Report •

#14
February 26, 2011 at 21:12:02
The orignal mainbaord had chipset failure problem , i had to repalce it , i tried cleaning ram, i have done chkdsk , , i have tried all other modes in safe mode like vga mose, debugging mode, last known good configuration, it only works fine in Safe mode & safe mode networking , the cpu is the orignal one it didnt come with new mainbaord , i have tried disabling all hardwares in safe bode and boot in normal but still the same problem, I tried to boot with diagnostic startup in msconfig but no changes , It freexez within a minute after it starts in normal, shall I order anew mainbaord from other merchant , thats the only solution left

Report •

#15
February 27, 2011 at 07:28:38
Re my #13. All OK in Device Manager then?

We all live on the same ball.


Report •

#16
February 27, 2011 at 10:58:45
You have NOT answered all of our questions.

Please answer the ones you have not answered !

Without that missing feedback, the only additional thing I have to say is
send the mboard you bought back to the seller and get another one !

However, there may be something else wrong with something inside the laptop.


Report •


Ask Question