BSOD at seemingly random times, memory dump blaming random drivers

salisian · 14 Apr 2014

I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into windows in 8-10 seconds (SSD) but the latest post-BSOD boot took about five minutes from typing my password into the login screen to where my desktop popped up. A subsequent reboot was at normal speed. The memory dumps always include the NT OS kernel, but then also some other driver (different each time), which I suspect just happens to be the one trying to run at the time of the error.

Things I've tested:
Temperatures (didn't really suspect them in the first place, but I'm running cool)
Memory (Both the native Windows test and memtest found no issues)
Hard drives (chkdsk came back clean)

All drivers are up to date, although the uploaded report might show an older version of my sound card driver, as I just reinstalled it at the behest of windows action center (which didn't make the notification go away, mind).

I'm hoping someone wiser than I can make sense of this, because it all seems so random to me. Thanks in advance to whoever that is.

koolkat77 · 15 Apr 2014

How many passes did you take memtest for?

Code:

Debug session time: Mon Apr 14 14:39:57.702 2014 (UTC + 6:00)
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 3:33:21.985
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BugCheck 1A, {41790, fffffa800b8e2ca0, ffff, 0}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800b8e2ca0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
BiosVersion = 2201
BiosReleaseDate = 11/22/2013
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Apr 10 10:21:01.348 2014 (UTC + 6:00)
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 8:53:05.394
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by : aswSnx.sys ( aswSnx+27e08 )
BugCheck 1A, {31, fffffa800f46b160, fffff8800a406000, fffff8a0099043dd}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa800f46b160
Arg3: fffff8800a406000
Arg4: fffff8a0099043dd
BUGCHECK_STR:  0x1a_31
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_31_aswSnx+27e08
BiosVersion = 2201
BiosReleaseDate = 11/22/2013
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Apr  9 15:00:24.319 2014 (UTC + 6:00)
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 14:51:19.270
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+c33 )
BugCheck 7E, {ffffffffc0000005, fffff88001291e53, fffff88003346318, fffff88003345b70}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
Bugcheck code 0000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001291e53, The address that the exception occurred at
Arg3: fffff88003346318, Exception Record Address
Arg4: fffff88003345b70, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7E_Ntfs!NtfsFlushVolume+c33
BiosVersion = 2201
BiosReleaseDate = 11/22/2013
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

I'd suggest you take them in the following manner:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

Remove Avast & replace with Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.