BSOD Stop error

Over the past year I've have had some BSOD Stop errors, had one about a month ago. A minidump was never created or should I say I could not find it at all. Everything is set up to create one. :confused

Here's today's Stop error message after udgrade installations of Mozilla Firefox and Opera, then restart of computer.


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


If this is the first time you've seen this 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.
If this is a new installation, ask your hardware or software manufacturer
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: 0x00000022 , 0x000202EF, 0x803009C30, 0x830009B78, 0x829CF200


Beginning dump of physical memory Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.

 

after doing some research, that error seems to be a hardware error. have you installed any new hardware recently?

http://msdn.microsoft.com/en-us/library/ms818901.aspx

maybe you should run scandisk to check your disk for errors, that's all the help i can give you right now.

 

No. The Stop error messages all happened after updating, upgrading, un/installing programs.

 

Most common causes of BSOD is RAM and video.

try booting from a memtest86 disk
http://www.memtest86.com/

Also, if you have a different video card or can switch to on-board video, see if that helps.

 

I also did some quick research, and there's very little info on the 0x00000022 BSOD error. However, it may also be due to a possible file system problem. Boot to your XP install disc, and enter the Recovery Console. Once you're at the prompt, type chkdsk c: /r and press Enter. It may take some time (like over 6 hours) so be patient. If it appears to lock up, or if you see the progress percentage indicator go backward, don't worry... this is normal, and it hasn't locked up. Just wait and it will finish. When it's done, type exit and press Enter to restart the PC, and remove the XP disc from the drive. If you don't have a Windows disc (which is needed to get to the Recovery Console unless it was installed previously), and if you can still get to your desktop, click Start > Run and type cmd and press Enter. This will open a command prompt Window. Type the chkdsk command, and it will ask if you want to force a volume dismount (answer NO) and if you want to schedule chkdsk to run at the next reboot (answer YES). Then type exit and press Enter, then restart the PC and chkdsk will start.

The following statement has no base in fact:

It should say "Some common causes of BSOD . . . " and not "Most . . ."

However, running full diagnostics on both your RAM and hard drive is always a good idea in a situation like this.

(NOTE: in the chkdsk command above, there is a space before and after the "c:" and if you don't use the spaces, the command does nothing)

 

Good point. Common causes of BSOD is RAM and Video.