Hi,
We have various different bug checks:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This indicates that a system thread generated an exception which the error handler did not catch.
BugCheck 1000007E, {
ffffffffc0000005, fffff80002f9409c, fffff880033166c8, fffff88003315f20}
The 1st parameter of the bug check is 0xc0000005 which indicates an access violation occurred, let's see what caused it:
Code:
2: kd> .exr 0xfffff880033166c8
ExceptionAddress: fffff80002f9409c (nt!MiLogPageAccess+0x00000000000001fc)
ExceptionCode: c0000005 (Access violation)
^^ Unsure of what this exact routine
is, but it's certainly a memory related routine.
NTFS_FILE_SYSTEM (24)
This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.
One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.
Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
BugCheck 24, {1904fb,
fffff8800317e718, fffff8800317df70, fffff8000318eae9}
If we run an .exr on the 2nd parameter of the bug check, we get the following:
Code:
0: kd> .exr 0xfffff8800317e718
ExceptionAddress: fffff8000318eae9 (nt!FsRtlTeardownPerStreamContexts+0x0000000000000069)
ExceptionCode: c0000005 (Access violation)
File systems call
FsRtlTeardownPerStreamContexts to free all per-stream context structures associated with a given FSRTL_ADVANCED_FCB_HEADER structure. When a file system tears down the stream context object for a file stream, it must call
FsRtlTeardownPerStreamContexts, which in turn calls the
FreeCallback routines of all per-stream context structures associated with the file stream.
MEMORY_MANAGEMENT (1a)
This indicates that a severe memory management error occurred.
BugCheck 1A, {
5003, fffff70001080000, 15537, 925d0003aa6e}
- The 1st parameter of the bug check is
5003 which indicates the working set free list is corrupt. Given the above bug checks + this *1A, this is probably a hardware error. More specifically, a RAM or HDD issue. Let's first rule out the possibility of driver(s) causing memory corruption.
-----------------
1.
AODDriver2.sys - Wed Sep 11 23:36:40 2013
^^ AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Very known to cause BSOD's, so please remove ASAP.
2. Various Asus PC Probe & software drivers are listed in your loaded modules list. I would go ahead and remove PC Probe and any other Asus bloatware that is installed. It's all unnecessary.
3. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes:
Avira removal - How do I uninstall my Avira product?
MSE - Microsoft Security Essentials - Microsoft Windows
4. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
Regards,
Patrick
