XPSP2 No Boot

[PardeGT]

I am having great difficulties with my system (specs in sig) as it always gets a BSOD (STOP: 0X0000007F) at the windows splash screen.

It ran fine for over a year and now nothing. Here's what I have tried to no avail:

-Ran R repair option (2nd screen) with XP PRO SP2 disk (several times throughout)
-Reset CMOS (this seemed to work for a day and then back to the same BSOD)
-Updated bios to 0709
-Ran quick and extended tests on hdd (0 errors)
-Pulled PCIe video, installed std pci vid card
-Tried ram with just one stick and different slots
-Unplugged everything but just cpu, 1 ram, video, and hdd
-Different PS

Any ideas other than trying a reinstall of the OS? Also, no overclocking or speed enhancements are set...all standard setting in bios.

Thanks for your replies.

[shadowpr]

http://support.microsoft.com/kb/137539/en-us

Try to run memtest86+ and see what that shows.

[PardeGT]

Thanks for the suggestion. Test came back with 0 errors. Sometimes, the windows splash screen just stays up with the bar going across constantly. Stays this way until I shut it off.

I'm really almost ready to think I may have an issue with this asus board even though I never have with any of the ones I used in the past.

[PardeGT]

Today I tried installing xp on a different drive with the system and it froze half way through installing devices, had to shutdown. I tried different sata cable and sata2 connector also with same result.

Any advice would be appreciated.

[Brothersoft]

Could it be the boot sector viirus? Just my guesswork.. Or have you ever checked the wiring/cables? I am sitting down here for the right answer..

[Panama Red]

Seems like I remember some comments from overclockers in the past that GSkill memory needs a voltage boost to run stable. Check the specs on your ram and manually increase the memory voltage in the bios to near the max rating of the ram. (ie: rated 2.8v, mobo putting out 1.95, increase to 2.5v) I think this is due to the tight timings that GSkill tries to run as default. When the mobo is set to Auto in the memory configuration, it tries to run the factory default timings but at a lower voltage.

FWIW, If the mobo you're talking about is the one in your sig, I have a system using the same mobo. It's been running great for quite some time now with 2Gb (4 x 512Mb) Corsair VS ram and a Pent D 950. I just reloaded it with a fresh XP install and my son is getting it for Christmas to replace his aging Socket A AMD machine.

[PardeGT]

Panama Red - your suggestion was my solution. The funny thing is that I have had this system running stock for over a year with no problems. I left the setup stock with no overclocking and no change to any of the voltage settings. I wonder why now it is complaining?

I did notice a couple things. The system within the last couple months had started to get flaky (occasional lock-up, reboot, usb unresponsive) but I couldn't find anything. It kept getting worse until I started getting BSOD and finally it would not boot.

The other thing is I had left the bios to autodetect the memory and just noticed that during bootup it recognizes the ram as PC5300 instead of PC6400. I had to manually set the 6400 setting for it to recognize it as such. I also had the memory voltage set as auto. The memory stick reads 1.8-2.0V on the sticker and the bios settings allow 1.8-2.3V so I set it at 2.1V. It seems to be stable now. I am wondering if I should back it down to 2.0V as do I chance damaging the memory with the 2.1V setting?

Thanks for you help!

[Panama Red]

Glad it worked! I guess I would back the vdimm down to within spec and see if it runs stable. Most components should handle a +or- 10% voltage variation but why take an unnecessary chance.

[PardeGT]

Bad news - pc is now having same symptoms as before locking up at windows splash screen or BSOD general stop error.

A friend had a P5E asus board he had not installed yet so I installed it just to see if I could get it to boot and it was the same story.

I am wondering if my ram is the problem even though it does not produce errors in Memtest? I've tried all different settings and voltages with no success now. Unfortunately, the same friend has not purchased ram yet so I'll have to find some elsewhere.

Any other ideas? Thanks.

[glc]

Raqm is cheap now - I'd bite the bullet and get some Corsair that will run at 1.8 or 1.9 volts.

Have you considered an incremental upgrade - a new motherboard and a Core 2 Duo?

[PardeGT]

GLC, yes I have - just not sure my use necesitates an upgrade. What do you see as the motivation for an upgrade? Higher power ram supported by the new chipset and/or the true dual processor vs my pentium D?

Thanks

[glc]

Not necessarily higher power ram - I do recommend 1.8 or 1.9 volt DDR2-800 CAS 5 ram for the P35 family chipset. The big reason is the far superior processors available at very low prices - the Core 2 Duo is worlds more efficient than the Pentium-D and runs a lot cooler. The only downside to the P35 is lousy IDE support.

With your Pentium-D and your ram, I recommend you run the ram at DDR2-533 speed. This should give you the best compromise between speed and stability.

[PardeGT]

Thanks for your suggestions GLC. I agree on the core duo processor; I was just planning on keeping the pentium d in use until the intel 45nm chips are out for awhile.

Unfortunately, before your suggestion for Corsair I had put in a purchase for 2-1GB Mushkin ddr2-800 siticks. They came today and they provided no solution either. I've tried timing both the Gskill & Mushkin down to ddr2-533 with no success either. Still locks up with a general stop BSOD.

Man, this is getting fustrating.

Could my cpu be the culprit? Never had one go bad but...

[Icyman23]

well...both your ram must be good. the only thing I can think of is your cpu or a usb/pci card/device.

try unplugging all unneccesary devices that you dont need, like any usb devices and/or pci cards

[PardeGT]

I had tried that before but never hurts to try again....no luck. Tried booting with only ram, hdd, cpu and vid; also had usb disabled. Vid(generic pci), hdd, Ram, PS have been changed out to rule them out as well. Same exact result.

[PardeGT]

In case I need a new processor I was doing some checking. I was looking at C2D cpus and wonder why the 1333 FSB Conroe's are cheaper than the 1066's? Here is an example from Newegg.

Intel Core 2 Duo E6750 Conroe 2.66GHz 1333FSB $190
vs
Intel Core 2 Duo E6600 Conroe 2.4GHz 1066FSB $230

I know my 955X chipset only handles up to 1066FSB but was just curious.

[glc]

The 955X does not support any Core 2 processors regardless of bus speed.

[PardeGT]

Oh crap, I see you are correct. I made the assumption that since the board supported the dual core pentium D it also supported the C2D's.

Ok, so back to my main problem. GLC, at this point what would you suggest to get to the root of my lockups?

Thanks.

[glc]

If it's not stable with minimum cards and known good ram conservatively timed, it sure is pointing to the motherboard. Processors generally work or do not work, no in between. How are the temperatures?

[PardeGT]

Well, I had tried using another motherboard my friend had, asus P5E, the only piece of his system he had purchased so far. I install that with just the minimum components (my current ones) and had the same BSOD. I kept thinging it was the OS so I reinstalled it using a different sata drive and cable (also different cd drive) and had the same failure.

The temp of the cpu runs between 50 and 70C depending on load as reported by the bios. I am just using the retail cooler with artic silver.

[PardeGT]

Ok, the solution was the processor.

My friend decided he wanted to go AMD so I bought the P5E board I had borrowed from him and then picked up a E6750 C2D. I just ran a repair on the OS and then loaded the drivers for the new board. All seems to work well now.

I then tried pulling the C2D out and installing the Pentium D and sure enough it goes to a BSOD during the windows splash screen - same as it did before.

Very weird as I agreed with you, GLC, and really didn't think it would be the cpu that was bad.

Thanks for all the replies.