BSOD is back...

Page 1 of 2 12 LastLast

  1. Posts : 21
    Seven64 Ultimate
       #1

    BSOD is back...


    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:
    https://www.sevenforums.com/crashes-d...-analysis.html

    https://www.sevenforums.com/crashes-d...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...
    Last edited by SenojNW; 02 Jun 2010 at 04:15.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    SenojNW said:
    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:
    https://www.sevenforums.com/crashes-d...-analysis.html

    https://www.sevenforums.com/crashes-d...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

    Code:
    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
    ---------
      My Computer


  3. Posts : 21
    Seven64 Ultimate
    Thread Starter
       #3

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

    Sounds like I need a clean install...
      My Computer


  4. Posts : 1,039
    Windows 7 Ultimate x64 Service Pack 1 (Build 6.1.7601)
       #4

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


  5. Posts : 21
    Seven64 Ultimate
    Thread Starter
       #5

    BSOD Diagnosis


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

    Thanks
      My Computer


  6. Posts : 21
    Seven64 Ultimate
    Thread Starter
       #6

    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...
      My Computer


  7. Posts : 21
    Seven64 Ultimate
    Thread Starter
       #7

    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.
    Last edited by SenojNW; 02 Jun 2010 at 03:14. Reason: various errors
      My Computer


  8. Posts : 5,056
    Windows 7 x64 pro/ Windows 7 x86 Pro/ XP SP3 x86
       #8

    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.
      My Computer


  9. Posts : 21
    Seven64 Ultimate
    Thread Starter
       #9

    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...
      My Computer


  10. Posts : 21
    Seven64 Ultimate
    Thread Starter
       #10

    bump...
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:59.
Find Us