Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BF3 & Crysis 2 freezing '.exe stopped responding', and BSOD's

17 Mar 2013   #1
Tvegas

Windows 7 Professional x64
 
 
BF3 & Crysis 2 freezing '.exe stopped responding', and BSOD's

Just in the last week I've been getting <name of game>.exe has stopped responding when playing 3D games. Battlefield 3 and Crysis 2, they will freeze, I then have to ctrl+alt+del out and see the underlying window with 'bf3.exe' or 'crysis2.exe' has stopped responding and will close.

Sometimes I can play for 30 minutes, sometimes only 5 minutes before they will freeze.

Also received a couple BSOD's:

Stop: 0x0a

Stop: 0xd1

I believe it's something I've installed in the last week, windows update, sound/video drivers. But I can't seem to track it down. Before this past week everything was running great with no errors.

System Specs:
GPU: Nividia Gefore Gtx 570
CPU: AMD 8350 8-core 4.0 ghz
Motherboard: Asus Sabertooth 990FX R2.0
RAM: Gskill Sniper Series 8 gb 1866
PSU: TX650
Sound: Creative Xifi xtreme gamer

Crash Dump Included.


My System SpecsSystem Spec
.
17 Mar 2013   #2
Saurabh A

Windows 7 64bit
 
 

Hi Tvegas,

The crash dump analysis:
Probably caused by : memory_corruption
IRQL_NOT_LESS_OR_EQUAL (a)

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, virus scanner, BIOS or an incompatible backup program.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff683ff7dbc48, 0, 0, fffff8000348d1f4}

Probably caused by : memory_corruption ( nt!MiUpdateWsle+2e4 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff683ff7dbc48, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000348d1f4, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b3100
 fffff683ff7dbc48 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiUpdateWsle+2e4
fffff800`0348d1f4 493338          xor     rdi,qword ptr [r8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  LogonUI.exe

TRAP_FRAME:  fffff8800bcbe550 -- (.trap 0xfffff8800bcbe550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800036b6600 rbx=0000000000000000 rcx=fffff70001080488
rdx=7ff0000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000348d1f4 rsp=fffff8800bcbe6e0 rbp=000000000000070f
 r8=fffff683ff7dbc48  r9=fffffa8000000000 r10=fffff683ff7f95a8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         ov up ei ng nz ac po nc
nt!MiUpdateWsle+0x2e4:
fffff800`0348d1f4 493338          xor     rdi,qword ptr [r8] ds:2680:fffff683`ff7dbc48=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000347a1e9 to fffff8000347ac40

STACK_TEXT:  
fffff880`0bcbe408 fffff800`0347a1e9 : 00000000`0000000a fffff683`ff7dbc48 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0bcbe410 fffff800`03478e60 : 00000000`00000000 fffff683`ff7dbc48 fffffa80`0bfba800 00000000`7fefb789 : nt!KiBugCheckDispatch+0x69
fffff880`0bcbe550 fffff800`0348d1f4 : fffffa80`00000028 fffff800`03496418 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0bcbe6e0 fffff800`034992bd : 00000000`00000a27 00000000`00000000 fffff700`01080000 00000000`a0000003 : nt!MiUpdateWsle+0x2e4
fffff880`0bcbe750 fffff800`03498adf : 22700001`da51d025 00000001`da51d121 fffffa80`0bfba928 00000000`00000001 : nt!MiCompleteProtoPteFault+0x2cd
fffff880`0bcbe7e0 fffff800`034975f3 : 00000000`001e3482 000007fe`ff2b5120 fffff683`ff7f95a8 fffffa80`0be21508 : nt!MiResolveProtoPteFault+0x1cf
fffff880`0bcbe870 fffff800`03487269 : 00000000`00000000 000007fe`ff2b5120 fffffa80`0bfba820 fffffa80`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0bcbe980 fffff800`03478d6e : 00000000`00000008 000007fe`ff2b5120 00000000`014c2501 00000000`00000001 : nt!MmAccessFault+0x359
fffff880`0bcbeae0 000007fe`ff2b5120 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01bef238 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff2b5120


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUpdateWsle+2e4
fffff800`0348d1f4 493338          xor     rdi,qword ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiUpdateWsle+2e4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiUpdateWsle+2e4

BUCKET_ID:  X64_0xA_nt!MiUpdateWsle+2e4

Followup: MachineOwner
Another crash:
Unable to load image \SystemRoot\system32\drivers\ctaud2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
Probably caused by : portcls.sys
'ctaud2k.sys' is related to 'Creative Audio Driver (WDM)'.
'portcls.sys' driver relates to 'Port Class (Class Driver for Port/Miniport Devices)' and gets installed with 'Windows Updates'.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {20, 2, 0, fffff880063abf0b}

Unable to load image \SystemRoot\system32\drivers\ctaud2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
Probably caused by : portcls.sys ( portcls!CIrpStream::ReleaseUnmappingIrp+12b )


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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880063abf0b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cd100
 0000000000000020 

CURRENT_IRQL:  2

FAULTING_IP: 
portcls!CIrpStream::ReleaseUnmappingIrp+12b
fffff880`063abf0b 488b4820        mov     rcx,qword ptr [rax+20h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880033b17e0 -- (.trap 0xfffff880033b17e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800bdb4e30
rdx=fffffa800bdb4e02 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880063abf0b rsp=fffff880033b1970 rbp=fffffa800bdb8c10
 r8=0000000000000000  r9=0000000000000000 r10=fffff8000301f000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
portcls!CIrpStream::ReleaseUnmappingIrp+0x12b:
fffff880`063abf0b 488b4820        mov     rcx,qword ptr [rax+20h] ds:0001:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030941e9 to fffff80003094c40

STACK_TEXT:  
fffff880`033b1698 fffff800`030941e9 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033b16a0 fffff800`03092e60 : 00000000`00000002 00000000`00000000 fffffa80`0763b380 fffffa80`07526420 : nt!KiBugCheckDispatch+0x69
fffff880`033b17e0 fffff880`063abf0b : fffffa80`0763b2c0 fffffa80`0bdb8c10 fffff880`73496302 00000000`00000000 : nt!KiPageFault+0x260
fffff880`033b1970 fffff880`063ab74f : 00000000`00000000 fffffa80`0bd4a780 fffffa80`0bdb4c88 fffffa80`0bb6b908 : portcls!CIrpStream::ReleaseUnmappingIrp+0x12b
fffff880`033b19b0 fffff880`063b4998 : fffffa80`0bdd8d60 fffffa80`0bdb8c10 fffffa80`0bd95e98 fffffa80`0bd95e98 : portcls!CIrpStream::ReleaseMapping+0x1f3
fffff880`033b1a20 fffff880`058068ae : 00000000`00000000 00000000`00000000 fffffa80`0bd95e70 fffffa80`0bd95e48 : portcls!CPortPinWavePci::ReleaseMapping+0x60
fffff880`033b1a60 00000000`00000000 : 00000000`00000000 fffffa80`0bd95e70 fffffa80`0bd95e48 fffffa80`0bdd8d60 : ctaud2k+0x68ae


STACK_COMMAND:  kb

FOLLOWUP_IP: 
portcls!CIrpStream::ReleaseUnmappingIrp+12b
fffff880`063abf0b 488b4820        mov     rcx,qword ptr [rax+20h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  portcls!CIrpStream::ReleaseUnmappingIrp+12b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: portcls

IMAGE_NAME:  portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc03

FAILURE_BUCKET_ID:  X64_0xD1_portcls!CIrpStream::ReleaseUnmappingIrp+12b

BUCKET_ID:  X64_0xD1_portcls!CIrpStream::ReleaseUnmappingIrp+12b

Followup: MachineOwner
---------
Please try the following steps to see if they help:
1. Uninstall 'Avast anti-virus' for testing purpose: avast! Uninstall Utility | Download aswClear for avast! Removal (download and install the uninstaller tool)
- Install 'Microsoft Security Essentials': Microsoft Security Essentials - Microsoft Windows (Select apt Operating System in the drop-down menu)
- Restart the system and check results.

2. Update the 'Creative X-Fi Audio Processor (WDM) drivers' from here and see if that helps: Creative Worldwide Support

3. Perform 'Memory Test' using the steps in the tutorial (Share Results): RAM - Test with Memtest86+
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
4. Perform 'Disk Check' through 'Command Prompt', using option 2 in the tutorial: Disk Check

5. If using any 'backup program', please uninstall it from the system to check if that helps.

6. Perform 'Windows Updates': Install Windows updates

Hope this helps. Do reply with the findings; would be glad to assist.
My System SpecsSystem Spec
18 Mar 2013   #3
Tvegas

Windows 7 Professional x64
 
 

Hey Saurabh,

I did a system restore, going to see how that works first.
I have other RAM that is working, I will swap them out to test that. And try your other suggestions.
I will let you know how it works out.

thanks for looking into this for me.
My System SpecsSystem Spec
.

18 Mar 2013   #4
Saurabh A

Windows 7 64bit
 
 

Hi Tvegas,

Thank you for the reply.

'System Restore' addresses software issues; may work if a 'software corruption/driver' is main culprit. Also install 'Windows Updates'; may help. Please observe the system performance to see if the issue re-occurs.

If you experience further issues, you may want to follow the steps I shared in my previous post. Also follow the steps listed in this tutorial to isolate the possibility of a 'Memory failure': RAM - Test with Memtest86+ You may want to swap the 'memory' with the extra 'memory card' that you have, only after an issue is detected with the currently installed 'RAM module'.

Do reply if you need any further assistance; would be glad to help.


My System SpecsSystem Spec
19 Mar 2013   #5
Tvegas

Windows 7 Professional x64
 
 

You were on the right track with a RAM issue. I swapped out my ram with 1333 mhz ram from my other system, worked great, no issues at all, and my games ran smoother, no stuttering. So I put my original 1866 mhz ram back in, had stuttering and then crashing after about 5 or 10 min of playing Crysis 2. I had a suspicion that my 1866 RAM was setup wrong in the BIOS.

I ended up setting the timing of my 1866 mhz RAM manually to '9 10 9 28' (per it's requirements) in the BIOS. Previously I had the ram set at 1866 in the BIOS and everything set to Auto, I guess this didn't work correctly, the timings had to be set manually.

I tested Crysis 2, ran very smooth and played for over an hour with no crashing. I'll do some more testing with Battlefield 3, but it looks like this might have fixed my issue.

On a side note, the default speed of my new ram is 1600 mhz, but Crysis 2 is a little choppy at that speed, even more so than the older 1333mhz RAM that I tested, not sure why this is?
My System SpecsSystem Spec
19 Mar 2013   #6
Saurabh A

Windows 7 64bit
 
 

Hi Tvegas,

Thank you for the response.

It appears that the system memory was causing trouble. Would recommend you to check the system performance with other games also (Battlefield 3, etc). If you continue experiencing issues, 'Memtest86' may help you to isolate the 'module' or 'card slot' that is responsible for 'distorted performance'.

Hope this helps.

My System SpecsSystem Spec
Reply

 BF3 & Crysis 2 freezing '.exe stopped responding', and BSOD's




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
"Crysis 3 has stopped working" error not resolved...
Hello, So I installed crysis 3 and the first time I tried to open it I saw the logo, then a black window opened (not full screen) and then I got the "Crysis 3 has stopped working" and windows trying to find a solution thing... I contacted EA support, thinking it was a problem with Origin, and...
Gaming
BSOD and display driver stopped responding and has recovered
Hello, I'm CrazyKilla Recently i got black ops 2, it started crashing without giving me a reason, and i finally saw the "Display driver stopped respoding and has recovered" at the bottom right of my screen, i found out that disabling SLI fixes this, i completed the game... Now i installed...
Graphic Cards
Driver stopped responding while playing Saints Row 3, then BSOD.
Hello everyone. I really need your help. I was playing Saints Row 3. And I got crashes occasionally. And I usually got this pop-up: Display driver stopped responding and has recovered But this time... While I was playing, I got a BSOD. Check the attachment for more details on it. It's a .dmp...
Graphic Cards
nvlddmkm stopped responding
Hello, recently I've been getting the same error over a period of anywhere between 10 minutes to an hour and it says Display driver nvlddmkm stopped responding and has successfully recovered. It usually happens when watching youtube videos or any videos in general. I also see it sometimes happen on...
Drivers
BSOD Display Drivers have Stopped Responding
Hello everyone! I've been having an issue with my computer for about 2 -3 months now, ever since I installed Windows 7 64 bit. The error occurs when I try to run games, such as Battlefield Bad Company 2, and Just Cause 2. One of 2 things seems to happen consistently. Either everything runs...
BSOD Help and Support
WMC has stopped responding
I just did a fresh install on my computer of Windows 7, only installed a few programs and BitDefender. However when I try to open Windows Media Center it instantly comes up as "media center has stopped responding" and then nothing happens. Does WMC require aero or something? I heard it may be...
Media Center


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 18:25.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App