Blue Screen after Windows 7 Re-installation

[Gregoshe]

Hey Everyone, I have been getting the BSOD quite frequently. I have re-installed windows 7 several times this year and my computer will run fine for a few days, sometimes weeks but then the same problem reoccurs. Problem sometimes occurs when I try to wake the computer from sleep, but sometimes occurs when the computer is awake. BlueScreenView points to ntoskrnl.exe at the +75bc0 address. Windows is currently up to date as well as all of my other drivers (motherboard/video etc...) Also I heard that the drivers for the MSI motherboard need to be downloaded from the MSI website instead of through live update so I downloaded the drivers from the official site. I will note that the first time I ran perfmon report the driver for my Bluetooth device was not installed properly as I had thought and is known to cause problems. Device manager also reported that the hardware was unknown until I installed the bluetooth atheros driver from the MSI website. Now it appears to be functioning properly. This is my first time posting here and if i am missing any information please let me know. I have attached sysnativefilecollectionapp and the perfmon report. Thanks in advance for your help.

G

Windows 7 64Bit
Intel(R) Core (TM) i7-3770k CPU @ 3.50GHZ currently not overclocked
16 GB Ram
MSI Z77 MPower
250gig Kingston SSD
1TB WD HHD
Nvidia GTX 660Ti
Corsair Hydro Series H100i

 

[x BlueRobot]

There is at least two bugchecks which I have found: Stop 0x7A and Stop0xF4. These bugchecks do complement each other.

[COLOR=#ff0000]BugCheck 7A[/COLOR], {fffff6fc50026140, [COLOR=#008000]ffffffffc000000e[/COLOR], 2fb3ff880, fffff8a004c286d4}

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

A address stored in paged pool has failed to be paged in due to a disk error, the exception code below shows a little more information. The bugcheck is actually reported from within the storage stack, which is why Kernel components are typically blamed for this type of bugcheck. The storage stack is a logical structure, with the hard disk being at the bottom, partition tables and addressing systems being in the middle and the top is the filesystem like NTFS.

0: kd> [COLOR=#008000]!error 0xc000000e[/COLOR]
Error code: (NTSTATUS) 0xc000000e (3221225486) - A device which does not exist was specified.

This seems to more of a hardware problem, it's most likely issues with the hard drive.

0: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff880`02936288 fffff800`02b43752 nt!KeBugCheckEx
01 fffff880`02936290 fffff800`02af791f nt! ?? ::FNODOBFM::`string'+0x36c1a
02 fffff880`02936370 fffff800`02ade1b9 nt!MiIssueHardFault+0x28b
03 fffff880`02936440 fffff800`02acecee nt!MmAccessFault+0x1399
04 fffff880`029365a0 fffff800`02da19c0 nt!KiPageFault+0x16e
05 fffff880`02936730 fffff800`02d9ca26 nt!CmpFindValueByNameFromCache+0xe0
06 fffff880`02936800 fffff800`02da1823 nt!CmQueryValueKey+0x136
07 fffff880`029368e0 fffff800`02acfe53 nt!NtQueryValueKey+0x381
08 fffff880`02936a70 00000000`7795142a nt!KiSystemServiceCopyEnd+0x13
09 00000000`0142e228 00000000`00000000 0x7795142a

For performance reasons, data which is accessed regularly a process is stored within the cache, when this data is referenced or the virtual address where the data is stored, then the data will be paged into physical memory. With this bugcheck, the storage stack has failed to retrieve the data within the page file.

I would recommend using the chkdsk command line tool first to check for any file system errors.

chkdsk /f /r

Full Syntax information - Chkdsk

Are both your driver SSDs? Have you checked for firmware updates?