BSOD While playing Multiple Games

kardius said:

Not sure if anything changed... But I re-did the Dmp + perfmon.

How could anything change. These are the same DMPs I did from before.

kardius said:

I thought so. Do i need to run verifier again?

No reports are getting dumped when i crash from games.

Edit:
Sorry, If I am coming off ungrateful or anything. I'm just confused as to what to do when no new dumps are being created from the crashes.

No worries Kardius. We have all been there

Yes you do need to run verifier.

Thanks for helping me out Zigzag. I appreciate the effort!

I'm at work at the moment, but when I get home I'll start up the process again and produce another 3 dmps. Should I run chkdsk and SFC Scans again? Or just go straight to Verifier?

kardius said:

Thanks for helping me out Zigzag. I appreciate the effort!

I'm at work at the moment, but when I get home I'll start up the process again and produce another 3 dmps. Should I run chkdsk and SFC Scans again? Or just go straight to Verifier?

Chkdsk, and SFC are easier. then verifier if you have too

zigzag3143 said:

Chkdsk, and SFC are easier. then verifier if you have too

Before you posted this, I started up verifier.

I got a BSOD at start-up, right before log-on screen. Started computer back up normally after that, had no issue, and was able to boot up Diablo 3 and play it while verifier was running. When I got notification of your post I turned off verifier, and ran chkdsk (no errors) and sfc (No errors).

In the zip is the new .dmp, with the others (sorry, let me know if you want me to get rid of em.), and the perfmon for today.

I hate only providing one sample for ya to look at, but it didn't crash again at boot like it was yesterday. SO Progress is being made!

Do you think I should turn verifier back on and run my system with it on to see if I can get a game to crash? Me and some friends are planning a game night tonight, So i'm sure it'll happen at some point.

Thank you!

kardius said:

zigzag3143 said:

Chkdsk, and SFC are easier. then verifier if you have too

Before you posted this, I started up verifier.

I got a BSOD at start-up, right before log-on screen. Started computer back up normally after that, had no issue, and was able to boot up Diablo 3 and play it while verifier was running. When I got notification of your post I turned off verifier, and ran chkdsk (no errors) and sfc (No errors).

In the zip is the new .dmp, with the others (sorry, let me know if you want me to get rid of em.), and the perfmon for today.

I hate only providing one sample for ya to look at, but it didn't crash again at boot like it was yesterday. SO Progress is being made!

Do you think I should turn verifier back on and run my system with it on to see if I can get a game to crash? Me and some friends are planning a game night tonight, So i'm sure it'll happen at some point.

Thank you!

Of the four crashes the first 3 were caused by Kern. The newest one was not run with verifier enabled so it is inconclusive. If you continue to crash my gut feeling says it is your Avast.

If so remove and replace with MSE.


Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

OK. I'll drop Avast, never really liked it much anyways, and pick MSE back up. I was weary about MSE, cause I was getting an OOBE error or something another coming up in the event viewer. I know MSE and the OOBE are connected, so that was reason I uninstalled that to begin with.

AFTER I've done all that... Should I run the computer with verifier up for a night to see if I can get a crash while playing Diablo 3? I had two crashes last night with Diablo (Black screens, no dumps made ), BUT i made it the whole night through KF without an Error before that. So either progress is definitely being made, or I got extremely lucky.

I'm a bit confused about how verifier works in a sense. I know it's to help create a crash for blue screen, at least that's my understanding. But would it prevent my computer from black screen crashing, and force a blue screen instead to produce a dmp file?

kardius said:

OK. I'll drop Avast, never really liked it much anyways, and pick MSE back up. I was weary about MSE, cause I was getting an OOBE error or something another coming up in the event viewer. I know MSE and the OOBE are connected, so that was reason I uninstalled that to begin with.

AFTER I've done all that... Should I run the computer with verifier up for a night to see if I can get a crash while playing Diablo 3? I had two crashes last night with Diablo (Black screens, no dumps made ), BUT i made it the whole night through KF without an Error before that. So either progress is definitely being made, or I got extremely lucky.

I'm a bit confused about how verifier works in a sense. I know it's to help create a crash for blue screen, at least that's my understanding. But would it prevent my computer from black screen crashing, and force a blue screen instead to produce a dmp file?

Good on Avast.

Run verifier and do whatever it is that tends to crash the machine. WHen it does crash upload the DMPS

Verifier catches (hopefully) a mis behaving driver and writes it to your page file for the next boot then from page file it writes the DMP.

Uninstalled Avast, Loaded up MSE, and started up Verifier and started playing diablo 3.

What do I do if it crashes, verifier doesn't catch it, and no dmp is made? =X Cause that just happened. >.<