TechSpot

bsod

By Kryxx
Jul 19, 2007
  1. Any Ideas? (dump included)

    Ive been doing some testing on all things that could be causing my bsod errors, one of them was my old audio (onboard) which i rectified. But now, I noticed that my new memory that I just popped in awhile ago was reading at : 5-5-5-15 T2 when the specs are supposed to be 4-4-4-15 T1. I have all the current bios/driver updates and no conflicting versions. I went in and manually set the correct timings and voltage as listed by the manufacturer.

    Would this mis-configuration cause hangups and crashes? It's the only hardware I can think of that could be the problem.

    I will post some dump files shortly after this recent change.

    This was the one I got before Trying these new settings :

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 40e38004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 8054510c, address which referenced memory

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


    READ_ADDRESS: 40e38004

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!WmiTraceMessageVa+73
    8054510c 8b5504 mov edx,dword ptr [ebp+4]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from badbed8e to 8054510c

    STACK_TEXT:
    80550134 badbed8e 889946f8 889946f8 87e425a0 nt!WmiTraceMessageVa+0x73
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    80550150 00000000 88168a30 804f1518 89c964e0 0xbadbed8e


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!WmiTraceMessageVa+73
    8054510c 8b5504 mov edx,dword ptr [ebp+4]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!WmiTraceMessageVa+73

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d

    FAILURE_BUCKET_ID: 0xA_nt!WmiTraceMessageVa+73

    BUCKET_ID: 0xA_nt!WmiTraceMessageVa+73

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






    Heres a dump after those settings :


    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: b0236144, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 804dc83f, address which referenced memory

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


    READ_ADDRESS: b0236144

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KeWaitForSingleObject+13d
    804dc83f 85be24010000 test dword ptr [esi+124h],edi

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: VGClient.exe

    LAST_CONTROL_TRANSFER: from 804e21e3 to 804dc83f

    STACK_TEXT:
    af2d4974 804e21e3 87b598e0 00000000 87b59870 nt!KeWaitForSingleObject+0x13d
    af2d49bc 805701b4 00000001 af2d4bf0 00000001 nt!Dr_kitf_a+0x3a
    af2d4d48 804ddf0f 00000001 0f66fea0 00000001 nt!SeCreateClientSecurity+0x4c
    af2d4d5c 00000000 0f66ff14 7c90eb94 badb0d00 nt!ZwSetBootEntryOrder+0xc


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KeWaitForSingleObject+13d
    804dc83f 85be24010000 test dword ptr [esi+124h],edi

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KeWaitForSingleObject+13d

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa

    FAILURE_BUCKET_ID: 0xA_nt!KeWaitForSingleObject+13d

    BUCKET_ID: 0xA_nt!KeWaitForSingleObject+13d

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


    didnt seem to do the trick, Any suggestions on what to try? Its gotta be hardware I know that.

    Edit : trying 1 stick of ram to see if its that. ( i know it says driver fault but I wouldnt know which damn driver it is =\ just goin through the steps )
     
  2. raybay

    raybay TS Evangelist Posts: 7,241   +9

    Isn't this a duplicate posting?
     
  3. Kryxx

    Kryxx TS Rookie Topic Starter

    hmm yea, sorry. My browser didnt show it as posted when I hit submit, and I noticed i was probably in the wrong category since It is more than likely a driver issue. I moved over there and it posted successfully. I dont see a delete option so I can't remove it =\

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