Solved BSOD while playing BF3

[SufferingKnave]

Hello all!

I recently made some changes to my computer hardware. I got a new motherboard and graphics card, and ever since I got the graphics card about 3-4 weeks back, I have been getting consistant daily blue screens while playing Battlefield 3. Before I got my 7950, I used a 6850, but I could not play Battlefield 3 on it because the PCB was bent around the universal waterblock and it would not cool it enough to do anything but surf the web.

I have done tons upon tons of research on my error code with no avail.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF8000306F524
BCP3: FFFFF88008DBC020
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\071813-8439-01.dmp
C:\Users\Jacob\AppData\Local\Temp\WER-10405-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I have reinstalled Windows 4 different times on either my SSD and HDD. I have ran MemTest for 8+ hours with no problems, I have deleted random programs I do not use (I use AVG Anti-virus), changed PCI slots just in case it is a bad slot, changed drivers on my 7950 from old 13.1's to the newest beta driver 13.6. Last but not least, I have ran diskcheck on both my HDD and SSD with no problems.
The only thing I would have to assume is a bad graphics card? It is the XFX Double Dissipation, which has been known to "crap out" after a few months or less. I have looked at the temperatures before crashes and it is not above 70 degrees Celsius MAX, but that is only for a few seconds till it is back down to the 65-68 range. (High-Ultra settings in BF3).

I am at a loss for ideas after a month of trial and error.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff8000306f524, [COLOR="Blue"]fffff88008dbc020[/COLOR], 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )

Usual causes:  System service, Device driver, graphics driver, memory

CONTEXT:  fffff88008dbc020 -- ([COLOR="SeaGreen"].cxr 0xfffff88008dbc020[/COLOR])
rax=0000000000000002 rbx=fffffa800ea1e060 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa800ea1e0b0 rdi=fffffa800eaadf20
rip=fffff8000306f524 rsp=fffff88008dbca00 rbp=0000000000000000
 r8=f7fffa800ea1e0b0  r9=0000000000000000 [COLOR="Red"]r10=f7fffa800ea1e0a0[/COLOR]
r11=000000000012019f r12=0000000000000001 r13=0000000000000300
r14=fffffa800e5a9060 r15=fffff88008dbcc20
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiDeliverApc+0xd4:
fffff800`0306f524 498b4a30        mov     rcx,qword ptr [r10+30h] ds:002b:f7fffa80`0ea1e0d0=????????????????
Resetting default scope

1: kd> [COLOR="SeaGreen"].formats f7fffa800ea1e0a0; .formats fffffa800e5a9060[/COLOR]
Evaluate expression:
  Hex:     f7fffa80`0ea1e0a0
  Decimal: -576466799371886432
  Octal:   1737777650001650360240
  Binary:  1111[COLOR="Red"]0[/COLOR]111 11111111 11111010 10000000 00001110 10100001 11100000 10100000
  Chars:   ........
  Time:    ***** Invalid FILETIME
  Float:   low 3.99059e-030 high -1.03837e+034
  Double:  -1.05588e+270
Evaluate expression:
  Hex:     fffffa80`0e5a9060
  Decimal: -6047073136544
  Octal:   1777777650001626510140
  Binary:  11111111 11111111 11111010 10000000 00001110 01011010 10010000 01100000
  Chars:   .....Z.`
  Time:    ***** Invalid FILETIME
  Float:   low 2.69401e-030 high -1.#QNAN
  Double:  -1.#QNAN

There seems to be a flipped bit within the r10 register, which is usually caused by the CPU, but can potentially be caused by the motherboard or the PSU.

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Run the Small FFT's, Large FFT's and Blend test each for least 2-4 hours, unless the temperature exceeds 80*C before the test has run for that suggested time interval.

Please boot into the BIOS, and then post the voltages for 3.3V, 5V and 12V rails.

Remove:

Start Menu\Programs\DriverUpdate

These driver installation programs always install corrupted, incompatible or outdated drivers, the best and only proven method is to visit the hardware vendor's website and then install the drivers from there via Windows or their own installation wizard.

Have you removed AVG?

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

 

[SufferingKnave]

Thank you for the quick reply!

I have uninstalled AVG and have been running a few hours without a blue screen while playing BF3. I know it is probably not the cause but it helps hah.

I never used the DriverUpdate program to download drivers, rather looked for which ones were "ancient/old" and went to the websites to download them; ex: Realtek, Gigabyte, AMD. This program has been removed as well.

I am currently running a scan from both the malwarebytes and security essentials and will post once finished with results. I will then move onto the stress test. Were you looking for the voltages before or after the test, or both?

UPDATE:
I have ran a full thorough scan with both Malwarebytes and Security Essentials with nothing found on either.

UPDATE #2:
The voltages of 3.3 and 12 volts are the only ones I had in my BIOS. I downloaded SpeedFan to see the rest of the voltages.

+3.3V: 3.33V
+5V: 5.00V
+12V: 12.42V

-12V: -10.72V
-5V: 4.05V
+5V: 3.60V

If I am not mistaken the -12V should be just a tad bit higher for stability?

 

[SufferingKnave]

Run the Small FFT's, Large FFT's and Blend test each for least 2-4 hours, unless the temperature exceeds 80*C before the test has run for that suggested time interval.

[/QUOTE]

I have tested with the Small FFT's with no errors and when I started the Large FFT's I got an error pretty quickly the first time I tested it.

It was in test 3:
FATAL ERROR: Rounding was 0.48828125, expected less than .4
Hardware failure detected, consult stress.txt file.
Torture Test completed 2 tests in 2 minutes - 1 errors, 0 warnings.

I have tested again for 2 more hours and it has yet to stop.  Is this a sign of a failing PSU?  I have a 5 year warranty on my OCZ ZX 850W series powersupply.

 

[x BlueRobot]

They seem to okay, and the CPU seems to be fault here. Do you have a another CPU to swap with, just to confirm?

 

[SufferingKnave]

I wish I did, but I do not unfortunately. Is there some other way to test for the CPU? If all else fails and you or others think it is the root of the problem, I have another year on my CPU's warranty.

 

[SufferingKnave]

I blue screened a few minutes ago, but this is a different one!

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80003072524
BCP3: FFFFF880093E8868
BCP4: FFFFF880093E80C0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\071813-8517-01.dmp
C:\Users\Jacob\AppData\Local\Temp\WER-12058-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1000007E[/COLOR], {[COLOR="SeaGreen"]ffffffffc0000005[/COLOR], fffff80003072524, fffff880093e8868, fffff880093e80c0}

Probably caused by : ndis.sys ( ndis!ndisReceiveWorkerThread+1dc )

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

CONTEXT:  fffff880093e80c0 -- (.cxr 0xfffff880093e80c0)
rax=0000000000000002 rbx=fffffa800cf9a060 rcx=0000000000000001
rdx=fffff88001673b9c rsi=fffffa800cf9a0b0 rdi=fffffa800d0df8d0
rip=fffff80003072524 rsp=fffff880093e8aa0 rbp=fffff880093e8b20
 r8=f7fffa800cf9a0b0  r9=0000000000000000 [COLOR="Red"]r10=f7fffa800cf9a0a0[/COLOR]
r11=fffff880093e8c80 r12=0000000000000001 r13=0000000000000000
r14=fffffa800ca7f5f0 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiDeliverApc+0xd4:
fffff800`03072524 498b4a30        mov     rcx,qword ptr [COLOR="Red"][r10+30h][/COLOR] ds:002b:f7fffa80`0cf9a0d0=????????????????
Resetting default scope

The nature of the crash is exactly the same, with the exact same CPU register having a flipped bit. You could try using the Intel CPU test, I think it's still compatible with AMD processors:

• http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

2: kd> [COLOR="SeaGreen"]lmvm Rt64win7[/COLOR]
start             end                 module name
fffff880`056b2000 fffff880`05752000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="Red"]Tue Sep 27 15:50:33 2011[/COLOR] (4E81E2B9)
    CheckSum:         0009FB77
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Realtek RTL8168D/8111D driver seems to be a possible cause, and outdated, please update it from here - Realtek

 

[SufferingKnave]

Well, I just got the same BSOD as the second posted. I updated my driver you said to and I still got it. Would it be safe to say it is my CPU? Money isn't a issue to get another, and my CPU is typically running at 100% while playing.

On a side note, I ran the Intel Stress Test without any problems.

 

[x BlueRobot]

I would say it's safe to say that the CPU is at fault here.

 

[SufferingKnave]

Okay, thank you! I just purchased a new CPU and it should be here by Wednesday. After a few tests, I will post results and if I get any more BSOD.

I truly appreciate your help!! Thank you!

 

[x BlueRobot]

Welcome, I'm glad to be able to help

 

[SufferingKnave]

This ended up being the problem. I gave this a week to test extensively and it is purring like a kitten! +rep !

 

[x BlueRobot]

I'm glad everything is running okay now