Random BSOD , 0xA

Archetype · 20 Feb 2015

Hello all,

I have been having quite a few issues on my new build (built 3 months ago). Golden (a very active contributor of the BSOD forum!) has helped me narrow down a few drivers that needed to updated which has helped tremendously in cutting down BSODs. I am now getting a phantom BSOD once in a blue moon which is very annoying so I would like to see if we can narrow down the cause. The last BSOD occurred when the wife was installing a game or two (I saw Trusted Installer in Win Debug) but the others seemed random and once more when I restarted with verifier enabled, started Far Cry 4, and was exiting the game (after I hit escape from the main menu and clicked exit).

Verifier: Enabled
Memtestx86+: Passes (10 Passes - Left on overnight and ran once more overnight)
Furmark Stress Test: Passes (Left running for 4 hours)
Intel CPU Test: Passes
Prime95 Stress Test: Passes (Ran for 6 hours)
SFC: Fails (CBS Log Attached)
WINSUR: Run

CPU: i74790k
RAM: 16 GB (8 GB x 2)Corsair Dominator (Tested on default specs, and XMP with Memtest)
Mobo: Asus Maximus Hero VII
Video: MSI GTX 760
OS SSD: Samsung 840 EVO (Firmware Up to date)

Thank you for the assistance.

Arc · 20 Feb 2015

All the different bugchecks.

Code:

BugCheck A, {fffff680003a3be8, 0, 0, fffff800034a85b7}

Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )

Followup: MachineOwner
---------

Code:

BugCheck 1A, {5010, fffff70001080000, adc, 266c044}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3504d )

Followup: MachineOwner
---------

Code:

BugCheck 1A, {41284, 49f0d001, 3e6ec, fffff70001080000}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53 )

Followup: MachineOwner
---------

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Let us know the results.

Archetype · 20 Feb 2015

Hello Arc; Thanks for the help.

Memtestx86+: Passed one test at 8 passes (4 weeks ago) and one at 12 passes when troubleshooting prior BSOD's (3 weeks ago).
Furmark: Ran for 30 minutes and temperature leveled out at 87c (Ran once before 5 hours at 89c) Missed the screenshot and no log found after enabling log per directions.
Prime95: Currently running. Will it automatically save the text file, or is there something I need to do before stopping the test after 2 hours?

Archetype · 20 Feb 2015

It looks like Prime95 was still running strong after 2 hours. I have attached the results from the Prime95 test as requested.

I also ran the Intel Processor Diagnostic tool and it passed all test with flying colors.

Archetype · 20 Feb 2015

Just had another BSOD earlier when the wife was launching TERA (Game), although this time it was a 0xC1 rather than 0x1A.

Any ideas?

Arc · 21 Feb 2015

Another memory corruption report.

Code:

BugCheck C1, {fffff980658dce10, fffff980658dcbe8, 4501f0, 32}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )

Followup: MachineOwner
---------

Are you sure that you tested the RAM with memtest86+ and nothing else? Asking it, because there are programs with deceptively similar names which are incompetent.

If memory is free of error for sure, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Archetype · 23 Feb 2015

I ran Memtest86+ for 18 hours and it found no errors.

I had another BSOD when exiting the game Terra (0x1A on shareduserdata.sys) which would be the second time that particular game has had a BSOD on exiting as well as Far Cry 4. Would the issues indicated in the CBS log cause any of this?

I have attached the dump from 2/23/2015 2:31:53 AM GMT.

Thank you.

Arc · 23 Feb 2015

If memory is free of error for sure, enable Driver Verifier to monitor the drivers.

Code:

BugCheck 1A, {3452, 15d7d000, fffff70001173318, dd200001afbba866}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35163 )

Followup: MachineOwner
---------

0x1A means MEMORY_MANAGEMENT BSOD.

Archetype · 03 Mar 2015

Hello all,

The computer had a few more BSOD's when the wife was playing a game and on Skype 2/28- 3/2, and once more today when I was pushing the computer to the limits this afternoon with CPU burner and Far Cry 4 running purposefully attempting to get it to crash.

Note: The last BSOD (3/3/15 - 1446) was the latest one with Verifier enabled (2/28-3/3 DMP's Driver Verifier was not enabled)

EDIT: Using WinDbg, it looks as if audiodg.exe was the source?

Code:

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98048724c60, address trying to free
Arg2: fffff98048724b68, address where one bit is corrupted
Arg3: 00000000004503a0, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

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


BUGCHECK_STR:  0xC1_32

SPECIAL_POOL_CORRUPTION_TYPE:  32

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  1

IRP_ADDRESS:  fffffa80122aa288

LAST_CONTROL_TRANSFER:  from fffff8000354ef43 to fffff800034beec0

STACK_TEXT:  
fffff880`0b7e1c08 fffff800`0354ef43 : 00000000`000000c1 fffff980`48724c60 fffff980`48724b68 00000000`004503a0 : nt!KeBugCheckEx
fffff880`0b7e1c10 fffff800`035c7bb3 : 00001f80`0010000f 0053002b`002b0010 fffffa80`122aa788 fffffa80`122aa300 : nt!MiCheckSpecialPoolSlop+0x83
fffff880`0b7e1c50 fffff800`035f394b : fffff800`0344a000 00000000`2b707249 00000000`00227b40 00000000`00000001 : nt!MmFreeSpecialPool+0x1d3
fffff880`0b7e1d90 fffff800`03969156 : fffffa80`1299f002 fffffa80`1299f010 00000000`00000000 fffff980`48724c60 : nt!ExFreePool+0x9e3
fffff880`0b7e1e40 fffff800`0396971c : fffff800`034d441c fffff980`48724c60 00000000`00000000 00000000`00000000 : nt!VfIoFreeIrp+0xe6
fffff880`0b7e1e70 fffff800`034d441c : 00000000`00000000 fffff980`48724c60 00000000`00000000 fffff6fc`00000248 : nt!IovFreeIrpPrivate+0x5c
fffff880`0b7e1eb0 fffff800`034b25f7 : fffffa80`122aa300 00000000`00000000 fffffa80`0caff200 56454442`00000000 : nt!IopCompleteRequest+0x54c
fffff880`0b7e1f80 fffff800`034c42fd : fffffa80`122aa300 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`0b7e2000 fffff800`034c360a : 00000000`00000000 fffff880`0b7e2140 00000000`00000000 fffff800`034e8b46 : nt!KiCommitThreadWait+0x3dd
fffff880`0b7e2090 fffff800`037b78df : fffffa80`00000004 fffff880`0b7e23e0 fffffa80`00000001 00000000`00000006 : nt!KeWaitForMultipleObjects+0x272
fffff880`0b7e2350 fffff800`037b7c56 : fffff6fb`7e000001 00000000`00000002 00000000`00000001 0000007f`ffffff00 : nt!ObpWaitForMultipleObjects+0x294
fffff880`0b7e2820 fffff800`034be153 : fffffa80`122aa300 00000000`00e5f7b8 fffff880`0b7e2a88 fffff800`037abadb : nt!NtWaitForMultipleObjects+0xe5
fffff880`0b7e2a70 00000000`7759186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e5f798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7759186a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCheckSpecialPoolSlop+83
fffff800`0354ef43 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiCheckSpecialPoolSlop+83

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  54b5f6ff

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xC1_32_nt!MiCheckSpecialPoolSlop+83

BUCKET_ID:  X64_0xC1_32_nt!MiCheckSpecialPoolSlop+83

Followup: MachineOwner
---------

Archetype · 02 Sep 2015

Just a quick update and a friendly reminder that in some extremely rare cases, Memtest86+ will not always catch faulty RAM. The previous sticks of RAM passed all of the stress testing and multiple Memtest86+ runs of 6 passes to 18 passes on default SPD settings, the XMP profile, and manual settings with manufacturer specs.

After having less errors with one stick of RAM installed, I decided it was time to RMA the RAM back to Corsair. The new RAM pair (same model and revision, just different color heat spreaders) is working great without issues.