BSOD playing Battlefield 3, System_Service_Exception

[PedroGoHard]

OS: Windows 7 Home Premium x64
CPU: AMD Phenom(tm) II X6 1075T Processor
Memory:8GB Kit (4GBx2), Ballistix 240-pin DIMM, DDR3 PC3-10600 memory module
HDD: HITACHI HDS721050CLA362 (500GB)
Graphics: NVIDIA GeForce GTX 260
Motherboard: ASUS M4A78LT-MLE
Security: MSE

After about 45 mins of gaming my comp would slow down for a minute and follow up with the BSOD. I also get a BSOD Memory_Management on my other games. Since both started coming up at the same time I believe there may be one solution to both problems.

 

[ePeen]

Hi, welcome to SevenForums!

Few different errors, only 1 dump points to a driver, which is dxgmms1.sys (direct x driver). The rest point to ntkrnlmp.exe as it doesn't know what's causing it, and the fourth is Pool Corruption. First thing I'd like you to do is uninstall your video card drivers and reinstall the latest version (pertaining to the directx driver error).

Two tests I'd like you to run:

Memtest:

Read the following to test your memory for errors.

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Dumps\Windows_NT6_BSOD_jcgriff2\022612-24850-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e45670
Debug session time: Sun Feb 26 15:34:45.379 2012 (UTC - 5:00)
System Uptime: 0 days 0:42:03.566
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8004b6dcb0, ffff, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8004b6dcb0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  javaw.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cec150 to fffff80002c7cc40

STACK_TEXT:  
fffff880`0a0a2278 fffff800`02cec150 : 00000000`0000001a 00000000`00041790 fffffa80`04b6dcb0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0a0a2280 fffff800`02c6a0ff : fffffa80`00000000 00000000`5fbfffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`0a0a2440 fffff800`02c7bed3 : ffffffff`ffffffff fffff8a0`0d075af8 fffff8a0`0d075b20 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0a0a2540 fffff800`02c78470 : fffff880`0452e4b2 fffff8a0`0277d5d0 fffffa80`070c1b30 fffffa80`06dd4b20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a0a26d8 fffff880`0452e4b2 : fffff8a0`0277d5d0 fffffa80`070c1b30 fffffa80`06dd4b20 fffff8a0`0d075af0 : nt!KiServiceLinkage
fffff880`0a0a26e0 fffff880`04519ac3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0a0a2710 fffff880`04514153 : 00000000`00000000 fffff8a0`0277d5d0 fffff8a0`0277d5d0 00000000`00000006 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x7b
fffff880`0a0a27c0 fffff880`044faaa7 : fffff8a0`0d2bd9d0 fffff8a0`044a0da0 fffff880`0a0a2930 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x483
fffff880`0a0a28a0 fffff880`04446469 : fffff8a0`04dbc2b8 fffff880`0a0a2d70 00000000`00000000 fffff8a0`106b38d0 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`0a0a28f0 fffff880`0443f610 : fffff880`0a0a2b58 fffff880`0a0a2fd0 fffff880`0a0a2d30 fffff880`0a0a2d30 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291
fffff880`0a0a2980 fffff880`04441b0c : fffff8a0`110aa000 fffff880`0a0a2fd0 fffff880`0a0a3200 00000000`00000701 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8
fffff880`0a0a2f80 fffff880`04444469 : 00000000`000001d8 00000000`00000001 fffff8a0`0d15e570 00000000`000001d8 : dxgkrnl!DXGDEVICE::OpenResource+0x5a0
fffff880`0a0a3060 fffff960`001af5be : 00000000`060ccfc0 00000000`00000000 00000000`000007d4 00000000`000007d5 : dxgkrnl!DxgkOpenResource+0x72d
fffff880`0a0a31f0 fffff800`02c7bed3 : 00000000`06a465b0 fffff880`0a0a32a0 00000000`06a435a8 00000000`7ef92000 : win32k!NtGdiDdDDIOpenResource+0x12
fffff880`0a0a3220 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`0452e4b2 488b0e          mov     rcx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

Followup: MachineOwner
---------


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Dumps\Windows_NT6_BSOD_jcgriff2\022512-33119-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e9b670
Debug session time: Sat Feb 25 14:06:06.843 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:42.669
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff780c0000000, a6d, ff0a6efffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2aa81 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff780c0000000
Arg3: 0000000000000a6d
Arg4: 00ff0a6efffffffe

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_5002

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d3e347 to fffff80002cd2c40

STACK_TEXT:  
fffff880`039ed358 fffff800`02d3e347 : 00000000`0000001a 00000000`00005002 fffff780`c0000000 00000000`00000a6d : nt!KeBugCheckEx
fffff880`039ed360 fffff800`02ce8fa0 : fffff6fc`c0053788 00000000`00000001 fffff880`00000010 fffffa80`053fd630 : nt! ?? ::FNODOBFM::`string'+0x2aa81
fffff880`039ed4d0 fffff800`02cc1c1e : fffff980`0a6e1000 00690000`00010000 fffffa80`00000000 ff0bfa80`09593580 : nt!MmCheckCachedPageStates+0x3c0
fffff880`039ed680 fffff800`02fbce10 : 00000000`00000000 00000000`00061000 fffffa80`09681d40 00000000`015a8420 : nt!CcFetchDataForRead+0x10e
fffff880`039ed6e0 fffff880`012a6f08 : fffff880`00000000 00000000`00000005 fffffa80`0001f000 fffffa80`00010001 : nt!CcCopyRead+0x180
fffff880`039ed7a0 fffff880`0102b098 : fffffa80`09681d40 fffffa80`09593518 00000000`00000000 fffffa80`09681d01 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`039ed980 fffff880`0102e8ba : fffff880`039eda50 00000000`015a8403 00000000`015a8400 fffffa80`09681d00 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`039ed9e0 fffff880`0104c630 : fffffa80`09681d40 00000000`00000000 fffff880`039edb40 00ff0000`00010000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`039eda20 fffff800`02fbc949 : fffffa80`09681d40 fffffa80`00000001 fffffa80`06add7b0 fffffa80`09681d40 : fltmgr!FltpFastIoRead+0x1d0
fffff880`039edac0 ff08f800`02cd1ed3 : 00000000`00d71001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
fffff880`039edbb0 00000000`00d71001 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00e0e4d0 : 0xff08f800`02cd1ed3
fffff880`039edbb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00e0e4d0 00000000`015a8420 : 0xd71001


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2aa81
fffff800`02d3e347 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2aa81

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+2aa81

BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+2aa81

Followup: MachineOwner


Loading Dump File [C:\Users\Icarus\Downloads\Dumps\Windows_NT6_BSOD_jcgriff2\022512-28516-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e49670
Debug session time: Sat Feb 25 11:27:43.403 2012 (UTC - 5:00)
System Uptime: 0 days 0:25:34.229
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c85f35, fffff8800a451fd0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1d5 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c85f35, Address of the instruction which caused the bugcheck
Arg3: fffff8800a451fd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiCommitThreadWait+1d5
fffff800`02c85f35 488bbb90000000  mov     rdi,qword ptr [rbx+90h]

CONTEXT:  fffff8800a451fd0 -- (.cxr 0xfffff8800a451fd0)
rax=000000007ef27000 rbx=ff00fa8009150060 rcx=fffff8800a452970
rdx=0000000000000000 rsi=fffffa8009150120 rdi=fffff88002fd5180
rip=fffff80002c85f35 rsp=fffff8800a4529b0 rbp=0000000000000000
 r8=fffffa8006e04bb8  r9=0000000000000000 r10=fffffffffffffff7
r11=00000000002f5b01 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffffa8009150168
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KiCommitThreadWait+0x1d5:
fffff800`02c85f35 488bbb90000000  mov     rdi,qword ptr [rbx+90h] ds:002b:ff00fa80`091500f0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c85f35

STACK_TEXT:  
fffff880`0a4529b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d5


FOLLOWUP_IP: 
nt!KiCommitThreadWait+1d5
fffff800`02c85f35 488bbb90000000  mov     rdi,qword ptr [rbx+90h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiCommitThreadWait+1d5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800a451fd0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiCommitThreadWait+1d5

BUCKET_ID:  X64_0x3B_nt!KiCommitThreadWait+1d5

Followup: MachineOwner


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Dumps\Windows_NT6_BSOD_jcgriff2\022512-28158-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e52670
Debug session time: Sat Feb 25 11:29:34.480 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:52.667
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002db99bc, fffff880054b1fc0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002db99bc, Address of the instruction which caused the bugcheck
Arg3: fffff880054b1fc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExDeferredFreePool+100
fffff800`02db99bc 4c8b02          mov     r8,qword ptr [rdx]

CONTEXT:  fffff880054b1fc0 -- (.cxr 0xfffff880054b1fc0)
rax=fffff8a004b79270 rbx=0000000000000001 rcx=fffffa8006999350
rdx=ff00f8a004b08680 rsi=0000000000000000 rdi=fffff8a004bc32f0
rip=fffff80002db99bc rsp=fffff880054b29a0 rbp=0000000000000000
 r8=ff00f8a004b08680  r9=fffff8a004b77830 r10=0000000000000000
r11=0000000000000000 r12=fffffa8006999140 r13=0000000000000000
r14=000000000000001a r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExDeferredFreePool+0x100:
fffff800`02db99bc 4c8b02          mov     r8,qword ptr [rdx] ds:002b:ff00f8a0`04b08680=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MpCmdRun.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002db99bc

STACK_TEXT:  
fffff880`054b29a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x100


FOLLOWUP_IP: 
nt!ExDeferredFreePool+100
fffff800`02db99bc 4c8b02          mov     r8,qword ptr [rdx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExDeferredFreePool+100

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .cxr 0xfffff880054b1fc0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+100

BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+100

Followup: Pool_corruption
---------

 

[PedroGoHard]

My RAM passed memtest but when running the driver verifier, a BSOD came up saying something about nvlddmkm.sys was what caused the BSOD. Is this the driver that's causing all the problems and if so, how do I fix it?

 

[ePeen]

Hi, nvlddmkm.sys is the nVidia video driver. Have you uninstalled your video card drivers and reinstalled the latest version?

 

[PedroGoHard]

Yes I got the latest drivers but I kind of think my problems started once I had installed that driver a while ago. Is it possible that this latest driver is causing the problem?

 

[ePeen]

Very possible! I'd recommend rolling back to a version that you were on previously that worked. Or a version before the latest

 

[PedroGoHard]

I thought this worked for a while since after I changed the driver everything worked fine for like a day. But today the problem is back. I got a BSOD saying system service exception and then later I got one saying bad pool header.

 

[ePeen]

Attach the latest dumps you've received, please.

 

[PedroGoHard]

Alright here you go.