Blue Screen Error

[Ansar]

So, I got a blue screen today...not that blue screen of death, but it basically says this:

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

A process or thread crucial to system operations has unexpectedly exited or been terminated.

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

...(check to make sure new hardware/software is properly installed - else, call manager)... I haven't installed any new hardware or software...

If this problem continues, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. ...recommendation about using Safe Mode...

Technical Information:

*** STOP: 0x000000F4 (0x8601C020, 0x8601C194, 0x805D1204)

Beginning dump of physical memory
Physical memory dump complete.

What's in bold is what confuses me. What is BIOS memory and how can I disable those two things: caching and shadowing...and will that stop this blue screen from appearing.

Also, any idea as to what the Technical Information means?

Thanks so much,
ansar

(I'm typing this from another computer, by the way. The one that has the blue screen doesn't last more than 5 minutes before the screen shows up...

 

[aimeeandbeatles]

I don't recommend messing around in the BIOS unless you know what you're doing. Lots of things can go wrong.

Have you tried resetting the CMOS?
http://www.computerhope.com/issues/ch000976.htm
If you don't know what a CMOS is, I'd recommend either finding a geeky friend or a local computer shop.

It can also be possible the CMOS battery is dying, and the settings are being "forgotten" between boot. (This is happening to my computer -- the BIOS keeps starting up in "safe mode" and nagging me to reset the processor frequency. I haven't changed anything!) You can usually pop the battery out of the mobo (make sure to ground yourself) and replace it. Either take it into a computer store or a pharmacy, they give you a new one, not too expensive I think.
http://www.computerhope.com/issues/ch000239.htm

 

[Cutlass]

You can go into the BIOS and change those settings as recommended. If the problem is recurring, and a new problem on an old computer, your longer term problem could either be a core Windows problem that will need a reinstall, or a hardware fault that's new.

 

[Ansar]

How do I go into the BIOS though...and aimee, do YOU know how to work this BIOS? I would imagine if they're telling the user such a detail, it can't be too complicated...

 

[aimeeandbeatles]

I don't know exactly what BIOS you have, but if you google the name, you can sometimes get a manual. (It usually says on the BIOS startup screen, the type of BIOS you're using. If I'm right, there's only a few main kinds.)

I found that on mine, if you unplugged the keyboard, it would make it pause at this screen so you can write down the info.

For example, my BIOS is a Phoenix Award BIOS.

 

[Maniacal]

To get into the bios usually you have to press DEL (the delete key, at least on the ones I've seen) during start up (text will appear usually at the bottom of the screen BEFORE windows begins to load). You will have a very short time to press the correct button.

 

[aimeeandbeatles]

My BIOS says to press, I think it's either F1 or F10.

 

[Maniacal]

It probably differs from vendor to vendor and version to version. I have an ASUS mobo.

 

[Padma]

Different BIOS vendors use different "entry" keys. DEL is what I have seen most, but I have also seen F2 and F12. I am sure there are others.

When you boot the computer, you should see a screen for a short while that says something like "Press DEL to enter setup". That's talking about the BIOS. Hit the requested key, and you will be taken to a DOS-like "Window", where you can make the changes needed. Most I have seen will include a line or two of navigation help at the top/bottom, like "PG DN for next screen, F10 to save, ESC to exit". You may have to explore a little to find where memory options for caching and shadowing are located. Make and save the changes, and when you exit the bios it will auto-reboot, to run with those changes. Let it come up to Windows, and see if it fixes your errors.

 

[GravityWave]

IIRC it usually tells you to disable BIOS caching and shadowing as a standard precaution - if you hadn't changed them before the crash it is unlikely they have anything to do with it, but it is probably worth a shot.

Personally I would try pressing F8 (keep tapping it if necessary) during startup to bring up the Windows boot menu and run Windows in safe mode. If it still crashes and you have Vista see if you have time to get to the Control Panel/Administration Tools/Memory Diagnostics and schedule a boot time memory test and also see if you can get to Control Panel/Administrative Tools/Computer Management/Event Logs and see if that sheds any light, else try disconnecting any hardware you don't need to boot the PC then enter BIOS and reset it to the factory defaults and then boot in to safe mode again and see if it crashes. If you have multiple sticks of RAM try with only 1 stick and then swap it with an other.

If it doesn't crash at all in safe mode then jump to the Control Panel, Administrative Tools/Computer Management/Event Logs and see if there is specifically something falling down and then try googling it. If not probably the easiest thing to try is a system restore point from a time when the PC was working... otherwise it's disabling all your startup programs, followed by trying uninstalling all your firewall and antivirus software (best make sure your not connected to the internet for that one), disabling hardware and rolling back your device drivers, and finally the most fun - reinstalling windows.

This is what I would personally do ... so no guarantees.

 

[aimeeandbeatles]

There's a lot of google stuff about the Stop error you got. (I tried googling the exact one, but it came back to here.)
http://www.google.com/search?q=STOP+0x000000F4

 

[lndm]

I agree with GravityWave. The chance this has something to do with the BIOS is slim. This error can just as easily happen if the HDD is failing, RAM is failing, or a process is buggy or malicious.