BSOD Bug Check 0x18

Hi,

Built this unit about 2 months ago and it started bsing about a week ago. I didn't have the dumps enabled so this is the last one that showed up. So far about 4 instances.

Specs:
Windows 7 Ultimate 64bit Retail
System and OS are about 2 months old


Attached are reports and a summary here:
On Mon 5/23/2011 11:59:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052311-21013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8003E48C20, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

On Sun 5/22/2011 12:28:34 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002CEC312)
Error: IRQL_NOT_LESS_OR_EQUAL

Thanks

netimports said:

Hi,

Built this unit about 2 months ago and it started bsing about a week ago. I didn't have the dumps enabled so this is the last one that showed up. So far about 4 instances.

Specs:
Windows 7 Ultimate 64bit Retail
System and OS are about 2 months old


Attached are reports and a summary here:
On Mon 5/23/2011 11:59:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052311-21013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8003E48C20, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

On Sun 5/22/2011 12:28:34 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002CEC312)
Error: IRQL_NOT_LESS_OR_EQUAL

Thanks

First thing you need to remove is


Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place. MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor

OR

SlySoft Virtual CloneDrive

thanks for the reply, i tried that duplexsecure but it didnt find anything, uninstall was greyed out. I have magiciso virtual and poweriso, other then that i got nothing else using virtual devices. I did a full search on c: and couldn't find sptd.sys

netimports said:

thanks for the reply, i tried that duplexsecure but it didnt find anything, uninstall was greyed out. I have magiciso virtual and poweriso, other then that i got nothing else using virtual devices. I did a full search on c: and couldn't find sptd.sys

My opologies you do not have sptd.sys. YOu do have asacpi.sys. I used the wrong speech in the earlier post. asacpi.sys is also a major cause of bsod's.

ASACPI.sys 3/27/2005 10:30:36 PM fffff880`043f1000 fffff300`043f9000 0xfffffa8000008000 0x42476c4c


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).

thanks, i updated it to 2009. I'll report back if it blue screens again.

alright so it bs'd again, report is attached.


crash dump file: C:\Windows\Minidump\053011-33509-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC32D2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001232D2, 0xFFFFF880022D50C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

netimports said:

alright so it bs'd again, report is attached.


crash dump file: C:\Windows\Minidump\053011-33509-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC32D2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001232D2, 0xFFFFF880022D50C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

I am afraid even in the newest crash you still have 2005 asacpi.sys

that was quick! idk what to tell you, here is a screenshot in device manager:

Double checked the two newest DMP files you uploaded. I bet you have two copies of it. search for it and see where each copy is.

You also have a 6 year old America online driver that I would update if I were you. Im checking the rest now. (wanatw64.sys)

I am also suspicious of your ESET, and VM software.

i searched and all i found was one in sys32/drivers, the old is sitting in C:\Windows\System32\DriverStore\FileRepository\atk2000.inf_amd64_neutral_a91abe245a6c41c8

there is no update for the aol desktop, and i downloaded it recently from their site about a week or two ago.

ESET, and VM software, what do you see on them? eset is always updated and the vm i dont use that often, and again it was recently installed.