HD Corruption after Fresh install of XP pro

[perillo34]

I just did a fresh isntall of Winxp pro on my brand new sata HD, I installed all the drivers for it, so now worries there, the install went perfect, but the first time loading up the Winxp load screen will appear for a split second, then boom blue screen stating problem occured windows had to stop in order not cause harm to the system, check for viruses, new hd drivers or controllers, run chkdsk. What the hell, it has done this everytime after four fres installs.

 

[ScrapSilicon]

complete error message plz

 

[perillo34]

A problem has been detected and windows has been shut down to prevent damage check for viruses run, chkdskf , etc....
STOP:0x0000007b (0xf894d64y, 0xc0000034, 0x0000000, 0x0000000) I dont know what the deal is the wiindows load screen flashes up then this error blue screen appears.

 

[thorin]

Try booting in safe mode.

Thorin

 

[perillo34]

How do you boot it in safe mode, automatically just goes on, do I need a boot disk

 

[ScrapSilicon]

Originally posted by: perillo34
How do you boot it in safe mode, automatically just goes on, do I need a boot disk

pressing F8 usually for most..anyway ..0x0000007b

 

[perillo34]

Could it be a SATA problem or an NF7-S problem, should I upgrade the bios or what any help would be great,

 

[ScrapSilicon]

Originally posted by: perillo34
Could it be a SATA problem or an NF7-S problem, should I upgrade the bios or what any help would be great,

so.....from the above linked webpage

Device Driver Issues
You may receive a "Stop 0x0000007B" error message in the following scenarios:
A device driver that the computer boot controller needs is not configured to start during the startup process.
A device driver that the computer boot controller needs is corrupted.
Information in the Windows XP registry (information related to how the device drivers load during startup) is corrupted.
Windows XP requires a miniport driver to communicate with the hard disk controller that is used to start your computer. If Windows XP does not supply a device driver for your controller or if Windows XP is using a corrupted or incompatible driver, you must replace the driver with a valid copy that is compatible with your controller and Windows XP.

During the first phase of the Windows XP installation, Setup displays the following message at the bottom of the screen:
Press F6 if you have to install a third-party SCSI or RAID driver.

Press F6 and then follow the instructions to install a mass-storage device driver from your Original Equipment Manufacturer (OEM). For additional information about using F6 to load an OEM device driver to support, click the following article number to view the article in the Microsoft Knowledge Base:
314859 Limited OEM driver support is available with F6 during Windows XP Setup

To determine if your hard disk controller is compatible with Windows XP and to obtain information about drivers that are included on the Windows XP CD-ROM or that are available for download, see the latest Windows XP Hardware Compatibility List (HCL). For additional information about the latest Windows XP HCL, click the following article number to view the article in the Microsoft Knowledge Base:
314062 The latest Windows XP hardware compatibility list

If your hard disk controller is not listed on the HCL, contact the manufacturer of your computer, system board, or hard disk controller for information about the availability of a driver. Microsoft does not guarantee that a resolution is available for non-HCL equipment. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
315239 Microsoft support policy for hardware that does not appear on the Windows HCL

might be of some assistance ..

 

[perillo34]

Tried all of the above, new drivers, everything still corrupt damnit, could it be memory

 

[mechBgon]

What are the complete system specs? Include the power supply brand/model too.

 

[perillo34]

Well I have the ABit Nf7-s v2 board, xp2700-m, pdp 3200 1-512mb, enermax 350watt model number 365g-vd I think, ummm WD 80gig Caviar SATA, geforce 4ti4200 gainward GS.

 

[ScrapSilicon]

what's that..?

pdp 3200 1-512mb

pdp..?

 

[mechBgon]

You might try adding some memory voltage, try 2.7 volts if it's been loafing around on AUTO. Also, make sure the memory is running synchronously with the CPU's bus speed, e.g. 166MHz base frequency for both. Don't have the CPU at 166 and the memory at 200, for instance... whether it's stable or not, it's going to cost you performance to have them out-of-sync.

 

[perillo34]

pdp memory is Patriot memory, its good stuff, clearing memtest for the past hour, still will this help get past the stop error screen 0x0000007B

 

[ScrapSilicon]

nm..running memtest

Originally posted by: perillo34
pdp memory is Patriot memory, its good stuff, clearing memtest for the past hour, still will this help get past the stop error screen 0x0000007B

you are narrowing things down..

ABit Nf7-s v2 board, xp2700-m, WD 80gig Caviar SATA

..

 

[mechBgon]

Long shot: maybe the driver files on the floppy are a little corrupted?

 

[perillo34]

You may be right, but should I just try a new floppy with some downloaded drivers or what, I mean I have some of them already slipstreamed into my winxp pro sp2 disk,

 

[zephyrprime]

I would try running the hard drive manufacturer's diagnostic software before I did anything else. You should then move on to the memory and CPU diagnostics. A methodical approach is more time efficient than just shooting in the dark.

 

[perillo34]

Hmm well I am going to use the old drivers off the website and see what happens, after this I really wont know what to do.

 

[ScrapSilicon]

Originally posted by: zephyrprime
I would try running the hard drive manufacturer's diagnostic software before I did anything else. You should then move on to the memory and CPU diagnostics. A methodical approach is more time efficient than just shooting in the dark.

I didn't see SATA wdc DLG tools on wdc.com..but ..are you using the driver
that came with the drive or SiliconImage 3112A SATA Driver from abit
..? ..also some had mentioned their sata cables as having loose
connections..[

 

[perillo34]

you think these loose connections could cause the problem, I think it might, but wouldnt it mess up on the install as well not just on the load up.

 

[perillo34]

Allright I just notice something when not running quick boot enabled in the bios, the bios memory test takes forever and keeps repeating itself, my old athlon 700 with pc133 512mb ram checked faster, so maybe it is the ram, but it doesnt make since for it tested fine in over 3 hours of memtest 86

 

[ScrapSilicon]

Originally posted by: perillo34
Allright I just notice something when not running quick boot enabled in the bios, the bios memory test takes forever and keeps repeating itself, my old athlon 700 with pc133 512mb ram checked faster, so maybe it is the ram, but it doesnt make since for it tested fine in over 3 hours of memtest 86

test ram in another system(s)..if no trouble ..it possibly might be either the slot(try another)/contacts or the board itself..

 

[perillo34]

I wish I could but I have no sytem anywhere capable of dealing with this ram, all pc-133 and older system mobos

 

[perillo34]

Tried a few slots on the board I have heard of some compatibility issues from the new egg reviews, but only 2