Sign in with
Sign up | Sign in
Your question

Stop error on new build...old HD

Last response: in Storage
Share
August 31, 2005 2:27:40 AM

I am stumped.

I bought the following for a new build:
-Asus P5WD2 Premium 955 ATX Mainboard
-Gigabyte 6800GT PCI-e
-WD Raptor 10k 37GB
-Crucial 2x512MB DDR2 800 RAM
-Intel P4 3.0GHz LGA 775 HT Processor

I carried over from my old system a Samsung SV6003H HD.

I am getting Stop 0x0000007B ( 0xF7C46528 , 0xC0000034 , 0x00000000 , 0x00000000 ) error message when trying to boot my new build.

I have tried each hard drive hooked up seperately and installing Windows XP Pro over the top of each HD (I cannot get it to install, same stop error).

My BIOS recognizes the Hard Drives and everything appears to be OK but then it errors out to the BSD with the stop message. None of the "fixes" I have found have helped my problem.

My old HD will boot in my old box and my new HD has nothing on it.

Any info is greatly appreciated.

More about : stop error build

September 1, 2005 2:12:43 AM

That sounds like a memory error, not a hard drive problem.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
September 1, 2005 5:00:24 PM

I will try to test the memory when I get home.


The second parameter with the 0x00000034 is supposed to indicate:

The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

* Disks or storage controllers that are failing, defective, or improperly configured.
* Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
Related resources
September 2, 2005 12:54:58 AM

I went to Crucial's website and noticed that my particular "make" of RAM isn't listed for my MB. I am awaiting response from Crucial on whether there is some problem with my compatability.

I hope this is the problem because I have no idea where else to look.
September 10, 2005 12:24:57 AM

Well the RAM was not the problem. My replacement RAM (which has been tested) is not fixing my stop messages.

I also purchased a new 300GB Maxtor HD and BIOS sees it but won't boot my Windows XP Pro disk copletely so I can install.

I am at a loss for words...
September 23, 2005 10:47:24 PM

--ASUS MB P5WD2 Premium Socket T (LGA 775) Intel 955X ATX Intel Motherboard
--GIGABYTE GV-NX68T256DH Geforce 6800GT 256MB 256-bit GDDR3 PCI Express x16 Video Card
--Western Digital 10,000rpm Raptor 37GB Hard Drive
--[2] Crucial Ballistix 512MB 240-Pin DDR2 SDRAM Unbuffered DDR2 800 (PC2 6400) System Memory (traded in for below RAM)
--Crucial Ballistix 1GB 240-Pin DDR2 SDRAM Unbuffered DDR2 667 (PC2 5300) System Memory - OEM
--Intel Pentium 4 630 Prescott 800MHz FSB 2MB L2 Cache LGA 775 EM64T Processor
--Aspire X-Navigator ATXA8NW-AL/500 Silver/Black Aluminum ATX Mid Tower Computer Case 500W Power Supply
--Memorex 52x CD-RW (purchased from local retail store)
--Maxtor DiamondMax 10 6L300S0 300GB 7200 RPM 16MB Cache Serial ATA150 Hard Drive - OEM


I have RMAed the RAM, Video card, and motherboard to try and solve this issue and it has not helped. The only thing I haven't returned is the CPU but it only hangs on the HDs for some reason...
September 26, 2005 3:26:52 AM

Both those RAM types run at non-standard voltage, I bet you didn't even bother to go into BIOS and raise voltage to the appropriate setting!

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
September 29, 2005 7:19:06 PM

I did not..

see a place to do so and didn't know that I had to. I will look into it when I get home! Thanks for your help...hope it works, this thing has been a thorn in my side.
October 6, 2005 5:13:41 AM

Had to reset the CMOS, remove a bad Sata drive, and move the CD-ROM to the blue IDE and it ended up working...yay!

<victory dance>
!