Dang blue screen!

Bobo

banned
If I leave my computer on for too long (20hrs+) it comes up with this message:

A problem has been detected and Windows has been shut down to prevent damage to your computer.

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you have seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. Ask your hardware or software manager for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select advanced startup options, and then select safe mode.

Technical information:

***STOP: 0x0000000A

(0x00CEBA10,
0x00000002, 0x00000000, 0x8051162F)

I have not installed any new software, but I put another stick of RAM in about a month ago. I have WinXP Home, SP2

Basically I'm asking, is this a major problem? Or just an OEM quirk?

I Googled for this, and Microsoft said that it is usually a hardware problem. The RAM that I put in, I had had in before, took it out, and then put it back in. It said to disable caching, shadowing, etc in the CMOS, but I couldn't find it.
 
Last edited:
Trippin...

well if your runnin your comp for that long then the RAM stick may be overheating or something onthe mobo... i suggest checking running temps so on...
 
mad_hatter said:
well if your runnin your comp for that long then the RAM stick may be overheating or something onthe mobo... i suggest checking running temps so on...

How? The only temp that I know is the HDD, about 95*F
 
I had looked there, and it says for problems during or after the installation of Windows. Like I said, i have not installed any new hardware or software in the last month, the RAM was about a month and a half ago. That's why this is so confusing me
 
Cromewell said:
how about testing the RAM too see if some of it is bad?

I had used it before in another computer for a couple of months and nothing ever happened, but it wouldn't hurt.

Memtest? Or do you have a better suggestion?
 
Cromewell said:
nope, memtest is good :)

I ran that, and after about 5 min the start bar and the icons disappeared, and the system froze up, and I had to restart it.

Edit: Actually that was probably my screensaver trying to come on:oI'll disable that next time.

I'll prolly run it overnight (tonight)
 
Cromewell said:
take the heatsink of a AthlonXP while its under load, that'll make some good fire

I don't have any XP's, I have a K6/2 333, an Intel P1 233, and an Intel p2 533, only the AMD and the p2 have SIMMs, the P1 doesn't, which sucks, that's the one I wanted to smoke out:mad:
 
take the heatsink of a AthlonXP while its under load, that'll make some good fire
Been there done that ... no fire ...... fire only happens if the thermal diode fails :P (makes me question the kinda mobo THG was using when they did that)
 
they had a board where the thermal diode couldnt measure the increase fast enough, it's supposedly been fixed but if you have an old revision board it can still be done
 
they had a board where the thermal diode couldnt measure the increase fast enough, it's supposedly been fixed but if you have an old revision board it can still be done
Heehee gotta find me an older board :P

was there heavy smoke?
Uh ... there wasnt even smoke ... the thing terminated itself when it hit 85C

WTH is a thermal diode?
Think temperature probe


Anyways ... back on topic...
 
Praetor said:
the thing terminated itself when it hit 85C
too bad....:D

Praetor said:
Anyways ... back on topic...

please!

I still don't think that this is a mem problem. The memtest got up to 500% coverage until the comp froze, so it apparantly isn't an obvoius problem
 
Back
Top