Overclock.net › Forums › Intel › Intel Motherboards › SkullTrail + XP Install.. help needed
New Posts  All Forums:Forum Nav:

SkullTrail + XP Install.. help needed

post #1 of 6
Thread Starter 
Hi All,

I cant get my head around this problem i have. stop 0x0000007B (0xF78D2524, 0xc0000034, 0x00000000, 0x00000000), please, please help me. This happens when it just starts to setup windows

Thinking this was the Raid driver playing up i downloaded and made a f6 floppy courtesy from intel using their f6flpy32.exe programme. I have tried to use the ich9 and the ich8r / 9r driver but both of them show the same stop code.

Has anyone got a skulltrail working with XP.. and if so.. how the smeg did you do it.. btw its xp SP2.

Ideas and thoughts really appreciated ive spent the last 2 days trying to work out whats wrong.

some piccies of it (as some people might think im trolling, this rig does exist)

The 200mm fan at the side ( i need to dremel another hole for the enermax psu fan)



2x zalman itanium 9700's and 140mm exhaust fan

,

top 2x 140mm exhaust fans



you can jsut make out the 2x 120mm fans middle drive bay rear and lower psu bay in front of psu's.

I still want to add another 120mm to the front middle drive bay and the lower front drive bay, then i can think about tweaking.

Firstly i just want to get this going, so please any help is appreciated

Specs

1x skulltrail 5400 xs
2xx 2gb Crucial FBDIMMS @667 ( was told by supplier that 800's dont work.. what was that about)
1x pny nvidia quaddro 3700
2x WD raptor 150's on sata 0+1 ( the top 2)
1x nec dvdRW on sata 5
1x intel 10GB Ethernet card (not in yet, just want to get it working first b4 connecting to my 4TB raid array)

Video edit suite, hence the parts.. but id love to see what it can do lol
My last edit suite was a dual xeon 2.8 on the infamous asus pc dl deluxe board.. and that was slapped in a thermal take with 13 fans in it (includes the fans in the drive caddies)
post #2 of 6
Since it's a 'boot device' error, and your boot device is the Optical drive, I'd look at that guy first...

Sidenote: why install an outdated OS on the most up-to-date hardware there is? The times that XP was superior are over now (esp. after SP1 for Vista).
    
CPUMotherboardGraphicsRAM
E8400 @ 3.8 GHz DFI LANPARTY DK X38-T2R eVGA 8400GS 2GB Mushkin DDR2 800 (single stick) 
Hard DriveOptical DriveOSMonitor
250GB WD SATA None Windows XP Pro 32-bit HP Pavilion f1703 
KeyboardPowerCaseMouse
N/A Corsair HX520 Coolermaster Cavalier N/A 
Mouse Pad
N/A 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
E8400 @ 3.8 GHz DFI LANPARTY DK X38-T2R eVGA 8400GS 2GB Mushkin DDR2 800 (single stick) 
Hard DriveOptical DriveOSMonitor
250GB WD SATA None Windows XP Pro 32-bit HP Pavilion f1703 
KeyboardPowerCaseMouse
N/A Corsair HX520 Coolermaster Cavalier N/A 
Mouse Pad
N/A 
  hide details  
Reply
post #3 of 6
woah, sweet workstation. I have to agree with Chozart though. I'm afraid I cannot help you out with this problem but i'm sure CyberDruid (a legendary member of this forum) might be able to help you because he has a skulltrail too. Good luck and welcome
    
CPUMotherboardGraphicsRAM
Core i5 4670k Gigabyte GA-Z87M-D3H  2GB Asus 270X DirectCU II 16GB Corsair Vengeance 
Hard DriveCoolingOSMonitor
500GB Crucial BX100, 120GB Samsung 850 EVO + ~... Corsair H80 Windows 10 Hazro HZ27WA 
KeyboardPowerCaseMouse
Razer BlackWidow Corsair CX750M Aerocool DS Cube Microsoft Sidewinder 
Audio
Cambridge Audio DACMagic. 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i5 4670k Gigabyte GA-Z87M-D3H  2GB Asus 270X DirectCU II 16GB Corsair Vengeance 
Hard DriveCoolingOSMonitor
500GB Crucial BX100, 120GB Samsung 850 EVO + ~... Corsair H80 Windows 10 Hazro HZ27WA 
KeyboardPowerCaseMouse
Razer BlackWidow Corsair CX750M Aerocool DS Cube Microsoft Sidewinder 
Audio
Cambridge Audio DACMagic. 
  hide details  
Reply
post #4 of 6
Linky

Quote:
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 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/315239/) Microsoft support policy for hardware that does not appear on the Windows HCL
If the System hive in the Windows XP registry is corrupted, Windows XP may not be able to load the miniport device driver that the boot controller requires. To resolve this issue, restore a registry backup. For additional information about restoring a registry backup, click the following article number to view the article in the Microsoft Knowledge Base:
307545 (http://support.microsoft.com/kb/307545/) How to recover from a corrupted registry that prevents Windows XP from starting

Back to the top
Hardware Issues
You may receive a "Stop 0x0000007B" error message if there is a resource conflict between the boot controller and another controller or between SCSI devices. You may also receive this Stop error message if drive translation is not being performed or if drive translation was changed. To troubleshoot this issue:
1.If an IRQ or I/O port address conflict exists between the boot controller and another controller, Windows XP either stops responding (hangs) or displays a "Stop 0x0000007B" error message. If you recently added new hardware, remove the new hardware or reconfigure it so that it does not conflict with the resources of any other installed controllers.
2.If you are using a SCSI hard disk, check the SCSI chain for correct termination. Remove any unused SCSI devices or make sure that each SCSI ID is unique.
3.Make sure that drive translation is turned on (if it is required) and that it has not been changed. For example, if you recently switched controllers, this issue may occur. For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
314082 (http://support.microsoft.com/kb/314082/) You receive a Stop 0x0000007b error after you move the Windows XP system disk to another computer

Back to the top
Other Issues
Other potential causes of a "Stop 0x0000007B" error message include:
•The boot volume is corrupted and cannot be initiated by Windows XP. If the file system is corrupted and if Windows XP cannot initiate the boot volume during the startup process, either move the drive to another computer that is running Windows XP and run the chkdsk command on that drive or try to create a parallel installation of Windows XP on the drive (in a separate folder). The Windows XP Setup program checks the integrity of the volume before it copies files, and it may fix some problems in the process.
•You are installing Windows XP on a mirrored boot partition that was created by Microsoft Windows NT 4.0. Windows XP does not support Windows NT 4.0 Ftdisk volume sets. If you are running Microsoft Windows 2000, you must convert all Ftdisk volume sets to dynamic volumes before you upgrade to Windows XP. If you are running Windows NT 4.0, break any mirrors and back up all the data on the stripe, the RAID5, or the extended volume sets before you upgrade to Windows XP. Ftdisk sets might not be accessible after the upgrade.
Another Linky
Mr. Windy
(13 items)
 
  
CPUMotherboardGraphicsRAM
Q9650 Asus Maximus II Formula EVGA GTX 460 8GB OCZ 800Mhz 
Hard DriveOSMonitorPower
2x300 V-Raptor, 2x1TB WD, 2xSegate 320GB Fedora 14 2x Samsung 245BW Corsair 750TX; APC BR1500 
Case
Soldam Windy Altium FC 700 
  hide details  
Reply
Mr. Windy
(13 items)
 
  
CPUMotherboardGraphicsRAM
Q9650 Asus Maximus II Formula EVGA GTX 460 8GB OCZ 800Mhz 
Hard DriveOSMonitorPower
2x300 V-Raptor, 2x1TB WD, 2xSegate 320GB Fedora 14 2x Samsung 245BW Corsair 750TX; APC BR1500 
Case
Soldam Windy Altium FC 700 
  hide details  
Reply
post #5 of 6
Thread Starter 
Hi Guys,
Unfortunately the latest version of Avid (www.avid.com) only works with XP, theres a new version due out in june, which is when this thing will finally see Vista Ultimate 64bit

Ive been through the raid driver in f6, but the thing i have noticed is the boot disk thats there on the intel site is for 7.8 and when i go into the raid setup, its 5.4. Ive just done a bios upgrade but cant see anyway to install / upgrade the raid before windows.... is this the problem??

Im just trying the same disk with an ata cdrom connected and loosing the sata optical, see if that gets somewhere..... just bloody daft that intels own bios upgrade didnt work with sata optical, so had to shove the old one in anyways

Its a virgin winxp disk.. virgin drives.. so im tempted to say its not there fault.. ive even looked into if there was a specific config for putting the sata's on the board.. thats how much im scratching my head... and thank god for USB floppy drives.. ( never.. ever thought id utter that) Nice pc shop owner lent me his so i can at least do the f6 thing
post #6 of 6
Thread Starter 
Ok, quick update.. I have got past the bloody stop error YAY!!!!!!!

I personally think it was the sata optical.. so go ATA if installing crappy XP. Next problem.. Setup cannot find any hard disk drives installed in the system.

I am using STOR_All32_f6flpy32_7.8.0.1012_PV_Intel and managed to find an old floppy to work of the controller (of another computer), cos i couldnt change the usb floppy to a: even after disabling the controller.. damn thing still fired up as b: even on another usb port....

EDIT: STOR_All32...... will only run if it see's you have a floppy on a: apart from that it just silent cancels

So i can see the drives in the raid setup.. i have setup a stripe with these drives.. i am using the new f6floppy... still seems to point to this for me.. as the drives are obviously kewl as i can see them in the matrix raid (CTRL+I)

Any clues on this one folks??
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › SkullTrail + XP Install.. help needed