Sign in with
Sign up | Sign in
Your question

BSOD, gaming, videos

Last response: in Windows 7
Share
December 21, 2011 10:14:06 PM

Hello,

I keep getting BSOD while playing video games and/or watching videos. It varies on length of when it happens, but usually around an hour or so.

I copied the latest dump file info:

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: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80001FA0AE1
BCP3: FFFFF8800B3A7030
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

And I also performed a WhoCrashed analyzer and got this for the latest BSODs:

On Wed 12/21/2011 11:52:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122111-19983-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80001FA0AE1, 0xFFFFF8800B3A7030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 12/21/2011 11:52:42 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80001FA0AE1, 0xFFFFF8800B3A7030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 12/21/2011 6:53:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122111-18813-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2841D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800702841D, 0xFFFFF8800BD40558, 0xFFFFF8800BD3FDB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 12/21/2011 5:44:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122111-26145-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20FF3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006D9EFF3, 0xFFFFF880087EB698, 0xFFFFF880087EAEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



Any help on the specific driver that needs to be updated or otherwise fixed. I have checked my graphics driver and updated it as a norm.

Thanks.

More about : bsod gaming videos

a b \ Driver
a b $ Windows 7
December 21, 2011 10:54:28 PM

There definatly seems to be a software conflict somewhere and not that it's a good thing but it does seem to be the same thing every time which means it's only the one thing you have to fix. One thing that can help out is to try and remember when this started and what you did with the computer at that time. One thing you can try is a complete reinstall of your video card. I would delete the drivers in control panel then remove the video card in device manager , shut down and unplug. Remove the video card from the slot while unpluged and wait a few minutes then put the card back in and power up , use the install disk that came with the card and install it then update the drivers. Hopefully that will help , if not then you will have to find what is conflicting with the video driver.
m
0
l
a b $ Windows 7
December 21, 2011 11:00:18 PM

What hardware?

Please include cpu, motherboard, gpu, and power supply (make and model).
m
0
l
Related resources
December 21, 2011 11:14:42 PM

geekapproved said:
What hardware?

Please include cpu, motherboard, gpu, and power supply (make and model).


CPU: AMD Phenom II 925 2.8 GHX
Motherboard: Asus MVP-Deluxe M3A32
GPU: AMD Radeon HD6870

Is there a way an easy way to see what the power supply is without opening the case?

If recalling correctly its 650watts. Not sure model and make.
m
0
l
a b $ Windows 7
December 22, 2011 12:41:39 AM

Are you afraid to open the case?


The fact that it only happens during games or movies points to either something overheating or your power supply is failing.

Download Hardware monitor (google it) and with it open it will record the max temps your cpu and gpu reached while your gaming or watching movies.
m
0
l
December 22, 2011 1:56:51 AM

geekapproved said:
Are you afraid to open the case?


The fact that it only happens during games or movies points to either something overheating or your power supply is failing.

Download Hardware monitor (google it) and with it open it will record the max temps your cpu and gpu reached while your gaming or watching movies.



Donwloaded HW Monitor...highest temp as of now is 65 degrees C.

Had another BSOD after playing for about 2 hours.

Opened case and unless I pull apart the power supply I can't see the model and manufacturer.

Did pull this from my old invoice though.
750 WATT OEM ATX PSU
m
0
l
a b \ Driver
a b $ Windows 7
December 22, 2011 2:34:15 AM

A 750w psu is a very decent sized psu and should be more than enough for your system unless it is going bad like geekapproved suggested. It's just odd that it takes 2hrs to get the BSOD , if it was overheating it would have done that long before 2hrs. You could try turning things off that are running in the background and you don't need at the moment when your playing your game. Look through the apps that are in the startup list and see if you can turn any of them off , you can always turn them back on later.
m
0
l
December 22, 2011 3:08:39 AM

inzone said:
A 750w psu is a very decent sized psu and should be more than enough for your system unless it is going bad like geekapproved suggested. It's just odd that it takes 2hrs to get the BSOD , if it was overheating it would have done that long before 2hrs. You could try turning things off that are running in the background and you don't need at the moment when your playing your game. Look through the apps that are in the startup list and see if you can turn any of them off , you can always turn them back on later.



I have very little running behind the just the game other than web browsing and such.

Does the crash report detail I added in the OP spell anything out? It mentioned a driver being an issue and not hardware that caused the BSODs.
m
0
l
December 22, 2011 3:29:38 AM

swooshrp said:
I have very little running behind the just the game other than web browsing and such.

Does the crash report detail I added in the OP spell anything out? It mentioned a driver being an issue and not hardware that caused the BSODs.


I tried running a stability test using AMD's OverDrive program to see if it would push the temps to anything bad. It was workig through the test for about 30 minutes when it BSOD again. This time the report was a little different for the WhoCrashed Analyzer.

On Thu 12/22/2011 5:21:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122111-22838-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80088EEB30, 0xFFFFFA80088EEE10, 0xFFFFF80001F9E8B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


Unfortunately I did not see what the temps were at right before the latest BSOD.

Any thoughts?

m
0
l
a b $ Windows 7
December 22, 2011 3:43:46 PM

So it reached 65c from gaming? If it get's that high gaming, it likely gets MUCH higher in a stress test.

Considering the max for your cpu is 62c, you definitely have a heat problem, not to say that's your entire problem though, but I would address the heat problem first.

I would consider booting to your Windows dvd and trying to do a repair. If that doesn't work I would consider re-loading Windows altogether.

As a side note, a generic 750w psu likely only put's out about 500w and that's being generous.
m
0
l
December 22, 2011 4:21:51 PM

geekapproved said:
So it reached 65c from gaming? If it get's that high gaming, it likely gets MUCH higher in a stress test.

Considering the max for your cpu is 62c, you definitely have a heat problem, not to say that's your entire problem though, but I would address the heat problem first.

I would consider booting to your Windows dvd and trying to do a repair. If that doesn't work I would consider re-loading Windows altogether.

As a side note, a generic 750w psu likely only put's out about 500w and that's being generous.


I have increased my GPU fan speed. It seemed it was defaulted to 20% for some reason. The latest gaming session put the temps around 80c for the GPU. The motherboard temps for TMPIN2 was around 65c. I did end up BSOD after about 2 hours.

Problem number 2, no gaming, just web browsing and such, the computer shut down and restarted. I was actually opening the case at the time and didnt see if it was a BSOD or something different. WhoCrashed report for latest non gaming crash is:

On Thu 12/22/2011 6:10:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122211-21918-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80084AA060, 0xFFFFFA80084AA340, 0xFFFFF80001FD38B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 12/22/2011 6:10:56 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80084AA060, 0xFFFFFA80084AA340, 0xFFFFF80001FD38B0)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


I have 4 fans not counting GPU. All working. I have a large CPU case and most of the air pushed by the fan is relatively cool to the hand. I will try a Windows repair.

Any more thoughts, greatly appreciated.
m
0
l
a b $ Windows 7
December 22, 2011 5:55:23 PM

The gpu was 80c in gaming or idle??

What's the cpu temp while gaming? Just run HW monitor and about 10 minutes into the game, alt/tab and see what HW monitor says for the cpu temp.

That part about it being a software issue and not hardware is throwing me off, it sounds like bad memory to me or a failing power supply.

I think the only way your going to find out, is to re-install Windows fresh and all your drivers fresh. If you still get the problem you know it's hardware, if not, you know it was a software or driver issue. I know it's time consuming and a hassle but I can't see any other way to figure out what the problem is considering the crash report is saying it's software.
m
0
l
December 22, 2011 8:36:22 PM

geekapproved said:
You can also try this
http://www.sevenforums.com/tutorials/1538-sfc-scannow-c...


GPU was 80c while playing...close to 2 hours. The BSODs seems to happen at around 2 hours of PC 'on-time'
I have sinced used the Windows DVD for repairing. It did mentioned that NET.Framework version 4 needed to be repaired.

I am now working through using Driver Verifier to test drivers. Currently sitting about 30 minutes and no BSOD.

I did notice TMPINT2 in the HW Monitor was climbing to 64c when under the driver verifier testing...

I feel it may be more of a PSU issue now, but I have no other evidence to support that than my gut. I am also going to try to install some older memory that like 2 months ago was used and things were more stable. It's more of a troublshooting hunch than anything.

Any other thoughts?
m
0
l
a b $ Windows 7
December 22, 2011 10:12:10 PM

Ok 80c is fine for a video card.

I want to know what your cpu temps are, try CORETEMP.

Don't try the memory unless you get another bsod, otherwise you wont know if the repair fixed it or the memory fixed it.
m
0
l
!