BSOD while gaming

[magere hein]

Hi everyone,

Last week I bought a new PC and everytime when I'm gaming I get a BSOD. Sometimes I get it after like half an hour sometimes I can play for 1 hour and a half and get none. There is like absolutly no logic in it.

I can get my system running all day whitout getting one but when I start to play games I get one. When I dare to play a game I get a BSOD.

What I tried is uninstalling my graphics drivers and re-installing them. My Windows is up to date. Updated my network driver.

It's the first time I get this. My last PC was also Windows 7 but he died when my PSU died and I had no problems at all.

My current hardware is:
CPU: AMD 1055T
Motherboard: Gigabyte 890FXA-UD5
RAM: 8GB GEIL Black Dragon (Quad kit)
PSU: Corsair 950TX

I attached the dump files.

If you need more info just ask .

I'll appreciate the help.

Thanks by forehand.

 

[magere hein]

I did some research and installed this update:
The October 2009 stability and reliability update for Windows 7 and Windows Server 2008 R2 is available.

The problem isn't gone after installing this update. However it has helped a bit .

 

[magere hein]

nobody?

 

[Jonathan_King]

Give me a minute, I'll run them and get back to you shortly.

 

[zigzag3143]

Hi everyone,

Last week I bought a new PC and everytime when I'm gaming I get a BSOD. Sometimes I get it after like half an hour sometimes I can play for 1 hour and a half and get none. There is like absolutly no logic in it.

I can get my system running all day whitout getting one but when I start to play games I get one. When I dare to play a game I get a BSOD.

What I tried is uninstalling my graphics drivers and re-installing them. My Windows is up to date. Updated my network driver.

It's the first time I get this. My last PC was also Windows 7 but he died when my PSU died and I had no problems at all.

My current hardware is:
CPU: AMD 1055T
Motherboard: Gigabyte 890FXA-UD5
RAM: 8GB GEIL Black Dragon (Quad kit)
PSU: Corsair 950TX

I attached the dump files.

If you need more info just ask .

I'll appreciate the help.

Thanks by forehand.

While Jonathan_king is doing your DMP's I have a couple fo questions

Are you running a RAID?

Are you overclocking?

When you removed your video driver did your remove all traces of teh current one before installing the new one?

 

[Jonathan_King]

Six different bugchecks in 7 dmps. To me, that suggests hardware failure.

One of the dmps mentions memory_corruption, so I recommend a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Two of them blame your graphics card (or the drivers for it). Just as Ken suggested, uninstall the drivers completely, then install a fresh copy.

Please keep an eye on your temperatures while gaming. Download Speedfan and post some temps after heavy usage.

Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Update these old drivers:

PxHlpa64.sys Mon Dec 10 18:49:01 2007
SCDEmu.SYS   Tue Aug 07 11:19:48 2007
pcouffin.sys Tue Dec 05 09:39:30 2006
adfs.SYS     Thu Jun 26 16:52:37 2008

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

BSOD BUGCHECK SUMMARY

​

[FONT=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed May 26 14:32:44.167 2010 (GMT-4)
System Uptime: 0 days 1:04:33.007
BugCheck 50, {fffffa800bffadcb, 0, fffff80002ee8dff, 2}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 27 13:20:31.053 2010 (GMT-4)
System Uptime: 0 days 0:39:13.152
BugCheck 50, {fffffaa009cbbce0, 0, fffff80002fad0f3, 5}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+275 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Crysis.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 27 12:38:29.772 2010 (GMT-4)
System Uptime: 0 days 0:55:13.714
BugCheck 24, {1904fb, fffff88007c51e48, fffff88007c516a0, fffff800031815f1}
Probably caused by : Ntfs.sys ( Ntfs!NtfsMapStream+5b )
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 11:04:58.379 2010 (GMT-4)
System Uptime: 0 days 1:27:45.184
BugCheck 1A, {41201, fffff680003b9730, 34e0000100576025, fffffa800945d9c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 12:49:48.643 2010 (GMT-4)
System Uptime: 0 days 6:24:09.389
BugCheck 1000007E, {ffffffffc0000005, fffff88004325412, fffff880078a18b8, fffff880078a1120}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+22 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 09:36:34.194 2010 (GMT-4)
System Uptime: 0 days 8:50:09.471
BugCheck A, {8, 2, 1, fffff800030d1534}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseMutant+274 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  conviction_gam
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 06:24:56.274 2010 (GMT-4)
System Uptime: 0 days 4:00:16.173
BugCheck C2, {d, fffff8a01c38a570, 7346704e, fffffa8000000003}
Probably caused by : Npfs.SYS ( Npfs!NpReadDataQueue+1b3 )
BUGCHECK_STR:  0xc2_d
PROCESS_NAME:  conviction_gam
[/FONT]

 

[magere hein]

Thanks for replying.

I'm now running furmark in stability test, I'm going to start memtest tonight and remove my video drivers with revo uninstaller. That program normaly removes every trace of it.

No I'm not Overclocking and I do not have RAID.
What I now did I set my RAM frequency at 1333MHz and set the voltage at 1.51V instead of auto.

 

[magere hein]

I have ran furmark in stability mode.
The max temp was 87°C and he reached it in about 4 minutes I think. I let the test run but the app crashed after 51 minutes and 34 seconds. He didn't bluescreen, he just gave the fault, furmark has stopped working ...
This is the message from the logs:

Faulting application name: FurMark.exe, version: 1.8.0.0, time stamp: 0x4b67effe
Faulting module name: atioglxx.dll, version: 6.14.10.9836, time stamp: 0x4be0d48d
Exception code: 0xc0000005
Fault offset: 0x006f87a4
Faulting process id: 0xe8
Faulting application start time: 0x01cb01b1fbc02330
Faulting application path: C:\Program Files (x86)\oZone3D\Benchmarks\FurMark_v1.8.0\FurMark.exe
Faulting module path: C:\Windows\system32\atioglxx.dll
Report Id: 8def6d99-6dac-11df-bd37-6cf049e788d5

Then I ran memtest as you said. I had 1 fault. I took a picture of my screen. I have added it to my post.

I didn't have run speedfan but as soon as I got home I posted the error from memtest.

Now I'm going to download speedfan and try to play another game.

 

[zigzag3143]

I have ran furmark in stability mode.
The max temp was 87°C and he reached it in about 4 minutes I think. I let the test run but the app crashed after 51 minutes and 34 seconds. He didn't bluescreen, he just gave the fault, furmark has stopped working ...
This is the message from the logs:

Faulting application name: FurMark.exe, version: 1.8.0.0, time stamp: 0x4b67effe
Faulting module name: atioglxx.dll, version: 6.14.10.9836, time stamp: 0x4be0d48d
Exception code: 0xc0000005
Fault offset: 0x006f87a4
Faulting process id: 0xe8
Faulting application start time: 0x01cb01b1fbc02330
Faulting application path: C:\Program Files (x86)\oZone3D\Benchmarks\FurMark_v1.8.0\FurMark.exe
Faulting module path: C:\Windows\system32\atioglxx.dll
Report Id: 8def6d99-6dac-11df-bd37-6cf049e788d5

Then I ran memtest as you said. I had 1 fault. I took a picture of my screen. I have added it to my post.

I didn't have run speedfan but as soon as I got home I posted the error from memtest.

Now I'm going to download speedfan and try to play another game.

If the problems ontinue you may also want to test the mobo slots one by one

 

[Fumz]

What bios version are you running?

That you can't pass memtest suggests one of three things: a bad kit which needs to be RMA'd, incorrect RAM timings/voltages, or you're using an older bios which needed a revision.

What memory timings are you running? Include the command rate.

Of course, it's also possible that your RAM is just not compatible with your board. Did you check to see if your Geil was on Gigabytes approved list?

 

[magere hein]

The BIOS that came with the Motherboard, I think it's the first revision.
The timings I use are 7-7-7-24 and the voltage is 1.51.

I put them manualy in.

I didn't find my memory on there list. But they say the following: "Memory modules listed below are for reference only. Due to massive memory models on the market, we can only verify some of them."

 

[Fumz]

It's never really a good idea to go with memory kits that aren't on the board's approved list. Yes, there are so many kits that they can't check them "all", but they do check the major vendors... Geil being one of them.

Is your command rate set at 1T or 2T, if 1, set it to 2T and try and pass memtest again. 21 hours with only 1 error... you might luck out and have it be a bios and/or timing thing.

If 2T gives you an error, then update the bios.

 

[magere hein]

Just played another game but, the game hang again but didn't get a BSOD. I ened it with task manager.

I set the timings to 2T and disabled the performance boost in the BIOS for the CPU. also I set my memory from ungaged to gaged mode.

I took another look at the logs and what I found was that there where a lot of app errors: namely, searchindexer.exe

Faulting application name: SearchIndexer.exe, version: 7.0.7600.16385, time stamp: 0x4a5bd212
Faulting module name: ESENT.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf7c
Exception code: 0xc0000005
Fault offset: 0x000000000005e1d1
Faulting process id: 0xcd8
Faulting application start time: 0x01cb02725ba0cbdd
Faulting application path: C:\Windows\system32\SearchIndexer.exe
Faulting module path: C:\Windows\system32\ESENT.dll
Report Id: b19238a3-6e68-11df-81c2-6cf049e788d5

It started when I stated playing the game and I see it 3 times in an hour.

I'm starting to fear that it is a bad memory thing. But I'm still going to run the memtest and if that fails again. I'm gonne test a single module at a time. This is going to take a while since I'm 13 hours away from home every day.

 

[BrownCowbell]

You may update PowerIso because old driver cause problem...

SCDEmu SCDEmu.SYS Tue Aug 07 11:19:48 2007

PowerIso.com

 

[magere hein]

I let memtest run again with the ganged mode, overdrive disabled and timing set to 2T. When I woke up this moring memtest has encounterd 1 error and was after 9 hours still in his first pas.

I looked up the memory on the website from GEIL and they say that the memory is best used with intel core I7 and P55 motherboards. Now my brother has a core I7 and a P55 motherboard.

I'm going to try and switch the memory modules and put my modules on his PC and his modules in mine and see if he gets errors to.

 

[magere hein]

When I got back home I got 2 errors (see image) whit the 2T timings and ganged mode.
Now I switched memory with that of my brother. He got OCZ reaper memory and I'm playing a game to test his mem on my board. The game is running now for like about 1 hour and 15 minutes and as far not a problem.
I changed the memory timings back to auto and back to unganged mode. I had to raise the voltage to 1.75 because the memory does his work at that voltage.

As far as now my brother doesn't have encounterd a problem either but it's a little to soon to say that it is solved.

I checked the temps, my CPU is 35°C and my graphics cart is like about 65°C.

I checked my logs again and did not found that app error form searchindexer. I'll have to wait till my brother stresses the memory till I know for sure that there is a problem with it.

Thanks for the help .

 

[magere hein]

Look like it hasn't helped. My brother had a BSOD after 40 minuten while playing splinter cell.

I'm running memtest now but it looks like there is something wrong with this memory.

 

[magere hein]

Ok it was faulty RAM. My brother had the same errors on his PC. I called my hardware vendor and I send the RAM back to them and switched it with RAM that was on the QVL from my motherboard.

I see no app error in the logs with my brother his RAM. I'm running it for a couple of days now without an error.

That one lessen I've learned. Always buy RAM from the QVL!!

 

[magere hein]

You may close this thread, I send the memory back to my hardware vendor and they agreed that it was faulthy memory, wendesday I got new memory and has tested the hell out of my PC. I played splintercell conviction for one hour and a half and he alsways bluescreened at that game within the hour.
Thursday I ran a couple of benchmarks like 3Dmark06 and PC mark05. I ran them four an houre and even OCed my PC to 3,5GHz and ran them again and no crash or bluescreen. Yesterday I played a game and without an error.

Again thanks for the help .

 

[Fumz]

Good stuff.