Hardware Analysis Community Forums http://www.hardwareanalysis.com/content/topic/2159/ 2009-11-08T00:08:00-05:00 http://www.hardwareanalysis.com/content/topic/2159/ /images/halogo.gif text/html 2003-10-25T00:06:07-05:00 James Golden http://www.hardwareanalysis.com/content/topic/2159/?o=20#69479 I was trying to install Windows XP on this:<br /> <br /> Gigabyte GA-7NNXP<br /> Athlon XP 1800<br /> <br /> My problem was during setup with about 30 minutes to go it would freeze up. After scouring MS site and Gigabyte site and doing EVERYTHING they said to try I got no further.<br /> <br /> So after 10 hours of watching my machine reboot I turn to good old Google... and viola! I find this page. My problem was like most of the others. It was the ram chips.<br /> <br /> I had 4 ram chips:<br /> 1 - 512meg PC3200 (400mhz)<br /> 3 - 128meg PC2100 (266mhz)<br /> <br /> I had the 512mb chip in slot 1. I proceeded to take out the other 3 chips and XP installed. I'll have to post what I figure out about getting the RAM chips to work together. The motherboard supports them all. text/html 2003-10-14T10:49:44-05:00 Richard Langton http://www.hardwareanalysis.com/content/topic/2159/?o=20#66667 After spending an entire day trying in vain to install XP, I finaly came to my senses and checked the internet to see if I could find an answer to my problem. The first page I found was this one. I removed one of my RAM sticks and problem solved. Don't I feel like a stuped head. If only I had checked the internet sooner. Thanx guys. text/html 2003-10-09T17:44:33-05:00 Tonatiu Camarillo http://www.hardwareanalysis.com/content/topic/2159/?o=20#65711 Hte problem is the frecuenci whit the memori works whit the motherboard... I have this problems tow times una whit a sys motherboard and the solution was to setup the bios whit safe values... and then it install XP correctly and the second time whit a Ipaq Compaq Pentium III this motherboard don't have safe values.. then I change the memori for works exactly whit the delaer espesify... and it work good.. I discober it makind the test memory..then fail.. works good whit win'98 .. but no whit XP... text/html 2003-09-16T01:49:20-05:00 Kevin Smith http://www.hardwareanalysis.com/content/topic/2159/#60613 you guys are great!!!!!!!!!!! this solved my(or should i say my dads but i created it)problem. Have now installed xp, and finally got a partition with 98 on it. again thanx 2 u guys. It was the guy who suggested the fail safe option in the bios that hit the nail on the head. Thanx dude!!!! <img src="/images/smilies/smile4.gif" width="14" height="14" border="0" alt=";)" title=";)"> text/html 2003-09-07T06:47:45-05:00 candy zheng http://www.hardwareanalysis.com/content/topic/2159/#58528 I removed one of my ram.The system was installed smoothly.But<br /> when I wanted to add the other stick of my rams,some error happens.<br /> stop :0x0000007E(0xC0000005,0xF84A454C,0xF894D3D8,0xF89D1D8)<br /> I wondered whether my ram was damaged. text/html 2003-09-06T05:51:50-05:00 candy zheng http://www.hardwareanalysis.com/content/topic/2159/#58305 I also got such a problem when i am trying to re-stall xp pro to my computer.And my computer :<br /> amd xp 2000+<br /> gigabyte 7vac<br /> ddr 333 kingston<br /> 60g harddisk seagate<br /> I can't decide whether it's a hardware problem.<br /> Since there are two system in my computer <br /> one is win xp,and the other one is linux 9.0<br /> I even can not start my linux and restall it too.<br /> text/html 2003-08-24T21:43:44-05:00 MacMan http://www.hardwareanalysis.com/content/topic/2159/#55351 I had the same problem, and it was ram related. But I didn't have to replace the ram, instead I just slowed it down from 200Mhz or whatever down to 100Mhz, and then XP installed fine.<br /> <br /> Also, when I disabled my level 1 cpu cache, the installer hung on loading the kernel debugger file.<br /> <br /> I'm using an ASUS motherboard with an AMD processor and PC3200 ram. XP's running fine now. text/html 2003-06-29T19:37:18-05:00 Seven ofNine http://www.hardwareanalysis.com/content/topic/2159/#42263 Yes! A very helpful thread.<br /> <br /> Although I'll probably never know the reason for the original crash of my original HDD, being vexed by the same setuppdd.sys error 4 didn't improve the dent in my head as I attempted to install XP Pro to a new Western Digital HDD.<br /> <br /> After reading this thread, I removed all extraneous PIC cards, the CDRW, and replaced the new memory with the old. XP Pro installed smoothly and the new memory, CDRW, and PCI cards were all accepted (one at a time) by the system and it is now running smoothly.<br /> <br /> Thanks! text/html 2003-06-28T23:21:16-05:00 Shane Mitch http://www.hardwareanalysis.com/content/topic/2159/#42127 You MUST disable virus protection within the bios for windows to install, or reinstall, as this virus protection does not enable writes to the MBR in your harddrive, and you will get the File setupdd.sys could not be loaded. The error code is 4&quot; errors as you stated, it's as simple as changing your bios into fail safe mode, installing windows, then reverting back to performance mode afterwards, I hope this helped someone, I had the same problems for a while, then I figured it out.<br /> text/html 2003-06-26T12:41:59-05:00 David Mycroft http://www.hardwareanalysis.com/content/topic/2159/#41673 I had a similar message from an Abit XG7-RAID that had a fully installed and working Win2k installation,<br /> STOP 0x000000A5 (0x00000011, 0x00000007, 0xEB8680C0, 0x0100000C) , after installing a drive cage. The cage was catching the DIMMs and I didn't install it. When I started the system I got this stop message.<br /> <br /> I reseated the DIMMs, removed and reinserted, and when I restarted the problem had gone.<br /> <br /> Definitely 1 vote for RAM related......<br /> <br /> text/html 2003-04-23T20:05:22-05:00 Dave http://www.hardwareanalysis.com/content/topic/2159/#31712 File setupdd.sys could not be loaded<br /> The error code is 4<br /> Press any key to exit.<br /> <br /> This is usually RAM related while trying to re-install XP Pro/Home after the PC crash's for no apparent reason &amp; you just cannot get any operating system back on, it even gives problems if you try to sneekily, bypass this, by thinking you will be clever by putting another hard drive in your system &amp; install onto that, forget it same problem. It also gives differing errors when you try to get around it by re-installing <br /> W2K/W2K Server &amp; 98, <br /> <br /> BUT &amp; its a big BUT its not guaranteed to be RAM related<br /> .<br /> You can try the following walk through but start by changing the RAM first of all which could save you a lot of time if changing the RAM solves the problem, however if it do's not then you have no option but to follow the following exhaustive checks to find the offending culprit.<br /> I got the above error 1 week outside of the computers warrenty so I was gutted, mine was the RAM, <br /> <br /> Here it is try changing your RAM first if it still gives the error then try the following:<br /> <br /> Remove everything that is installed or connected to your computer so the only things remaining in the case are:<br /> <br /> Motherboard, processor, and cooling fan<br /> Graphics card<br /> One stick of RAM <br /> One hard drive<br /> One CD ROM drive <br /> <br /> That's it. No sound card, no network interface card, no modem, no extra hard drives or CD ROM drives. Especially important is not to have more than one memory stick, and it should be a minimum of 128MB. Connect up the monitor, the keyboard and the mouse and power up the machine. Go into the BIOS settings and look for a setting for the basic BIOS default configuration. Select it, then make sure that if you're booting from a CD ROM that the CD drive is the first boot device.<br /> <br /> Reboot and let the installation process begin. I haven't kept track of numbers, but in the vast majority of cases the installation was completed with no problem. Once you have the basic operating system in place it's a simple matter to start adding back in the extra memory, drives, and devices that were stripped out initially. <br /> <br /> A FINAL TIP. I know it's tempting to add everything else back in at once after a successful install. DONT DO IT. Something was causing a problem initially or you wouldn't be using this procedure. Add the pieces back one memory stick, one hard drive, one network interface card at a time and test the system for proper operation after each addition.<br /> text/html 2003-01-28T08:23:22-05:00 Scott C http://www.hardwareanalysis.com/content/topic/2159/#20484 Having the exact same problem with an Asus A7N8X. This is after I swapped out a Gigabyte 7VAXP. I'm starting to lean toward the memory. Being that this is a common problem, has anyone seen a definitive solution to this? text/html 2003-01-19T20:44:58-05:00 Dr. TaaDow http://www.hardwareanalysis.com/content/topic/2159/#19630 seems alot of people are having problems with gigabyte boards too, and seems there is terrible tech support... so my advice.. stay away from them ;-) text/html 2003-01-19T20:42:26-05:00 Dr. TaaDow http://www.hardwareanalysis.com/content/topic/2159/#19629 EPoX 8K5A2+<br /> Athlon XP 1700+<br /> 512MB <a target="_blank" href="/action/r/http://www.crucial.com/">Crucial</a> PC2700 333MHz DDR RAM<br /> (2) Maxtor ATA133 40GB HDD's (RAID)<br /> (1) IBM ATA100 20GB HDD (RAID)<br /> 64MB GeForce2 MX400<br /> DVD-ROM<br /> CDRW<br /> 300W Power Supply (El Cheapo)<br /> <br /> all that running on a 300w p/s... not one problem whatsoever... 300w is enuf for an athlon xp processor text/html 2003-01-19T03:43:56-05:00 Ted M http://www.hardwareanalysis.com/content/topic/2159/#19593 Hi, I just had the same setupdd.sys problem (with XP Pro) and I must admit the above mentioned letters helped tremedously! Thanks to everyone that contributed. However, my problem was linked to a bad cd-rom. I went with swapping it first---since it seemed to drag out booting from it in the first place. I swapped it with a known good drive and the install flew. My hardware: memory (256 sd), 200 watt power supply, XP 2000 processor, and a seagate hd. XP just finished installing from the cd I first recieved the error from. I hope this helps someone.