Hp blue screen

Slgrieb, thanks for the info. I have already tried a known good Antec true 430 from a good sysytem and crashes still happen.

Kodiak, All 4 sticks have passed memtest, although I have had bad sticks pass these tests before. Also, no overclocking on this system. It was just a new system that never worked from the original HP deployment image.

Noonoo, I still have the original drive. I would just try a clean install on a seperate SATA drive, not activate it, and start to load drivers and see where it crashes.

I will start my work list here in a few hours and then update these posts.

Very interesting thread river. If this hadn't been a new machine I would say you had a corrupted video driver. I just can't recall seeing this on a new machine, though. Also, my take is that when you installed the new motherboard, you installed a new video driver. And you also got an error installing Vista, right? Do you have a video card available that uses something other than an nVidia chip?

There are many posts about finicky memory issues with AM2 boards, so i am ordering 3 set of memory from crucial: BL2KIT12864AL804 . Certified by Crucial to work with board. I feel the original samsung M378T6553CZ3-CD5 is bad and that my Kingston KHX4300D2K2/1G is incompatable with new ASUS board, although it would boot and run with HP version of Asus board.

I tried new nic ( and disabled onboard Nvidia NIC) - still errors.
I tried an old PCI video card still errors.
I feel if it were CPU, i wouldn't be getting this far at all.
I tried a different ATX case with a different BIOS and turned off all caching,etc. - still errors
I tried new cables, a different outlet and different power cord. - still errors.
All drivers, including chipset at most recent versions.
I did not wipe and reload.

I will have more to post later this week after new memory arrives.

Thanks all for your help so far.

:flames:
New memory came in this afternoon. Installed and BSOD 0x0000008E. I went into BIOS and manually set CAS, tRCD, tRP and tRAS without any change or benefit (except back to original 0x0000000A BSOD).

I am also getting other errors like "internet explorer has encountered an error and will be closed" and "lsass.exe has encountered an error and the system will shutdown." I guess these could come from the initial install if the files where not correctly installed before the random system reboots.

I have not changed CPU or done WAR. I am leaning towards a wipe and reload. (I backed up my activation files). If I encounter reboots during WAR, I would assume it is still a hardware error, but I have changed all components other than CPU. I still don't think I would get this far if it is CPU.

Suggestions?

Why not just run a repair install?

All right. Cleaned house. Fresh install of XP Pro SP2. Got rid of HP's version of media center. Updated all drivers, installed Adobe Reader and some apps. No crashes of explorer and no BSOD's yet.

I am going to reset some bios options back to their defaults, the if all goes well, start enabling hardware, the adding back the original components such as the memory.

Lastly, I will install windows updates.....

I am now leaning towards the fact that it was a software/driver issue. BUT i got random reboots during a clean install of Vista so I figured it was a hardware issue....

..so some more troubleshooting

I have reset Bios memory settings to auto, re-enabled caching and spread spectrum and HT support - no issues.

I have re-connected all devices - no issues.

I have re-installed ORIGINAL memory chips - no issues.

I have NOT reinstalled original HP motherboard to see if issues come back.

I have NOT tried a clean re-install from CD's (not recovery partition) of original OS (media center).

I am currently installing MS updates.

My current conclusion is bad HP motherboard was cause of reboots/BSOD and never allowed a clean install of OS. When I ghosted the image to another HD and did MB swap I believe I brought those problems into the new system with the ghosted drive.

i will update final results after this weekend when i have had more time to evaluate and test

Does this conclusion make sense?

Does to me!

Looking for something totally different, I found http://nvidia.custhelp.com/cgi-bin/n...i=&p_topview=1

sounded strangely familiar.

everything ran good for the last few days...even on the HP MB. So i am going to try an use the HP recovery partition to get back to the original setup and then see if Slgrieb's link provides a solution.

One side note - the recovery partition was not bootable nor did the F10 button work to load the recovery process. I followed the instructions at http://www.gripe2ed.com/scoop/commen...8/113551/618/1 and am now performing a recovery installation.

I'll post more soon, but looks as if this could have been a driver issue - a driver for a device not even installed.

no dice.
setup keeps failing with "the system is not fully installed please run setup again" I have also followed the instructions from HP over athttp://h10025.www1.hp.com/ewfrf/wc/d...71747&rule=915.

Now I just get freezes at xp splash screen. does not work in safe mode either.

hp recovery partition relaoded the OS. I ran drivercleaner pro as posted in the NVIDIA link slgrieb posted and found no Nvidia WDM drivers.... but i did find ATI WDM drivers. This is an HP branded ASUS Motherboard w/ NVIDIA chipset. I don't believe ATI drivers should be on here. I know they don't play nice together from previous systems. I used Drivercleaner to remove all ATI drivers.

Still crashes - 0x00000050 and then 0x0000000A.

Would anyone suggest using the driver cleaner to remove all the Nvidia drivers as well? and then install them from new sources?

OR

I could load an OEM media center 2005 and use the HP sn# to see if it is the install or maybe something just doesn't play well with media center.

Still lots of wierd behaviors: errors in RPC, mshtml, drwatson.

I then tried to remove all NVIDIA drivers in safe mode using drivercleaner pro. When i restarted windows, there was no "new hardware found" dialogs, so i looked at device manager and there were NO yellow driver issues.

I even tried to manually install the NVIDIA chipset drivers as directed by HP and when i point to the .inf file windows says this filw was not intended for your hardware. Under automatic mode it says no better match was found.

Every couple reboots i have to go back into settings and performance and uncheck the restart box so i can get BSOD stop messages from the screen.

Also HP's 6150LE driver (nv4_disp.inf) has a version of 8.2.0.8 The same file on the ASUS website and CD is only at version 8.2.0.5

All advice will be considered.

i still can't get HP's version to behave. I can install oem version of MCE on original HP hardware and it runs find with no BSOD's. It won't accept either the serial from the case sticker or the original key that is on the HP install and says i must activate it. (but this was just for test purposes) I also copied the wpa files from the original HP install into the oem install - no luck.

This point to a driver issue or a corrupt .sif.

I will try to copy the i386 folder from the HP recovery partition, delete the drivers folder and see if i can just get a clean MCE CD.

I have given up.
I installed MCE 2005 OEM from disks. The serial from the .sif and the serial from original install would not take. The case sticker would work for entry but required activation. I even copied the wpa files from the HP installation to this one. I called MS talked to the computer and was given new activation code. No hardware had changed. Bith CD disks had the same info :
[Pid]
ExtraData=786F687170637175716954806365EF
Pid=76487OEM

One of these serials should have been a VL that did not require activation (which is why i got the " this serial has been activated too many times" when i used the case sticker)

I tried to extract the I386 files from the recovery partition, but i could not get the MCE functionality - only xp sp2. The media center .cab is in a folder called cmpnents on the HP main partition but not on the recovery. It might be part of the preload folder that has the data.inp files and base.inp files. MCE must be installed at the initial installation and cannot be added to later from what i undersatnd.

All is working flawlessly with original hardware and drivers from HP site. This may have been a DRIVER issue. I could not determine which one. OR it could have been a corrupt install or some HP bloatware that didn't play nice.