BSOD Team Fortress 2 Crash Report

[TWillie]

Team Fortress 2 BSOD Crash Report

View attachment 207959

ntoskrnl.exe & nvlddmkm.sys just crashed the system with a Critical BSOD error. Nvidia display driver ver. 296.10
All drivers current.

 

[zigzag3143]

No DMPs included in upload try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[TWillie]

I have added the .txt extension to the .dmp file to upload it. It was included as a .dmp file in my earlier upload.

 

[writhziden]

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


Loading Dump File [D:\Kingston\BSODDmpFiles\TWillie\04182012 Team Fortress 2 BSOD ntoskrnl.exe+27740 nvlddmkm.sys+2af649\Windows_NT6_BSOD_jcgriff2\041812-31012-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`02a57000 PsLoadedModuleList = 0xfffff800`02c9b650
Debug session time: Wed Apr 18 15:32:02.555 2012 (UTC - 6:00)
System Uptime: 0 days 1:22:43.240
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa80101be968, 2, 0, fffff880101b37ff}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa80101be968, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880101b37ff, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d05100
 fffffa80101be968 

CURRENT_IRQL:  2

FAULTING_IP: 
portcls!CPortWavePci::Notify+f
fffff880`101b37ff ff5018          call    qword ptr [rax+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  hl2.exe

TRAP_FRAME:  fffff800042b0570 -- (.trap 0xfffff800042b0570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80101be950 rbx=0000000000000000 rcx=fffffa8004280250
rdx=fffffa8004280250 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880101b37ff rsp=fffff800042b0700 rbp=0000000000000000
 r8=00000000b1a3ac80  r9=0000000001cd1daa r10=fffff80002a57000
r11=fffff800042b07e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
portcls!CPortWavePci::Notify+0xf:
fffff880`101b37ff ff5018          call    qword ptr [rax+18h] ds:fffffa80`101be968=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad3229 to fffff80002ad3c80

STACK_TEXT:  
fffff800`042b0428 fffff800`02ad3229 : 00000000`0000000a fffffa80`101be968 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`042b0430 fffff800`02ad1ea0 : 00000000`00000000 00000000`00000002 fffffa80`0a3d9070 fffffa80`04175520 : nt!KiBugCheckDispatch+0x69
fffff800`042b0570 fffff880`101b37ff : fffff800`042b0848 fffff880`04461882 fffff800`042b0848 fffff880`0483fb20 : nt!KiPageFault+0x260
fffff800`042b0700 fffff880`0492c671 : fffff800`02c48e80 fffffa80`0a0f8b60 fffff800`042b0e88 00000000`00000003 : portcls!CPortWavePci::Notify+0xf
fffff800`042b0730 fffff800`02c48e80 : fffffa80`0a0f8b60 fffff800`042b0e88 00000000`00000003 fffff800`02c48e80 : ctaud2k+0x6671
fffff800`042b0738 fffffa80`0a0f8b60 : fffff800`042b0e88 00000000`00000003 fffff800`02c48e80 fffff880`0492daa5 : nt!KiInitialPCR+0x180
fffff800`042b0740 fffff800`042b0e88 : 00000000`00000003 fffff800`02c48e80 fffff880`0492daa5 fffff800`02c4b080 : 0xfffffa80`0a0f8b60
fffff800`042b0748 00000000`00000003 : fffff800`02c48e80 fffff880`0492daa5 fffff800`02c4b080 00000000`0000ca00 : 0xfffff800`042b0e88
fffff800`042b0750 fffff800`02c48e80 : fffff880`0492daa5 fffff800`02c4b080 00000000`0000ca00 fffffa80`041755c0 : 0x3
fffff800`042b0758 fffff880`0492daa5 : fffff800`02c4b080 00000000`0000ca00 fffffa80`041755c0 fffffa80`04175600 : nt!KiInitialPCR+0x180
fffff800`042b0760 fffff800`02c4b080 : 00000000`0000ca00 fffffa80`041755c0 fffffa80`04175600 00000000`00000000 : ctaud2k+0x7aa5
fffff800`042b0768 00000000`0000ca00 : fffffa80`041755c0 fffffa80`04175600 00000000`00000000 fffff800`02ad931a : nt!KiInitialPCR+0x2380
fffff800`042b0770 fffffa80`041755c0 : fffffa80`04175600 00000000`00000000 fffff800`02ad931a fffff800`042b0830 : 0xca00
fffff800`042b0778 fffffa80`04175600 : 00000000`00000000 fffff800`02ad931a fffff800`042b0830 fffff800`02ade95c : 0xfffffa80`041755c0
fffff800`042b0780 00000000`00000000 : fffff800`02ad931a fffff800`042b0830 fffff800`02ade95c 00000000`00000000 : 0xfffffa80`04175600


STACK_COMMAND:  kb

FOLLOWUP_IP: 
portcls!CPortWavePci::Notify+f
fffff880`101b37ff ff5018          call    qword ptr [rax+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  portcls!CPortWavePci::Notify+f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: portcls

IMAGE_NAME:  portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc03

FAILURE_BUCKET_ID:  X64_0xD1_portcls!CPortWavePci::Notify+f

BUCKET_ID:  X64_0xD1_portcls!CPortWavePci::Notify+f

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

The above crash appears to have been caused by a corrupted driver for your Creative Audio device. Recommend uninstalling and re-installing the Creative Audio device drivers.

First, download the latest drivers for the device from Creative Worldwide Support.

To re-install, use the following steps.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Expand Sound, video and game controllers
6. Right click the Creative Audio device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device and hit OK
9. Restart the computer only if Windows asks you to
10. Install the downloaded driver for the Creative Audio device.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Expand Sound, video and game controllers
7. Right click the Creative Audio device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device and hit OK
10. Restart the computer only if Windows asks you to
11. Install the downloaded driver for the Creative Audio device.