The Shootist
|
 posted on 13/7/04 at 08:51 PM |
|
|
Hey Terry....
I may have missed it, but did you try another Power Supply.
I had a brand new 430W True Power that would shut-down if you bumped the table.
Also are you running XP, Win 2K, or any other NT variants? These will restart on error as default from the install. You can disable this auto reset
function to diagnose problems.
MS put in the Auto Reset function because their OS BSOD's so often that servers must be able to reset themselves.
|
|
|
|
|
Spyderman
|
| posted on 14/7/04 at 12:38 PM |
|
|
I have not tried another power supply as I didn't think it was that (could be wrong tho' ). It is hapening to two different computers.
I hope it is not the psu as I bought it from Ebuyer.com and they are B.....ds for ignoring their returns requests. Have had some fans waiting for
three weeks to return as they arrived damaged.
I'm running XP and have now disabled the auto-reset, thanks Pete. If we'd had a cat and I'd cought it any where near my PC it would
be getting flying lessons!
I'm awaiting next error now. When it did go to BSOD it usually showed "Machine_check_exception", but I don't know what that
means!
Thanks for the help so far guys!
Terry
Spyderman
|
|
|
pbura
|
| posted on 16/7/04 at 09:39 PM |
|
|
Terry, did you get your trouble resolved? According to Microsoft, your hardware supplier should be able to explain the codes:
http://support.microsoft.com/?kbid=329284
Looks like a warranty issue!
Pete
Pete
|
|
|
Spyderman
|
| posted on 17/7/04 at 11:47 PM |
|
|
Pete, no joy yet!
Have checked with component web sites for compatability errors and only hint was for graphic card. Downloaded newest drivers and it crashed!
I tried it with a different card and had the same issues.
It is definately more stable before SP1 is installed. In fact it is impossible to use after!
I am getting different BSOD errors showing now like "IRQL not less or equal, page fault in non paged area and the latest - Stop:c00002a {Fatal
system eror}"
Have been in touch with suppliers and they have replaced MB and memory. They seem to think it is software based.
Disabling the auto-reset has made no difference, it is still going to BSOD.
Terry
Spyderman
|
|
|
pbura
|
| posted on 18/7/04 at 02:34 AM |
|
|
Terry, this is an ugly problem. Check this out:
http://www.hardwareanalysis.com/content/search/results/?Keywords=irql+not+less+or+equal+xp&Where=1
Disabling the auto-reset was so that error messages would display so you can record them. They typically tell what driver is causing the problem, or
give a memory address from which you can identify the device that is acting up. Take a good read through Part VII, Appendix C of the XP Resource
Kit:
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd
_stp_hyzf.asp
Pay close attention to all the parameters of your error messages. Right now, I'm not sure if c00002a is part of the message code, or the area
of memory in which the error occurred. I suspect the latter, in which case you can identify the device by looking at the 'Resources' tab
of each device in Device Manager. Probably one of our techies has a better way 
I noticed that one program that causes both the "IRQL" and "non-paged" messages is Norton Antivirus. Apparently, Symantec has
some info on their website about "IRQL not less or equal" but I wasn't able to get at it because I don't have NAV.
Another suspect area is unsigned device drivers. Here's an article about how to identify iffy drivers and test them:
http://support.microsoft.com/default.aspx?scid=kb;en-us;308514&sd=tech
The XP Resource Kit has a very thorough troubleshooting section for stop messages, with hex dumps and debuggers ad nauseum. I'm sure
you'll be able to figure it out.
Please feel free to post more details of error messages, etc. I'd be glad to help any way I can.
Pete
Pete
|
|
|
Spyderman
|
| posted on 27/7/04 at 11:27 PM |
|
|
Pete, the second link you give does not work (resource). Any other links?
In the past twenty minutes this damn thing has either reset or gone to BSOD at least six times.
It is not consistent with the errors either, but most often is usually "irql not less or equal" or "stop 0x0...." and a
different end code "7f, 8e, 0a" etc.
Whatever I try has so far been in vain. I'm almost suicidal at the moment!
Terry
Spyderman
|
|
|
pbura
|
| posted on 28/7/04 at 12:14 AM |
|
|
Terry,
The link's OK, just not opening to a particular page I had it on. Use the index tree over on the left side to open up Part VII, Appendix C.
Everything you ever wanted to know about BSODs, and more.
The main thing is to capture all the information from the error messages, then either call Microsoft or go through the troubleshooting steps described
in the same appendix.
Just had an idea: use a digital camera to record the buggers.
How's the computer in safe mode? If it's OK then, that would indicate a bum driver.
Computers are significantly less complicated than, say, TV sets. You'll beat the bastard, so keep your chin up and, uh, stay away from sharp
instruments
Pete
Pete
|
|
|
hortimech
|
| posted on 7/8/04 at 12:43 PM |
|
|
why hasn't anybody suggested the best cure for this possible software problem.
format the hard drive and install some variant of linux, just think no BSOD, no virus problem, best yet no IE problems. If you go and buy one of the
linux mags at the moment it will only cost you the price of the mag for SUSE 9.1.
I run mandrake 9.2, this has been up now for 6 months nonstop.
Why does everything happen to me
|
|
|
Spyderman
|
| posted on 9/8/04 at 01:28 PM |
|
|
I have tried Linux in the past, but could not get used to it. It was like stepping back in time and working with DOS!
Plus there is the problem of running current software that depends on MS Windows. Virtually every piece of software I own or use needs Windows. I
don't know enough and would guess most others are not enthusiastic enough to learn Linux. I just want something to do what it says on the tin!
A reason I am not to keen on new cars is the inability to tinker without first getting a degree!
Terry
Spyderman
|
|
|
Spyderman
|
| posted on 8/4/05 at 05:01 PM |
|
|
I think I finaly found out what the problem was all along with both computers!
It turned out to be the co-processor fan on my older machine. Was still running but started making noises. Replaced it and it has not missed a beat
since. Ironically before discovering the problem I installed Suse 9.1 Linux on it and it proved very reliable and extremely stable. I now run this
constantly on this machine.
My newer machine which is now a year old, turns out to be the processor causing the problems. Even though this had been sent back twice and they say
is working fine. This time when it came back with the MB the Bios was set to processor type 1500/266. I tried it at this setting and it seemed very
stable. The processor is an AMD 2600/333. I altered the Bios to 2600/333 and it would not even boot. Same with 2600/266 setting.
When set to 2400/266 it is running ok, but seems to take a while after booting to settle down. Can't check email for about 10 mins after
booting.
Looks like they have been testing the processor on minimal settings and refuse to replace it. Shan't buy anything from Komplett.co.uk again.
Anyone know where I can get an Athlon 2600/333 for a good price?
Might even try upto 2800 if cheap enough as that is all my board will take I think.
It seems strange that processors that are so dependent on good heatsinks have such small heatsink pads on them!
Terry
ps. Vince, did you ever get yours sorted?
[Edited on 8/4/05 by Spyderman]
Spyderman
|
|
|
Peteff
|
| posted on 8/4/05 at 06:50 PM |
|
|
I altered the Bios to 2600/333 and it would not even boot
It sounds more like memory not clocking up problem than processor. My mate had some extra fitted by someone because his cad program was crashing and
when it came back it was running as 1100 processor instead of 1600 and memory as pc100. The memory was taken back and tested and proved faulty,
replaced and now runs normal again. I've just had mine in bits, win2000 memory paging stop error. I reseated everything and cleaned the dust out
and it's working now. edit:- What's the heatsink pad? The square bit in the middle of Athlons is the processor core. I usually scrape the
heatsink goo off and replace it with some arctic silver compound.
[Edited on 8/4/05 by Peteff]
yours, Pete
I went into the RSPCA office the other day. It was so small you could hardly swing a cat in there.
|
|
|
Spyderman
|
| posted on 10/4/05 at 12:13 PM |
|
|
I have had the memory changed several times and it has not altered anything.
The only components in the PC that are the same as when the problem started are the graphics card and the processor. The graphics card I checked by
swapping in a different card and made no difference.
The memory is DDR400.
Spyderman
|
|
|
