Cpu Fail?

Im not sure, never burned out a processor, if that happened. The other day i took out one of my NICS, had two in, and tried booting. But recently on my AOPEN mobo board w/ AMD duron 700 just stopped working. The puter POSTS and runs through BIOS just fine and dandy finds everything fine, the cpu and disks. But if i try to boot xp it gives me this error, A problem has been detected and windows has been shut down to prevent damage to your computer. IRQL_NOT_LESS_OR_EQUAL
Technical Information: *** STOP 0x0000000A (0x00000420. 0x000000FF. 0x00000000, 0x804E9DA9)
Beginning dump of physical memory.
Physical memory dump complete.

I have never seen this before, it doesnt even go near the boot seq, for xp, I tried booting red hat 8 on it, and gives me a kernel panic. Any help would be nice. Thanx

IF it was a CPU failure, you wouldn't even get past teh post.

Microsoft support site. http://www.microsoft.com/technet/tre...d_stp_hwpg.asp

Looks like it might have something to do with a incompatible driver or something along that extent.

Can you boot into safe mode?

no cant even boot to safe mode, its gives me once again another blue screen with this:
STOP: c0000135 {Unable to locate componet}
This application has failed to start b/c winsrv was not found. Re-installing the application may fix this problem.

Should i try to boot to dos w/ win98 boot disk w/ no ram disk and try to redo eveything on the box? I couldnt even get to the x installer for red hat 8 before the kernel panic. This box has never done this before. Thanx

It sounds to me like a hard drive problem. But trust me. It's not the chip. I burned a p4 2.4 a couple months back when I didn't notice the 1mm space between the CPU and the heatsink. There was no thermal paste on the heatsink at all, but it was still on the chip. It took all of 10 seconds. Sounds like the system is detecting the hard drive in question on the control pins, but the data pins are somehow not transmitting / recieveing. Try a different IDE cable, or maybe it's just a loose one or a bent/broken pin.

P.S. Yeah... That's right. The Thermaltake Volcano 7 does NOT fit on a P4 board... despite the product advertising. And they only warrant the cost of the product, not the chip thier false advertising and substandard engineering burnt. It was half may fault too, I know, but still... it was half thiers, too. :mad: (sorry, just venting... that was a $250 (cdn.) mistake)

Your best bet would be to probably reinstall your system. If you have a XP disk then I'd just put it in the drive and boot from that. then install windows again. But just for kicks, try putting the NIC you took out back in.

Dunno why the hdd is being blamed.. system files lost or corrupted.. take cheyenne1212 advice.. BTW you won't get far with a win98 boot disk.. unless you have installed XP with the FAT32 file system.. and if thats the case.. no bloody wonder your having problems..
Warm install.. loose some of yer progs.. but keep your data.. backup what you can.. of yoiur data.. format the hdd in NTFS.. clean install Win.. you could risk running the system after the warm install.. but I dont recommend it..

Cheers

It's the error messages like

IRQL_NOT_LESS_OR_EQUAL
and
STOP: c0000135 {Unable to locate componet}

I also had a hard drive give blue screens when setting up my current box. It was just a pin that wasn't connecting properly on the hard drive. The BIOS could see the hard drive, but couldn't transmit to or from it. But I did find this online:

Quote:

---

0528 » Stop: c0000135 {Unable to Locate DLL}.

If you receive the subject message at start up, the file is either missing from %SystemRoot%\System32 or the Software Hive of your registry is corrupt.

There are various ways to fix the problem:

1. Use tip 181 to copy the file from the CD-ROM. You may have to reapply your latest Service Pack.

2. Boot to an alternate install of Windows NT and look in the original \System32. If the file is missing, copy it from the alternate install or expanded Server Pack (SPName.exe /X).

3. Check the Software Hive for corruption by booting to an alternate install of Windows NT and loading the original Software Hive using tip 182. When locating the Software Hive, it is the Software file with the Windows Icon, not the Notepad icon. If you receive a Registry Editor could not load ..... message, the software Hive is corrupt. You must restore the registry or run a repair / repair registry files.

---

Guess I was wrong.

Source

/edit/

And

Quote:

---

Additional Information:

The IRQL_NOT_LESS_OR_EQUAL or Stop 0x0000000A errors are able to be generated by both software and hardware issues. The message indicates that a kernel mode process or driver attempted to access a memory address that it did not have access to.

---

Source

/edit/

Only thing I found from M$ relative was:
Blue Screen STOP Message C0000135 Appears at Startup

Did you remove the NIC from the control panel ( system/hardware/device manager ) before you shut down and removed it ?

Maybe you might try reinstalling it, then removing the drivers for the second NIC first, before you physically remove it.

XP does not like hardware changes!

AS far as Linux, were they different NICs ? If you have two of the same type NICs the drivers will be loaded as modules, but may be part of the kernel if they are not of the same type.

Why did you remove the second NIC ??

Its definetly not the processor.

I think this has nothing to do with hardware, and its more of a s/w problem

Just re-install ur OS and hopefuly u will be ok.


Cheers:)

If it doesn't boot in safe mode, its likely hardware. A bad memory stick can cause this error, and is pretty easy to troubleshoot, provided you have more than 1 stick in your box, or some spares laying around.

One caveat to that though, where does it give the STOP message when you boot, particularly in safe mode?

Hi.

1. It is NOT the CPU.......................it would not POST if it were.
2. It is NOT the RAM.......................you would have had an error message during POST
3. I doubt if it is the HDD, they tend to work or not? Although it is a possibility, so check the connections, you might have moved something when you took the NIC card out?

Sounds like software corruption to me.

I suspect the sneaky security "feature" in XP, that maps to your hardware configuration to stop you ripping off Uncle Bill by loading the software onto more than one machine. You changed your hardware environment. As has already been said "XP doesn't" like that :(

How do you boot into RedHat..............I would imagine it is through XP?.....so if XP is in trouble, you may not get a clean shot at your RH boot?............I guess if all else fails you might have to reinstall XP, but try the repair option first.

I had a load of problems with XP at first due to adding hardware I think.............it is quite stable now, but I must have re-installed 3 times to get there. My own fault ....I should have finished building the machine first :D


Good luck

Not to argue Nihil, but I just had a system that was had run fine for over a year and then started giving STOP 0As at boot. Wouldnt get in with safe mode, wouldnt reinstall, etc. Turned out it was a bad dimm. The memory tester in bios isn't the best, to really check a stick of memory you need to run a good utility against it. I've also seen this with a bad bios chip on the board. Particually a K7N2 Mb with an athlon 2400, system got hosed, would post, detect all the hardware, but did the fun stop messages at boot, and funnily enough, if you went into the bios setup, and just let it sit long enough, it would lock up in bios setup too. Seemed to lock or generate a stop after about 2 minutes of being up.

Trying to boot into redhat is a good suggestion, if he boots into it and it has a kernel dump or whatnot, that might help pinpoint the problemo.

I actually experienced the same problem very recently. I tried safe mode and still the same message. I thought the motherboard was failing so I replaced that. Still I received the same error, even after a format and reload. Then I switched memory and hard drives and still received the same error message. Then I swapped operating systems and still the same message. I found out researching the error message it could have been almost anything, but then I swapped out processors and it booted right up. this error message seems to be the worst because what I have read varied from the OS being the problem to RAM being the problem....So my advice would be to swap parts out and test if you have spare parts. This was a funny problem for me because I knew it couldn't be the processor and I was wrong. I would at least give a CPU swap a chance because it definitly worked for me.

I`m having the same problem with one of my boxes at the moment, i havn`t had chance to sort it yet but i`m leaning towards it being a problem with the hard drive or ide cable. have you tried a diffrent ide cable and hard drive on your computer? if you havnt then it would be worth trying.
failing that then RebelToTheEnd`s advice is you only route.

mark

it didnt boot when i put the nic back in, i took that nic out cause i used to use it as a firewall, for testing and stuff, i had two in it. so i took one out, to use a couterstike machine, and it gave me all this mess. but i will try reloading everything, and formating in ntfs. then load red hat 8, if that doesnt work, then just gonna go through the long process of redoing everything. lol, try first w/ the cable and go one by one, until the ram and procesor. thanx for all your guys help though.

i just thought i`d follow up on my earlier post. I got round to fixing the box that had the same errors, it turned out to be just the ide cable, i swapped it over and now theirs no problems.
It may not work for you but its good to know that things can be fixed so cheaply! :)

mark

lol, i ran throuhg everything including ide cabels, even took the processor out, started it up, and then re sat it after it was power down, it worked for my other machine that had some prob. but anyways got to the ram, the slots are all filled up w/ 3 128 sticks of pc133 ram, so i took them all out, and resat them one by one, until i got a error, it happened to be just resitting the ram for some reason, cause the box runs w/ no prob at all. no errors, in fact jus got done installing red hat 8, w2k, and xp. but thanx for the advice for future errors on other machines. thanx