5 BSOD in 4 weeks on new build

Not to go against Dave's advise but how about a short test to see if raid was the orig prob and not mem? My mobo does 8Gb fine with default voltages...
You can always set it back but in your situation Id check if the ram tests ok in default voltage before blaming the mobo slots...

Quoting some previous posts for reference.

Dave76 said:

Download and install all new drivers from the Gigabyte web site and then any others you think you will need.
...Edit...
General causes of "STOP 0x0000007F" errors are usually hardware caused, including RAM.

You have a lot of RAM installed.
Anything over 4GB will usually require a memory controller voltage bump, as will RAM cards 2GB or larger, and when four RAM cards are installed.
...Edit...
Go to your BIOS and tell us what the CPU, RAM and CPU integrated memory controller voltages are.
Your CPU memory controller voltage is called 'CPU NB VID Control' in the 'System Voltage Control' section of the BIOS.
...Edit...
This tutorial explains how to run the test when looking for bad RAM cards or bad motherboard slots.
RAM - Test with Memtest86+

Not a good sign that the RAM failed in slots 1 & 3, try them in slots 2 & 4, one at a time.
This will help to troubleshoot the cause, motherboard, CPU integrated memory controller, or....
Other possibilities are PSU, including loose connections, and of coarse motherboard RAM slots.

Dave76 said:

...Edit...

The temps are good.

You will need to go to your BIOS for the RAM and CPU integrated memory controller voltages.

Go to BIOS > 'MB Intelligent Tweaker(M.I.T.)' > 'System Voltage Control' set this to Manual > DRAM Voltage control,
If all you can see is 'AUTO' then select it and you should see a list of the options, one of them should be selected.

Your CPU memory controller voltage is called 'CPU NB VID Control' in the 'System Voltage Control' section of the BIOS.
If you have done the above settings ('System Voltage Control' set this to Manual) then select 'CPU NB VID Control'.
If all you can see is 'AUTO' then select it and you should see a list of the options, one of them should be selected.
If you can't see any selected then select 1.200v.
'Save and Exit' before leaving the BIOS.

The 'CPU NB VID Control' will likely need to be bumped to a higher voltage than 1.200v, but it is best to raise this slowly in order to get the lowest voltage setting that runs stable.

Let us know the memtest86+ results.

Can you post the 'CPU NB VID Control', this is important, you have to get it from BIOS.
Also get the 'DRAM Voltage control', this is needed to verify the RAM voltage before we start bumping the voltages.

dballs said:

after i reformatted i didn't get a BSOD but one when i was rendering to memory in video editing. so i ran memtest86+ and got errors at %33-%37.

I tested each stick in slot one and got errors with all of my ram sticks in slot one at around %34

I tested a stick in slot one and slot 3 and got errors just the same in both

I brought my ram to my friends house and got 0 errors. ram sticks seem to be fine.

could i really have 2 bad slots on my motherboard? could this just be a settings issue (timing/voltage?). should i warranty my motherboard or buy a different one?

-RAM: 2X G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model F3-10666CL9D-8GBRL (16GB total)
-MOBO: GIGABYTE GA-880GA-UD3H AM3 AMD 880G SATA 6Gb/s USB 3.0 HDMI ATX AMD Motherboard

As mentioned above, can be motherboard slots, CPU integrated memory controller or PSU.

dballs said:

I did all my tests at default voltages. Memtest86+ runs before OS loads off a disc. So the RAID isn't doing anything during tests. I think they did have something to do with the other bsods maybe. By regardless my memory still isn't stable.

Correct, memtest86+ runs by itself, no windows settings are involved and minimal hardware. This is one of the reasons it is a good RAM test.



From your dump files.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

This is blaming a Windows kernal driver, which is what happens when the debugger can't find the true cause, this can indicate a hardware failure.

Have you updated your BIOS when you first got the system?
Which BIOS version do you have?

Confirm that you have updated all of your drivers, motherboard first then any others.

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
 
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+6231336365626435
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
EXCEPTION_RECORD:  fffff88002f8ca68 -- (.exr 0xfffff88002f8ca68)
ExceptionAddress: fffff80002ed902f (nt!PoIdle+0x000000000000004f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME:  fffff88002f8cb10 -- (.trap 0xfffff88002f8cb10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f8cd78 rbx=0000000000000000 rcx=fffff88002f64180
rdx=00001bd700000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed902f rsp=fffff88002f8cca0 rbp=0000000000000000
 r8=fffffa800c907050  r9=0000000000000000 r10=fffff80002e50000
r11=fffffa800dfea300 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!PoIdle+0x4f:
fffff800`02ed902f 41f6460402      test    byte ptr [r14+4],2 ds:00000000`00000004=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ec76be to fffff80002ecfcd0
STACK_TEXT:  
fffff880`02f8bb48 fffff800`02ec76be : 00000000`00000000 00000000`00000000 fffff880`02f8c2c0 fffff800`02efb890 : nt!KeBugCheck
fffff880`02f8bb50 fffff800`02efb55d : fffff800`030d66a4 fffff800`03014ccc fffff800`02e50000 fffff880`02f8ca68 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8bb80 fffff800`02efa335 : fffff800`030170fc fffff880`02f8bbf8 fffff880`02f8ca68 fffff800`02e50000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8bbb0 fffff800`02f0b3b1 : fffff880`02f8ca68 fffff880`02f8c2c0 fffff880`00000000 fffffa80`0dfea210 : nt!RtlDispatchException+0x415
fffff880`02f8c290 fffff800`02ecf382 : fffff880`02f8ca68 fffff880`02f64180 fffff880`02f8cb10 fffff880`02f64180 : nt!KiDispatchException+0x135
fffff880`02f8c930 fffff800`02ecdc8a : fffffa80`0dfa1000 fffff880`05672f41 fffffa80`00000000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f8cb10 fffff800`02ed902f : 00000000`002fe577 00000000`00000001 fffff880`02f64180 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8cca0 fffff800`02ec79fc : fffff880`02f64180 fffff880`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x4f
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x2c
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ec76be 90              nop
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------

Event log issues.

Code:

 
Event[23]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-07-05T16:32:12.000
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: dballs-PC
  Description: 
The dump file at location: C:\Windows\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Code:

Event[3150]:
  Log Name: System
  Source: Disk
  Date: 2011-06-29T11:14:28.908
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: dballs-PC
  Description: 
The driver detected a controller error on \Device\Harddisk2\DR2.

Three of these in a row.
This was a couple of weeks ago, but you should D/L and run Western Digital Lifeguard– Quick Test and Extended Test, if you haven't already.


Do you have to power off the computer a lot?
Seeing a lot of power off errors.

Code:

Event[19624]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-06-08T14:40:03.745
  Event ID: 7030
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: dballs-PC
  Description: 
The JMB36X service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.

This is an error for your AMD RAID controller.

Code:

 
*** WARNING: Unable to verify timestamp for jraid.sys
*** ERROR: Module load completed but symbols could not be loaded for jraid.sys
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys

Update these drivers.


Also noticed errors with your Graphics card drivers.
What version are they?
Update them if one is available.

dballs said:

Can you post the 'CPU NB VID Control', this is important, you have to get it from BIOS.
Also get the 'DRAM Voltage control', this is needed to verify the RAM voltage before we start bumping the voltages.

-CPU NB Vid and Dram Voltage is at 1.1500v
-timming is 9 9 9 24

This is the normal range for the CPU NB Vid voltage, usually 1.100v.
Bump this to 1.200v.

If the DRAM voltage is correct, verify and report back, it should be at stock setting of 1.500v, either way bump it to 1.550v.

Run memtest86+ again with all RAM cards installed, if you get any errors you can stop the test.
Pass or fail, run memtest86+ with one RAM card in slot 2 or 4, if you haven't tested these slots yet and in slot 1 0r 3 if you have tested slots 2 and 4 already.

For all memtest86+ runs, you can stop the test if you get any errors.

Report the results.

dballs said:

Have you updated your BIOS when you first got the system?
Which BIOS version do you have?

-There is a BETA bios (F8F). other than that i have the latest stable bios (F7). should i install the BETA BIOS?

I do not recommend using a beta BIOS, stay with F7.

dballs said:

Confirm that you have updated all of your drivers, motherboard first then any others.

-done. but why would this matter since i am getting the errors in memtest86+? that loads without OS.

Some of the drivers can affect different hardware and how it is being used by the system. Old drivers are known to cause all types of BSODs.
Generally it is a good idea to keep your drivers up to date.

dballs said:

This was a couple of weeks ago, but you should D/L and run Western Digital Lifeguard– Quick Test and Extended Test, if you haven't already.

-quick test passed ill run extended tonight.

It is important to run the extended test.
Let us know the results.

dballs said:

Do you have to power off the computer a lot?
Seeing a lot of power off errors.

-i power it off all the time. i don't keep my system running when im not using it. bad?

I meant pushing the power button when the system is running.
Do you select Start/Shutdown when closing your computer?

Opinions vary, I always shutdown my system when not in use.

dballs said:

-and ill test slots 2 and 4 later. I'm tired tonight. Just got off work.

thanks for your all your help! that was a most excellent post

Your welcome.

Disconnect both the RAID drives, one of the monitors, any other non-essential devices, and check if you have the same problems.
You want a bare bones system.
Next step will be to disassemble everything, connect one peice of hardware at a time and check the beep code.
Check your mobo manual for the beep code list.

Check that your motherboard standoffs are positioned correctly.
Look for grounding points.
Ensure all cables are correctly placed and firmly attached.

From your first post.

3rd time getting BSOD:
*** STOP: 0x0000007F (0x0000000000000008, 0x0000000080050031, 0x00000000000006F8, 0xFFFFF80003888F72)

4th time getting BSOD:
*** STOP: 0x0000007F (0x0000000000000008, 0x0000000080050031, 0x00000000000006F8, 0xFFFFF80003888F72)
*** dxgmms1.sys - address FFFFF880061B2360 base at FFFFF880061A2000, DateStamp 4ce799c1

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

5th time getting BSOD:
*** STOP: 0x0000003B (0X00000000C0000005, 0xFFFFF96000093BFA, 0xFFFFF88008B0C210, 0x0000000000000000)
*** win32k.sys - Address FFFFF96000093BFA base at FFFFF96000010000, DateStamp 4d2415ea

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Cause: This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

6th time:
***STOP: 0x000000BE (0xFFFFF960002E22D8, 0x80900003ED6AC021, 0xFFFFF88002A64960, 0x000000000000000B)

STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes: Device driver, Memory
This is issued if a driver attempts to write to a read-only memory segment.



This can be caused by a faulty motherboard.

RAM, possible CPU (Integrated memory controller), HDD and Graphics card failures.
Makes me suspect the PSU. Do you have another PSU or can borrow one to test with?