BSOD's

Alternator · 25 Jun 2015

Hello, I have been getting BSOD's that I haven't been able to link to anything and am frustrated by this...
Although they seem to appear less often when I put the computer to sleep instead of shutting it down.

I only have 3 memory dumps right now as I forgot to un-tick memory dump cleaning in CCleaner.

Edit: Somehow deleted a part of the name for this thread "Seemingly random BSOD's"

Arc · 26 Jun 2015

Code:

BugCheck D1, {2, 7, 8, 2}

Probably caused by : System ( INVALID_CONTEXT )

Followup: MachineOwner
---------

Make it sure that the system is having the right software. Post a report following the Windows Genuine and Activation Issue Posting Instructions

Alternator · 27 Jun 2015

Code:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-D96PV-T9B9D-M8X2Q
Windows Product Key Hash: Fq/JsPUI1NdT6veDtiDB8N1RQUs=
Windows Product ID: 00359-OEM-8992687-00246
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {2D95C4E3-BB0A-4C31-A883-2AFBC1A7B71F}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_rtm.101119-1850
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{2D95C4E3-BB0A-4C31-A883-2AFBC1A7B71F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-M8X2Q</PKey><PID>00359-OEM-8992687-00246</PID><PIDType>2</PIDType><SID>S-1-5-21-3496718586-3760924570-3190509343</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7919</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V1.6</Version><SMBIOSVersion major="2" minor="8"/><Date>20141223000000.000000+000</Date></BIOS><HWID>05570900018400F4</HWID><UserLCID>0425</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>FLE Standard Time(GMT+02:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>MSI_NB</OEMID><OEMTableID>MEGABOOK</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800246-02-1033-7601.0000-1342015
Installation ID: 014182475356012234310330080965874020935995503093788911
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: M8X2Q
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 27.06.2015 17:43:04

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MgAAAAAAAwABAAEAAAAEAAAAAQABAAEAHKLADUhWGhN0xG6VjuMKQ/p1dq9F4aDmyPY=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			ALASKA		A M I
  FACP			ALASKA		A M I
  HPET			ALASKA		A M I
  MCFG			ALASKA		A M I
  FPDT			ALASKA		A M I
  FIDT			ALASKA		A M I
  ASF!			INTEL 		 HCG
  SSDT			Ther_R		Ther_Rvp
  SSDT			Ther_R		Ther_Rvp
  SSDT			Ther_R		Ther_Rvp
  SSDT			Ther_R		Ther_Rvp
  SSDT			Ther_R		Ther_Rvp
  UEFI			ALASKA		A M I
  DMAR			INTEL 		BDW 
  SSDT			Ther_R		Ther_Rvp
  SLIC			MSI_NB		MEGABOOK

Arc · 27 Jun 2015

I have requested NoelDP to have a look at this report. He is the best person in the world to interpret those reports.

NoelDP · 28 Jun 2015

(such nice words, Arc!

)

There is no problem with the report that I can see - The machine is an MSI 7919 Gaming laptop, activated using the MSI SLIC table and Key. (I think it's close to being the first time I've ever seen an MSI Key appearing in a log!)
The WAT (KB971033) update isn't installed - which shouldn't change the result, but may give a little more information as it checks some extra files/settings/registry entries.

Arc · 28 Jun 2015

Than you so much, Noel. :) Now we have minimized the first possibility of a BSOD caused by system.

The next, I would Suggest Alternator to run SFC /SCANNOW Command - System File Checker

See how it goes.

Alternator · 28 Jun 2015

"Windows Resource Protection did not find any integrity violations." :/

Arc · 28 Jun 2015

Then it is strange at this point why it is blaming the "system" for the BSOD.

A memory corruption may cause any sort of issue. Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. A camera snap before closing memtest86+ would be nice.

Layback Bear · 28 Jun 2015

I'm surly confused.

MSI makes a MSI USA - Computer, Laptop, Notebook, Desktop, Mainboard, Graphics and more Retail motherboard that a i5-4690k fits on.

System Specs.

Computer type PC/Desktop
OS Windoows 7 Home Premium x64 SP1
CPU i5-4690k
Motherboard MSI Z97M Gaming

From this I'm not seeing the same information as is posted in the
Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data-->

It appears that the BSOD Zipped file and the MGADiag log are not coming from the same computer.

When Noel post the log looks good, then the log is good, no question about it.

From the BSOD Zipped file I'm seeing this.

GenuineIntel ~3501 Mhz
BIOS Version: American Megatrends Inc. V1.6, 23.12.2014

I hope some one understands why I'm confused.

Their are some things in the BSOD logs.

SSASSIN-PC-N_25_06_2015_235317,43.zip

That are not matching the information in post #3
Diagnostic Report (1.9.0027.0):

Alternator · 28 Jun 2015

I couldn't get memtest86+ to detect my USB stick so I tried running memtest86 by Passmark instead.
I only ran one pass of 13 tests with no errors, but I will make it run through the night.

These are all from this computer though...
Could these miss-matches be the cause of these BSOD's?