BSOD

[Aaron.T]

Hello,
I recently upgraded my MOBO and CPU (Asus sabertooth z87 & Intel i7-4771 Haswell) and re-installed my win7 operating system. After doing so I have  received 2 BSOD messages. I was hoping I could get some help resolving those messages?
I look forward to hearing from you,
Aaron

PS: BSOD logs are attached

PSS: I have installed around 150 updates since I have gotten those BSOD messages. *update* Well over 200 updates now.

[recovering disk space, attachment deleted by admin]

[Allan]

1) After installing the OS did you install all drivers (including the chipset driver) from the OEM websites and NOT from Windows Update?

2) Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

[Aaron.T]

I was able to install all the drivers except one is still flagged in the device manager called "unknown device." Also here is the BSOD file:

==================================================
Dump File         : 012314-31761-01.dmp
Crash Time        : 1/23/2014 2:45:24 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff960`00134283
Parameter 3       : fffff880`0a1f2020
Parameter 4       : 00000000`00000000
Caused By Driver  : win32k.sys
Caused By Address : win32k.sys+c4283
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+71f00
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\012314-31761-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 293,216
Dump File Time    : 1/23/2014 2:46:36 PM
==================================================

==================================================
Dump File         : 012314-19203-01.dmp
Crash Time        : 1/23/2014 9:59:55 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : 00000000`00000020
Parameter 2       : ffffffff`c000009d
Parameter 3       : fffffa80`08538078
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor         : x64
Crash Address     : ntoskrnl.exe+71f00
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\012314-19203-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 300,992
Dump File Time    : 1/23/2014 10:01:22 PM
==================================================

[Allan]

While this could be directly related to the new components you've installed, it could also be a bad sector on the hd or bad ram. Please do the following:

1) download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

2) right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r  (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

Also, please run full scans with BOTH your installed AV and with MalwareBytes

[Aaron.T]

Hello,
Sorry for the wait. I ran checkdisk and memtest and both had no error. Also ran the scans producing nothing as well. However I've haven't had any BSOD since the last 2nd that I posted, so maybe its fixed itself if that is at all possible.
Thanks,
Aaron