BSOD is back...

[SenojNW]

Guys
Well my system remained stable for almost a month - then two BSOD in rapid succession tonight.

I've attached the dump files if someone could take a look and provide some pointers?

Here's my history:
http://www.sevenforums.com/crashes-debugging/80397-minidump-file-analysis.html

http://www.sevenforums.com/crashes-debugging/76499-bsod-diagnosis.html

Interestingly this time after rebooting my Logitech diNovo bluetooth keyboard/mouse won't work at all... Edit: keyboard was just up to its usual connectivity antics - not related to this I don't think.

Thanks guys...

 

[zigzag3143]

Guys
Well my system remained stable for almost a month - then two BSOD in rapid succession tonight.

I've attached the dump files if someone could take a look and provide some pointers?

Here's my history:
http://www.sevenforums.com/crashes-debugging/80397-minidump-file-analysis.html

http://www.sevenforums.com/crashes-debugging/76499-bsod-diagnosis.html

Interestingly this time after rebooting my Logitech diNovo bluetooth keyboard/mouse won't work at all...

Thanks guys...

These were caused by portcls.sys which is win 7 sound driver. I would run a system file check to verify and repair these files.
Type cmd in search>right click and run as admin>sfc /scannow


Let us know the results as you may have to run it more than once.

let us know if you need help

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (4)\051210-18626-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`01804000 PsLoadedModuleList = 0xfffff800`01a41e50
Debug session time: Wed May 12 08:49:06.319 2010 (GMT-4)
System Uptime: 0 days 3:39:32.991
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880038e80eb, fffff88009a11bc0, 0}

Probably caused by : portcls.sys ( portcls!xDispatchCreate+f7 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880038e80eb, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009a11bc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
portcls!xDispatchCreate+f7
fffff880`038e80eb ff5018          call    qword ptr [rax+18h]

CONTEXT:  fffff88009a11bc0 -- (.cxr 0xfffff88009a11bc0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800511eb78
rdx=fffffa8003b0cb98 rsi=fffffa8003b0cb90 rdi=fffffa8003aa2540
rip=fffff880038e80eb rsp=fffff88009a12590 rbp=fffffa8004d278d0
 r8=fffffa8003b0cba0  r9=0000000000000000 r10=fffff800019ef7c0
r11=fffff88009a12520 r12=fffffa800511eb78 r13=0000000000000001
r14=0000000000000000 r15=fffffa8004d27780
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
portcls!xDispatchCreate+0xf7:
fffff880`038e80eb ff5018          call    qword ptr [rax+18h] ds:002b:00000000`00000018=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  OUTLOOK.EXE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880038e80eb

STACK_TEXT:  
fffff880`09a12590 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : portcls!xDispatchCreate+0xf7


FOLLOWUP_IP: 
portcls!xDispatchCreate+f7
fffff880`038e80eb ff5018          call    qword ptr [rax+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  portcls!xDispatchCreate+f7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: portcls

IMAGE_NAME:  portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc03

STACK_COMMAND:  .cxr 0xfffff88009a11bc0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_portcls!xDispatchCreate+f7

BUCKET_ID:  X64_0x3B_portcls!xDispatchCreate+f7

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

 

[SenojNW]

Just ran it - it didn't find any problems. Shall I run again?

Sounds like I need a clean install...

 

[Crispy]

Try reinstalling Microsoft office, OUTLOOK.EXE looks to be the faulting program.

 

[SenojNW]

BSOD Diagnosis

Could someone take a look at these dumps and let me know where they are pointing?

Thanks

 

[SenojNW]

Thanks for moving this mods... sorry bout that.

BTW - between my original post above and the post yesterday I have done a full clean install of Win7 and all programs etc.

Attached is one from today with verifier running.

Don't know what to try next...

 

[SenojNW]

BlueScreen View is pointing to 'ntoskrnl.exe' as causing the BSOD for 3 out of the 4 occasions since I did the clean install. Others were 1) 'cmudaxp.sys' (with 'ntoskrnl' at the same time) and 2) 'portcls.sys'

No activity in particular seems to trigger this.

Can I rule out hardware? As per earlier posts I have replaced my RAM and scanned hard drives.

And seeing these are Windows drivers should I have all drivers selected in verifier? I followed the instructions on the forum and didn't select any Microsoft drivers.

 

[Bill2]

I havent looked at your dumps but going by what you are saying.

Portcls.sys and Cmudaxp.sys

The first one is a windows audio driver and the second is a C-Media driver thats part of the Asus driver set.

Update/ downdate/ reinstall all your sound drivers. If you have a separate sound card (in addition to your onboard sound), remove it, then check.

 

[SenojNW]

Thanks Bill
What about all the reference to 'ntoskrnl.exe'?

I actually have a HT Omega Claro sound card installed which would explain the C-Media driver as I have nothing Asus in this system. I'll update my system specs in my profile.

I'll try reinstalling the drivers for the Claro before I remove it as I would dearly prefer to have that running rather than the sh*tty onboard sound seeing this is a HTPC...

 

[SenojNW]

bump...

 

[Jonathan_King]

ntosknrl.exe is just the default file debuggers like WhoCrashedIt and BlueScreeView blame. It is inaccurate, because we know that file does not cause BSODs, being a core Windows file.

Follow Bill's advice. Your sound drivers are causing the issue. Please uninstall them and install a fresh copy.

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_dump verifier.zip\060210-15678-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`01864000 PsLoadedModuleList = 0xfffff800`01aa1e50
Debug session time: Tue Jun  1 22:46:52.851 2010 (GMT-4)
System Uptime: 0 days 0:15:37.912
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8005fa5b60, 2, 1, fffff88003a3698e}

Unable to load image \SystemRoot\system32\drivers\cmudaxp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
Probably caused by : cmudaxp.sys ( cmudaxp+2a98e )

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

 

[SenojNW]

Thanks Jonathan
Well I uninstalled my Claro soundcard and got a BSOD when I tried to reinstall its drivers so I guess that's a fair sign...

So I've pulled the card, uninstalled the drivers and related aps, and am running on Realtek onboard sound (after re-enabling in mobo BIOS). Will see if the BSOD's stop...