Random BSOD

[bry2121]

I have been having random BSOD lately, not sure why. I attached the zip with the information required in the forum sticky. Also, here is the copy of the WinDBG of the dump:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03057650
Debug session time: Tue Jun 14 20:20:55.719 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:23.093
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 21, {fffffa8008c82060, 2, fff800000000000e, fff7fffffffee26a}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
16.1: kd:x86> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
QUOTA_UNDERFLOW (21)
This bugcheck occurs if a kernel component mishandles quota charges and
returns more quota than was previously charged to a particular quota block.
Arguments:
Arg1: fffffa8008c82060, The process (if any) that was initially charged.
Arg2: 0000000000000002, The quota type in question (paged pool, nonpaged pool, etc.)
Arg3: fff800000000000e, The initial charge amount to return.
Arg4: fff7fffffffee26a, The remaining (unreturned) charge.
Debugging Details:
------------------

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x21
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0

STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: INVALID_KERNEL_CONTEXT
Followup: MachineOwner
---------
16.1: kd:x86> lmvm Unknown_Module
start end module name

Thanks for your help!

 

[zigzag3143]

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

 

[bry2121]

I just updated the ASACPI.sys as you recommended. We will wait and see if another BSOD occurs, as they were random.

I'm a little skeptical though about this fix since I must have had this driver for 3 years or so and have very rarely had a BSOD before. In the past week I have been getting them often. Any other possible causes?

 

[zigzag3143]

I just updated the ASACPI.sys as you recommended. We will wait and see if another BSOD occurs, as they were random.

I'm a little skeptical though about this fix since I must have had this driver for 3 years or so and have very rarely had a BSOD before. In the past week I have been getting them often. Any other possible causes?

The following actions might prevent an error like this from happening again:

1. Download and install updates and device drivers for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.

 

[bry2121]

I am still getting the random BSOD after following your suggestions...any other ideas? Any help is greatly appreciated! Thanks again!

 

[zigzag3143]

I am still getting the random BSOD after following your suggestions...any other ideas? Any help is greatly appreciated! Thanks again!

if you are still getting the BSOD's please upload the DMP files for us to examine.

 

[bry2121]

The MEMORY.DMP should be included in the original post in the .zip. Thanks again

 

[zigzag3143]

The MEMORY.DMP should be included in the original post in the .zip. Thanks again

Newest DMP is from 6/13/2011.

In it you have asacpi.sys loaded

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

 

[bry2121]

Sorry about that. For some reason the last crash did not produce a MEMORY.DMP. It looks like the last one was just deleted and none is left. THere is a mini-dump however. I attached the mini-dump. When it crashes again hopefully it will produce a full memory.dmp for me to upload. Thanks!

 

[bry2121]

Hi again. It crashed again last night, and did produce a MEMORY.DMP this time. When zipped, it is 250 MB large, and is not allowing me to attach it. How can I get you the .DMP?