Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Can anyone help me read these minidump files?
New Posts  All Forums:Forum Nav:

Can anyone help me read these minidump files?

post #1 of 98
5/6/12 at 10:46am
Thread Starter 
I've been getting BSOD's lately in my system and I'd like to have some help to find out the cause.

Here is the .zip file with them.

http://dl.dropbox.com/u/21018119/Minidumps.zip
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
post #2 of 98
5/6/12 at 1:51pm
Sure can smile.gif

I've taken a look at your dumps, most are 1E bugchecks that are pointing to the probable cause sptd.sys which is the SCSI Pass Through Direct Host for Daemon Tools and Alcohol 120 (MANY known issues with Win7). After checking your loaded drivers list, dtsoftbus01.sys is listed, so you DO have Daemon Tools installed, so it's the scsi pass through driver for Daemon Tools in your case.

1. Fully remove Daemon Tools as it's unfortunately a virutalization program that interferes with the functionality of way too many things in Windows 7, especially its pass through driver, so it causes many BSOD and crash related instances. Optional programs: PowerISO, ImgBurn, etc.

2. After you've removed Daemon Tools and restarted, use DuplexSecure's SPTD Uninstaller to fully ensure that SPTD is removed correctly. After you've done that, restart one last time.

Driver(s) the need to be updated:
Quote:
3xHybr64.sys - Wed Mar 28 21:44:34 2007 (ASUS Hybrid TV Tuner by Philips Semiconductors GmbH, may have ATI chipset - SAA713x PCI TV Card). Update here.

ASACPI.sys - Sun Mar 27 22:30:36 2005

Your ASACPI.sys driver (Asus ATK0110 ACPI Utility, a known BSOD maker in Win7. Also a part of the Asus PCProbe and AISuite Utilities) is the pre 2009 version of the driver (2005 to be exact) and the pre 2009 driver is a very large causer of BSODs as well. Please update that driver here.

KMWDFILTER.sys - Thu Mar 29 03:00:40 2007 (UASSOFT.com HID (mouse) Driver). Suspect that this is a Kensington Mouse Works driver - but there's nothing listed here AFAIK: http://www.uassoft.com/

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\050512-19874-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304c650
Debug session time: Sun May  6 00:34:10.039 2012 (UTC - 4:00)
System Uptime: 0 days 0:49:24.647
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

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

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3038333636656238
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8000463c618 -- (.exr 0xfffff8000463c618)
ExceptionAddress: fffff88000e501d2 (Wdf01000!FxRequestBase::CompleteSubmitted+0x000000000000011e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8000463c6c0 -- (.trap 0xfffff8000463c6c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=72ededa5b75ce8e1 rbx=0000000000000000 rcx=fffffa8009703a90
rdx=fffffa8009702a10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000e501d2 rsp=fffff8000463c850 rbp=0000000000000000
 r8=fffffa8009702a00  r9=0000000000000000 r10=fffffa8009116a80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Wdf01000!FxRequestBase::CompleteSubmitted+0x11e:
fffff880`00e501d2 ff5018          call    qword ptr [rax+18h] ds:0003:72ededa5`b75ce8f9=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7c67e to fffff80002e84c50

STACK_TEXT:  
fffff800`0463b6f8 fffff800`02e7c67e : 00000000`00000000 00000000`00000000 fffff800`0463be70 fffff800`02eafc80 : nt!KeBugCheck
fffff800`0463b700 fffff800`02eaf94d : fffff800`0308d71c fffff800`02fca078 fffff800`02e08000 fffff800`0463c618 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`0463b730 fffff800`02eae725 : fffff800`02fcdfac fffff800`0463b7a8 fffff800`0463c618 fffff800`02e08000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`0463b760 fffff800`02ebf6a1 : fffff800`0463c618 fffff800`0463be70 fffff800`00000000 fffffa80`09116a80 : nt!RtlDispatchException+0x415
fffff800`0463be40 fffff800`02e84302 : fffff800`0463c618 fffffa80`09702a10 fffff800`0463c6c0 fffffa80`091c5830 : nt!KiDispatchException+0x135
fffff800`0463c4e0 fffff800`02e82c0a : fffffa80`0975ddd0 fffffa80`0975db40 fffffa80`09753461 fffff880`09d84b28 : nt!KiExceptionDispatch+0xc2
fffff800`0463c6c0 fffff880`00e501d2 : fffffa80`096f1d30 00000000`00000000 fffffa80`0975ee40 fffff800`033f2524 : nt!KiGeneralProtectionFault+0x10a
fffff800`0463c850 fffff880`00e26c9b : fffffa80`091c5830 fffffa80`091c5830 fffffa80`091c5840 fffffa80`07379501 : Wdf01000!FxRequestBase::CompleteSubmitted+0x11e
fffff800`0463c8d0 fffff880`00e26dc4 : 00000000`00000002 fffffa80`08408248 00000000`00000000 fffffa80`06df2dc0 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`0463c940 fffff800`02e70845 : 00000000`00000000 fffff800`0300e340 00000000`0000000b fffff800`02fb31a1 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`0463c970 fffff800`02e886c1 : fffffa80`0737971b 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x55
fffff800`0463c9b0 fffff880`08157631 : fffffa80`08245050 fffffa80`09703b00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`0463caa0 fffff880`08157b0f : fffffa80`06e8a502 fffffa80`07379570 00000000`ffffffff fffffa80`08245eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`0463cb80 fffff880`0815566f : fffffa80`08245eb0 fffffa80`082451a0 fffffa80`08246050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`0463cbe0 fffff880`08146f89 : fffffa80`08245050 00000000`00000000 fffffa80`08245e02 fffffa80`08245eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`0463cc20 fffff880`010ab570 : fffffa80`081fb000 fffffa80`08245ec8 fffffa80`08245e00 fffff800`0463ccc8 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`0463cc50 fffffa80`081fb000 : fffffa80`08245ec8 fffffa80`08245e00 fffff800`0463ccc8 00000000`00000010 : sptd+0x46570
fffff800`0463cc58 fffffa80`08245ec8 : fffffa80`08245e00 fffff800`0463ccc8 00000000`00000010 00000000`00000246 : 0xfffffa80`081fb000
fffff800`0463cc60 fffffa80`08245e00 : fffff800`0463ccc8 00000000`00000010 00000000`00000246 fffff800`0463cc98 : 0xfffffa80`08245ec8
fffff800`0463cc68 fffff800`0463ccc8 : 00000000`00000010 00000000`00000246 fffff800`0463cc98 00000000`00000018 : 0xfffffa80`08245e00
fffff800`0463cc70 00000000`00000010 : 00000000`00000246 fffff800`0463cc98 00000000`00000018 00000000`00000000 : 0xfffff800`0463ccc8
fffff800`0463cc78 00000000`00000246 : fffff800`0463cc98 00000000`00000018 00000000`00000000 fffffa80`081fc24d : 0x10
fffff800`0463cc80 fffff800`0463cc98 : 00000000`00000018 00000000`00000000 fffffa80`081fc24d fffff800`02ff9e80 : 0x246
fffff800`0463cc88 00000000`00000018 : 00000000`00000000 fffffa80`081fc24d fffff800`02ff9e80 fffffa80`08245eb0 : 0xfffff800`0463cc98
fffff800`0463cc90 00000000`00000000 : fffffa80`081fc24d fffff800`02ff9e80 fffffa80`08245eb0 fffffa80`08245ec8 : 0x18


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sptd+46570
fffff880`010ab570 ??              ???

SYMBOL_STACK_INDEX:  10

SYMBOL_NAME:  sptd+46570

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sptd

IMAGE_NAME:  sptd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d6aa630

FAILURE_BUCKET_ID:  X64_0x1E_0_sptd+46570

BUCKET_ID:  X64_0x1E_0_sptd+46570

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

0: kd> !thread
GetPointerFromAddress: unable to read from fffff800030b6000
THREAD fffff80003007cc0  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80002ff5ba4
Owning Process            fffff800030081c0       Image:         <Unknown>
Attached Process          fffffa800671e9e0       Image:         System
fffff78000000000: Unable to get shared data
Wait Start TickCount      189999       
Context Switch Count      2067889             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!KiIdleLoop (0xfffff80002e7c930)
Stack Init fffff8000463cdb0 Current fffff8000463cd40
Base fffff8000463d000 Limit fffff80004637000 Call 0
Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff800`0463b6f8 fffff800`02e7c67e : 00000000`00000000 00000000`00000000 fffff800`0463be70 fffff800`02eafc80 : nt!KeBugCheck
fffff800`0463b700 fffff800`02eaf94d : fffff800`0308d71c fffff800`02fca078 fffff800`02e08000 fffff800`0463c618 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`0463b730 fffff800`02eae725 : fffff800`02fcdfac fffff800`0463b7a8 fffff800`0463c618 fffff800`02e08000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`0463b760 fffff800`02ebf6a1 : fffff800`0463c618 fffff800`0463be70 fffff800`00000000 fffffa80`09116a80 : nt!RtlDispatchException+0x415
fffff800`0463be40 fffff800`02e84302 : fffff800`0463c618 fffffa80`09702a10 fffff800`0463c6c0 fffffa80`091c5830 : nt!KiDispatchException+0x135
fffff800`0463c4e0 fffff800`02e82c0a : fffffa80`0975ddd0 fffffa80`0975db40 fffffa80`09753461 fffff880`09d84b28 : nt!KiExceptionDispatch+0xc2
fffff800`0463c6c0 fffff880`00e501d2 : fffffa80`096f1d30 00000000`00000000 fffffa80`0975ee40 fffff800`033f2524 : nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff800`0463c6c0)
fffff800`0463c850 fffff880`00e26c9b : fffffa80`091c5830 fffffa80`091c5830 fffffa80`091c5840 fffffa80`07379501 : Wdf01000!FxRequestBase::CompleteSubmitted+0x11e
fffff800`0463c8d0 fffff880`00e26dc4 : 00000000`00000002 fffffa80`08408248 00000000`00000000 fffffa80`06df2dc0 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`0463c940 fffff800`02e70845 : 00000000`00000000 fffff800`0300e340 00000000`0000000b fffff800`02fb31a1 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`0463c970 fffff800`02e886c1 : fffffa80`0737971b 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x55
fffff800`0463c9b0 fffff880`08157631 : fffffa80`08245050 fffffa80`09703b00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`0463caa0 fffff880`08157b0f : fffffa80`06e8a502 fffffa80`07379570 00000000`ffffffff fffffa80`08245eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`0463cb80 fffff880`0815566f : fffffa80`08245eb0 fffffa80`082451a0 fffffa80`08246050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`0463cbe0 fffff880`08146f89 : fffffa80`08245050 00000000`00000000 fffffa80`08245e02 fffffa80`08245eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`0463cc20 fffff880`010ab570 : fffffa80`081fb000 fffffa80`08245ec8 fffffa80`08245e00 fffff800`0463ccc8 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`0463cc50 fffffa80`081fb000 : fffffa80`08245ec8 fffffa80`08245e00 fffff800`0463ccc8 00000000`00000010 : sptd+0x46570
fffff800`0463cc58 fffffa80`08245ec8 : fffffa80`08245e00 fffff800`0463ccc8 00000000`00000010 00000000`00000246 : 0xfffffa80`081fb000
fffff800`0463cc60 fffffa80`08245e00 : fffff800`0463ccc8 00000000`00000010 00000000`00000246 fffff800`0463cc98 : 0xfffffa80`08245ec8
fffff800`0463cc68 fffff800`0463ccc8 : 00000000`00000010 00000000`00000246 fffff800`0463cc98 00000000`00000018 : 0xfffffa80`08245e00
fffff800`0463cc70 00000000`00000010 : 00000000`00000246 fffff800`0463cc98 00000000`00000018 00000000`00000000 : 0xfffff800`0463ccc8
fffff800`0463cc78 00000000`00000246 : fffff800`0463cc98 00000000`00000018 00000000`00000000 fffffa80`081fc24d : 0x10
fffff800`0463cc80 fffff800`0463cc98 : 00000000`00000018 00000000`00000000 fffffa80`081fc24d fffff800`02ff9e80 : 0x246
fffff800`0463cc88 00000000`00000018 : 00000000`00000000 fffffa80`081fc24d fffff800`02ff9e80 fffffa80`08245eb0 : 0xfffff800`0463cc98
fffff800`0463cc90 00000000`00000000 : fffffa80`081fc24d fffff800`02ff9e80 fffffa80`08245eb0 fffffa80`08245ec8 : 0x18
Reply
Reply
post #3 of 98
5/6/12 at 1:57pm
Thread Starter 
One more thing: GPU stressing has been causing BSOD's before the current ones. Last week my system was showing artifacts and multiple BSOD's related to graphics drivers. I took the PC to a friend of mine, who completely cleaned it physically and removed all the dust in it. It seemed to work fine. Ran Furmark for 15 minutes without a problem.

But then I got those BSOD's. And a few hours ago, I tried using OCCT to stress test my GPU and, well, lost video signal and got a BSOD (which I couldn't see 'cause I lost video).

A reset brought it back to normal but a friend says my GPU might be dying already.

And yes I do have DAEMON.
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
post #4 of 98
5/6/12 at 2:02pm
It could be, but none of the minidumps attached were signs of the GPU having anything to do with it. Your GPU could be an entirely different issue which we'll further discuss after we've taken care of what I've written above.

It's likely Daemon Tools and its passthrough driver are just interfering with the function of many important system drivers / 3rd party drivers. As I said though, if you're still crashing after thoroughly follow all of my recommendations, please keep me updated by attaching further dump files.
Reply
Reply
post #5 of 98
5/6/12 at 2:18pm
Thread Starter 
I got rid of DAEMON Tools and that SCSI thingy. I'm getting the latest drivers for my TV Tuner (It's an Encore ENLTV-FM), but AFAIK I installed the latest drivers when I did a clean install 2 months ago...

ASACPI.sys I don't know how it cancause a BSOD because I don't use AISuite or PCProbe. How do I solve this?
Edited by Icekilla - 5/6/12 at 2:32pm
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
post #6 of 98
5/6/12 at 2:25pm
Quote:
Originally Posted by Icekilla View Post

I got rid of DAEMON Tools and that SCSI thingy. I'm getting the latest drivers for my TV Tuner (It's an Encore ENLTV-FM), but AFAIK I installed the latest drivers when I did a clean install 2 months ago...
ASACPI.sys I don't know how it cancause a BSOD because I don't use AISuite or PCProbe. How do I solve this?

ASACPI.sys is a driver for the Asus Utility you have installed. What this utility does is essentially monitor the voltages and such of your system, and it's also essentially a pass through for the BIOS to the OS, allowing you to overclock in the BIOS. This as you may or may not know is never recommended anyway, so unless you're using it to monitor voltages and such (which any other free HWM program can do) I'd just uninstall it, or you can update it from the Asus download link I provided and navigating to the page of your respected board and clicking (Utilities) and downloading the latest version of the utility you have installed.
Reply
Reply
post #7 of 98
5/6/12 at 2:29pm
Thread Starter 
That's the problem: I don't have that tool installed in my computer (I do know it but never used it really).

EDIT: Looks like I do have those files in my system...

267

Question is: What are they doing there?
Edited by Icekilla - 5/6/12 at 2:38pm
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
post #8 of 98
5/6/12 at 2:37pm
Interesting, now that you mention it, I don't see any utility actually listed as far as drivers go, just ASACPI.sys. Well, in that case, if it's especially not being used and there's no Asus utilities installed, simply navigate to C:/Windows/System32/drivers and rename ASACPI.sys to ASACPI.old

This will stop the driver from loading. Also, good work so far, thanks for patience and cooperation.
Reply
Reply
post #9 of 98
5/6/12 at 2:41pm
Thread Starter 
Are you sure that won't cause conflicts? Should I rename both to .old?
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
Vanessa
(18 items)
  		  
CPUMotherboardGraphicsRAM
Intel Core i5 2500k Gigabyte GA-Z77-D3H EVGA GTX 660ti SuperClocked PNY Optima MD4096SD3-1333 
Hard DriveHard DriveHard DriveOptical Drive
Western Digital WD500AAKX 500GB SATA Seagate ST2000DL003 ADATA AS510S3-120GM-C 120GB SSD Lite-On iHAS224-06 
CoolingOSMonitorMonitor
Cooler Master Hyper 212+ Windows 7 Ultimate x64 Samsung B1930  Benq G92HDA 
PowerCaseAudio
Corsair TX750 750W PSU Gray Acteck Octanux Logitech Z623 2.1CH 
View all
  hide details  
Reply
post #10 of 98
5/6/12 at 2:46pm
Quote:
Originally Posted by Icekilla View Post

Are you sure that won't cause conflicts? Should I rename both to .old?

It won't cause conflicts because the driver isn't in use as no application or program is using it, but it is loaded. What do you mean by "both" exactly? What second driver are you referring to?
Edited by pjBSOD - 5/6/12 at 2:48pm
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Can anyone help me read these minidump files?