Hello Nightsworn, welcome to PCHF.

Please can you follow the posting instructions for this section (or BSOD's link on my signature) for instructions on how to collect all of the log files we need. Quite often, one log file isn't enough to diagnose stop errors, particularly if the problem is caused by hardware such as faulty RAM can cause complete random stop errors. Personally, I tend to use at least two or more for comparison.

Hey Nighhtworn,

Your problems appear to be caused by your onboard nForce audio driver (nvapu.sys).

Downloading the latest drivers from the nVidia web site should resolve your problems: http://www.nvidia.com/Download/index.aspx?lang=en-us

BUGCHECK

Code:

Loading Dump File [C:\Users\admin\Desktop\PCHF\Mini062412-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
WARNING: Inaccessible path: 'C:\Program Files\Debugging Tools for Windows (x64)\symbols'
Symbol search path is: C:\Program Files\Debugging Tools for Windows (x64)\symbols;http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120504-1619
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b2c0
Debug session time: Sun Jun 24 14:43:55.350 2012 (GMT+1)
System Uptime: 0 days 1:50:41.966
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck C2, {7, cd4, 908060da, 804ec8b1}
 
Unable to load image nvapu.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvapu.sys
*** ERROR: Module load completed but symbols could not be loaded for nvapu.sys
Probably caused by : portcls.sys ( portcls!CPortPinWavePci::DeviceIoControl+202 )
 
Followup: MachineOwner
---------
 
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 908060da, Memory contents of the pool block
Arg4: 804ec8b1, Address of the block of pool being deallocated
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0xc2_7
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
LAST_CONTROL_TRANSFER:  from 8054c5c1 to 80533876
 
STACK_TEXT:  
f4070868 8054c5c1 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f40708b8 804f13f7 804ec8b1 00000000 00000000 nt!ExFreePoolWithTag+0x2be
f40708e4 f7d9d240 82136790 82136848 ffffffff nt!IopfCompleteRequest+0x156
f407090c f7d9b74d 82158280 82136790 820ba008 portcls!CPortPinWavePci::DeviceIoControl+0x202
f4070928 f8226f1f 82136790 820ba008 f4070950 portcls!DispatchDeviceIoControl+0x49
f4070938 f7d9b8c0 82136790 820ba008 00000000 ks!KsDispatchIrp+0x126
f4070950 f7d9b881 82136790 820ba008 f4070b6c portcls!KsoDispatchIrp+0x43
f4070960 f7b96d23 82136790 820ba008 00000000 portcls!PcDispatchIrp+0x5f
WARNING: Stack unwind information not available. Following frames may be wrong.
f4070b6c 804e3807 82136790 820ba008 820ba008 nvapu+0x12d23
f4070b7c f6461774 e23bd2a8 00000000 820ba008 nt!IopfCallDriver+0x31
f4070bcc f64642a2 820ba008 00000000 e2275c58 sysaudio!ForwardIrpNode+0x1b2
f4070c24 f8226f95 822cf790 820ba008 f4070c58 sysaudio!CPinInstance::PinDispatchIoControl+0x153
f4070c34 804e3807 822cf790 820ba008 806f0070 ks!DispatchDeviceIoControl+0x28
f4070c44 80568211 820ba150 81a149d0 820ba008 nt!IopfCallDriver+0x31
f4070c58 8057714a 822cf790 820ba008 81a149d0 nt!IopSynchronousServiceTail+0x70
f4070d00 8057966d 00000214 000002c4 00000000 nt!IopXxxControlFile+0x611
f4070d34 804de7ec 00000214 000002c4 00000000 nt!NtDeviceIoControlFile+0x2a
f4070d34 7c90e514 00000214 000002c4 00000000 nt!KiFastCallEntry+0xf8
046dfdc4 00000000 00000000 00000000 00000000 0x7c90e514
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
portcls!CPortPinWavePci::DeviceIoControl+202
f7d9d240 ebb9            jmp     portcls!CPortPinWavePci::DeviceIoControl+0x202 (f7d9d1fb)
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  portcls!CPortPinWavePci::DeviceIoControl+202
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: portcls
 
IMAGE_NAME:  portcls.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  48025ccc
 
FAILURE_BUCKET_ID:  0xc2_7_portcls!CPortPinWavePci::DeviceIoControl+202
 
BUCKET_ID:  0xc2_7_portcls!CPortPinWavePci::DeviceIoControl+202
 
Followup: MachineOwner
---------
 
kd> lmvft m nvapu
start    end        module name
f7b84000 f7be4b00   nvapu    nvapu.sys   
    Loaded symbol image file: nvapu.sys
    Symbol file: nvapu.sys
    Image name: nvapu.sys
    Timestamp:        Tue May 25 23:58:02 2004 (40B3CF7A)
    CheckSum:         00067B1F
    ImageSize:        00060B00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I suspected under Legacy > nForce audio, but I don't have enough information about your system to know for certain.. What is the full make and model of the PC?

It should be printed on a label on the PC, usually on the side, sometimes on the back, occasionally even underneath.. it really depends on the make of the PC unless it was custom built.

Where did you buy it from? do you have any of the original documentation? do you have recovery media? anything at all?

There's a little utility that might help called SIW.
After you run it, click on the save button will create a .html document you'll be able to upload here?

It looks like the Legacy > nForce 1/2 series you'll need Night.

At what point do you get that night? seems to download OK for me, and there are also mirror sites to choose from.