Printable View
OK, my computer's pretty old but it's not that bad...
AMD K6-2 500MHz
SOYO 5EMA+ m/board
256MB PC100 SDRAM
15GB HDD
3dfx Voodoo3 2000
SB Live!
Windows XP sp1
Just recently it has started rebooting (ie. as if I am pressing the reset button) when the computer is under heavy stress - eg. when gaming or converting mp3s.
Anyone got any ideas as to what's causing this? My first thought is overheating, but why would I start having problems now after years of running stably?
I have the same problem sometimes. Im running AMD 1000mhz and when it restarts understress. I thought overheating as when it got to 49 it restarted its self and I noticed its done it twice at that temperature. If you find a cure send it my way too please Lamsey!
Go to Start>Control Panel>System>Advanced>Startup and Recovery - settings>Remove the check mark in System Failure [ ] Automatically restart.
Now when you load your system... It will not restart but it will give you an error message. You can then use that error message to diagnose the problem.
Thank you Somebody1234! Will try this later when it's not so very, very late!
hi i have had this problem before after buying new h/d and motherboard (from recomendation of so called pc specialist :angry: )i found the problem to be the ram. :rolleyes: spent £200 on a £50 fix <_< good luck ;)
The cpu and video card fans may have filled up with dust/grit over the years and it's making them less effective.Quote:
Originally posted by Lamsey@3 June 2003 - 20:17
Anyone got any ideas as to what's causing this? My first thought is overheating, but why would I start having problems now after years of running stably?
A good cleaning might help...
kick the thing!
Or make yourself a lovely shiny new computer and give that one to me! (after you've fixed it...)
:lol:
Three main causes for a spontaneous restart:
Ram failure- diagnose with DocMem from simtel. (posted in software today) A major source of blue screens in win9x
PowerSupply problem- Do you ever smell burning rubber or is there a lot of heat coming from the exhaust?
Extremely incompatable software- normally though you'd get a dump message or blue screen with this.
OK, I did what Somebody1234 said, and I got a blue screen instead of a reboot.
Here is what it said:
:blink:Quote:
Originally posted by The Blue Screen Of Death
A problem has been detected and Windows has been shut down to prevent damage to your computer.
IRQL_NOT_LESS_OR_EQUAL
.....
.....
.....
STOP: 0x0000000A (0x0000031C, 0x00000002, 0x00000000, 0x804F1542)
Contact your system administrator for details.
ah my old enemy, the IRQL_NOT_LESS_OR_EQUAL screen, I take it your using XP? Get yourself service pack one, worked for me, install and watch your prob float away......
could be a hardware problem or a virus (if a hacker gets in your system... there are many ways to mess it up without antivirus warning)
As I already said, I have XP with sp1.Quote:
I take it your using XP? Get yourself service pack one, worked for me, install and watch your prob float away......
It's not a hacker, as the problem started before this computer became online (which was yesterday).Quote:
could be a hardware problem or a virus (if a hacker gets in your system... there are many ways to mess it up without antivirus warning)
Hardware? I still think it might be overheating. Must try to improve cooling...
Unless anyone else has any ideas?
I had this once before. It occurred after i'd installed a modem driver which XP didn't like. Having rolled back all was ok once again.
Thinking back, there are quite a few ms knowledge base articles on it. It's to do with hardware/driver /XP compatibility. Are you sure you haven't installed any new drivers? Or maybe a windows update is causing a conflict.
If you want to rule out overheating take the side off your box, maybe turn it on it's side- heat rises.
Good Luck mate!
I haven't installed any new drivers for a long time... don't see why it would suddenly start happening now if it was a driver issue.
I haven't cleaned my fans for a while, so I'll try that soon, see what happens.
Wouldn't turning the box on its side affect the workings of the drives?!
:blink: [/b][/quote]Quote:
Originally posted by Lamsey+4 June 2003 - 16:41--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (Lamsey @ 4 June 2003 - 16:41)</td></tr><tr><td id='QUOTE'> OK, I did what Somebody1234 said, and I got a blue screen instead of a reboot.
Here is what it said:
<!--QuoteBegin--The Blue Screen Of Death
A problem has been detected and Windows has been shut down to prevent damage to your computer.
IRQL_NOT_LESS_OR_EQUAL
.....
.....
.....
STOP: 0x0000000A (0x0000031C, 0x00000002, 0x00000000, 0x804F1542)
Contact your system administrator for details.
Sorry for the delay in answering you, Lamsey.
Go to Microsoft Knowledge Base with that information. Most likely you will find the solution there. Sorry that I have not gone to research it myself as I don't have the time right now.
If I have some time a bit later I will look it up.
Good luck. :)
I love those specs! some of the best stuff I've used and still do use occasionally.Quote:
AMD K6-2 500MHz
SOYO 5EMA+ m/board
256MB PC100 SDRAM
15GB HDD
3dfx Voodoo3 2000
SB Live!
Windows XP sp1
Windows Update had a driver for the AMD K6-2 that they kept trying to install onto my AMD XP 2000+
I have No idea what that was all about but I just kept declining and I see now it's been corrected.
If it's a real driver update then it might help to look into it.
Have you run all the c:>chkdsk /f /r repairs yet?
If it's IRQ related maybe after running checkdisk, reset CMOS and start with defaults loaded or change the IRQ assignments in BIOS from auto? to something else, then restart and set them back to auto again.
If it's a CPU heat problem, usually it stops dead, shuts down, and maybe restarts (sometimes repeatedly) or it might wait a while. you won't see any thing on screen because it terminates all power at the critical point where it overheats.
itz the motherboard... itz a safe fail switch thing... happens to me too
i got a
umm
asus motherboard p4e75 <-- something like that
2.66 ghz procesor
512 ram
80gb hard drive
ati radeon 9000
windowz xp corporate
+ wen running alot of programs like
n64 emulator, winamp, photoshop, microsoft word <-- it just resets on me...
might be the video card :/ since it only resets when im using the n64 emulator with other programs
edit >> i have 6 fans!! so i doubt there will be any overheating... :/ curious...
OK... will try MS KB, then will tinker with BIOS.
Thanks for the help guys - will let you know how I get on...
@Lamsey,
I wanted to say that I looked into the KB. Boy that's a f**ed up site at MS. :lol: Anyway I am still looking into that error code. I just found out that MS has a 9 CD set that is used to analize those codes. I'm not sure what the CD set is called??? Looking into that too. :)
It may be easiest at this point to do a flash of your CMOS to the latest revision. Reset the CMOS and make sure all the settings are to the base settings for your hardware (No overclocking or pushing the RAM). Remove your RAM module(s) and clean their contacts with an eraser and make sure the slots are clean then reinsert them. Try it like that. If that doesn't work...
It might be easier to do a clean install of your Windows than diagnosing it with the KB. You could try that on a spare HD if you have one handy. That way you can test to see if it's a software or hardware based problem.
Hope this helps you.
I've just been on that KB and I've come to the conclusion that it's damn near impossible to find anything out from MS.
Will try cleaning up my case and the components. Then I'll see about mucking around with BIOS... :ph34r:
edited to say thanks for continuing help :beerchug:
I've always found MS TechNet ResourceKit site useful to diagnose errors:
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
Step-1: Check Your Software
Step-2: Check Your Hardware
Have you ever wondered about these as well?
Common Stop Messages
Hmmm...AMD does jack-all for heat protection so I don't think it's that. They overheat-they die is how AMD seems to go (I've killed 3 oc'ed procs when cooling failed). Try to run a walking ones pattern through the RAM, most of the diagnostic software packages can do it. It will determine if the RAM's dropping bits.
thats ecxactlly what i did and instead of just reebooting i get one of those fatal brain dumps. did SORT of solve my problem. i lifted my pc an inch of the carpet that helped lol. try it it increases the airflow in the case, therefore reducing temperature.Quote:
Originally posted by Somebody1234@4 June 2003 - 02:31
Go to Start>Control Panel>System>Advanced>Startup and Recovery - settings>Remove the check mark in System Failure [ ] Automatically restart.
Now when you load your system... It will not restart but it will give you an error message. You can then use that error message to diagnose the problem.