Blue Screens and Random Reboots

I'm guessing third party softwares are messing up your system. I saw that you mentioned something like 'trayit''...that interfere with MSE
Can you please go to Run-->Type in msconfig-->choose startup tab and turn off everything except system process and see if problem goes away

~Tuan

I couldn't see a lot from the minidump file. Can you please enable Driver Verifier. It is driver stress test that will let us know if the BSODs caused by bad driver

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Reboot into Windows, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

Your latest dump pointed to Tibia.exe as the cause. That does not necessarily mean it was the cause; it could have conflicted with something else. Tibia.exe belongs to the software Tibia Player or Adobe AIR by CipSoft GmbH. Try to udate this program, in fact make sure all of your Adobe software is updated.

I agree with Tuan, do run driver verifier until it causes a BSOD or for for 24 hours. Carry on your normal computer operations while it is running.

Do a CPU stress test as well, using Prime95.

You are correct. It was running at the time and may not be the cause. Also I see that the driver spsys.sys was unloaded. SPSYS.SYS is the Windows Licensing System file; so I have to ask if your copy of Windows is validated and legitimate? This is not an accusation, just a question in the process of eliminating possibilities.

CarlTR6 said:

You are correct. It was running at the time and may not be the cause. Also I see that the driver spsys.sys was unloaded. SPSYS.SYS is the Windows Licensing System file; so I have to ask if your copy of Windows is validated and legitimate? This is not an accusation, just a question in the process of eliminating possibilities.

Yeah it's validated and legitimate, I even have the sticker on the side from where I got it built, also I've had this error for ages now and not only on this OS, I used to have Vista Home Premium x64 before and I had the problem on that too

Ok, I did driver verifier and here are the blue screens

Hope you guys can help

Edit: Thanks, will let you know if problems arise

Both dmps are nearly identical and point to ASACPI.sys as the cause.

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_062410-23634-01.zip\062410-23634-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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`02a0b000 PsLoadedModuleList = 0xfffff800`02c48e50
Debug session time: Thu Jun 24 11:25:34.654 2010 (GMT-4)
System Uptime: 0 days 0:00:49.745

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 184, fffffa8007a34160, fffff880041e0257}

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

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: fffffa8007a34160, Address of the current process.
Arg4: fffff880041e0257, 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 fffff80002f053dc to fffff80002a7b600

STACK_TEXT:  
fffff880`087855b8 fffff800`02f053dc : 00000000`000000c4 00000000`000000f6 00000000`00000184 fffffa80`07a34160 : nt!KeBugCheckEx
fffff880`087855c0 fffff800`02f1aae4 : 00000000`00000184 fffffa80`07a34160 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08785600 fffff800`02cd7580 : 00000000`00004c4e fffff880`08785830 00000000`00000000 fffffa80`046d4100 : nt!VfCheckUserHandle+0x1b4
fffff880`087856e0 fffff800`02d53425 : 00000000`00000000 fffff880`000f0001 00000000`00000000 fffffa80`00000000 : nt! ?? ::NNGAKEGL::`string'+0x20e1e
fffff880`087857b0 fffff800`02f1a878 : fffffa80`0625b968 fffff800`02f1dbcc fffffa80`046d4060 fffffa80`046d4060 : nt!ObReferenceObjectByHandle+0x25
fffff880`08785800 fffff880`041e0257 : fffff980`1592ecf0 00000000`00000002 fffffa80`046d41b0 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`08785850 fffff980`1592ecf0 : 00000000`00000002 fffffa80`046d41b0 00000000`00000000 fffffa80`046d41d8 : ASACPI+0x1257
fffff880`08785858 00000000`00000002 : fffffa80`046d41b0 00000000`00000000 fffffa80`046d41d8 00000000`00000000 : 0xfffff980`1592ecf0
fffff880`08785860 fffffa80`046d41b0 : 00000000`00000000 fffffa80`046d41d8 00000000`00000000 00000000`00000001 : 0x2
fffff880`08785868 00000000`00000000 : fffffa80`046d41d8 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`046d41b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ASACPI+1257
fffff880`041e0257 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

Here is a thread on the Asus site you can read about this driver and the utility.

ASUSTeK Computer Inc.-Forum- ATK0110 ACPI Utility Drivers

Although, I think you driver is current, I suggest that you reinstall it from the Asus site. Go to this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th 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.