Announcement

Collapse
No announcement yet.

F3-10600CL7D-4GBPI Problems

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • F3-10600CL7D-4GBPI Problems

    F3-10600CL7D-4GBPI (2x2GB)
    Intel Q8200
    GA-EP45T-DS3R
    Gigabyte HD4850

    I've been having a problem with the memory stated. The computer runs just fine with both sticks of memory in however when I start playing a game not long after the game either crashes or I get a BSOD. If I remove one of the sticks of memory everything works perfectly without crashing or giving me a BSOD. I've run Memtest for well over 3 hours and both sticks came up with no errors. Do you know what's wrong?

  • #2
    try to uninstall ATI CCC and install only driver
    thanks


    G.S

    Comment


    • #3
      Removed all ATI drivers with drive cleaner and installed 8.12 driver only. Problem still persists.

      EDIT

      It also crashes while watching videos so it is definently ATI related.
      Last edited by Shutey; 01-06-2009, 09:42 PM.

      Comment


      • #4
        it would be more possible to be video issue, but not sure it's driver or hardware problem....


        G.S

        Comment


        • #5
          I've tried single stick with both memory sticks again and one particular stick replicates the problems I had when I had inserted both sticks into the motherboard. Is it likely it's just a faulty stick?

          EDIT

          I ran memtest with that single stick. 9 Passes and no errors. I'm really clueless as to what's causing my problems.

          EDIT2

          I had another BSOD with the memory stick I had just tested. I was not playing a game or movie at the time. I can post a minidump if that would help.
          Last edited by Shutey; 01-07-2009, 11:36 PM.

          Comment


          • #6
            could you post the code on the blue screen?
            it might help us to find out the reason
            thanks


            G.S

            Comment


            • #7
              I've put both sticks into slots 3 and 4 instead of 1 and 2. Haven't had a problem yet running games. Will reply again if the problem returns.

              Comment


              • #8
                ok
                we'll wait for your feed back
                thanks


                G.S

                Comment


                • #9
                  Problem still persists. Reformatted and reintalled windows as well but it's still happening. Here's a minidump.

                  KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
                  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: c0000005, The exception code that was not handled
                  Arg2: 8204b2b9, The address that the exception occurred at
                  Arg3: 9b164a40, Trap Frame
                  Arg4: 00000000

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


                  EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

                  FAULTING_IP:
                  nt!ObAssignSecurity+12
                  8204b2b9 ff762c push dword ptr [esi+2Ch]

                  TRAP_FRAME: 9b164a40 -- (.trap 0xffffffff9b164a40)
                  ErrCode = 00000000
                  eax=00000000 ebx=87e64030 ecx=9b164b00 edx=00000000 esi=00000000 edi=8431cd40
                  eip=8204b2b9 esp=9b164ab4 ebp=9b164ae4 iopl=0 nv up ei pl zr na pe nc
                  cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
                  nt!ObAssignSecurity+0x12:
                  8204b2b9 ff762c push dword ptr [esi+2Ch] ds:0023:0000002c=????????
                  Resetting default scope

                  CUSTOMER_CRASH_COUNT: 1

                  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

                  BUGCHECK_STR: 0x8E

                  PROCESS_NAME: lsm.exe

                  CURRENT_IRQL: 0

                  LAST_CONTROL_TRANSFER: from 8204b282 to 8204b2b9

                  STACK_TEXT:
                  9b164ae4 8204b282 bb9ac380 9b164b00 00000008 nt!ObAssignSecurity+0x12
                  9b164b04 8205282c bb9ac380 9b164bec 9b164b50 nt!ObAssignObjectSecurityDescriptor+0x24
                  9b164b14 8204b31e b7175560 00000003 00000000 nt!SeDefaultObjectMethod+0x32
                  9b164b50 8208c899 9b164b00 00000001 b7175560 nt!ObAssignSecurity+0x77
                  9b164c84 8204f58e b7175560 00000000 00000008 nt!ObInsertObject+0x542
                  9b164d30 82051a8f fffffffe 00000008 00000000 nt!NtOpenThreadTokenEx+0x157
                  9b164d4c 81e9ba1a fffffffe 00000008 00000000 nt!NtOpenThreadToken+0x18
                  9b164d4c 77259a94 fffffffe 00000008 00000000 nt!KiFastCallEntry+0x12a
                  WARNING: Frame IP not in any known module. Following frames may be wrong.
                  00c4f228 00000000 00000000 00000000 00000000 0x77259a94


                  STACK_COMMAND: kb

                  FOLLOWUP_IP:
                  nt!ObAssignSecurity+12
                  8204b2b9 ff762c push dword ptr [esi+2Ch]

                  SYMBOL_STACK_INDEX: 0

                  SYMBOL_NAME: nt!ObAssignSecurity+12

                  FOLLOWUP_NAME: MachineOwner

                  MODULE_NAME: nt

                  IMAGE_NAME: ntkrpamp.exe

                  DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa

                  FAILURE_BUCKET_ID: 0x8E_nt!ObAssignSecurity+12

                  BUCKET_ID: 0x8E_nt!ObAssignSecurity+12

                  Followup: MachineOwner

                  Comment


                  • #10
                    would you like to try to install older version of ATI driver or try to flash to motherboard bios?
                    if both eays can't solve this problem, please RMA with your local seller or directly to us
                    thanks


                    G.S

                    Comment


                    • #11
                      No need I discovered the culprit!

                      The motherboard was overclocking the memory so I set it to default and everything is running fine.

                      I really appreciate the help you gave me though, thanks a lot.

                      Comment


                      • #12
                        you're welcome


                        G.S

                        Comment

                        Working...
                        X