Author Topic: Having XP boot up problems with asus p4b533-vm (Read 462 times)

Kaz · « **on:** November 08, 2002, 03:53:44 AM »

posted this on dejanews' asus forum was wondering if anyone else had the same/similar problem.

Just got a new mobo/ram/cpu to upgrade my current system
p3 733mhz, tyan mobo, 256mb ram, gigabyte geforce 3, sb live value, WD caviar 20gb HD, win XP home(upgrade cd), 250w power supply.

here's what i got, asus p4b533-vm mobo, p4 1.5mhz w/heatsink/fan, 512mb ddr pc2700 ram.

Problem is that XP won't load with the new stuff installed, POST goes fine but as soon as XP is about to load i get the blue screen of death which flashes on very briefly before the pc reboots and then goes through this loop. :rollseyes:
Here's some of what i managed to get:

"A problem has been detected and Windows has been shut down to prevent damage to your computer. If this is the first time you've seen this stop error screen restart your computer. If this screen appears again, follow these steps: Check for viruses on your computer. Remove any newly installed......"

That's all i got, seems that other ppl had similar problems and were some were able to fix them by disabling the bios virus boot scan which i already tried.

My HD is partitioned i dunno if that could be the problem. Also, the manual recommends two connections from the power supply to the mobo, the one i have only has one

Any suggestions will be greatly appreciated

GRUNHERZ · « **Reply #1 on:** November 08, 2002, 05:58:42 AM »

Well I just built a new computer for the first time and faced some difficulties.

Definitely buy a new PS, at least a good 350 watt from somebody like Antec or Enermax, I'm using one by Sparkle and it seems good too - you should have this power anyway regardless if it's causing the problem. And I certainly think you should use the AUX power plug to the MB, a new PS should have both styles of AUX power connections.

My main problem was bad cheap generic (OCZ) RAM which presented similar OS loading problems. Get good name brand RAM and buy it from a local place with a return policy for memory so you can get your money back if it doesnt solve the problem.

I'm far far far far from an expert on this but I hope it gets the ball rolling on this thread.

214thCavalier · « **Reply #2 on:** November 08, 2002, 04:41:01 PM »

Suffered similar problems preventing me loading XP.
Rest of the message for me was about virus checking or removing any newly installed hard drives etc, basically it cant read you hard drive for whatever reason.
In my case it was having a MB with a highpoint raid controller onboard, problem was because the driver file with the XP installation is now outdated and does not support the functions of the newer hardware, because of this XP kicks it into touch and refuses to continue setup.
Now i have always previously run my single HD on the raids controller to get UDMA 133 access.
The links below explain what is very likely happening to you.
There are various ways around it but in my case what eventually worked was booting from IDE 1 instead of using the raid controller and in addition i removed all other drives including the CD/DVD drive temporarily until the install was complete.
I had the boot drive only installed.
If you have a driver for a raid controller or similar when XP first starts intall watch for the press F6 to install driver message and follow it, however i read somewhere this frequently still does not take or cure it and was the case for me.

If the stop code you are getting starts with 0x0000007B etc then its very likely a hard drive controller issue.

These may help

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q225125

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q220845

AKDejaVu · « **Reply #3 on:** November 08, 2002, 04:59:59 PM »

I had this exact same problem with a defective video card. You might want to check to make sure its seated.

Also, pull out all other hardware and try that too.

bloom25 · « **Reply #4 on:** November 09, 2002, 02:14:14 AM »

Kaz, are you saying that you just switched those components and didn't reinstall Windows? If that's the case there is no way you will get the system to work. You MUST reinstall the OS with Windows XP.

Kaz · « **Reply #5 on:** November 09, 2002, 07:17:14 AM »

Thanks for the suggestions I'll try this stuff out and let ya know how it goes. BTW I DID install the new components without reinstalling XP so that is one of the problems if not the only problem.

Kaz · « **Reply #6 on:** November 14, 2002, 10:43:00 AM »

Finally got the patience to try again...hehe did the repair install and guess what? it works!!

thanks much for all the suggestions, made sure everything was properly seated, made sure the RAM was doing its thing, checked the links, all worthwhile..again thanks a bunch