Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: Bodhi on August 15, 2008, 04:29:00 PM
-
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
-
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.
-
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.
-
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.
-
And then to trun off the comp after writing all pertinent info,press the button and hold..
Falcon23 :salute
-
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
-
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.
-
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
-
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.
-
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
-
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?
-
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.
-
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).
-
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.
-
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.
-
I built the machine with anothers help in January / Febuary.
No new drivers installed. Not sure how to check the other two.
-
I built the machine with anothers help in January / Febuary.
No new drivers installed. Not sure how to check the other two.
When your machine starts to boot hit he pause button. There should be a BIOS revision number on the screen. Then hit enter to get it going again and enter the BIOS (usually the F12 or Delete key... check your mobo documentation). Go to advanced chipset features and somewhere within there there will be an option to set RAM timings. Just poke around... you'll find it. Go in there and see what they are and re-set them manually if they are not in spec. Then go to system voltages and check the RAM voltage. Set it to system spec if it's not there.
To get your RAM specs go to newegg or to your RAM manufacturer's web-site and do a search on your RAM part #. You'll see a set of numbers like 4-4-4-12 @ 2.0 V. Those are your timings and voltage.
[EDIT] I just went to the Abit web-site and the newest BIOS is version 16 released in March. It says "Fixed Quick Power On Self Test function abnormality" which may or may not be related to your problem.
-
BaldEagl,
No luck on that. Running out of options. Prolly end up taking it to someone to get the rest done.
-
Bohdi like Roy said its most likely a RAM issue.
pull all ram out accept 1 stick try em all see if any particular stick went bad on ya.
-
If the problem exists for all sticks of RAM, then I am going to lean towards the motherboard going toodles or the power supply.
-
Roy, we are going to try a reinstall tomorrow and see if that helps. Testing of all RAM, and hopefully Motherboard. Not sure what it will get us, but I am beyond my expertise.
Will advise as we figure it out.
Thanks to all for all your help.
-
Post your dump files here.
Left click my computer - system properties - advanced - startup and recovery - make sure you have "write an event..." enabled and under Write debugging information Small memory dump (64KB)
Then go to c:\Windows\minidump and locate the latest file and upload it and post link here, i'll take a look.
-
By the way, during the re-install, avoid installing IE7, and SP3.
-
Courious, why not install IE7 & SP3?
Wabbit
-
I found a serious problem when IE7 was inadvertently installed on a system here. Programs stopped flushing the video buffer.
SP3 caused a really odd series of problems with file ownerships in a new installation. I am still chasing this one down.
Still looking at what system files IE7 is replacing/updating as well. Seems some Vista system files found their way into the IE7 distribution which could be the issue.
It also may be a hardware and software combination problem. Still too early to tell. Just giving Bodhi a heads up so we have some common good ground to work from.
-
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
Bodhi,
I have just experienced the same problem as you have. About a week ago my system started acting up exactly the same as yours. I thought it may be software and restored my HD from an image from a month ago. After a bit the blue screen and reboot happened again and several more times.
I had built my system in March using Crucial Ballistix RAM. A month or so ago, I wanted to add 2 more GB of the same type but when I went to Newegg, the reviews really slammed the Crucial RAM so I held off buying it. Many failures happening within a few months of installation. Ah ha, a light comes on. I replaced my RAM with some Corsair and so far no reboots, everything fine. Try replacing your RAM, it worked for me.
Salute,
BeDee
-
The problem witrh Crucial's Ballistix line of DDR2 RAM is the voltage requirements. It is higher than almost all other suppliers.
I have been having really good luck with ASUS motherboards using G.Skill PC8500 RAM, where the FSB is higher than 800Mhz.
One of the key things to note when looking for DDR2 RAM is the voltage. It seems to be all over the place and some motherboards will not support more than 1.8V.
-
I'm using G.Skill in my Asus board. Good timings and was a great price when I bought it. $220 for 2gb back in Jan. '07, $80 for 2 more gb in May '07, and they probably run about $40 now.
-
The problem witrh Crucial's Ballistix line of DDR2 RAM is the voltage requirements. It is higher than almost all other suppliers.
I have been having really good luck with ASUS motherboards using G.Skill PC8500 RAM, where the FSB is higher than 800Mhz.
One of the key things to note when looking for DDR2 RAM is the voltage. It seems to be all over the place and some motherboards will not support more than 1.8V.
Skuzzy,
That is interesting about the voltage. When I selected the RAM to use during my build, I referred to Asus' Users Guide which listed a "Qualified Vendors List" and purchased the RAM from the list. Anyway, I believe my problem was with faulty RAM and am happy system is good to go, it's been running 2 days with out a hiccup.
Thanks for the tip to prevent the computer from automatically rebooting upon a system crash.
Salute,
BeDee
-
The recommended vendors list is a for sure 100% guarantee that the ram is going to work with the motherboard. But I've never referred to it when buying ram/motherboard (gamble I guess?). I've always taken it to as the recommendations for car parts in your car owners manual. Sorry Motorcraft, I'm doing fine without some of your parts.
-
Bodhi,
I have just experienced the same problem as you have. About a week ago my system started acting up exactly the same as yours. I thought it may be software and restored my HD from an image from a month ago. After a bit the blue screen and reboot happened again and several more times.
I had built my system in March using Crucial Ballistix RAM. A month or so ago, I wanted to add 2 more GB of the same type but when I went to Newegg, the reviews really slammed the Crucial RAM so I held off buying it. Many failures happening within a few months of installation. Ah ha, a light comes on. I replaced my RAM with some Corsair and so far no reboots, everything fine. Try replacing your RAM, it worked for me.
Salute,
BeDee
I used Corsair memory. Memory has tested fine. It appears to be a motherboard issue. Abit's customer service sucks butt. I ordered a board from ASUS this afternoon. When I get it, I am going to file a complaint with my CC company with regards to the MB purchase and see how Abit likes that.
-
It was the motherboard. Replaced it with a new ASUS board, and I am no longer having the issues.
ABIT sucks the proverbial donkey stick though... still can not get them to refund my money or take the POS back.