TechSpot

BSOD Unknown faulty driver

By Darknesh
Apr 7, 2009
  1. My system has been running without any major problems for long time and now suddenly i started getting bsods and complete freezes couple times per hour.
    When this started i didnt install anything new on my system or change any important things.
    Bsod/freeze occurs more likely if i use many programs.
    I tried updating all my drivers, removed all non important drivers and restoring system.

    My minidumps was too large to be attached so ill just paste my debug here:

    1.

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff80001cbb107, The address that the exception occurred at
    Arg3: fffffa60071209c8, Exception Record Address
    Arg4: fffffa60071203a0, Context Record Address

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


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {POIKKEUS} Laiton k sky Yritettiin suorittaa laiton k sky.

    FAULTING_IP:
    nt!KiExitDispatcher+237
    fffff800`01cbb107 ff ???

    EXCEPTION_RECORD: fffffa60071209c8 -- (.exr 0xfffffa60071209c8)
    ExceptionAddress: fffff80001cbb107 (nt!KiExitDispatcher+0x0000000000000237)
    ExceptionCode: c000001d (Illegal instruction)
    ExceptionFlags: 00000000
    NumberParameters: 0

    CONTEXT: fffffa60071203a0 -- (.cxr 0xfffffa60071203a0)
    rax=6c617ef354a729e0 rbx=000000009995661f rcx=fffffa60082d7198
    rdx=009995661f44ab60 rsi=fffffa60082fa250 rdi=0000000000000000
    rip=fffff80001cbb107 rsp=fffffa6007120c08 rbp=0000000000000001
    r8=0000000000fc0000 r9=0000000000000000 r10=fffff80001dd54c0
    r11=fffff800032a9d50 r12=0000000000000004 r13=00000000000001cf
    r14=fffffa8007e694d0 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
    nt!KiExitDispatcher+0x237:
    fffff800`01cbb107 ff ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x7E

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc000001d - {POIKKEUS} Laiton k sky Yritettiin suorittaa laiton k sky.

    MISALIGNED_IP:
    nt!KiExitDispatcher+237
    fffff800`01cbb107 ff ???

    LAST_CONTROL_TRANSFER: from fffffa8007de0ca8 to fffff80001cbb107

    FAILED_INSTRUCTION_ADDRESS:
    nt!KiExitDispatcher+237
    fffff800`01cbb107 ff ???

    STACK_TEXT:
    fffffa60`07120c08 fffffa80`07de0ca8 : fffffa80`07e694e0 00000000`00000000 fffff800`01cb776a fffffa60`00000003 : nt!KiExitDispatcher+0x237
    fffffa60`07120c38 fffffa80`07e694e0 : 00000000`00000000 fffff800`01cb776a fffffa60`00000003 00000000`00000018 : 0xfffffa80`07de0ca8
    fffffa60`07120c40 00000000`00000000 : fffff800`01cb776a fffffa60`00000003 00000000`00000018 fffffa60`07120c60 : 0xfffffa80`07e694e0


    FOLLOWUP_IP:
    nt!KiExitDispatcher+237
    fffff800`01cbb107 ff ???

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KiExitDispatcher+237

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .cxr 0xfffffa60071203a0 ; kb

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: X64_IP_MISALIGNED

    BUCKET_ID: X64_IP_MISALIGNED

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

    2.

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

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s.

    FAULTING_IP:
    nt!CmpCacheLookup+12a
    fffff800`01ece6fa 418b4424fc mov eax,dword ptr [r12-4]

    CONTEXT: fffffa6009cb8990 -- (.cxr 0xfffffa6009cb8990)
    rax=0000000063e957e8 rbx=0000000000000000 rcx=0000000000001641
    rdx=0000000007eca2af rsi=0000000000000003 rdi=fffff88000c3f808
    rip=fffff80001ece6fa rsp=fffffa6009cb91f0 rbp=fffffa6009cb9360
    r8=000000006b75f972 r9=0000000000000005 r10=0000000000000000
    r11=0000000000000000 r12=00000000000000c0 r13=fffffa6009cb9368
    r14=fffff88000c3f808 r15=0000000000000002
    iopl=0 nv up ei pl nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
    nt!CmpCacheLookup+0x12a:
    fffff800`01ece6fa 418b4424fc mov eax,dword ptr [r12-4] ds:002b:00000000`000000bc=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: taskeng.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80001ecf395 to fffff80001ece6fa

    STACK_TEXT:
    fffffa60`09cb91f0 fffff800`01ecf395 : fffffa60`09cb9330 fffffa60`00000004 fffffa60`09cb9770 fffffa60`09cb9750 : nt!CmpCacheLookup+0x12a
    fffffa60`09cb92d0 fffff800`01ecfd5a : fffffa60`09cb9b70 fffffa60`09cb9750 fffffa60`09cb9740 fffffa60`09cb9758 : nt!CmpBuildHashStackAndLookupCache+0x276
    fffffa60`09cb9670 fffff800`01edf73e : 00000000`00000040 fffff880`00000000 fffffa80`083c4b10 fffff800`01ee1f01 : nt!CmpParseKey+0x20a
    fffffa60`09cb9910 fffff800`01ee3944 : 00000000`00000018 fffffa80`0812cd01 00000000`00000040 fffffa80`03cc8dc0 : nt!ObpLookupObjectName+0x2ce
    fffffa60`09cb9a20 fffff800`01ecaf2f : fffffa80`00000001 00000000`00000000 fffffa80`0455d601 00000000`00000001 : nt!ObOpenObjectByName+0x2f4
    fffffa60`09cb9af0 fffff800`01c5fdf3 : 00000000`0321ee48 fffffa60`00000001 00000000`0321ecc0 00000000`00000000 : nt!CmOpenKey+0x25d
    fffffa60`09cb9c20 00000000`77505b9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0321ec78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77505b9a


    FOLLOWUP_IP:
    nt!CmpCacheLookup+12a
    fffff800`01ece6fa 418b4424fc mov eax,dword ptr [r12-4]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!CmpCacheLookup+12a

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

    STACK_COMMAND: .cxr 0xfffffa6009cb8990 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_nt!CmpCacheLookup+12a

    BUCKET_ID: X64_0x3B_nt!CmpCacheLookup+12a

    Followup: MachineOwner
    ---------
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

  3. Darknesh

    Darknesh TS Rookie Topic Starter

    Memory looks fine
     
  4. Spyder_1386

    Spyder_1386 TS Rookie Posts: 498

    hi Darknesh

    Update your hardware drivers ... that error is usually caused by driver issues. Install one at a time so you can see which one was the problem child.

    Spyder_1386 :)
     
  5. Darknesh

    Darknesh TS Rookie Topic Starter

    Looks like that reinstalling nod32 antivirus solved problem. Thanks for your tips.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...