CTD Issues

[Bodhi]

I am getting crash to desk top issues when I try to run AH2, any windows media files, and a couple other programs.  The screen goes quickly to a blue screen and then it reboots. 

After reboot, it says windows has recovered from a serious issue.  Says to update Bios.  but it also mentions a memory issue.  Computer is a

Abit IP35 Pro LGA 775 Intel P35
Intel core 2 E8400 3.0 Ghz
4 meg Corsair DDR2 RAM
768 MEg 8800GTX vid card
running XP

[Fulmar]

If you can, post what exactly the error messages say it would be most helpful.

On my old computer I suddenly would get random BSOD or reboots when playing games.  Sometimes I could play for 45 minutes and sometimes 4 minutes.  And the BSOD would mention something about the nvidia display driver.  Long story short, my PSU was going bad and during game play (increased power usage) the computer would crash/BSOD.  I had first thought drivers, then bad video card, and then BFG (video card company) told me to check my PSU - which it was.

[Bodhi]

Power Supply is less than six months old.

I can not get the blue screen to stop so I can read it....  the computer flashes it up, and then reboots.

[Skuzzy]

Right-click "My Computer", select "Properties".  Select the "Advanced" tab, then press the "Settings" button in the "Startup and Recovery" section.

Uncheck "Automatically restart" in the "System Failure" section.

That will stop the automatic booting when the operating system crashes.

[falcon23]

And then to trun off the comp after writing all pertinent info,press the button and hold..
                                                                        Falcon23

[Bodhi]

These are the two codes I have gotten after the reboot.

BCCode: 1000000a   BCP1: 00000016   BCP2: 0000001c   BCP3: 00000000   BCP4: 80502392   OSVer: 5_1_2600   SP:2_0    Product: 256_1

The second one was all the same except BCP4: 804FA11E

[Bodhi]

Right-click "My Computer", select "Properties".  Select the "Advanced" tab, then press the "Settings" button in the "Startup and Recovery" section.

Uncheck "Automatically restart" in the "System Failure" section.

That will stop the automatic booting when the operating system crashes.

Will try that right now.  Thanks Roy.

[Bodhi]

This is what I got on the blue screen after I did what Roy suggested.

IRQL_NOT_LESS_OR_EQUAL

Bunch of standard system advice like safe start and disabling new hardware.  Then:

Technical Info
*** STOP: 0x0000000A (0x00000017, 0x0000001c, 0x0000000, 0x804Fa11E

Beginning dump of physical memory
Physical memory dump complete

[Fulmar]

A few things I'd try...
- Make sure your BIOS is up to date.  Some companies provide changelogs to their releases and you can view if a new BIOS has corrected some related issue.
- Make sure your video card drivers are current.
- Check your audio drivers, either onboard or the sound card you use.
- Check your PSU voltages, either in the BIOS or using a program like Speedfan.
- Try running MemTest86
- If you have 2 x 2gb memory chips, try just using one chip and testing your system out, then try the other.  If you're using 4x1gb chips, try using one pair at a time, or one chip at a time and repeat (I know time consuming).
- Make sure your system temperatures are normal during idle and load
- Run a Checkdisk for HD errors.
- Double check BIOS settings with the user manual, make sure something goofy or IRQ conflict is coming up.

[Fulmar]

UPDATE:
Error Message:

IRQL_NOT_LESS_OR_EQUAL

Explanation:

This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

User Action:

This error usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If you encounter this error while upgrading from Windows NT 4.0 or earlier, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturers to obtain updates of these tools. For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. You should also run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows 2000 drivers. Disable sync negotiation in the SCSI BIOS, check the cables and the SCSI IDs of each device, and confirm proper termination. For enhanced integrated device electronics (EIDE) devices, define the onboard EIDE port as Primary only. Also, check each EIDE device for the proper master/slave/stand-alone setting. Remove all EIDE devices except for hard disks. If the message appears during an installation of Windows 2000, make sure that the computer and all installed peripherals are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://www.microsoft.com. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6077.mspx?mfr=true

[Bodhi]

Fulmar, I appreciate your help.  I am trying a system restore to a couple of weeks ago.  If this does not work, I am going to off load all my stuff to another drive and do a fresh install.

How do you update your bios?  Is there a utility that will do it for me?

[Skuzzy]

I have also seen that error occur with bad RAM.

Check the software first.  If iti s software it would not surprise me if you had to reformat and re-install Windows.

[BaldEagl]

How do you update your bios?  Is there a utility that will do it for me?

Go to your motherboard manufacturer's web-site and do a search for the latest BIOs.  They will likely have instructions.  If not come back here.

It's easy to do but make absolutely sure you don't power off at any time during the process (including unintentionally like during a thunderstorm).

[Bodhi]

still getting the problem.

Tried replacing all the RAM one by one.  That did not work. 

Tried removing windows media player.  That did not work.

abit-usa was not responding when I tried to get in... 

this is really frustrating.

[BaldEagl]

Is this a new machine or have you had it for a while?  Knowing this would be helpful.

Are your RAM timings and voltages set correctly?  That and the BIOS seem like the two most likely places to start.  Also, did you recently update any drivers?  You may not have properly deleted the old ones and are now getting a conflict.