Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Random BSOD when full screen apps are open. (Was Solved)
New Posts  All Forums:Forum Nav:

Random BSOD when full screen apps are open. (Was Solved) - Page 2

post #11 of 14
Thread Starter 
Well I'm back again. Everything working fine since except today I was playing a game and got a bluescreen. It was strange, instead of rebooting, the computer shut down. It restarted, I didn't see the motherboard splash screen and it shut down again. Then it started back up and now it works fine. Haven't tried any games since. Can a bad graphics card cause the random reboots? I might just take this card and buy a new one if that can fix it. Thanks.
EDIT: I failed to mention that the other day, maybe a week ago, my computer shut down randomly, no blue screen happened, I checked the folder and there was no dmp file. So its either my PSU or my graphics card, or possibly both?
Edited by Skinnedm - 8/26/13 at 4:00pm
post #12 of 14

Do you have any latest dump files to attach? If not, let's run some hardware diagnostics. Start with a Memtest for no less than ~8 passes (several hours). I also cannot stress enough if anything is OC'd you need to bring it to stock asap:


Download Memtest86+ here:


Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:



There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:

Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click .

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -


You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.


post #13 of 14
Thread Starter 
Thanks for the reply Patrick. There is no new dmp file. The computer shut down before I could read the blue screen itself and before windows could create a dmp file. I have cleaned out the pc and installed the newer beta drivers. Before playing any games though, I'm going to run all the Windows updates I missed. My bios also seems to be outdated. Could that be the reason for the graphics card having issues?
post #14 of 14

Good work! Also, yes, it's always a possibility, especially on newer-gen motherboards where BIOS updates are important.


New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Random BSOD when full screen apps are open. (Was Solved)