Announcement

Collapse
No announcement yet.

BSOD Memory problem? Raise volts? or usb ?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    BSOD Memory problem? Raise volts? or usb ?

    EDIT: Problem solved, dram from 1.64 to 1.66 = 8 hours STABLE @ OCCT Large Data Set :)

    My settings:
    I7 920 D0 @ 4.2ghz w/ HT Enabled (200x21) @ 1.248v (CPU-Z)
    Gigabyte X58 Extreme Motherboard F8b bios
    OCZ 6GB DDR3 12800 @ 8-8-8-24 XMP Profile
    2x 4890
    Corsair HX 1000

    QPI/VTT: 1.30
    DRAM Voltage: 1.64
    QPI/PLL: 1.84
    Load Line Calibration: Enabled
    All Others: Auto

    I was able to run Prime 95 Small FFT w/ round of checking for 8 hours stable with the settings above.

    Ran OCCT Large data set around 2 hours test, and bsod after 40 minutes, and got the bsod(edit).

    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: occttest.exe

    CURRENT_IRQL: f

    STACK_TEXT:
    fffff800`0404bc18 fffff800`0313b72a : 00000000`00000124 00000000`00000000 fffffa80`08ddac6e 00000000`be000000 : nt!KeBugCheckEx
    fffff800`0404bc20 fffff800`02d3f3b3 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalBugCheckSystem+0x12e
    fffff800`0404bc90 fffff800`0313b097 : fffff800`00000c3e fffff800`0404be70 fffff800`0404bef0 00000000`00000000 : nt!WheaReportHwError+0x243
    fffff800`0404bcf0 fffff800`02c6f8b1 : 00000000`4179bf80 fffff800`0404bef0 00000000`39ba2220 00000000`00000000 : hal!HalReadDmaCounter+0x191b
    fffff800`0404bd30 fffff800`02c6f6f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x71
    fffff800`0404be70 00000000`00617c7e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
    00000000`0a3bb100 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x617c7e


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN

    BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN

    Followup: MachineOwner
    ---------
    Since it's an 0x124 error i tried something different i drop the qpi/vtt voltages to 1.24 and ran OCCT LARGE DATA again got this bsod and dump, it isn't 0x124 error anymore... 0x124 error usually means raise voltage or lower voltages, then i got different error below as you can see..

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffffa6003117e43, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002e47080
    0000000000000008

    CURRENT_IRQL: 2

    FAULTING_IP:
    usbuhci+4e43
    fffffa60`03117e43 48895808 mov qword ptr [rax+8],rbx

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: occttest.exe

    TRAP_FRAME: fffffa6001922b60 -- (.trap 0xfffffa6001922b60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa6001922cf8 rbx=0000000000000000 rcx=fffffa8007f49880
    rdx=fffffa8008dac258 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffa6003117e43 rsp=fffffa6001922cf8 rbp=fffffa8008dac010
    r8=0000000000000000 r9=0000000000000000 r10=fffffa8006457000
    r11=fffffa800a4d9bb0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    usbuhci+0x4e43:
    fffffa60`03117e43 48895808 mov qword ptr [rax+8],rbx ds:b300:fffffa60`01922d00=0000000000000002
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002c723ee to fffff80002c72650

    STACK_TEXT:
    fffffa60`01922a18 fffff800`02c723ee : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffffa60`01922a20 fffff800`02c712cb : 00000000`00000001 fffff800`03137e45 00000000`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x6e
    fffffa60`01922b60 fffffa60`03117e43 : fffffa60`03115197 00000000`00000002 fffffa80`08dac010 00000000`00000000 : nt!KiPageFault+0x20b
    fffffa60`01922cf8 fffffa60`03115197 : 00000000`00000002 fffffa80`08dac010 00000000`00000000 fffffa80`07f481a0 : usbuhci+0x4e43
    fffffa60`01922d00 fffffa60`03120eaa : fffffa80`07f48f00 fffffa60`0313b0a0 00000000`00000000 fffffa60`031206d6 : usbuhci+0x2197
    fffffa60`01922d30 fffffa60`03126e0e : 00000000`00000020 00000000`00000004 fffffa80`08dac010 fffffa80`07f48bf0 : USBPORT+0x1eaa
    fffffa60`01922d60 fffffa60`03136717 : 00000000`38496573 fffffa80`07f481a0 fffffa80`0000000e 00000000`00000000 : USBPORT+0x7e0e
    fffffa60`01922dd0 fffffa60`0312218b : fffffa80`32696368 fffffa80`07f48bf0 fffffa60`30745378 fffffa80`07f481a0 : USBPORT+0x17717
    fffffa60`01922e50 fffffa60`00a4e98a : fffffa80`07f00000 00000000`34776478 fffffa60`057e3ca0 fffffa80`07f48050 : USBPORT+0x318b
    fffffa60`01922ea0 fffffa80`07f00000 : 00000000`34776478 fffffa60`057e3ca0 fffffa80`07f48050 00000000`00000f44 : sptd+0x4398a
    fffffa60`01922ea8 00000000`34776478 : fffffa60`057e3ca0 fffffa80`07f48050 00000000`00000f44 fffffa60`01922f70 : 0xfffffa80`07f00000
    fffffa60`01922eb0 fffffa60`057e3ca0 : fffffa80`07f48050 00000000`00000f44 fffffa60`01922f70 00000000`75113301 : 0x34776478
    fffffa60`01922eb8 fffffa80`07f48050 : 00000000`00000f44 fffffa60`01922f70 00000000`75113301 00000000`00000000 : 0xfffffa60`057e3ca0
    fffffa60`01922ec0 00000000`00000f44 : fffffa60`01922f70 00000000`75113301 00000000`00000000 00000000`00000000 : 0xfffffa80`07f48050
    fffffa60`01922ec8 fffffa60`01922f70 : 00000000`75113301 00000000`00000000 00000000`00000000 fffffa80`07f48bf0 : 0xf44
    fffffa60`01922ed0 00000000`75113301 : 00000000`00000000 00000000`00000000 fffffa80`07f48bf0 fffffa60`005ec180 : 0xfffffa60`01922f70
    fffffa60`01922ed8 00000000`00000000 : 00000000`00000000 fffffa80`07f48bf0 fffffa60`005ec180 fffffa60`005ef580 : 0x75113301


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbuhci+4e43
    fffffa60`03117e43 48895808 mov qword ptr [rax+8],rbx

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: usbuhci+4e43

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usbuhci

    IMAGE_NAME: usbuhci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 479199d4

    FAILURE_BUCKET_ID: X64_0xD1_usbuhci+4e43

    BUCKET_ID: X64_0xD1_usbuhci+4e43

    Followup: MachineOwner
    ---------
    Anyone got ideas? USB Problem ? or just raise qpi/vtt volts.
    MODULE_NAME: usbuhci
    IMAGE_NAME: usbuhci.sys
    0xD1 error is ? O-o

    Edit: tried 2.6qpi/vtt then ran occt large data, almost 3 hours then bsod:

    check next post character limit..
    Last edited by zerosaku; 07-14-2009, 04:52 PM. Reason: solved
    Tags: None
  • #2
    Re: BSOD Memory problem? Raise volts? or usb ?

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

    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
    An attempt was made to write to readonly memory. The guilty driver is on the
    stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffffa6003112e48, Virtual address for the attempted write.
    Arg2: 0000000105267121, PTE contents.
    Arg3: fffffa6001922b60, (reserved)
    Arg4: 000000000000000a, (reserved)

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


    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xBE

    PROCESS_NAME: occttest.exe

    CURRENT_IRQL: 2

    TRAP_FRAME: fffffa6001922b60 -- (.trap 0xfffffa6001922b60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa6001922cf8 rbx=0000000000000000 rcx=fffffa80080f1880
    rdx=fffffa8008e22f28 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffa6003112e43 rsp=fffffa6001922cf8 rbp=fffffa8008e22ce0
    r8=0000000000000000 r9=0000000000000000 r10=fffffa8006451000
    r11=fffffa8006213af0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    usbuhci+0x4e43:
    fffffa60`03112e43 48895808 mov qword ptr [rax+8],rbx ds:3380:fffffa60`01922d00=0000000000000002
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002c6f58a to fffff80002c61650

    STACK_TEXT:
    fffffa60`01922a68 fffff800`02c6f58a : 00000000`000000be fffffa60`03112e48 00000001`05267121 fffffa60`01922b60 : nt!KeBugCheckEx
    fffffa60`01922a70 fffff800`02c601d9 : 00000000`00000001 fffff800`03126e45 00000000`00000000 00000000`00000002 : nt!MmAccessFault+0x28a
    fffffa60`01922b60 fffffa60`03112e43 : fffffa60`03110197 00000000`00000002 fffffa80`08e22ce0 00000000`00000000 : nt!KiPageFault+0x119
    fffffa60`01922cf8 fffffa60`03110197 : 00000000`00000002 fffffa80`08e22ce0 00000000`00000000 fffffa80`080f01a0 : usbuhci+0x4e43
    fffffa60`01922d00 fffffa60`0311beaa : fffffa80`080f0f00 fffffa60`031360a0 00000000`00000000 fffffa60`0311b6d6 : usbuhci+0x2197
    fffffa60`01922d30 fffffa60`03121e0e : 00000000`00000070 00000000`00000004 fffffa80`08e22ce0 fffffa80`080f0bf0 : USBPORT+0x1eaa
    fffffa60`01922d60 fffffa60`03131717 : 00000000`38496573 fffffa80`080f01a0 fffffa80`0000000e 00000000`00000000 : USBPORT+0x7e0e
    fffffa60`01922dd0 fffffa60`0311d18b : fffffa80`32696368 fffffa80`080f0bf0 fffffa60`30745378 fffffa80`080f01a0 : USBPORT+0x17717
    fffffa60`01922e50 fffffa60`00a4d98a : fffffa80`07f34000 00000000`34776478 fffffa60`09926ca0 fffffa80`080f0050 : USBPORT+0x318b
    fffffa60`01922ea0 fffffa80`07f34000 : 00000000`34776478 fffffa60`09926ca0 fffffa80`080f0050 00000000`00000f44 : sptd+0x4398a
    fffffa60`01922ea8 00000000`34776478 : fffffa60`09926ca0 fffffa80`080f0050 00000000`00000f44 fffffa60`01922f70 : 0xfffffa80`07f34000
    fffffa60`01922eb0 fffffa60`09926ca0 : fffffa80`080f0050 00000000`00000f44 fffffa60`01922f70 00000000`748e3301 : 0x34776478
    fffffa60`01922eb8 fffffa80`080f0050 : 00000000`00000f44 fffffa60`01922f70 00000000`748e3301 00000000`00000000 : 0xfffffa60`09926ca0
    fffffa60`01922ec0 00000000`00000f44 : fffffa60`01922f70 00000000`748e3301 00000000`00000000 00000000`00000000 : 0xfffffa80`080f0050
    fffffa60`01922ec8 fffffa60`01922f70 : 00000000`748e3301 00000000`00000000 00000000`00000000 fffffa80`080f0bf0 : 0xf44
    fffffa60`01922ed0 00000000`748e3301 : 00000000`00000000 00000000`00000000 fffffa80`080f0bf0 fffffa60`005ec180 : 0xfffffa60`01922f70
    fffffa60`01922ed8 00000000`00000000 : 00000000`00000000 fffffa80`080f0bf0 fffffa60`005ec180 fffffa60`005ef580 : 0x748e3301


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbuhci+4e43
    fffffa60`03112e43 48895808 mov qword ptr [rax+8],rbx

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: usbuhci+4e43

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usbuhci

    IMAGE_NAME: usbuhci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 479199d4

    FAILURE_BUCKET_ID: X64_0xBE_usbuhci+4e43

    BUCKET_ID: X64_0xBE_usbuhci+4e43

    Followup: MachineOwner
    ---------
    the usb errors are really weird.. so im gonna try going back to qpi/vtt at 1.30 and dram from 1.64 to 1.66 see if anything happens.

    Comment

    • #3
      Re: BSOD Memory problem? Raise volts? or usb ?

      This BSOD usually means your CPU has reached its max overclock and cant take it any more.

      Try these to be sure:

      1. Try 1.4V CPU Vcore
      2. Check if the system is stable at 200 MHz Bclk by reducing the multiplier to x19 and setting the CPU voltage to say 1.28 v.

      Comment

      • #4
        Re: BSOD Memory problem? Raise volts? or usb ?

        My above comments are due to the fact QPI / VTT voltage isnt helping.

        Comment

        • #5
          Re: BSOD Memory problem? Raise volts? or usb ?

          are you sure its the max overclock ? o_O anyway i am still testing occt again almost 2 hours stable with 1.66 dram voltage now.

          i did a search in xtremesystem and overclock.net didnt find anything related to that error with overclocking. although someone said to increase dram voltage thats all.

          Comment

          • #6
            Re: BSOD Memory problem? Raise volts? or usb ?

            Problem solved, dram from 1.64 to 1.66 = 8 hours STABLE @ OCCT Large Data Set

            please close

            Comment

            Previous template Next
            Working...
            X