Blue Screens and Random Reboots

CarlTR6 · 24 Jun 2010

You are right; the same ASACPI.sys problem. I am going to ask for help with this to see if there is something I have overlooked. Keep watching this thread and we will get additional input.

Yes, you leave your computer running while Prime95 runs. That is something you might want to do overnight.

Lordbob75 · 24 Jun 2010

Hey guys.

Looking at the latest dump points out something interesting. It was still caused by ASACPI.sys, but with the process AiNap.exe. This is an ASUS motherboard utility, and is possibly conflicting with ASACPI. Try removing the AI Nap utility (if installed).

Additionally, here are some out of date drivers that might be causing problems:

Code:

secdrv   secdrv.SYS   Wed Sep 13 06:18:38 2006

Code:

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


Loading Dump File  [C:\Users\David\AppData\Local\Temp\Temp1_062410-28345-01.zip\062410-28345-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:  SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList =  0xfffff800`02c40e50
Debug session time: Thu Jun 24 14:07:23.566 2010 (UTC - 7:00)
System Uptime: 0 days 0:00:41.642
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                              *
*                        Bugcheck Analysis                                     *
*                                                                              *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 184, fffffa800804cb30, fffff88004420257}

Unable to load image ASACPI.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for  ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+1257 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                              *
*                        Bugcheck Analysis                                     *
*                                                                              *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This  is
because the driver was specified in the registry as being suspect (by  the
administrator) and the kernel has enabled substantial checking of this  driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and  0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000184, Handle value being referenced.
Arg3: fffffa800804cb30, Address of the current process.
Arg4: fffff88004420257, Address inside the driver that is performing the  incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  AiNap.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002efd3dc to fffff80002a73600

STACK_TEXT:  
fffff880`087195b8 fffff800`02efd3dc : 00000000`000000c4  00000000`000000f6 00000000`00000184 fffffa80`0804cb30 : nt!KeBugCheckEx
fffff880`087195c0 fffff800`02f12ae4 : 00000000`00000184  fffffa80`0804cb30 00000000`00000002 00000000`00000000 :  nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08719600 fffff800`02ccf580 : 00000000`00000000  fffff880`08719830 00000000`00000000 fffffa80`046d3900 :  nt!VfCheckUserHandle+0x1b4
fffff880`087196e0 fffff800`02d4b425 : 00000000`00000000  fffff880`000f0001 00000000`00000000 fffffa80`00000000 : nt! ??  ::NNGAKEGL::`string'+0x20e1e
fffff880`087197b0 fffff800`02f12878 : fffffa80`06773968  fffff800`02f15bcc fffffa80`046d37b0 fffffa80`046d37b0 :  nt!ObReferenceObjectByHandle+0x25
fffff880`08719800 fffff880`04420257 : fffff980`1058ccf0  00000000`00000002 fffffa80`046d3900 00000000`00000000 :  nt!VerifierObReferenceObjectByHandle+0x48
fffff880`08719850 fffff980`1058ccf0 : 00000000`00000002  fffffa80`046d3900 00000000`00000000 fffffa80`046d3928 : ASACPI+0x1257
fffff880`08719858 00000000`00000002 : fffffa80`046d3900  00000000`00000000 fffffa80`046d3928 00000000`00000000 :  0xfffff980`1058ccf0
fffff880`08719860 fffffa80`046d3900 : 00000000`00000000  fffffa80`046d3928 00000000`00000000 00000000`00000001 : 0x2
fffff880`08719868 00000000`00000000 : fffffa80`046d3928  00000000`00000000 00000000`00000001 00000000`00000000 :  0xfffffa80`046d3900


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ASACPI+1257
fffff880`04420257 83462001        add     dword ptr [rsi+20h],1

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ASACPI+1257

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ASACPI

IMAGE_NAME:  ASACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0b72fd

FAILURE_BUCKET_ID:  X64_0xc4_f6_ASACPI+1257

BUCKET_ID:  X64_0xc4_f6_ASACPI+1257

Followup: MachineOwner
---------

~Lordbob

CarlTR6 · 24 Jun 2010

In addition to what Lordbob suggested, and his advice is spot on, Captain Jack Sparrow suggested that you rename ASACPI.sys to ASACPI.old because it just a Motherboard Utility and to uninstall all the Asus utilities as well. And that concurs with what Lordbob is suggesting.

This is the great thing about this forum. There are so many knowledgeable folks here that if one of us can't come up with a solution, someone else can.

Don't worry about the secdrive.sys driver. Yes it is old; but it is a a Windows system driver and there is not an update for it. You can safely ignore it.

After you try these, please post back and let us know.

jason786 · 25 Jun 2010

I really do appreciate all the help, and time spent to assist me

I uninstalled AI Suite which are all the Asus utilities that I had, I then rebooted in driver verifier mode and I didn't get a blue screen on startup (currently on verifier mode as I type this)

I was going to rename the file afterwards but I'm going to trail my computer like this for a while and post back

However, one thing that is bugging me is that shouldn't all the clean installs I have done eliminated any driver problems? Because in all my previous installs I've never had AI Suite installed, it was just recently that I decided to install it because my computer fans were getting loud (I'm still not sure why). Could all these clean installs lead it to being a hardware error? The thing is, I have changed my PSU, Graphics Card and Hard drive since I first got the PC, and the RAM got through many passes on memtest too.

So basically, I had blue screens before AI Suite was installed, so I'm not sure if this is the main problem if you see what I'm saying. But I'll run the PC like this for a while and check if I get BSoD

I'm thinking about running Prime95 overnight.

jason786 · 25 Jun 2010

Oh no!
I've still got driver verifier running, and my PC just rebooted itself without leaving a blue screen!

Edit: Ok, just received a blue screen after writing that message

It seems that firefox caused the problem but I'm not quite sure what to do about it :/

CarlTR6 · 25 Jun 2010

Firefox may or may not have caused it. FF may just be the victim. It is another 101 error - hardware, or drivers, or both. I do see that ASACPI.sys is still there.

Recommend you rename ASACPI.sys ASAP and see what how things go from there.

jason786 · 25 Jun 2010

Although, I renamed it and will let you know how things turn out!

CarlTR6 · 25 Jun 2010

Very good. Please keep us updated. We want to fix this problem. :)

jason786 · 25 Jun 2010

CarlTR6 said:

Very good. Please keep us updated. We want to fix this problem. :)

Just received a blue screen, the ASACPI.sys had been renamed too

Edit: I just received another blue screen!

However, this one was due to driver verifier it seems! Hope we are getting closer

CarlTR6 · 25 Jun 2010

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_062510-19468-01.zip\062510-19468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
Debug session time: Fri Jun 25 14:58:20.038 2010 (GMT-4)
System Uptime: 0 days 5:52:33.113

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002a9931f, fffff88003866c30, 0}

Probably caused by : win32k.sys ( win32k!SfnDWORD+ea )

Followup: MachineOwner
---------

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002a9931f, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003866c30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KeSetEventBoostPriority+3f
fffff800`02a9931f f00fba2907      lock bts dword ptr [rcx],7

CONTEXT:  fffff88003866c30 -- (.cxr 0xfffff88003866c30)
rax=0000000000000002 rbx=fffff880009ec180 rcx=ffff00000651f8e0
rdx=fffffa8006216190 rsi=0000000000000000 rdi=ffff00000651f8e0
rip=fffff80002a9931f rsp=fffff88003867600 rbp=fffffa8007b17060
 r8=0000000000000000  r9=0000000000000000 r10=fffff900c0882d80
r11=0000000001162d80 r12=fffff880009ec180 r13=fffffa8006216190
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!KeSetEventBoostPriority+0x3f:
fffff800`02a9931f f00fba2907      lock bts dword ptr [rcx],7 ds:002b:ffff0000`0651f8e0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  msnmsgr.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ada764 to fffff80002a9931f

STACK_TEXT:  
fffff880`03867600 fffff800`02ada764 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`00000403 : nt!KeSetEventBoostPriority+0x3f
fffff880`03867670 fffff800`02adc5fa : fffff900`c0844770 00000000`7efdb800 fffff900`c07c3770 00000000`00000003 : nt!ExpReleaseResourceForThreadLite+0x2cf
fffff880`038676d0 fffff960`000ee1ea : 00000000`00000004 00000000`00000018 00000000`00000000 00000000`00000000 : nt!ExReleaseResourceAndLeavePriorityRegion+0x12
fffff880`03867700 fffff960`00091452 : fffff900`c0849060 00000000`00000000 00000000`00000000 fffff900`c0882d80 : win32k!SfnDWORD+0xea
fffff880`038677e0 fffff960`000ae4be : 00000000`00000000 fffff900`c0844770 00000000`00000000 00000000`00000000 : win32k!xxxHkCallHook+0x3e2
fffff880`03867870 fffff960`000ae05f : 00000000`00000003 00000000`00000000 00000000`00000000 fffff880`03867a78 : win32k!xxxCallHook2+0x452
fffff880`038679e0 fffff960`000ea68f : fffff880`009ec180 fffff800`02ad98af 00000001`00000000 fffffa80`07b17060 : win32k!xxxCallHook+0x37
fffff880`03867a30 fffff960`000a332c : 00000000`00000000 fffff900`c0882d80 00000000`000002b1 00000000`00000410 : win32k!xxxSendMessageTimeout+0x22b
fffff880`03867ae0 fffff960`000cfde8 : 00000000`000704a2 00000000`00000410 fffffa80`00000001 fffff880`00000000 : win32k!xxxWrapSendMessage+0x1c
fffff880`03867b30 fffff800`02acf853 : fffffa80`07b17060 fffff880`03867ca0 00000000`0010de08 00000000`72c42450 : win32k!NtUserMessageCall+0xf8
fffff880`03867bb0 00000000`72c8fc3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0010dde8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72c8fc3a


FOLLOWUP_IP: 
win32k!SfnDWORD+ea
fffff960`000ee1ea 4c8d5c2438      lea     r11,[rsp+38h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!SfnDWORD+ea

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376

STACK_COMMAND:  .cxr 0xfffff88003866c30 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!SfnDWORD+ea

BUCKET_ID:  X64_0x3B_win32k!SfnDWORD+ea

Followup: MachineOwner
---------

I hate to tell you this; but ASACPI.sys still shows in the drivers list of this latest dmp file.

ASACPI.sys Wed May 13 21:25:17 2009 (4A0B72FD)

After you renamed it, did you reboot?