Hi everyone (sorry for english!).
In my pc in sgnature, I get bsod if run occt togheter with p2p programs (torrent).
The blue screen show this :
Stop: 0x0000007f (0x00000000, 0x00000000, 0x00000000)

I found this error in microsoft support , but this was useless.
I checked my memory with memtest for all night, no errors found.
I tried to open crash dump file with debugging tools for windows and this say:

Probably caused by: ASACPI.sys (ASACPI+7f0)

I get this bsod only if I run occt with p2p , i don't overclock.If I run occt "alone" no bsod even for four hours.
The error is always this, I never got different error.
The pc works very well. I play games and I used other benchmark everything is ok.
Also I tried to use orthos or prime with p2p programs, no bsod.

Hi and welcome to Bleepingcomputer.
Can you give us some information of your computer is it a desktop, what windows system are you using Xp, 95.
I assume it's Xp since you posted it in the Windows Xp forum.
Might want to look at this >http://answers.yahoo.com/question/index?qid=1006052024880

I use XP 32 bit and in signature there are the components. My HD is western digital 500 GB sata 2 16MB buffer. I checked it with many hd tools , everything ok. I have two partitions in this hd.

The error seems to be with a controller on your motherboard (an ATK0110 ACPI Utility). Uninstalling it and reinstalling the latest version may fix the problem.

I'm not familiar with the occt tool - but if it's a overclocking or system checking utility it may be conflicting with the ACPI utility. That could also cause the BSOD's. The P2P app can contribute to this instability also.

Does the system BSOD with just the P2P and not using the occt tool?

Could you post the results of your crash dump for us to have a look at?

Sorry but I don't know how i can post crash dump file. Also How can I unistall and reinstall ACPI controller?

To post the crash dump, you'll have to copy the text of the crash dump in the debugging tools window, then paste it into your next post.

As for the ACPI controller - we'll need to know the exact make and model of your system (the exact make and model of the motherboard if it's a custom build).

Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini050308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat May 3 11:39:15.046 2008 (GMT+2)
System Uptime: 0 days 0:27:35.766
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
................................................................................
.....................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {0, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for ACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
*** WARNING: Unable to verify timestamp for ASACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ASACPI.sys ( ASACPI+7f0 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

MODULE_NAME: ASACPI

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 411c2d04

BUGCHECK_STR: 0x7f_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from 805a11d1 to 804f9dc6

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a58fa934 805a11d1 0000007f ba68f1ce 89b90bd0 nt+0x22dc6
a58fa98c 80541474 a58fa998 a58faa18 ba68f1ce nt+0xca1d1
a58fa998 ba68f1ce badb0d00 00000000 ba68a5b7 nt+0x6a474
a58faa18 ba6908ac 89b8f000 89b90cb0 00008000 ACPI+0x181ce
a58faa34 ba68bba2 89b8f000 89b90bd0 00000000 ACPI+0x198ac
a58faa5c ba68d4e2 00000000 00000000 ba694d58 ACPI+0x14ba2
a58faa74 ba68d5b0 89b8f000 00000000 ba694d58 ACPI+0x164e2
a58faa90 ba68c906 89b8f000 00000000 00008004 ACPI+0x165b0
a58faab0 ba68caee 89bb2ff8 e4318c08 00000001 ACPI+0x15906
a58faaf8 ba6883ae 89bb2ff8 e4318c08 00000001 ACPI+0x15aee
a58fab20 ba691612 89bb2ff8 e4318c08 00000001 ACPI+0x113ae
a58fab50 ba691799 89b84ce8 880721a0 89bb2ff8 ACPI+0x1a612
a58fab64 ba67de12 89b84ce8 880721a0 00fffa54 ACPI+0x1a799
a58fab94 804ef095 89b84ce8 ba692ecc 00000000 ACPI+0x6e12
a58fabc8 badfc7f0 89b84ce8 0032c004 881383c8 nt+0x18095
a58fac1c badfc3f7 89b84ce8 8803ba70 8803ba70 ASACPI+0x7f0
a58fac64 8057f56d 88f85278 8803ba70 881aaca0 ASACPI+0x3f7
a58fad00 805780c2 00000158 00000000 00000000 nt+0xa856d
a58fad34 8054086c 00000158 00000000 00000000 nt+0xa10c2
a58fad64 7c91eb94 badb0d00 00fff930 a58fad98 nt+0x6986c
a58fad68 badb0d00 00fff930 a58fad98 a58fadcc 0x7c91eb94
a58fad6c 00fff930 a58fad98 a58fadcc 00000000 0xbadb0d00
a58fad70 a58fad98 a58fadcc 00000000 00000000 0xfff930
a58fad74 a58fadcc 00000000 00000000 00000000 0xa58fad98
a58fad98 00000000 009a6320 0000000a 00000000 0xa58fadcc


STACK_COMMAND: kb

FOLLOWUP_IP:
ASACPI+7f0
badfc7f0 ?? ???

SYMBOL_STACK_INDEX: f

SYMBOL_NAME: ASACPI+7f0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ASACPI.sys

BUCKET_ID: WRONG_SYMBOLS

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

Although the symbol files weren't initialized, there's enough info here to suggest that ASACPI.sys is the likely cause of the problem. What is the exact make and model of your system (or exact make and model of the motherboard if it's a custom build)?

My pc is in signature. I bulit by myself. Motherboard is asus maximus formula.
Yesterday, I install sp3 of xp 32 bit, and no bsod. I am not still 100% sure, but I tested occt & p2p programs 5 times after installed sp3 no bsod. Why?

Sorry, but I didn't notice your sig (eye problems).

Here's a link to the downloads page for your mobo in Italian ( http://it.asus.com/prog_content/middle_dow...amp;modelmenu=4 )

I'm having real problems with the Asus USA website so I can't provide any links from there - and I can't read enough Italian to navigate that website.

BUT, let it run for a while to see if SP3 fixed it - if it still gives problem, then you can try updating the chipset drivers.

thank you for support. Today I have problem too for connect to asus web site.
But I think to known that OCCt is "strange" program (this my opinion).
Because after installed sp3 no more bsod. But you can download and install (use) this program in two different way:
- autoinstall (.exe file)
- zip file but, you don't install, you only run the program.

With sp2 both made bsod. With sp3 , the first (.exe file) made bsod, but with the second no bsod. (all test with p2p open),
and the error is always tha same.

P.S. : I checked , in my pc I have already installed tha latest chipset driver.

1) Sometimes the latest driver can get corrupted - so that's still a possibility.

2) BUT, I think you found the problem when you used the .zip file. Something in the installer isn't working well with Windows (could be a registry entry that's incorrectly made) - so stick with the version that doesn't install.

Sorry, but I didn't fixed! Bsod came again. Now I can say it is random, and difficult to understand. Without p2p 90% goes fine, but sometime (few) bsod. With p2p 10% goes fine, 90% bsod. What asacpi.sys is and do? Can be psu?