Sign in with
Sign up | Sign in
Your question
Solved

BSOD 0x0000007E issues while playing games. Need help. Any ideas?!!?

Tags:
Last response: in Systems
Share
June 26, 2013 1:01:00 PM

here are the two BSODs I've been getting: http://www.flickr.com/photos/23306508@N05/ (newest one on the left).

I've had the RAM replaced relatively recently. Just tried a friend's GPU in my rig in case that was the issue but got another bsod.

my computer specs:

CPU: Intel i5-3570K 3.40 GHz 6MB smart cache
Mem: 8GB
Motherboard: Asus P8Z77-V LX Intel Z77 Chipset DDR3
GPU: AMD 7970 HD
PSU: 700 Watt - Standard Power Supply - SLI/CrossFireX (no brand name. just from CyberPowerpc)
OS: Windows 7 home x64

It usually happens while playing for a little bit. Either during game or when switching to another game. Ex. played Planetside 2 for about 10 minutes yesterday, went to switch to BF3, got this message. Ex.2 played HITMAN for a few hours, screen froze, went to this message.

I ordered the computer from Cyberpower a year or so ago. I got the AMD card from a guy that worked for AMD in sales at a networking lunch. Was a brand new card (took the plastic off) and loaded it in. Other than that, haven't done anything to the computer.

Also, I scanned for drivers and all are up to date. There were messages about mouse drivers, sound card drivers, and usb drivers that were "out of date" however. I sometimes plug in and pull out my xbox controller and have a logitech wireless mouse. Didn't think I needed to do anything as when I plug anything into the deck, the drivers auto load.
Related resources
June 26, 2013 8:02:37 PM

Can you borrow a decent power supply? Possibly the PSU but more likely the drivers. What card did you use previously and did you do a driver clean before the new card was installed.
m
0
l
June 26, 2013 8:02:56 PM

been looking back of your first blue screen (dxgmms1.sys ) this look like you need to update your graphic driver ,i would suggest you use this to read the minidump files that wil help us confirm the issue http://www.resplendence.com/whocrashed
m
0
l
June 28, 2013 9:23:37 AM

anti-painkilla said:
Can you borrow a decent power supply? Possibly the PSU but more likely the drivers. What card did you use previously and did you do a driver clean before the new card was installed.


used a 6990 to test it. have always had the 7970. as far as driver clean, i uninstalled the 7970 drivers after downloading the 6990 drivers. shutdown. plugged in the 6990. then restarted and installed their drivers.
m
0
l
June 28, 2013 9:25:42 AM

scout_03 said:
been looking back of your first blue screen (dxgmms1.sys ) this look like you need to update your graphic driver ,i would suggest you use this to read the minidump files that wil help us confirm the issue http://www.resplendence.com/whocrashed


awesome. Is this a safe program to use? I tried some other ones a little while back and had to reformat the hd and start clean. Should I just download this and run it and then post the errors?
m
0
l
June 28, 2013 10:59:00 AM

dolwload it and post the resule of the scan .
m
0
l
June 29, 2013 2:08:08 PM

scout_03 said:
dolwload it and post the resule of the scan .


here's the resule of the scan. thanks for the help scout!

System Information (local)
--------------------------------------------------------------------------------

computer name: RAGINPWNER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8543367168 total
VM: 2147352576, free: 1928175616




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 6/26/2013 12:30:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062913-72197-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x21128)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880053D0128, 0xFFFFF88003CDA558, 0xFFFFF88003CD9DB0)
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 that cannot be identified at this time.



On Wed 6/26/2013 12:30:51 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0xF868)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880053D0128, 0xFFFFF88003CDA558, 0xFFFFF88003CD9DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 that cannot be identified at this time.



On Thu 6/13/2013 2:09:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062513-12979-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D32C8F, 0xFFFFF88006D92B50, 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 that cannot be identified at this time.



On Wed 6/12/2013 4:35:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061213-15428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF6F3D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002D56F3D, 0xFFFFF8800335C788, 0xFFFFF8800335BFE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
m
0
l
June 29, 2013 2:50:45 PM

Just joining 2 dots; Cyberpower pc ----- pc issues
because we *dont* see that often
m
0
l
July 1, 2013 7:40:14 AM

scout_03 said:
this is for the 3b error code http://support.microsoft.com/kb/980932/en-us it would also be a good thing to check your video card driver even the one for the intel chipset for the vga and the hotfix on asus http://www.asus.com/Motherboards/P8Z77V_LX/#support_Dow...


thank you!! i haven't done the above yet as over the weekend it looked like i didn't need to. the last time my computer blue screened (last week)) when i had my friend's 6990 in it to see if it was my gpu, i just shut everything off and then took it out. saturday, i decided i was going to troubleshoot it and loaded my gpu back in. turned it on and booted in safe mode. computer automatically added the drivers to the card. so i restarted. went to windows update, noticed i had like 3 updates to do, and did so. gamed all day saturday and yesterday with no problems. computer still seems to be running fine. perhaps it was a driver issue? which is weird because i would always go to the amd website to get the latest drivers. do you think i should still do the above checks for the 3b error code, etc? or just leave it as is.
m
0
l

Best solution

July 1, 2013 10:52:05 AM

if you dont have bsod it leave it this way and place i use to check my driver is this with the ma config plug in http://www.touslesdrivers.com/ use the google translator and you will have the english version of the page ,this is also free for the driver you need .
Share
July 1, 2013 11:43:38 AM

scout_03 said:
if you dont have bsod it leave it this way ano place i use to check my driver is this with the ma config plug in http://www.touslesdrivers.com/ use the google translator and you will have the english version of the page ,this is also free for the driver you need .


Big thanks for the tips and help Scout. Really appreciate it. Back to pc gaming!
m
0
l
July 1, 2013 8:14:17 PM

your welcome if you need more help i will be around .
m
0
l
July 2, 2013 10:01:45 AM

scout_03 said:
your welcome if you need more help i will be around .


well, looks like i spoke too soon. got both of the same blue screens last night. played a few minutes of skyrim, threw on nazi zombies for about 10 minutes, got the 3b error code. restarted, uninstalled my amd drivers, restarted, and then went to amd.com and did the auto detect gpu and installed the recommended drivers for the HD 7xxx series 64 bit which i have. then played tomb raider for about 20 minutes. quit that and started a GTA IV download via steam. let it run. woke up this morning to the 0x10000007E BSOD. no idea what's going on.

as far as the mother board drivers, how do i know which ones i need? i went to http://www.asus.com/Motherboards/P8Z77V_LX/#support_Dow... and saw a bunch of things to download. i downloaded the hotfix, went to run it, and was told that it wasn't for my computer. the vga download just registered my motherboard.

is there a program that i can run that can scan for updates and for what drivers i need? i tried one a while back but it was scam software and didn't do anything.
m
0
l
!