BSODs with multiple error codes on fresh install

Welcome, and use your computer you normally would, and then switch to a different graphics card if any problems arise.

After removing the video card I got two more BSODs. So I went ahead and removed all of the AMD drivers using Driver Sweeper. I enclosed the minidumps in case they are helpful.

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8000317ea5c, fffff8800337f818, fffff8800337f070}

Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )

Code:

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Code:

CONTEXT:  fffff8800337f070 -- (.cxr 0xfffff8800337f070)
rax=7cfffa800992e738 rbx=000000000020a404 rcx=00000000000000f0
rdx=fffff8a007939258 rsi=fffffa8006b71968 rdi=0000000000000400
rip=fffff8000317ea5c rsp=fffff8800337fa50 rbp=0000000000000000
 r8=fffffa800b1e0004  r9=fffffa8006b71048 r10=fffffa800992d0d0
r11=fffffa800982b7a0 r12=0000000000000000 r13=fffffa8006b71000
r14=fffff8a007942060 r15=000000000000001e
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!MiEmptyPageAccessLog+0xdc:
fffff800`0317ea5c 488b08          mov     rcx,qword ptr [rax] ds:002b:7cfffa80`0992e738=????????????????

Code:

0: kd> .formats 7cfffa800992e738
Evaluate expression:
  Hex:     7cfffa80`0992e738
  Decimal: 9007193207587661624
  Octal:   0763777650001144563470
  Binary:  01111100 11111111 11111010 10000000 00001001 10010010 11100111 00111000
  Chars:   |......8
  Time:    Fri Aug 30 04:19:18.766 30143 (UTC + 1:00)
  Float:   low 3.53657e-033 high 1.06329e+037
  Double:  1.27648e+294
0: kd> .formats fffff8a007939258
Evaluate expression:
  Hex:     fffff8a0`07939258
  Decimal: -8108771143080
  Octal:   1777777612000744711130
  Binary:  11111111 11111111 11111000 10100000 00000111 10010011 10010010 01011000
  Chars:   .......X
  Time:    ***** Invalid FILETIME
  Float:   low 2.22041e-034 high -1.#QNAN
  Double:  -1.#QNAN

Code:

FAULTING_IP: 
nt!MiEmptyPageAccessLog+dc
fffff800`0317ea5c 488b08          mov     rcx,qword ptr [rax]

I think there may be a possibility of a flipped bit, in one of the CPU registers, the register with the flipped bit also seems to be the register in which the crash occurred. Your Intel onboard graphics card is also being blamed, this makes sense, since I'm sure that the Intel graphics are integrated with the CPU.

Code:

0: kd> lmvm igdkmd64
start             end                 module name
fffff880`04aa5000 fffff880`04fc11c0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Sat Mar 09 02:10:00 2013 (513A99F8)
    CheckSum:         0052A265
    ImageSize:        0051C1C0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Run this stress test (CPU) - CPU - Stress Test Using IntelBurnTest

The first two times I ran the standard test it would BSOD, and it passed on the third. It passed the test on high on the 2nd try. But it BSODs each time on the very high test. The temps were under 55C each time. I've attached the minidumps if they're helpful.

This is the first thing I've been able to do that will force a BSOD every time. Does this conclusively point to the CPU or the MoBo socket? Anything else I can do to narrow it down?

The NTSTATUS error is consistent throughout all the crashes:

Code:

0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

memory_corruption also seems to be a common factor, and can relate to the CPU caches and registers.

We can check the CPU again with a different stress test, to see if we get the same results:

• Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

I ran three tests with Prime95 and each time I got a BSOD before the two hour mark (though the last time got real close to two hours). I've enclosed the minidumps.

I poked around online and a lot of folks seem to think reseating the CPU might help. Do you think that should be my next course of action?

You could try reseating the CPU, and see if it makes any difference, and I'll look at the dumps now. It does seem to pointing to a CPU fault if it constantly crashes on CPU tests.

Code:

BugCheck 7F, {8, 80050033, 406f8, fffff800030cee2f}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Code:

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

The bugcheck indicates the CPU generated a trap (type of interrupt), which the kernel wasn't able to catch and process. More specifically, the first parameter contains the value of 8 which indicates that a Double Fault occurred this happens, when the the CPU was processing a earlier fault (General Protection Fault) and failed to copy the contents of the fault into the registers.

The most common cause for this BSOD is a hardware problem, furthermore, the other two BSODs indicated your Intel graphics driver as a potential cause, which I'm sure resides as your onboard graphics card on your Intel processor.

After reseating the CPU, the temps are still good, but now I'm getting a BSOD about every 45 minutes. It was initially pretty stable, so I reinstalled the video card and uninstalled the onboard graphics, but after several hours I started getting a pretty steady stream of BSODs. I've attached the minidumps.

I'm leaning towards the MoBo as the faulty part in the chain, but I'm not sure. I guess I could RMA the Motherboard first and see if the problem persists.

Code:

BugCheck 1E, {ffffffffc0000005, fffff88003120ad0, 0, 0}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+1a7d0 )

Code:

Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Code:

1: kd> lmvm Rt64win7
start             end                 module name
fffff880`05c1d000 fffff880`05cec000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Mon Mar 04 07:25:55 2013 (51344C83)
    CheckSum:         000D1FB8
    ImageSize:        000CF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Realtek network adapter seems to be causing problems, however, the driver seems to be most probably the most update version, therefore it may well be a bad motherboard.

Code:

1: kd> lmvm atikmpag
start             end                 module name
fffff880`04730000 fffff880`047c4000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Mar 29 01:09:45 2013 (5154E9D9)
    CheckSum:         00091A60
    ImageSize:        00094000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your graphics card driver was also blamed for the issue, I've noticed that it will blame any device which is not disabled and connected to the motherboard.