BSOD 3b during installation process and occasionally on startup


  1. Posts : 4
    Windows 7 Professional x64
       #1

    BSOD 3b during installation process and occasionally on startup


    Hello,

    I recently added a second SSD to my setup. Everything worked fine for some time until yesterday morning. Normal Windows startup would lead straight to BSOD 3b.

    All Hard-drives worked fine in safe mode and since my installation of Windows 7 had been running for about three years without any issues I thought there must be some compatibility issues and that it might be time for a clean install. Now I don't get bccode 3b on startup anymore (which is good), but when installing large software (5 GB +, which is quite annoying since that is exactly what I got this second SSD for in the first place).

    I uninstalled all graphics drivers beside my NVIDIA drivers, updated all system drivers with "Slimdrivers" and I still get the SYSTEM SERVICE EXCEPTION 3b..

    So here is my zip.
    Any help would be much appreciated.
    Thanks

    Edit: Actually the BSOD occurs randomly while browsing and working with word, excel and acrobat - and thus is not restricted to startup and installation-processes
    Last edited by Homrich; 07 Jan 2015 at 09:08.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Both the BSODs are caused by cumon.sys, which is an element of Comodo.

    Uninstall Comodo, at least as a test.

    Let us know the result.
    ______________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88001174095, fffff8800b5e0570, 0}
    
    *** WARNING: Unable to verify timestamp for cumon.sys
    *** ERROR: Module load completed but symbols could not be loaded for cumon.sys
    Probably caused by : cumon.sys ( cumon+1095 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffff88001174095, Address of the instruction which caused the bugcheck
    Arg3: fffff8800b5e0570, 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: 
    cumon+1095
    fffff880`01174095 0fb7040b        movzx   eax,word ptr [rbx+rcx]
    
    CONTEXT:  fffff8800b5e0570 -- (.cxr 0xfffff8800b5e0570;r)
    rax=ffffffffffffffe9 rbx=0000077ff4a1ef54 rcx=fffff8800b5e10ae
    rdx=00000000000001e9 rsi=fffffa80088d42c0 rdi=0000000000000000
    rip=fffff88001174095 rsp=fffff8800b5e0f58 rbp=0000000000fe9da0
     r8=0000000000000017  r9=0000000000000000 r10=000000007fffffff
    r11=fffff8800b5e1080 r12=000000000043504d r13=fffff8800b5e1080
    r14=000000000000004d r15=ffffffffffffffff
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    cumon+0x1095:
    fffff880`01174095 0fb7040b        movzx   eax,word ptr [rbx+rcx] ds:002b:00000000`00000002=????
    Last set context:
    rax=ffffffffffffffe9 rbx=0000077ff4a1ef54 rcx=fffff8800b5e10ae
    rdx=00000000000001e9 rsi=fffffa80088d42c0 rdi=0000000000000000
    rip=fffff88001174095 rsp=fffff8800b5e0f58 rbp=0000000000fe9da0
     r8=0000000000000017  r9=0000000000000000 r10=000000007fffffff
    r11=fffff8800b5e1080 r12=000000000043504d r13=fffff8800b5e1080
    r14=000000000000004d r15=ffffffffffffffff
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    cumon+0x1095:
    fffff880`01174095 0fb7040b        movzx   eax,word ptr [rbx+rcx] ds:002b:00000000`00000002=????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  CPM.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8800117c506 to fffff88001174095
    
    STACK_TEXT:  
    fffff880`0b5e0f58 fffff880`0117c506 : 00000000`00000000 fffffa80`075527c0 fffffa80`088d42c0 00000000`000007ff : cumon+0x1095
    fffff880`0b5e0f60 00000000`00000000 : fffffa80`075527c0 fffffa80`088d42c0 00000000`000007ff 00000000`003a0044 : cumon+0x9506
    
    
    FOLLOWUP_IP: 
    cumon+1095
    fffff880`01174095 0fb7040b        movzx   eax,word ptr [rbx+rcx]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  cumon+1095
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cumon
    
    IMAGE_NAME:  cumon.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e64a34a
    
    STACK_COMMAND:  .cxr 0xfffff8800b5e0570 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_cumon+1095
    
    BUCKET_ID:  X64_0x3B_cumon+1095
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_cumon+1095
    
    FAILURE_ID_HASH:  {3cb15640-824f-17a0-773a-219d9e916458}
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm cumon
    start             end                 module name
    fffff880`01173000 fffff880`011aa000   cumon    T (no symbols)           
        Loaded symbol image file: cumon.sys
        Image path: \SystemRoot\system32\drivers\cumon.sys
        Image name: cumon.sys
        Timestamp:        Mon Sep 05 15:54:10 2011 (4E64A34A)
        CheckSum:         000370A6
        ImageSize:        00037000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #3

    Thanks for the quick reply.

    It's uninstalled and I will let you know if that did the trick. I have used the uninstall manager of comodo for months and never had any issues with it.
      My Computer


  4. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #4

    Indeed. Comodo was the problem.

    Thanks!
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Welcome.

    Let us know for any further issue.
      My Computer


 

  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 15:16.
Find Us