Frequent BSODs on Windows 7 Professional 64-bit

[antaresprime]

Over the past 3 months, my computer has been having frequent BSODs. My hardware is a few months old (see attached for specs), and I have already installed Windows from scratch several times in an attempt to eliminate the BSODs. My latest installation is also from scratch, yet it has already BSODed 2 days after I started using it.

I believe my hardware is OK, because

1. RAM modules passed memtest with zero problems
2. Installed Windows from scratch on 2 different hard drives, one of them brand new, and still had frequent BSODs
3. Returned the motherboard to ASUS and got a certified replacement, which latest installation of Windows is running on
4. CPU is brand new and passed Intel Processor Diagnostic Tool with zero problems

The only thing that has remained relatively constant is the suite of software/drivers that I always install with Windows. This suggests that one or more pieces of software/drivers and/or some combination of software/drivers is causing the BSODs.

I have stockpiled a history of minidumps and kernel memory dumps from all the BSODs that I’ve been having. Let me know if you need access to them.

Info about my computer

Windows 7 Professional 64-bit (6.1, build 7601)

What was original installed OS on system? Same as above.

Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Bought Windows 7 from my university.

Age of system (hardware): several months

Age of OS installation - have you re-installed the OS? Several weeks. OS was installed from scratch.

CPU: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz (4 CPUs), ~3.5GHz

Video Card: Intel(R) HD Graphics 4600

MotherBoard: ASUS Z87-A BIOS Date: 08/15/14 15:17:17 Ver: 21.03

Power Supply - brand & wattage (if laptop, skip this one): Corsair HX 750, 750 Watts

System Manufacturer: not applicable, built the computer myself

Exact model number (if laptop, check label on bottom): not applicable

Laptop or Desktop?: desktop

 

[Jared]

Welcome to Sysnative, I will try to help you with your problem.
Lets begin.

[B][I]KERNEL_DATA_INPAGE_ERROR (7a)[/I][/B]
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb80000000, lock type that was held (value 1,2,3, or PTE address)
Arg2: [COLOR="#FF0000"][B]ffffffffc000000e[/B][/COLOR], error status (normally i/o status code)
Arg3: 0000000188d25880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff70000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

We have a 0x7A bugcheck, this indicates important Kernel mode code couldn't be brought into memory from disk.
The exception error was ffffffffc000000e, this is the error that tell us why we crashed.
It means no such device, basically the drive just disappeared.

fffff880`037e0ed8 fffff800`030fb752 : 00000000`0000007a fffff6fb`80000000 ffffffff`c000000e 00000001`88d25880 : [COLOR="#0000CD"]nt!KeBugCheckEx[/COLOR]
fffff880`037e0ee0 fffff800`030af91f : fffffa80`0abe73b0 fffff880`037e1050 fffffa80`0afc8ec8 fffffa80`0abe73b0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`037e0fc0 fffff800`0309628a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`030b9306 : [COLOR="#FF0000"]nt!MiIssueHardFault+0x28b[/COLOR]
fffff880`037e1090 fffff800`03086cee : 00000000`00000000 fffff700`00000000 ffffffff`ffffff00 00000000`00000004 : [COLOR="#FF0000"]nt!MmAccessFault+0x146a[/COLOR]
fffff880`037e11f0 fffff800`030aff68 : 00000000`00000000 00000000`ffffffff 00000000`00000016 00000000`00000000 : [COLOR="#FF0000"]nt!KiPageFault+0x16e[/COLOR]
fffff880`037e1380 fffff800`0337b5ab : 00000000`ffffffff fffff8a0`00000000 00000000`00000000 00000000`00000000 : [COLOR="#800080"]nt!RtlFindClearBits+0xa8[/COLOR]
fffff880`037e13c0 fffff800`033775aa : ffffffff`ffffffff fffff880`037e17e0 00000000`00000000 fffff680`003f7ef8 : [COLOR="#800080"]nt!MiScanUserAddressSpace+0xdf[/COLOR]
fffff880`037e1410 fffff800`03087e53 : fffff880`037e17f0 fffff800`03086dfd 00000000`00000000 00000000`7efdf318 : [COLOR="#800080"]nt!NtSetInformationProcess+0x375[/COLOR]
fffff880`037e1760 fffff800`03084410 : fffff800`03376ec2 00000000`00000000 fffff800`03383a9f 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`037e18f8 fffff800`03376ec2 : 00000000`00000000 fffff800`03383a9f 00000000`00000000 fffffa80`06a29c00 : nt!KiServiceLinkage
fffff880`037e1900 fffff800`0337583c : 00000000`00004000 00000000`00040000 00000000`00000000 00000000`00001000 : nt!RtlCreateUserStack+0x122
fffff880`037e19f0 fffff800`0337514a : fffffa80`0afc8b30 fffff880`037e2858 fffffa80`06a29d00 fffff880`037e2440 : nt!PspAllocateThread+0x5bb
fffff880`037e1c10 fffff800`03379029 : fffffa80`00000004 00000000`00000000 00000000`00000001 fffff880`037e2440 : nt!PspCreateThread+0x1d2
fffff880`037e1e90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateThreadEx+0x25d

We have some normal functions, just looking up addresses and then removing them. We then access pageable memory which hits a pagefault, this goes through the process (usually) of a hard fault that brings the memory from disk (off the page file) and into the memory (RAM).

So why did it fail?

Well we were bringing memory back from disk and the disk suddenly disappeared. Essentially going boom and then bugcheck as nothing will work anymore.

---

[B][I]CRITICAL_OBJECT_TERMINATION (f4)[/I][/B]
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: [COLOR="#006400"]fffffa80099aeb30[/COLOR], Terminating object
Arg3: [COLOR="#800080"]fffffa80099aee10[/COLOR], Process image file name
Arg4: fffff800033d3270, Explanatory message (ascii)

This bugcheck indicates a critical system process terminated, this always results in a bugcheck as the process is required for Windows to function correctly.

3: kd> [COLOR="#006400"]dc fffffa80099aee10[/COLOR]
fffffa80`099aee10  73727363 78652e73 00000065 02000000  [COLOR="#800080"][B]csrss.exe[/B][/COLOR].......
fffffa80`099aee20  00000000 00000000 00000000 00000000  ................
fffffa80`099aee30  00000000 00000000 09a36f78 fffffa80  ........xo......
fffffa80`099aee40  0b79cc98 fffffa80 00000000 00000000  ..y.............
fffffa80`099aee50  00000000 00000000 0000000b c3408dff  ..............@.
fffffa80`099aee60  00000000 00000000 fffdf000 000007ff  ................
fffffa80`099aee70  00000000 00000000 00000000 00000000  ................
fffffa80`099aee80  00000000 00000000 00000113 00000000  ................

csrss.exe terminated, this is the Client/Server Runtime Subsystem. It's responsible for performing important routines, for example, it contains win32k.sys which is the graphics device driver that performs window functions as well as setting up the graphics device interface. Without csrss there would be no display so Windows wouldn't work, there are lots of other things but I won't go into detail.

3: kd> [COLOR="#006400"]!error 0xc0000006[/COLOR]
Error code: (NTSTATUS) 0xc0000006 (3221225478) - [COLOR="#FF0000"][B]The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.[/B][/COLOR]

This means an I/O caused the process to crash.
I suspect it happened when a thread for the process was paged out to disk, it tried to bring back that address to memory, it hit a disk error so it couldn't bring the memory back, making the thread go boom as it can no longer process so it terminates and we bugcheck.

I'd say you either have a bad disk (most likely) or a bad motherboard which wouldn't surprise me given it's ASUS, they usually just send the motherboard back and say it's repaired/replaced.

I suggest running SeaTools DOS, download and run it from here.

SeaTools for DOS | Seagate

Put it on a USB flash drive or burn it to a disk then boot from it.
Run everything except Fix All and anything under the Advanced tests.