Stop error, blue screen in XP

Achtung

Senior member
Jul 31, 2001
656
0
0
My computer recently crashed while I was playing NHL 2002. Now, when I start it up, I get this blue screen telling me this:

The BIOS in this system is not fully ACPI compliant. Please contact your system vendor or visit http://www.hardware-update.com for an updated BIOS. If you are unable to obtain an updated BIOS supplied by your vendor that is ACPI compliant, you can turn off ACPI mode during text mode setup. To do this, simply press F7 key when you are prompted to install storage drivers. The system will not notify you that the F7 key was pressed-it will silently disable ACPI and allow you to continue your installation.

Technical Information:
*** STOP: 0x000000A5 (0x00000011,0x00000006,0x00000000,0x00000000)


I can't startup Windows, and I have no idea how to fix this. I tried going to the Gigabyte website (my board manufacturer) and getting a BIOS update, but apparently you can only do the update through Windows.

I think I've seen this error once before, but a simple hard boot fixed it. This time, nothing works, not even trying safe mode. Please someone tell me I'm not seriously f*cked here.... :(

Thanks for any help you can provide.
 

Achtung

Senior member
Jul 31, 2001
656
0
0
It appears to be a Dual Bios motherboard (GA-7VRXP). Actually, when I first started the computer, I got a CMOS Checksum error, and the only way I could get past it was to reset the values to default. But when I did that, I lost my settings for time/date, as well as the IDE settings. I went through auto-detect and it found everything just fine, so I assumed the problem was fixed. Maybe I screwed something up that way?

Thanks.
 

AndrewNF

Senior member
Sep 1, 2001
284
0
0
I've seen this message come up from a bios settings change on my old BX board. One possibility is changing the "ACPI enabled" setting. Turning off ACPI after Windows has been installed can stop it from booting. Turning it on may also cause problems, but I haven't seen that myself.
I've also seen similar stop errors from manually setting RAM too fast (also on a BX board). Slow down the CAS latency from 2 to 2.5 or 3, or set it to SPD auto dectect.
 

Achtung

Senior member
Jul 31, 2001
656
0
0
Well, my CAS settings are auto-set to 2.5 (the setting listed on my RAM chip), so I cant seem to change those. How would I change the ACPI setting? Is that in the BIOS setup?

Right now, it really seems like its something in the BIOS. I just wish I could narrow it down a bit more.
 

Achtung

Senior member
Jul 31, 2001
656
0
0
Any idea if I should load optimized defaults? Or how about fail-safe defaults? I'm not sure if that would make the situation worse.
 

busmaster11

Platinum Member
Mar 4, 2000
2,875
0
0
Originally posted by: Achtung
Well, my CAS settings are auto-set to 2.5 (the setting listed on my RAM chip), so I cant seem to change those. How would I change the ACPI setting? Is that in the BIOS setup?

Right now, it really seems like its something in the BIOS. I just wish I could narrow it down a bit more.

Achtung,

Since your roommate Nick told me about this, lemme just try my hand in here...

Have you tried Andrew's suggestion of toggling off ACPI?

You often get a CMOS Checksum error after clearing CMOS or after flashing it. Do you get it every time? If only once, it's nothing to worry about and you can try setting to failsafe defaults, then changing things one by one afterward. My hunch is that it somehow got fried, and your board wasn't able to goto the backup BIOS or something.

You need to let us know the board model and revision, BIOS revision, and exactly when this error occurs and if its precisely duplicable...

 

Achtung

Senior member
Jul 31, 2001
656
0
0
Well, I've tried looking for a way to toggle off ACPI, but I can't seem to find it in the BIOS. It might be set differently or something.

I have a Gigabyte GA-7VRXP, running "AMIBIOS SIMPLE SETUP UTILITY - VERSION 2.00". I'll give you a rundown of what happened to lead up to this problem:

A few days ago, over winter break, I had a crash, which I thought was caused by a problem with my video driver. I didn't use my computer for the rest of break, and I brought it back to school with my on Wednesday. When I started it up here, I got a CMOS Checksum error, and it said I should reset my CMOS settings to their default values, which I did. When I started up the computer again, it informed me that Windows had not properly shut down, and it asked me whether to Start Windows normally, go into Safe Mode, or use the last settings that worked. I chose the last option. At that point, I got the blue screen that I haven't been able to resolve since. So the problem is most definitely reproduceable.

Here's what I suspect--one of two things happened.
1. When my game crashed, it somehow screwed up my BIOS settings when I had to reboot without properly shutting down Windows, or
2. In transporting my computer back to school in my car, some hardware could have gone bad.

Thanks again for all the help! :)
(This is also posted in the Motherboards forum, since I figured it wouldn't fall off the first page so quickly in there--sorry about the x-post)
 

busmaster11

Platinum Member
Mar 4, 2000
2,875
0
0
Originally posted by: Achtung
Well, I've tried looking for a way to toggle off ACPI, but I can't seem to find it in the BIOS. It might be set differently or something.

I have a Gigabyte GA-7VRXP, running "AMIBIOS SIMPLE SETUP UTILITY - VERSION 2.00". I'll give you a rundown of what happened to lead up to this problem:

A few days ago, over winter break, I had a crash, which I thought was caused by a problem with my video driver. I didn't use my computer for the rest of break, and I brought it back to school with my on Wednesday. When I started it up here, I got a CMOS Checksum error, and it said I should reset my CMOS settings to their default values, which I did. When I started up the computer again, it informed me that Windows had not properly shut down, and it asked me whether to Start Windows normally, go into Safe Mode, or use the last settings that worked. I chose the last option. At that point, I got the blue screen that I haven't been able to resolve since. So the problem is most definitely reproduceable.

Here's what I suspect--one of two things happened.
1. When my game crashed, it somehow screwed up my BIOS settings when I had to reboot without properly shutting down Windows, or
2. In transporting my computer back to school in my car, some hardware could have gone bad.

Thanks again for all the help! :)
(This is also posted in the Motherboards forum, since I figured it wouldn't fall off the first page so quickly in there--sorry about the x-post)
Are you able to go into safe mode at all?

My guess is your firmware fried; but before replacing your mobo I'd try something like this to be sure its not the memory:
http://www.simmtester.com/PAGE/products/doc/docinfo.asp
 

Achtung

Senior member
Jul 31, 2001
656
0
0
Looks like its fixed. :)

I had to buy a new floppy drive, which was apparently why I couldn't get the new firmware flashed into the BIOS. And actually, I didn't even need to go into DOS to flash it, since Gigabyte's Award BIOS has a utility allowing me to flashit from within the setup. I'm wondering if something is still off though, because I'm actually using the backup BIOS (its a Dual BIOS mobo). That's something I might look into later on. For now, I'm just glad its working.

Thanks!