BSOD playing DOTA 2 several errors

Happosai · 11 Sep 2013

Been having bsod for the last week, on multiple occasion but more so when playing DOTA 2 and when restarting comp.

koolkat77 · 11 Sep 2013

Please post this report before we begin:

Activation Issue Posting Instructions

Happosai · 12 Sep 2013

Code:

 
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-T7KBY-9FQB6-V9R8H
Windows Product Key Hash: N/z/FGEFTZfX9pbGf3aabGCExBc=
Windows Product ID: 00359-OEM-8992687-00191
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {6878249A-A883-4A61-93D3-325E3B4F227D}(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_gdr.130801-1533
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-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{6878249A-A883-4A61-93D3-325E3B4F227D}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-V9R8H</PKey><PID>00359-OEM-8992687-00191</PID><PIDType>2</PIDType><SID>S-1-5-21-693020012-2351770980-2427065574</SID><SYSTEM><Manufacturer>Alienware</Manufacturer><Model>Aurora</Model></SYSTEM><BIOS><Manufacturer>Alienware</Manufacturer><Version>A11</Version><SMBIOSVersion major="2" minor="5"/><Date>20091028000000.000000+000</Date></BIOS><HWID>2CFA3E07018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ALWARE</OEMID><OEMTableID>ALIENWRE</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-800191-02-1033-7600.0000-2532013
Installation ID: 001701806434466862635025554571100392865176040691760822
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: V9R8H
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 9/12/2013 8:40:19 AM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 9:10:2013 20:31
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:

HWID Data-->
HWID Hash Current: LgAAAAEAAgABAAEAAAACAAAAAQABAAEAonYoinrkqn+QpTgdfukkXbpZAsvqgg==
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   ALWARE  ALIENWRE
  FACP   ALWARE  ALIENWRE
  HPET   ALWARE  MI09    
  MCFG   ALWARE  MI09    
  SLIC   ALWARE  ALIENWRE
  OEMB   ALWARE  ALIENWRE
  SSDT   DpgPmm  CpuPm
  ASPT   ALWARE  PerfTune
  WDTT   ALWARE  OEMWDTT

Hopefully I did it right

Xyrus

koolkat77 · 13 Sep 2013

Looks fine :) thank you.

Your Msinfo is corrupted. Please re-upload it.

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post. Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

Happosai · 13 Sep 2013

here is the files you wanted hopefully I did this right as well. thanks in advance.

Xyrus

koolkat77 · 13 Sep 2013

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000008d, 
Arg2: 000000000017a69b
Arg3: 0000000000510020
Arg4: fffff68000027123
 
Debugging Details:
------------------
 
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
 
BUGCHECK_STR:  0x4E_8d
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  2
 
LAST_CONTROL_TRANSFER:  from fffff80002ec0e9d to fffff80002e7a880
 
STACK_TEXT:  
fffff880`009a9c08 fffff800`02ec0e9d : 00000000`0000004e 00000000`0000008d 00000000`0017a69b 00000000`00510020 : nt!KeBugCheckEx
fffff880`009a9c10 fffff800`0311947a : fffffa80`05507b60 00000000`00000080 fffffa80`05507040 fffff800`02e58d99 : nt!MmZeroPageThread+0x90c
fffff880`009a9d40 fffff800`02e58da6 : fffff800`02ff4e80 fffffa80`05507b60 fffff800`03002c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!MmZeroPageThread+90c
fffff800`02ec0e9d cc              int     3
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt!MmZeroPageThread+90c
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc36
 
IMAGE_NAME:  memory_corruption
 
FAILURE_BUCKET_ID:  X64_0x4E_8d_nt!MmZeroPageThread+90c
 
BUCKET_ID:  X64_0x4E_8d_nt!MmZeroPageThread+90c
 
Followup: MachineOwner
---------

------------------------

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+

Tip

Pay close attention to Part 3 of the tutorial "If you have errors"
Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Happosai · 13 Sep 2013

ran the tests for 4 passes and no errors were found.

Xyrus

Happosai · 13 Sep 2013

had to stop it due to my nephew messing with the comp and accidently stopping the tests. is that fine or do I have to do 3 more passes of the ram tests?

koolkat77 · 13 Sep 2013

I would take memtest for longer.

Do you get BSOD in safe mode?

Happosai · 13 Sep 2013

I didn't bsod I used the usb boot memtest. my nephew just pressed esc button so it canceled the test. Ill redo the test again when I go to sleep. so how long should I do it for more than 7 passes? BTW I reinstalled windows 7 and updated it prior to doing the memtest. played dota 2 and went smoothly with no bsod. however I am curious as to what was the cause of the bsod before.

Xyrus