BSOD when playing games

[Josh185]

I have gotten 2 BSOD while playing games. The screen doesn't stay up long enough for me to read it like the windows xp ones do but after I restart, I get a pop up with the text below...

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

Additional information about the problem:
  BCCode:    1000008e
  BCP1:    C000001D
  BCP2:    929E1417
  BCP3:    803F0D24
  BCP4:    00000000
  OS Version:    6_0_6001
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini031709-01.dmp
  C:\Users\Josue\AppData\Local\Temp\WER-39593-0.sysdata.xml
  C:\Users\Josue\AppData\Local\Temp\WERE2BF.tmp.version.txt

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

Can anyone please help me determine the cause of these BSOD?

Edit: System specs are in my profile.

 

[H2SO4]

If you zip up the file mentioned in that report and upload it here someone might be able to help:

"C:\Windows\Minidump\Mini031709-01.dmp"

 

[Josh185]

Thank you H2SO4 for the suggestion.

I tried putting them into a zip file but I get an access denied error. I'm not sure how to get around that.

 

[H2SO4]

Copy them to another folder first and zip them up there. The system prevents casual writes under the \Windows folder.

 

[Josh185]

Awesome that worked. I have attached the files to this post.

 

[H2SO4]

I think you've got a hardware problem. Try installing this hotfix first though (there's a download link at the top of the page):

Error message when you put a Windows Vista-based or a Windows Server 2008-based computer to sleep, or you wake the computer up: "STOP: 0x0000009F"

The newer crash is in USB-handling code and that hotfix updates virtually all USB binaries. If MS already know about this issue that (new) hotfix may contain a solution.

The older crash looks like a very probable hardware issue. Possibly the RAM, or inadequate cooling, or you're overclocking... it's hard to tell from a minidump, sorry.

 

[Josh185]

Thank you H2SO4 for the reply.

I have installed the hotfix you recommended.

Any suggestions on how I can narrow down the hardware issue?

I have my CPU overclocked by 100Mhz.

CPU doesn't go over 45c from what I have seen.

My graphics card gets a little hotter than that but according to the catalyst control center, its within normal range.

 

[Josh185]

Update:

I checked out my memory and found that I was running it with less voltage than it was designed. The manufacturer states 2.0v-2.1v but my motherboard was only giving it 1.9v. I increased voltage to 2.050v.

The timings also by spd are 5-5-5-15-48 but I was running them at 5-5-5-15-25. I changed the timings to 5-5-5-15-38 with my motherboard max for tRC being 42.

Do you think this would have been the cause?

 

[smarteyeball]

It's certainly possible. Have you tried running memtest86+ with those timings?

 

[Josh185]

No, I am not familiar with memtest86+. I found a few sites with different versions. Is http://www.memtest.org/ the right place to download this tool?

 

[Klaudius]

Over the short time I have been on this forum I have noticed that alot of BSD problems are AMD chips + Overclock.

In general, put the whole system back to normal.
If the problem goes away try the following:
Over clock the system incrementally up till you see the problem happening again.

In my opinion, and in general the AMD chips are more prone to crash out when overclocking, than Intel ones. This is just in my experience, and remember "past performance does not guarantee future results"

Good luck to you. Seems like an awesome rig you've got yourself

 

[H2SO4]

Or you could just not overclock at all and avoid crashes by running the hardware within its design limits. Most people wouldn't dream of pouring nitroglycerin into their car's tank in order to make it go a little faster, lest it should go "boom", and yet that's exactly what overclocking equates to in PC terms.

 

[sygnus21]

Or...you could just overclock with caution. Plenty of people here are running overclocked systems just fine without problems, including me.

While I cannot argue that the safest way to a stable system is not to overclock, overclocking done right, can and does yield just as stable a system as a non-overclocked system, but with the added benefits of a performance increase.

Overclocking is always risky business, but if done in moderation with an understanding of the limits of your equipment, you can achieve successful overclocks with no problems.

Whether you have an overclocked system or not, there’s no guarantee that you won’t suffer crashes or other problems, just as there’s no guarantee that you will have problems because your system is overclocked!

And without tweakers, technology wouldn’t be where it is today.


Just my two cents

 

[Klaudius]

yep I agree and I agree, but how many times have you seen someone say the following:

"Hey guys, I'm new to all this but I have this system that keeps crashing, I dont know why but its a 2.8ghz OcteenCORE Overclocked or some thingy with an uber heat sink on it. My machine is running in some type of liquid, and there is a refrigerator attached to the box.
All my other games worked just fine, Microsoft word, minesweeper .. etc till i ran crysis at 30000x 140000.. please help !! Btw My brother told me it was a great idea to run an athelon x9000 with 64tb of ram, he says it should be just fine, and that intel is crap"

I used to have this happen all the time.

 

[sygnus21]

Yeah, and I agree with your point... which goes to my point on moderation and understanding.

Case in point, everyone says my Intel Core 2 Quad Q6600 (2.4GHz) can do 3+ gig easily; however my system won't allow me to go past 3GHz without occasional crashes.

Though I would like go past 3gig, I understand that my MB won't allow certain options, and the fact that I have a "B3" Q6600, instead of a "GO" Q6600, which creates a heat problem, limits my options to run past 3GHz stable.

Understanding this, I've found that the sweet spot for my overclocked system is 2.9GHz. I clearly understand that pushing it beyond that is asking for trouble.

Moderation & Understanding.

At any rate we’re getting away from the original poster’s question, which is where we should be focused - BSOD when playing games

 

[sygnus21]

No, I am not familiar with memtest86+. I found a few sites with different versions. Is Memtest86+ - Advanced Memory Diagnostic Tool the right place to download this tool?

To answer the question - yes, that's the correct place to download it from. Also you might want to read up on it here - What is memtest86+, what do I use it for? - The Corsair Support Forums. It's a little long winded but has great info.

It was last updated on 2/24/2009

 

[Josh185]

Thank you all for your responses.

I tested my memory today at 5-5-5-15-38 @ 2.050v with memtest86+ and it passed with no errors.

The only thing that caught my eye with memtest is that it said my memory was running at 5-3-3-15-38, however CPU-Z and AMD overdrive shows it as the correct timings.

As far as overclocking, right now my cpu is running at 2.8Ghz with default being 2.7Ghz. I had not had any issues with AMD cpu's as far as overclocking them. Prior to this cpu, I had an Athlon 64 3200+ running at 2.4Ghz with its normal being 2.0Ghz and it never once bluescreened over the 3+ years I had it. I figured the 100Mhz overclock on this Kuma core cpu would be easy. I haven't really tried to go higher than that due to my stock cooling but I have seen people get it to 3.2Ghz with the same motherboard.

I'll try testing my pc now that I have correct the memory timings and voltages. Hopefully that was the cause of the BSOD. I'll follow up after a while to let ya'll know how it goes.

 

[sygnus21]

Thank you all for your responses.

I tested my memory today at 5-5-5-15-38 @ 2.050v with memtest86+ and it passed with no errors.

The only thing that caught my eye with memtest is that it said my memory was running at 5-3-3-15-38, however CPU-Z and AMD overdrive shows it as the correct timings.

What does the BIOS say???

I ask that because memtest bypasses the operating system and just tests the memory itself. You could run memtest without having Windows installed. If memtest is saying your timings are one thing, but a windows based software is saying something else, I'd check to BIOS to see which is right.

 

[Josh185]

My bios shows the timings as 5-5-5-15-38, which is why the memtest timings seemed odd.

 

[sygnus21]

Hmmm...that is odd. Maybe it's because you have an AMD board and processor? I don't know. Perhaps someone who has used memtest with an AMD board could explain?