[devil_himself]

==
1. Click Start, click Run, type "sigverif" (without the quotation marks), and then click OK.
2. Click Advanced.
3. Click Look for other files that are not digitally signed.
4. In the Look in this folder box, type "x:\Windows\system32\drivers" (without the quotation marks), where x is the letter
of the drive where Windows XP is installed.
5. On the Logging tab, make sure the Save the file signature verification results to a log file check box is selected, and then
click OK.
6. Click Start.

NOTE: The log file is named Sigverif.txt, and it is saved in the Windows folder. Attach It In Your Next Reply!
==

==
Go To Start > Run <> verifier > Create Custom Settings (For Code Developers) > Select Individual Settings From A Full List > Check Everything Except "Low Resources Simulation" > Select Driver Names From A List > Select "Not Signed" Drivers In Batches of "5".

Not Signed Drivers Can Be Found In "Sigverif.txt"

Note -- > Don't Select More Than 5 Drivers At Once As It Can Degrade Performance Causing Slow BootUp.

Wait For The Next Crash Or Wait For A Day . Upload The "Minidump" Of That Crash .

Now Open "Verifier" Again And Select The Next 5 Drivers ..And So On
==

[Monica21]

No crashes Friday after I updated drivers, none yesterday, but three first thing this morning.

Here's the minidump along with the sigverify.txt. The two drivers that aren't signed (aside from AVG) aren't loaded. I don't know if that makes a difference.

http://www.elricm.com/Monica/Downloads/Minidump.zip

[Old Rich]

Have you examined the Capacitors on the motherboard and video card for leakage and/or bulging? Bad Caps can cause the otherwise unexplainable BSOD's you seem to be experiencing.

http://www.badcaps.net/pages.php?vid=5

[Monica21]

To my highly untrained eye, the capacitors look fine. I would also hope that the various tech support people I have seen over the past year would look for that, but one can't always be sure. Your link did mention that a cap could fail without any physical signs of a bad cap. If that's the case, how can you tell?

If I had my digital camera I'd post pictures, but I don't know if that would do any good.

[Old Rich]

If you do not see any bulging or leaking caps, it's probably not your problem. What Power supply do you have?

[Monica21]

It's a SilverStone Strider 750W.

edit: Something I just noticed from my dxdiag on the first page, my mouse and keyboard are listed under PS/2 devices and they're both USB. Is that just a dxdiag thing, or do I need to fix it?

[Monica21]

Here I go again:

http://www.elricm.com/Monica/Downloads/Minidump.zip

Blue screen this morning after opening Firefox. It asked me to update something, I clicked "Next", then the first bsod. I restarted in Safe Mode with Networking and got a bsod. I don't think it's in the minidump, so here's the code:

C000021a {fatal system error}
f 0xC0000005 (0x00000000, 0x00000000)

Restarted in Safe mode w/ Networking, Firefox encountered and error and needs to close. Dr Watson post mortem debugger encountered an error and needs to close. Blue Screen.

Restarted in Safe mode w/ Networking, didn't get a login screen.

Restarted in Safe mode, to try and to burn the minidump since I couldn't get online, then got a PFN_LIST_CORRUPT bsod.

Restarted in Safe Mode w/ Networking and was finally able to upload the minidump. Ran Firefox in Safe Mode.

[Monica21]

This is new:




And then it loads the memory really slowly:



It eventually loaded, but then I got a blinking cursor for about 10 minutes and it never listed my devices. I finally just shut it down.

I have the most up-to-date BIOS I can get without using a beta version of F13.

[Monica21]

bump?

[Old Rich]

I would change out the power supply to see if that makes a difference

[devil_himself]

From Debugging Tools Help :-

Bug Check 0xA5: ACPI_BIOS_ERROR

Parameter 1    Parameter 2     Parameter 3    Parameter 4          Cause 
0x11               0x3          0              0                    The system could not load RSDT.

If you are not performing debugging, this error indicates that you have to obtain a new BIOS. Contact your vendor or visit the internet to get a new BIOS.

If you cannot obtain an updated BIOS, or the latest BIOS is still not ACPI compliant, you can turn off ACPI mode during text-mode setup. To turn off ACPI mode, press the F7 key when you are prompted to install storage drivers. The system does not notify you that the F7 key was pressed, but it silently disables ACPI and enables you to continue your installation.

[Monica21]

Originally Posted by simpswr

I would change out the power supply to see if that makes a difference

Why do you suspect the power supply? It's had a rail check and is fine. Also, I don't have a spare power supply.

[Monica21]

Originally Posted by devil_himself

If you are not performing debugging, this error indicates that you have to obtain a new BIOS. Contact your vendor or visit the internet to get a new BIOS.

But the error doesn't make sense. As I said, the BIOS is updated. F12 is the most current full release. I found information on another website that says all BIOS are ACPI compliant now so the error is misleading, but I didn't get much more information than that.

[Old Rich]

Originally Posted by Monica21

Why do you suspect the power supply? It's had a rail check and is fine. Also, I don't have a spare power supply.

Just my experience that otherwise unexplainable failures are often caused by a faulty powersupply . .

[Rollin' Rog]

If you open a command prompt (start > run cmd) and at the prompt enter:

fsutil dirty query c:

does it report "dirty" or "not dirty"?