BSOD while playing full-screen games

pizzamanxl · 28 Jun 2014

It is a BSOD crash, however the screen just goes black until restart rather than the bsod screen. Not sure why. See atatched, thanks in advance for your help. Sorry I could not give much info; hopefully DM Logs give more.

Boozad · 28 Jun 2014

First and foremost you need to update to Service Pack 1 via Windows Updates.

Code:

Host Name:                 MEDIA1
  OS Name:                   Microsoft Windows 7 Home Premium 
  OS Version:                6.1.7600 N/A Build 7600
  OS Manufacturer:           Microsoft Corporation
  OS Configuration:          Standalone Workstation
  OS Build Type:             Multiprocessor Free
  Registered Owner:          Travis
  Registered Organization:   
  Product ID:                00359-112-0000007-85509
  Original Install Date:     6/27/2014, 2:39:09 AM
  System Boot Time:          6/28/2014, 2:15:39 PM
  System Manufacturer:       To Be Filled By O.E.M.
  System Model:              To Be Filled By O.E.M.
  System Type:               x64-based PC
  Processor(s):              1 Processor(s) Installed.
                             [01]: AMD64 Family 21 Model 1 Stepping 2 AuthenticAMD ~3300 Mhz
  BIOS Version:              American Megatrends Inc. P1.40, 10/2/2013

Report back after the successful update.

pizzamanxl · 28 Jun 2014

Service pack 1 failed to update when I originally tried to update it. I will try again.

pizzamanxl · 28 Jun 2014

Update successful this time. I went ahead and induced another bsod by letting a game run and ran the DM logs again just in case that helps.

Also this window came up on reboot (after bsod not after update):

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    124
  BCP1:    0000000000000000
  BCP2:    FFFFFA8007CD77F8
  BCP3:    0000000000000000
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\062814-11637-01.dmp
  C:\Users\Travis\AppData\Local\Temp\WER-13681-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Boozad · 28 Jun 2014

And the update ran through Windows Updates?

pizzamanxl · 28 Jun 2014

Boozad said:

And the update ran through Windows Updates?

Yes

Boozad · 28 Jun 2014

All of your dumps are 0x124s which indicates a hardware error. To try to pinpoint the problem you need to run a series of tests outlined below.

Your other logs are showing signs of hardware errors although I'm not picking up exactly what. Follow the trouble shooting steps below.

Warning

If you're overclocking your system, revert back to stock clocks now.

Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them.

Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Run chkdsk. Disk Check

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them.