Frequent errors and BSOD's when playing games.

Rafaelis · Apr 29, 2015

Hello.

I am having a problem when I play games on my one-year old computer. I get frequent BSODs and crashes to desktop/game freezes etc. Errors I should not be having with the rig I use. Since I am no expert in the art of understanding error codes, I hope someone here can give me an idea of what is going on with my computer.

The BSOD's:

On Mon 27-04-2015 04:10:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042715-11450-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031B1EE4, 0xFFFFF8800D06EFA0, 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 Mon 27-04-2015 04:10:03 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, 0xFFFFF800031B1EE4, 0xFFFFF8800D06EFA0, 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 that cannot be identified at this time.

On Mon 27-04-2015 03:20:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042715-11450-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x21133)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007195133, 0xFFFFF880061C4558, 0xFFFFF880061C3DB0)
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 Mon 20-04-2015 20:39:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042015-16317-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0xA (0xFFFFFA8067346DA0, 0x2, 0x1, 0xFFFFF80002EF17CE)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 29-03-2015 21:59:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033015-8330-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0xFFFFFA80625CD9E0, 0x2, 0x1, 0xFFFFF80002EF5B6E)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 25-03-2015 01:27:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032515-7581-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x7633)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x5B449C0, 0xFFFFF8A0053449D0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that the current thread is making a bad pool request.
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 Tue 13-01-2015 00:42:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011315-16894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002ED64DD)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 15-12-2014 02:39:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121514-8377-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4A (0x76F3161A, 0x2, 0x0, 0xFFFFF88008638B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 14-12-2014 21:55:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121414-8876-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4A (0x774E161A, 0x2, 0x0, 0xFFFFF88009A96B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 11-12-2014 22:43:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121114-8174-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033984E0, 0xFFFFF88007DBAF40, 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.
_________________________________

Examples of errors from Event Viewer when playing GTA5:

Faulting application name: GTA5.exe, version: 1.0.335.2, time stamp: 0x5533d504
Faulting module name: GTA5.exe, version: 1.0.335.2, time stamp: 0x5533d504
Exception code: 0xc0000096
Fault offset: 0x0000000000e7d558
Faulting process id: 0x1b28
Faulting application start time: 0x01d0820d8c6f552c
Faulting application path: C:\Program Files\Rockstar Games\Grand Theft Auto V\GTA5.exe
Faulting module path: C:\Program Files\Rockstar Games\Grand Theft Auto V\GTA5.exe
Report Id: 26429c51-ee01-11e4-af59-d43d7ef73a7a
_______________________
Faulting application name: GTA5.exe, version: 1.0.335.2, time stamp: 0x5533d504
Faulting module name: socialclub.dll, version: 1.1.5.8, time stamp: 0x5529e19f
Exception code: 0xc0000005
Fault offset: 0x0000000000483265
Faulting process id: 0x129c
Faulting application start time: 0x01d082097ec33ca7
Faulting application path: C:\Program Files\Rockstar Games\Grand Theft Auto V\GTA5.exe
Faulting module path: C:\Program Files\Rockstar Games\Social Club\socialclub.dll
Report Id: addce7e7-ee00-11e4-af59-d43d7ef73a7a
_______________________
Faulting application name: GTA5.exe, version: 1.0.335.2, time stamp: 0x5533d504
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000282ef9bd2
Faulting process id: 0x48c
Faulting application start time: 0x01d0807e68402259
Faulting application path: C:\Program Files\Rockstar Games\Grand Theft Auto V\GTA5.exe
Faulting module path: unknown
Report Id: 2bf918f8-ec75-11e4-9f80-d43d7ef73a7a
_______________________
Faulting application name: GTA5.exe, version: 1.0.335.2, time stamp: 0x5533d504
Faulting module name: nvwgf2umx.dll, version: 9.18.13.5012, time stamp: 0x55258f68
Exception code: 0xc0000005
Fault offset: 0x0000000000872102
Faulting process id: 0xfd0
Faulting application start time: 0x01d0807941851b3b
Faulting application path: C:\Program Files\Rockstar Games\Grand Theft Auto V\GTA5.exe
Faulting module path: C:\Windows\system32\nvwgf2umx.dll
Report Id: eee10d97-ec6f-11e4-9f80-d43d7ef73a7a

My specs:

GPU: MSI GeForce GTX770 GAMING 2GB TWIN FROZR.
CPU: Intel Core i7 4771 3.5GHz.
RAM: 8 x Crucial DDR3 PC1600 4GB CL9 Balistix Sport L.
OS: Windows 7 Ultimate x64.
MOBO: MSI Z87-GD65 GAMING Motherboard.
COOLER: Intel BXTS13X Liquid Cooling Solution 1150/5/.
PSU: Antec TruePower Classic TP-750C (750W) 80.
MONITOR: Dell 27" UltraSharp u2713HM.

johnbl · Apr 29, 2015

most of the errors indicate memory corruption. the one bugcheck BAD_POOL_CALLER
means that the system found a driver that is corrupting memory.
and it was detected as a filter driver.

You can run memtest86 and confirm your memory is ok (can not hurt)
but I would change the memory dump type to kernel memory dump, reboot and run
cmd.exe as an admin then run
verifier.exe /standard /all
this will force the system to check your device drivers for common errors and bugcheck and name the bad driver if it is detected.
use:
verifier.exe /reset
to turn off the extra checking after you get your next bugcheck or your system will run extra slow until you do.

put the new memory dump on a server and post a link. someone with a windows debugger can look at your filters with
!fltkd.filters 1
debug command and see if they can see a corrupted structure and figure out what the cause is. (or make a good guess)
who knows the verification might even name the bad driver.

Rafaelis · Apr 29, 2015

Ok I just changed to kernel memory dump and ran my game and got a BSOD. This time a new error I hadn't gotten before. So now I don't know if I should get this bugcheck analyzed (since it's a first) or wait until I get a BSOD like the ones I usually get?

On Wed 29-04-2015 20:49:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042915-18470-01.dmp
This was probably caused by the following module: e22w7x64.sys (e22w7x64+0x23008)
Bugcheck code: 0xC9 (0x24C, 0xFFFFF880053A7008, 0xFFFFF9807BD44EE0, 0x103)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\e22w7x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_VERIFIER_IOMANAGER_VIOLATION

johnbl · Apr 29, 2015

go ahead and put the memoy.dmp file on a server and post a link. It will be a much bigger file than a minidump.
or just update your killer ethernet drivers. (lots of bugs in these drivers, try the current version from your motherboard vendor)

bugs in network driver tend to break antivirus scanners, streaming games and nvidia GPUs drivers that have shadowplay enabled. (just fyi) memory corruption by these drivers can break any other driver in the system

the hope is verifier will find a bad driver when it makes a mistake and force a bugcheck as proof. This is often before the mistake has a chance to crash some other driver. Most often you will not get the same bugcheck unless verifier does not find any problems. Then the extra debug info is still saved to the memory dump and extra debug commands will work.

Rafaelis :

Rafaelis · Apr 29, 2015

The Killer Ethernet BSOD I just got when starting GTA5 (twice in a row) both happened after I turned on the verifier. So I guess it forced a bugcheck, like you say.

I am currently uploading the memory.dmp to dropbox here:

https://www.dropbox.com/s/qu96sdj2ga6owiu/MEMORY.rar

It's a pretty big file though. 1.65 GB... Gonna take a while.

Rafaelis · Apr 29, 2015

I am also updating the ethernet drivers.

johnbl · Apr 29, 2015

verifier already named the bad driver when it bughcecked. e22w7x64.sys
I can still look at the memory dump and maybe see something else that has problems but for this first bugcheck the answer will be update e22w7x64.sys as your only fix. Even if is just to get verifier to find the next driver with a problem.

Rafaelis :

Rafaelis · Apr 29, 2015

I hope my update of the Killer Ethernet driver from MSI fixes the e22w7x64.sys problem.
The memory.dmp should be uploaded in about 10 minutes. I just RAR-zipped it and re uploaded (and updated the above link), because the other file would take an hour to finish. I would greatly appreciate it, if you'd take a look.

johnbl · Apr 29, 2015

windows tries to make your system run faster by loading programs into RAM even if you have not requested it.
if you have lots of RAM it will just cram every program you have run in the last few months into standby memory.
it makes the memory dump pretty big. you can clear the programs that are being loaded if you run rammap.exe and find the empty menu item and tell it to empty the standby list.
https://technet.microsoft.com/en-us/library/ff700229.aspx

just fyi

Rafaelis :

Rafaelis · May 1, 2015

Well I'm sadly still getting random BSOD's and errors when playing games on my computer. I think I'll just have to take it back to the shop. Could be a faulty HDD

On Fri 01-05-2015 22:19:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050215-11294-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x7BE7D)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x10015, 0xFFFFFA8029F2A160)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation BAD_POOL_CALLER

On Fri 01-05-2015 22:19:19 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9E40)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x10015, 0xFFFFFA8029F2A160)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Fri 01-05-2015 01:27:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050115-11356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E836B4, 0xFFFFF880092B34A0, 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.

johnbl · May 2, 2015

go to the msi website and update your killer ethernet driver to a current version.

from the memory dump:
bug was caused by e22w7x64.sys
\SystemRoot\system32\DRIVERS\e22w7x64.sys Wed Dec 05 08:43:48 2012

Killer e2200 PCI-E Gigabit Ethernet Controller

you also have overclcoking drivers installed (unrelated to this problem)

---------------
a bad pool caller error code is not likely to be a hard drive problem.
more likely to be a driver problem because of a conflict.

check for a conflict with your motherboard audio source with that of the nvidia GPU card sound support.
if you have a monitor that has speakers that are connected by the video cable, then go into windows control panel device manager and disable any graphic card High def audio support. Reboot your machine, go into BIOS and update it or reset it to defaults to get the system to reassign interrupts and DMA channels and rebuild the database of settings it hands off to windows.

if you have any other audio source that you don't have speakers attached to, turn them off. Ie if you don't use the motherboards sound, then disable it in BIOS.

I see you uploaded a memory dump, I will take a quick look

Rafaelis :

Rafaelis · May 5, 2015

I did update the ethernet driver, and it fixed some random crashes to desktop. But others still happen. Playing without internet connection seems to prevent most crashes to desktop when playing GTA5, but I still get these BSODs. I'll look into the audio stuff. I just get sound through headphones. I disabled all NVIDIA audio and the digitial audio.

Search

Frequent errors and BSOD's when playing games.

Rafaelis

Reputable

johnbl

Polypheme

Rafaelis

Reputable

johnbl

Polypheme

Rafaelis

Reputable

Rafaelis

Reputable

johnbl

Polypheme

Rafaelis

Reputable

johnbl

Polypheme

Rafaelis

Reputable

johnbl

Polypheme

Rafaelis

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page